Skip to content

From scanned paper to a database: extracting data without retyping

By USA AI Corp · · 3 min read

The people in this story are made up. The problems are the ones we hear most.

Flowchart

The workflow in Document Processing Factory

  1. StartDriver photo or scan, sent by email
  2. StepIngestion
  3. StepClassification (bill of lading / delivery receipt / other)
  4. StepExtraction (shipment number, date, consignee, pieces, weight, signature present)
  5. StepSave to database
  6. DoneBilling queries

The billing clerk and the box of receipts

Before

  1. Driver hands in paper
  2. Clerk retypes
  3. Typos and missing receipts
  4. Invoice delayed

After

  1. Photo or scan emailed
  2. Fields extracted
  3. Row in database
  4. Invoice ready

Marcus does billing for a regional trucking company with a couple dozen trucks. Customers are invoiced only after delivery is proven, and proof is paper: a signed delivery receipt, sometimes a bill of lading with handwritten notes about shortages or damage.

Drivers hand in paper at the end of the week or snap photos on their phones. Marcus types the shipment number, delivery date, consignee, piece count and any exception notes into the billing system. A missing receipt means an invoice can't go out. A typo in a shipment number means it goes to the wrong customer. When a customer disputes a charge months later, someone digs through boxes for the original.

The information exists. It's just locked in images.

OCR alone isn't the whole answer

Plain OCR

  1. Image
  2. Wall of text

Document processing

  1. Image
  2. Document type
  3. Named fields
  4. Database columns

Plain OCR turns an image into text. That helps with searching, but Marcus doesn't need a wall of text; he needs the shipment number in the shipment number column. Getting from page to field means knowing what kind of document it is and where each value lives on it, even when two customers' forms look different. (We cover the difference in OCR vs AI document processing.)

The workflow in Document Processing Factory

  1. Scan or photo by email
  2. Ingestion
  3. Classification: bill of lading / delivery receipt
  4. Extraction
  5. Database row by shipment number
  1. 01Ingestion. Scans and driver photos are sent to a billing email address, and an ingestion widget brings them in from there.
  2. 02Classification. A classification widget, trained on Marcus's own documents, separates bills of lading, delivery receipts and everything else.
  3. 03Extraction. For each type he picks the fields:
DocumentFields
Delivery receiptShipment or PRO number, delivery date, consignee, pieces delivered, exception notes
Bill of ladingShipment number, shipper, consignee, pieces, weight, ship date
  1. 04Save to a database. Every document becomes a row keyed by its shipment number, so billing can query it.

What changes for billing

  • Invoices wait for the pileBillable when processed
  • Missing proof unnoticedQuery shows gaps
  • Disputes mean digging boxesSearch by shipment number
  • Damage notes buriedFilterable field
  • Invoices go out sooner. A delivery receipt becomes billable data when it's processed, not when the clerk reaches it in the pile.
  • Missing proof is visible. A simple query shows shipments delivered with no receipt on file.
  • Disputes get easier. Search by shipment number instead of digging through boxes.
  • Exceptions stand out. Damage and shortage notes become a field you can filter on, so a person reviews those before the invoice goes out.

The same pattern elsewhere

Bring in → Sort → Extract → Store

  • Packing slips
  • Field service tickets
  • Inspection checklists
  • Paper archives

Any business with paper that must become rows has this problem: warehouse packing slips, field service tickets signed by customers, inspection checklists, old paper files a company wants searchable. The steps are the same: bring in, sort, extract, store.

Before you trust the numbers

  1. Run side by side
  2. Test real handwriting
  3. Add validation checks
  4. Keep a pointer to the original
  • Run it side by side. For the first weeks, compare extracted values against what a person would have typed.
  • Watch handwriting. Handwritten notes are the hardest part of any scan. Test with your real ones.
  • Validate what you can. A shipment number should match a shipment that exists; a delivery date shouldn't be before the ship date. Checks like these catch errors before they reach an invoice.
  • Keep the original. Store where each original file lives alongside its row, so anyone can check the source.

Common questions

Quick answers.

Can it read phone photos, not just scanner output?

Test with your own phone photos during setup, since that's what drivers and field staff actually send.

Do I need a new database?

Not necessarily. The output widget can save to a database or send the data to existing software through an API call.

What about our old paper archive?

Back files can go through the same workflow, which makes years of paper searchable.

Ready when the work is.

Show us what is slowing your business down.

Book a call

Not ready to talk?

Written brief

Skip the call.
Send a brief.

A few sentences is plenty. We read every brief and reply by email within one business day.

Try it free. If you love it, keep it. If it's not for you, we take it back, no questions asked.

We only use this to reply to you. Privacy policy