Freight billing

Proof of Delivery Scanning and POD Data Extraction

Upload signed PODs, delivery receipts and photos from drivers, and get one clean row per load back: PRO and BOL numbers, consignee, delivery date and time, pieces, receiver, signature and every exception note.

DocuOCR is POD scanning for the billing desk, not another app for drivers. It reads the paperwork that still comes back from owner operators, partner carriers and receivers, flags the PODs with shortages, damage or a missing signature, and exports rows your TMS or accounting system can match to the freight invoice the same day.

  • Scans, PDFs and phone photos
  • Any carrier or receiver form
  • OS&D exceptions flagged
  • Rows keyed by PRO and BOL
Upload a POD, no signup

PDF, JPG, PNG, BMP, HEIC, TIFF

Upload a document to extract

Drop in a signed POD or a driver photo to see the numbers, dates, counts and exceptions DocuOCR reads.

Encrypted in transit
Excel and CSV export
Confidence on every value

What proof of delivery scanning does for billing

Proof of delivery scanning turns a signed paper POD into data. The software reads the reference numbers that tie the delivery to a load, the date and time it was received, how many pieces arrived against how many shipped, who signed and what they wrote in the exceptions box. Billing can then release clean loads to invoice, hold the ones with shortages or damage for a claim, and stop chasing missing paperwork by email.

Most search results for POD scanning describe driver apps and barcode SDKs that capture a signature on a phone. That works when you control every driver. It does nothing for the stack of receiver stamped forms, partner carrier PDFs and blurry dock photos that land in the billing inbox, and that stack is what DocuOCR reads.

Worked example

One LTL delivery receipt with a shortage

Sample input: a phone photo of a one page delivery receipt for an LTL shipment of 14 pieces, signed by the receiver at a distribution center, with "2 CTNS SHORT, 1 CRUSHED" written across the exceptions box. This is the row DocuOCR returns.

POD fieldExtracted valueConfidence
PRO number4471 0928 310.99
BOL numberBL-2026-1184720.99
Customer POPO 55120-B0.97
ShipperHarlan Fixtures Co., Dayton OH0.98
ConsigneeMidway Supply DC 4, Joliet IL0.98
Delivery date2026-11-120.96
Arrival and departure08:10 in, 10:45 out0.88
Pieces shipped140.99
Pieces received120.91
Weight1,860 lb0.98
Receiver printed nameD. Okafor0.84
Signature presentYes0.97
Exception2 cartons short, 1 crushed0.86
Seal numberSL 00933210.95

What billing does with this row

  • Hold the invoice. Pieces received (12) is lower than pieces shipped (14) and the exception field is not empty, so the load goes to the OS&D queue instead of being billed at full value.
  • Check detention. The receiver kept the truck 2 hours 35 minutes. If your rate confirmation pays detention after 2 hours free time, that is 35 billable minutes you can add with the POD as backup.
  • Review two values. The handwritten receiver name (0.84) and exception note (0.86) are below a 0.90 review threshold, so a person confirms them on screen next to the image. Everything else exports as read.

The exported row is keyed by PRO, BOL and PO, the same numbers that sit on your freight invoice and in the TMS. A join on any of them tells you which delivered loads have a clean POD, which have an exception, and which have no POD at all, which is usually the longest list.

Freight brokers have their own reason to keep this tidy. Under 49 CFR 371.3 a broker keeps a record of each transaction for three years, and a searchable table of POD data is far easier to produce than a folder of images.

What we extract

The fields a POD carries

The default POD template covers what carrier billing, broker settlement and 3PL accounting teams ask for. Rename, remove or add fields, for example your own load number format or a temperature reading on reefer deliveries.

Reference numbers

  • PRO number
  • Bill of lading number
  • Customer PO and order numbers
  • Load or trip number
  • Seal and trailer numbers

Delivery facts

  • Shipper and consignee
  • Delivery date
  • Arrival and departure times
  • Pieces and pallets shipped and received
  • Weight and freight description

Receipt and exceptions

  • Receiver printed name
  • Signature present or missing
  • Shortage, overage and damage notes
  • "Subject to count" and refusal remarks
  • Accessorials written on the form (liftgate, inside delivery)

PODs often arrive stapled to the bill of lading. The bill of lading OCR page covers the shipment side of the same packet, and the logistics document processing overview covers rate confirmations, freight invoices and customs paperwork.

How it works

From a stack of PODs to rows ready to bill

  1. Upload the PODs

    Scans from the office copier, driver photos or the PDFs partner carriers email, one POD per file. On Plus and above you upload up to 50 files at once, and each file comes back as its own row.

  2. AI reads each POD

    Reference numbers, dates, counts, the receiver and the exceptions box are read from any layout, printed or handwritten, with no template per carrier.

  3. Review what is flagged

    Low confidence values go to the review queue, and the Checks page lists every POD with a missing signature, an OS&D note or a piece count mismatch, each linked to its document, so a clerk checks a handful instead of the whole stack.

  4. Export and match

    Download Excel or CSV with your own column names, or pull JSON from the REST API, and join on PRO, BOL or PO against open invoices.

