Proof of Delivery for Sage 100
Signed delivery tickets from the door scanner matched to their invoice in Sage 100 overnight and shown beside it in the customer’s portal. The ones that can’t be placed wait for a person.
Dispatch & deliveryUpdated Oct 202620 ERPs
See it work on Sage 100.
Click through the steps. Fictional data, in Sage 100’s terms; the real thing runs on Sage 100.
| Ticket | Scanned | Order | Customer | Status |
|---|---|---|---|---|
| POD_251016_064512.pdf | Oct 16, 6:45 am | SO 88412 | Harbor Point Builders | Linked by barcode |
| POD_251016_071058.pdf | Oct 16, 7:10 am | SO 88420 | Northline Drywall | Linked by order number |
| POD_251016_073301.pdf | Oct 16, 7:33 am | not read | Westfield Masonry? | Unlinked · 2 suggestions |
| POD_251016_081947.pdf | Oct 16, 8:19 am | SO 88431 | Cedar & Stone Framing | Linked by barcode |
Four tickets from the Main St door station. Barcode first, printed order number second, a model for what the scanner couldn’t read.
Tools in this workflow.
Pieces your customers and your team use directly, on their own or inside this workflow.
The problem, as it happens in Sage 100.
The signed ticket is the thing that ends a short-pay argument, and it’s a PDF named by the time it was scanned, in a folder with ten thousand others and nowhere near the invoice in Sage 100. Finding it means knowing the delivery date, opening a few, and hoping the driver got a signature.
Customers ask for it anyway, and the AR clerk becomes a search engine.
How it works.
- 1
Scans are read overnight
Every ticket the warehouse door station scans is picked up nightly. The barcode and the printed order number are read; a model reads what the scanner couldn’t.
- 2
Each ticket finds its invoice
Matched to the invoice in Sage 100 by order number, customer and delivery date. The PDF is stored and linked, never altered.
- 3
It shows up where it’s needed
Beside the invoice in the customer portal, attached to the weekly invoice email for the customers enrolled in it, and on the AP card when the ticket is a vendor’s.
- 4
The rest wait for a person
Tickets that can’t be placed sit in Unlinked PODs with suggestions: the barcode’s order, the printed number, the customer’s deliveries that week. Pick the invoice or mark it no invoice.
How it connects to Sage 100.
Lunica picks up the tickets the door station scans from the scan share, reads the barcode and the printed order number, and matches each one to its order and invoice in Sage 100 through Sage 100’s ODBC driver, under a user that can only read: the order header, the customer maintenance record, the delivery date and the invoice it became. A signed ticket for a vendor’s delivery is matched to the receipt and the purchase order the same way.
Nothing is written to Sage 100 by Lunica, nothing is written to the scan share, and nothing is sent on its own. The linked ticket lives in Lunica’s private document store and is shown beside the invoice in the portal and on the invoice email a person sends. Where you keep tickets behind the invoice in Paperless Office, a person files it there from the link. A ticket that can’t be placed waits in Unlinked PODs until a person picks the invoice or marks it no invoice.
What a week looks like.
- Short-pay disputes end with a link, not a search.
- Every linked ticket is one click from its invoice.
- Unlinked tickets are a short list, not a folder.
- Nothing is written to the scan share, ever.
Questions
Does it change anything in the scan folder?
No. It reads the share. It never writes to it, and never deletes or replaces a ticket once linked.
What if the ticket has no barcode?
The printed order number is read instead. If neither resolves, the ticket waits in Unlinked PODs for a person.
Where are the PDFs stored?
In the portal’s private document store, under your account, served only to signed-in users of that customer.
Does it write to Sage 100?
No. The ticket is linked to the invoice in Lunica’s store and shown in the portal. If you keep tickets behind the invoice in Paperless Office, a person files it there from the link.
What about vendor delivery tickets?
A signed ticket for a vendor’s delivery is matched to the receipt and the purchase order and shows on the AP card, so the three-way match has the signature beside it.
Does the driver do anything differently?
No. Same ticket, same scanner.
Does it need a server?
Lunica runs on one Windows server inside your network, beside the Sage 100 server, set up and maintained by Lunica. It reads Sage 100 through Sage 100’s ODBC driver, under a user that can only read. There is no inbound connection from outside your network.
What does Lunica read in Sage 100?
The customer maintenance record, open items and terms, purchase orders and receipts, the item record, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Sage 100?
Nothing lands in Sage 100 without a person. What belongs in Sage 100 goes back as a Sage 100 import or Visual Integrator job where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Paperless Office. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Proof of Delivery is written for every system on the list. You’re reading the Sage 100 version.
See it on your Sage 100 data.
Thirty minutes. We walk the workflow on Sage 100 data, then map it to yours.