/ THE SHORT ANSWER
- 01Separate transport milestones from customer acceptance.
- 02Match split shipments at order-line level.
- 03Send collections an evidence-backed balance and dispute status.
/ dotSuper point of view
Collections becomes more effective when delivery evidence describes what the customer accepted, not merely where the carrier last scanned the shipment.
Ask what the delivery event actually proves
Distinguish dispatch, carrier milestones and customer receipt.
Give shortages, damage and missing proof their own exception owners before collections contacts the buyer.
A logistics event should update the shipment record, while payment readiness follows the contract and the evidence required for the actual customer transaction.
Indonesia's NLE portal connects government and private logistics services, including domestic vessel and trucking links.
That provides local context for connected logistics data.
It does not eliminate the distributor's need to define what each event means commercially.
[1]
For an inter-island order, departure from an origin warehouse, arrival at a port and receipt by a customer are different events.
If your system labels all of them delivered, finance cannot tell whether a collection call is timely or premature.
Worked hypothetical: a split shipment hides a shortage
The commercial value is IDR50 million before tax, calculated as 200 multiplied by IDR250,000.
The first shipment delivers 120 cartons.
The second shipment dispatches 80, but the customer accepts only 75 while five are investigated as missing.
Total accepted quantity is 195 cartons, and the unresolved five cartons represent IDR1.25 million.
A carrier's completed milestone for the second shipment must not overwrite the five-carton exception.
Logistics links both receipts to the order, and collections sees the accepted quantity plus the unresolved issue before contacting the customer.
Whether any amount is currently billable or due depends on the contract and finance policy.
The scenario does not prescribe withholding payment.
It shows how a line-level evidence chain gives the commercial team the information needed to make that decision.
Model the shipment around order lines and accepted units
Add separate legs where goods move through different handlers.
Keep customer-facing quantities tied to the original sales unit so milestones do not replace quantity evidence.
Record planned quantity, dispatched quantity, received quantity and accepted quantity separately.
A customer can physically receive damaged cartons without accepting them under the agreed commercial process.
The distinction should remain visible to logistics and accounts receivable.
Use an explicit conversion when the warehouse handles cartons but the invoice uses pieces.
Store the approved pack size with the product and transaction.
A later catalogue change should not silently alter the units on an earlier shipment.
Do not let a photographed delivery note become the only structured record.
Extract or enter its key fields, retain the source and assign a reviewer where the evidence is unclear.
The document image supports the record; it should not be the entire workflow.
Build an evidence checklist for the disputed last leg
That might be the destination warehouse, a reseller branch or a site receiving on behalf of another entity.
Define what the contract and your operating policy require as acceptance evidence.
The proposed checklist below is a commercial workflow design.
It is not a universal Indonesian proof-of-delivery standard.
Agree it with the teams that actually dispatch, receive and resolve customer disputes.
Keep personal details in delivery evidence proportionate to the purpose.
Staff should be able to confirm the authorised receiving role without circulating unnecessary identity documents through every operational dashboard or customer follow-up message.
| Evidence | Question resolved |
|---|---|
| Order and line reference | Which sale does this delivery support? |
| Leg and carrier reference | Which movement produced the event? |
| Unit and pack conversion | How do cartons relate to billed quantity? |
| Received and accepted quantity | What reached and was accepted by the customer? |
| Shortage or damage record | What remains disputed? |
| Authorised receipt evidence | Who acknowledged the handover? |
Connect finance without making tax records delivery evidence
Keep the related tax-document workflow connected to the sale, but do not use its completion as evidence that a shipment reached the customer.
[2]
Send collections a short, structured packet: invoice reference, due status under policy, accepted quantity, dispute owner and next expected action.
A collector should not have to call three warehouses merely to discover that a delivery complaint is already being investigated.
Handle missing evidence differently from confirmed non-delivery.
The absence of a receipt may reflect a documentation gap rather than missing goods.
Assign someone to obtain the evidence without recording an unsupported claim about what physically happened.
Extra event detail can become expensive to maintain.
Start with the milestones that change a business decision.
Collecting every possible carrier scan creates noise if none of them helps establish acceptance, investigate a shortage or explain a customer balance.
Improve one route using the disputes it actually creates
This prevents logistics automation from being credited with problems it cannot solve.
Measure the share of invoiced orders with usable delivery evidence and the age of unresolved delivery exceptions.
Also track how often collections contacts a buyer while an acknowledged dispute remains open.
That is a direct measure of internal coordination.
Choose one route and agree the receiving evidence with the relevant customers and handlers.
Make the capture process practical for their available devices and connectivity.
A simpler consistently completed record can outperform a detailed form people abandon.
The next useful change is one shared reference between the shipment, receipt and invoice.
Once that link is reliable, the team can decide which additional events are worth integrating and which remaining disputes need a commercial process rather than more software.
What this page cannot conclude
- 01No regional logistics performance statistics or route-time guarantees are asserted.
- 02NLE portal services do not prove that a particular carrier offers a usable integration.
- 03Hypothetical commercial calculations exclude tax and do not determine billing entitlement.
- 04This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Sources
- 01National Logistics Ecosystem portalLembaga National Single Window Indonesia · accessed Sep 15, 2026
- 02Coretax: official guidance and resourcesDirektorat Jenderal Pajak Indonesia · accessed Sep 15, 2026
This article was researched and drafted with AI assistance. Sources and limitations are provided for scrutiny; it is not an independent professional review or a compliance certification.
Our editorial standard · Found an error? Send a correction with its source.
/ CITE OR SHARE THIS GUIDE
Make the evidence easy to verify.
When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.
dotSuper Research Desk. (September 15, 2026). Close Indonesian Delivery Gaps Before Chasing Payment. dotSuper. https://dotsuper.net/feeds/applied-systems/indonesia-inter-island-delivery-evidence