Developers can post PODs straight from an email inbox or document store to the OCR API and write the result back to the TMS. If you only need the raw tables out of long carrier statements, PDF to Excel does that without a field template.

What it costs

Priced by page, not per load or per driver

Driver ePOD apps are usually billed per driver or per vehicle each month, and imaging add ons inside a TMS are quoted with the TMS. DocuOCR charges for the pages you read. A POD is normally one page, two if the BOL is attached.

Plans and page allowances are on the pricing page. Yearly billing is roughly half the monthly rate.

OperationPages a monthPlanCost per POD
Carrier, 1,200 loads, POD plus BOL2,400Starter, $49about 4 cents
Broker, 4,500 loads, one page POD4,500Plus, $149about 3 cents
Broker, 8,000 loads, POD plus BOL16,000Pro 35K, $499about 6 cents
3PL, 30,000 delivery receipts30,000Pro 35K, $499under 2 cents

Costs use monthly billing and assume every page in the allowance is a POD. On yearly billing each figure roughly halves. Compare that with a billing clerk keying a POD in about a minute, and the time saved shows up in days sales outstanding as much as in payroll, because clean loads are invoiced the day the paperwork arrives.

Honest comparison

POD extraction software, a driver ePOD app or TMS imaging

These three tools solve different parts of the POD problem, and plenty of fleets run two of them. DocuOCR is the first column.

DocuOCR (POD extraction)Driver ePOD appTMS document imaging
What it doesReads PODs that already exist and returns the data as rowsCaptures signature, photo and GPS on the driver phone at deliveryStores POD images against the load, often with manual indexing
Works with paper from partnersYes, any carrier or receiver formNo, only deliveries made with the appStores the image, data is keyed by hand
Needs driver adoptionNoYes, every driver on every stopDrivers or staff still scan and upload
Exceptions and counts as dataYes, flagged for reviewYes, if the driver enters themUsually no, they stay in the image
Pricing modelPer page, from $49 a monthUsually per driver or vehicle a monthQuoted with the TMS
Best forBilling teams clearing mixed paperwork from many sourcesPrivate fleets that control every deliveryTeams that need a document archive inside the TMS

If your drivers already use an ePOD app, keep it. DocuOCR picks up what the app never sees. For a wider view of extraction tools, the best document data extraction software comparison covers the field.

Who it is for

Teams that bill against paperwork every day

Asset carriers

Clear the POD stack from owner operators and team drivers before month end, and bill detention and lumper charges with the receipt that proves them.

Freight brokers

Get POD data from dozens of partner carriers in one format, release carrier pay only on a clean POD, and keep a searchable record of every load.

3PLs and warehouses

Read the delivery receipts for outbound customer orders, catch shortages before the customer disputes the invoice, and report delivery dates by account.

FAQ

POD scanning questions

Straight answers for billing, settlement and operations leads.

How do you scan a proof of delivery?

Scan the signed POD or delivery receipt on any office scanner or take a clear phone photo, then upload the PDF or image to DocuOCR. It reads the PRO and BOL numbers, consignee, delivery date, pieces, receiver name, signature and any exception notes, and returns them as one row you can export to Excel or CSV, or pull as JSON through the REST API for your TMS.

Can OCR read a signed POD with handwriting?

Yes, within limits. Printed fields such as PRO number, shipper and consignee read reliably, and handwritten receiver names, times and short exception notes are read by the AI model with a confidence score. Anything below your threshold, such as a scrawled count or a smudged time, is flagged for a person to check before export.

Can I match PODs to invoices automatically?

DocuOCR extracts the PRO, BOL and load or order numbers from each POD, which are the same keys on your freight invoice. Export the POD rows and join them to open invoices in your TMS, accounting system or spreadsheet. Loads with no matching POD, or a POD with an exception, show up before the invoice goes out.

Does a photo of a POD work as well as a scan?

A flat, well lit photo of the full page works for extraction, and most driver photos taken at a dock are good enough. Folded corners, glare across the signature block and pages shot at a steep angle lower the confidence score. Those PODs are flagged for review rather than exported with a guessed value.

How much does POD scanning software cost?

DocuOCR is priced by monthly pages, not per load or per driver. Starter is $49 a month for 2,500 pages, Plus is $149 for 10,000 and Pro 35K is $499 for 35,000, with yearly billing at roughly half the monthly rate. A carrier with 1,200 loads a month and two page POD packets fits on Starter.

Do I still need a driver ePOD app?

Not to use DocuOCR. An ePOD app captures the signature on a phone at delivery and suits fleets that control every driver. DocuOCR handles the paper and photos that still arrive from owner operators, partner carriers and receivers who insist on signing their own forms, which is where back office keying usually piles up.

Bill delivered loads the day the POD arrives

Upload this week's PODs, review the flagged exceptions and export rows your billing team can match to invoices. Pick a page plan when you are ready to run every load.