Acumatica Proof of Delivery with SuiteFleet

1. Start with the Acumatica order

Open the source order SO 004812 for Summit Industrial Supply and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains two lines with quantities 4 and 6 in the units shown.

Use an SO order with shipment processing enabled. Confirm its approval, credit, stock, and shipping rules before creating the shipment. Keep Order Type with Order Nbr.; the visible number alone is not the complete business key.

Sales Orders is SO301000 and Shipments is SO302000. One shipment may include multiple orders for the same customer, so the correlation must preserve every participating order line. Lot or serial splits and warehouse details must survive any aggregation into one delivery stop. Acumatica Sales Orders reference.

2. Configure the evidence mapping

Preserve this relationship before exporting delivery work:

Record acceptance against shipment lines and splits where needed. Confirmed means the shipment operation progressed; it is not evidence that the named recipient accepted each unit.

3. Define and check the evidence requirements

Agree the evidence policy before dispatch: which shipments need a recipient name, photographs, signature, and completion information, and who reviews missing evidence. Only require capture methods verified in the deployed driver workflow. Confirm that the connector can retrieve each required evidence field.

Before opening proof, match the task to Shipment 006245 through the correlation record. Names, addresses, and order display numbers alone are insufficient when the customer receives repeat or split shipments.

Distinguish the expected consignee from the person who actually accepted the goods. Validate file access and retention requirements with the deployment owner so a saved link remains useful to the intended support team.

4. Review proof of customer handover

Open Proof from the task or Reports → POD Analysis → Full proof. Review delivery photos, signature, recipient, and recorded completion together. Review Proof of pickup and Proof of delivery separately. Confirm customer receipt from the delivery record.

Do not infer received item quantities from a photograph, a signature, or the package count. Store the event time with its time zone. This example uses America/Chicago (CDT).

A confirmed shipment of selected quantities can leave other order lines outstanding under the configured shipping rules. Do not use Complete Order merely to remove a delivery exception from the queue.

If there is a shortage, refusal, or disputed recipient, preserve the original evidence and record the exception. Retain the source shipment and line keys during review; do not create a new shipment simply because proof needs correction.

5. Store controlled evidence references

Validate the contract-based REST endpoint, version, entities, actions, and custom fields in the actual tenant. The form labels in this guide are logical mappings, not unverified REST property names. Confirm which supported action owns shipment confirmation and inventory posting. Acumatica Shipments reference.

Write recipient, event time, outcome, and evidence references only to validated destinations. Check whether the interface stores a file, an attachment relationship, or an external URL. Apply access controls to the evidence location; a link in a transaction does not itself grant appropriate access.

Handle status and attachment updates independently. If the status sync succeeds but a photo reference fails, retain the partial integration error and retry that operation safely. Verify the target record after retry before reporting a clean sync.

6. Verify the result in Acumatica

Attach delivery details to the shipment or a related customization. Confirm Shipment and sales-order completion belong to Acumatica’s shipment workflow; a shipment’s Completed status can involve invoice release. Do not force native statuses from a Delivered task. Acumatica Sales Orders reference.

Read back the linked record and review every outstanding allocation before marking the full order delivered. Test partial shipment, partial acceptance, failed delivery, duplicate completion, and delayed writeback. Keep inventory posting, receipt evidence, and payment reconciliation under their respective configured rules.