SCANNED DOCUMENT TO STRUCTURED DATA

From scanned page to structured row.

Data entry automation can extract supplier, invoice number, dates and amounts from documents into a draft record. Supported confidence scores are one check, not proof of accuracy. The proposed workflow checks required fields, totals, currency, supplier identity and duplicates against the original; a person approves accounting entries before posting.

Updated

Why this page · Data entry

What you’ll find here.

Shows one fictional, illustrative invoice next to the structured data it becomes, with the extraction rule behind each field named, rather than a general promise that 'AI can read your documents'.

  • Built on documented document-processing services from Microsoft and Google, not an unnamed 'AI tool'
  • The before and after example is shown in full, field by field, not summarised
  • Supported confidence scores are combined with field checks and human approval before accounting entries are posted
The work · repeated every week

The job, broken down.

  • Reading scanned or emailed invoices, receipts and forms
  • Extracting the fields a specific document type needs
  • Checking supported confidence scores and flagging missing or uncertain required fields
  • Flagging anything below the threshold for a person
  • Writing confirmed data into the spreadsheet or accounting system
Before → after · illustrative

The same job, handled.

Illustrative: the shape of the change, not a client result
The task todayWith AI doing the legwork
Invoice details are typed in by hand from a scanned copyFields can be extracted into a draft and checked against the original
A mistyped figure is only caught if someone notices laterConfidence and validation checks support a person's approval before posting
The original document gets filed separately from the dataThe original is retained or linked where the destination supports it
How it works

Built in steps.

01

Connect

We connect the inbox, scanner folder or upload point documents already arrive at, so nothing needs saving somewhere new first.

02

Extract

Each document is read using a document-processing service, and the fields your business actually needs, supplier, invoice number, date, amounts, are pulled out by name.

03

Check confidence

Where the selected model supplies a confidence score, it is checked against an agreed threshold. Missing scores or required values also require human review rather than automatic posting.

04

Hand over

Required fields, supplier identity, currency, invoice number, totals and duplicate checks are reviewed against the original. A person approves accounting entries before posting; the original document is retained or linked where the destination supports it. Payment is outside this scope.

A worked calculation · inputs, not results

Do the maths.

Typing supplier invoice details into the accounting system by hand from a scanned copy.

Illustrative inputs through the published formula (hours a year = times a week × minutes ÷ 60 × people × 52)
Input or stepValue
Times a week30
Minutes each time6
People doing it1
Cost per hour£14
Hours a year156 (about 21 working days)
Cost a year£2,184

Illustrative inputs, not a client's figures: thirty scanned invoices a week, six minutes each to read and type up by hand. Change the inputs to your own with the calculator. See how we calculate this.

These are illustrative workflow scopes. The audit checks the actual software, supported access, licences, permissions and human review rules before a build is agreed.

A worked example: one invoice, before and after

This is an illustrative, invented invoice, not a real supplier’s document.

Before, as a scanned page might read:

EXAMPLE SUPPLIER LTD
Invoice No: INV-20456
Date: 12/09/2026
Due: 12/10/2026

Description: Fixings, assorted, x40 boxes
Net: 340.00
VAT: 68.00
Total: 408.00

After, as structured data:

FieldValueExtraction rule
SupplierExample Supplier LtdTaken from the document’s letterhead line
Invoice numberINV-20456Matched against a label such as “Invoice No”
Invoice date2026-09-12Matched against a label such as “Date”
Due date2026-10-12Matched against a label such as “Due”
Net340.00Matched against a currency figure next to “Net”
VAT68.00Matched against a currency figure next to “VAT”
Total408.00Matched against a currency figure next to “Total”

Each row above is an intended field mapping: the workflow looks for the relevant label and value, then checks the extracted result against the original. When a document does not match the expected layout closely enough, for example a supplier’s invoice in an unfamiliar format, a confidence score may not reveal the problem. The proposed workflow therefore validates required fields, totals and layout assumptions and sends failed checks for human review rather than relying on confidence alone.

What is actually doing the reading

The extraction itself runs on a document-processing service built for exactly this job. Microsoft describes its Azure AI Document Intelligence as “a machine-learning based OCR and intelligent document processing service to automate extraction of key data from forms and documents,” and Google’s Document AI is described the same way: it “takes unstructured data from documents and transforms it into structured data,” including “parsing receipts and invoices for expense report validation” as a named use case. Neither vendor publishes a guaranteed accuracy figure for an arbitrary document, which is exactly why the confidence threshold and human check sit on top of the extraction, rather than trusting every field blindly.

Where this saves the most time

The businesses that benefit most are the ones with a steady stream of the same kind of document, supplier invoices, delivery notes, expense receipts, because the extraction rules are built once for that document type and then apply to every one that follows. A one-off, unusual document is rarely worth automating on its own; a weekly stack of the same invoice layout usually is.

The tools · built inside them

On the tools you already use.

  • Xero, QuickBooks or similar accounting software
  • A scanner or phone camera
  • Google Sheets or Excel
  • n8n
  • Make
Industries · where this job matters most

Who needs it most.

Sources · checked and dated

Where the facts come from.

  1. What is Azure AI Document Intelligence?Microsoft Learn
  2. Document AI overviewGoogle Cloud
FAQ · straight answers

Questions, answered straight.

What does data entry automation actually read?

It reads documents such as scanned or emailed invoices, receipts and forms, using a document-processing service such as Microsoft's Azure AI Document Intelligence or Google's Document AI, both of which are built to turn unstructured documents into structured, database-ready data.

What happens if a field cannot be read confidently?

Confidence-score coverage depends on the chosen model and field. The proposed validation rule flags missing required values or scores and scores below the agreed threshold for human review before posting. Confidence alone does not establish accuracy.

Is this the same as OCR software I could buy myself?

It uses the same kind of underlying document-processing service, but the rules for which fields to pull, where to send them and when to flag a person are built around your specific documents and your accounting or record system, not a generic template.

What does data entry automation cost?

A workflow like this is usually a fixed-price package agreed in writing before any work starts (most clients begin with the AI Opportunity Audit at £495, credited against a build). The Fractional AI Team at £1,500 a month covers ongoing work if you want it looked after. Prices exclude VAT where applicable.

Can it handle handwritten documents?

It depends on how legible the handwriting is; printed and typed documents are read far more reliably than handwriting. The AI Opportunity Audit checks a sample of your actual documents before anything is quoted.

Extracted. Checked. Recorded.

✳ 20-minute call · with Daniel

Start with a 20-minute call.

Tell us the job that keeps coming back. We’ll tell you honestly what’s worth automating and what isn’t, and put a number on each one.