Proof of delivery
Line-by-line proof of delivery.
Line-by-line proof of delivery is a delivery record in which the receiver accepts or refuses each line of the invoice at the handover, then signs the whole record once. Instead of one yes for the whole delivery, every line carries its own answer: accepted or refused.
Why a signature alone is not enough.
A single signature says a delivery arrived. It does not say which lines were refused, so the dispute starts after the truck has left: the invoice covers everything, the customer pays for part of it, and both sides argue from memory.
When each line is accepted or refused at the dock, the record answers that on the spot. Finance knows what was accepted before it bills, and a refusal is a fact with a time, a place and a signature, not a phone call a week later.
How it works in Momona.
- 01
Your ERP sends the invoice.
Your ERP sends the ZATCA e-invoice XML it already produces, and each line becomes part of the delivery record.
ZATCA XML - 02
The operator is tracked.
From the moment the delivery leaves until it reaches the dock.
Live tracking - 03
The receiver checks every line.
At the dock, the receiver accepts or refuses each line of the invoice, offline if there is no signal, and signs.
Line by line · Offline - 04
The result comes back to you.
Accepted and refused lines go back to your ERP, and finance gets a CSV of every refusal.
ERP · CSV
One answer for the whole delivery, or one for every line.
| Whole-delivery proof | Line-by-line proof | |
|---|---|---|
| What the signature covers | Whole-delivery proofThe delivery as a whole | Line-by-line proofEvery line's answer, accepted or refused |
| A refused line | Whole-delivery proofA note, a call or an email later | Line-by-line proofMarked refused at the dock, in the record |
| What finance gets | Whole-delivery proofA signature to match against the invoice | Line-by-line proofAccepted and refused lines, and a CSV of every refusal |
| In a dispute | Whole-delivery proofWho signed, and when | Line-by-line proofWhich lines were accepted, by whom, when and where |
What the signed record holds.
- 01Each line of the invoice, accepted or refused.
- 02The receiver's signature, and the time and place of the handover.
- 03Photos taken at the handover.
- 04The evidence level: a code only the receiver holds, or a counter-signature from the receiver's own staff.
- 05A signature from the operator's phone, made with its own key. Once confirmed, the record cannot be changed.
Questions.
Does it work without signal at the dock?
Yes. The receiver can accept or refuse each line and sign offline, when there is no signal.
Which invoice format does Momona read?
Today, the ZATCA e-invoice XML that ERPs already produce. Orders and sites can also come in through the REST API, webhooks or CSV import.
Which ERPs does it work with?
SAP, Oracle, Dynamics 365 and others, through the REST API, webhooks and CSV import that come with every plan. Work inside your own systems is scoped and quoted separately.
Can a signed record be changed?
Not once it is confirmed. A delivery can be edited until then; after confirmation, the signed record stays as it was.
Who signs at the dock?
The receiver, at the handover. The record also states its evidence level: a code only the receiver holds, or a counter-signature from the receiver's own staff.
What happens to refused lines?
They go back to your ERP with the accepted ones, and finance gets a CSV of every refusal.
How is it priced?
By deliveries recorded a month: up to 1,000, 3,500 or 10,000. Unused deliveries don't carry over.
See line-by-line proof in a demo.
A walk through one delivery, from the invoice to the signed record.