SAP Business One Proof of Delivery with SuiteFleet

1. Start with the SAP Business One order

Open the source order 1256 for Harbor Office Products 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.

Review the sales order’s customer, delivery date, ship-to address, availability, and open item quantities. Create a Delivery for the intended quantities through the supported base-document workflow. Do not use manual Close as a delivery event.

Business One distinguishes visible DocNum from internal DocEntry. Preserve base-document relationships when copying a sales order to a Delivery. A single customer can have several orders and delivery documents with the same address; matching by customer code and address alone is unsafe. SAP Business One sales orders.

2. Configure the evidence mapping

Preserve this relationship before exporting delivery work:

Customer acceptance should be recorded against the Delivery and its line relationship. Do not infer a signed receipt from a document’s closed state or from conversion to an A/R invoice.

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 Delivery 1854 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).

If 4 cases are copied to one Delivery and 6 remain open, only the first Delivery should receive the completed task result. A retry must not create a second Delivery document for the same goods.

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

SAP’s Service Layer documents Orders and DeliveryNotes. Use the version and protocol supported by the deployment and discover its fields and user-defined fields. Verify base-line relationships and posting behavior before creating a delivery through the interface. SAP Business One deliveries.

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 SAP Business One

Write verified last-mile results to Delivery user-defined fields or a related delivery record supported by the implementation. Keep the Delivery’s native document state separate from the custom Delivered result. Check the original order’s remaining open quantities instead of treating Closed as proof of receipt. SAP Business One sales orders.

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.