Read Every Document.
Once.
Documents arrive in different formats and several teams need different parts of them. We build a controlled pipeline that extracts the data once, validates it and records every exception before posting to company systems.
$12.88
ALL OTHERS COST PER INVOICE (ARDENT, 2025)
17.4 days
ALL OTHERS INVOICE CYCLE (ARDENT, 2025)
One document type
IN THE FIRST PHASE
Document automation needs more than OCR
The old version of document automation usually meant template rules, supplier-specific workflows and a support contract for every edge case. It worked on tidy invoices. It fell over on mixed packs, bad scans and anything with tables, stamps or handwritten notes.
Vision-language models suit messy documents because they read the page as an image and return structured data. Claude, Gemini, GPT and open-weight models still need testing on your own files, but the engineering problem has shifted from "can we read this page?" to "can we validate and post the result safely?"
That second question is the one worth building properly.
YESTERDAY'S OCR STACK
- A template per supplier, breaks on a logo change
- Confidence scores nobody trusts
- Tables and stamps it can't see
- A human reviewing every line anyway
- Enterprise licences, locked-in contracts
VLM-BASED PIPELINE
- One pipeline, tested layouts, fewer templates
- Field-level checks before anything posts
- Tables, signatures and stamps checked
- Humans only see the edge cases
- Document-level cost and accuracy tracking
How a document pipeline works
An invoice, referral letter and lease need different fields and review rules. The pipeline gives each document a defined route from receipt to the target system.
Intake
A shared inbox, a Dropbox folder, an upload widget, an EDI feed. Wherever the documents already arrive. We don't ask your suppliers to change.
Read
A vision model extracts the fields you asked for. Totals, dates, parties, line items, VAT, signatures. As structured data with a confidence score per field.
Check
Totals add up. VAT number checks pass. Supplier exists. PO is open. Date is in range. The rules your team already runs in their head, written down once.
Review
The clean ones post through on their own. The edge cases land in a review queue with the document and the extraction side by side. One click to accept, fix or reject.
Post
Into Xero, Sage, NetSuite, Salesforce, your CRM, your warehouse, your bespoke app. Whatever the document was going to become, it becomes it. With a full audit trail.
Documents we process
Anything that arrives as a PDF, scan, photo or email attachment and ends up in someone's inbox to be typed up. These are common starting points.
Supplier invoices & credit notes
PO matching, VAT validation, GL coding, posting to Xero or Sage. Usually the first finance workflow worth inspecting.
Contracts & MSAs
Parties, term, renewal dates, liability caps, payment terms. Pulled into a register your legal and ops teams can search.
KYC, KYB & right-to-work
Passports, driving licences, share registers, Companies House filings. Captured, checked and retained against your policy and sector rules.
Insurance claims & FNOL
First notice of loss forms, repair quotes, medical reports, photos. Triaged, summarised, attached to the right claim file.
Customs, freight & PODs
Commercial invoices, packing lists, C88 / CDS entries, proof of delivery. Tied back to shipments in your WMS.
Clinical letters & referrals
NHS referrals, discharge summaries, lab results. Structured into the right record, with the bits that need a clinician's eyes flagged for them.
How we take it into live use
We assess the document flow, prove one class against representative examples and connect the approved result to the systems that need it.
You own the code, the prompts, the model choice and the data. We can host it on your stack or ours. If your AP team is on Xero today, they're still on Xero tomorrow.
BOOK A DOCUMENT AUDITDocument audit
We review a representative set of the documents causing the most work. The output records who touches them, where they go, which fields are retyped, the exceptions and the systems that need updating.
Pick the model, write the schema
We choose the model that wins on your document type (Claude, Gemini, GPT or open-weight), define the fields you need, and write the rules a reviewer would use to accept or reject. You see real extractions on your real documents before we wire anything up.
Launch the first pipeline
Intake, read, check, review queue, post. Running on your real volume, with your team in the loop. We run it alongside the manual process until the numbers match.
Watch, learn, add the next one
Every reviewer correction feeds the next prompt, rule or schema change. We track accuracy per field, cost per document, and where humans still get pulled in. Once it's steady, we move on to the next document type.
Audit and validation controls
Documents carry the most sensitive data your business handles: National Insurance numbers, bank details, medical history, contract terms. Sending that material to a generic scanner without a DPIA, a processor contract and access controls is asking for trouble.
Pipelines log every extraction, reviewer decision and model version. Personal data stays in the regions you approve. Anything sent to a model is redacted where possible, run under agreed processing terms, or routed to a self-hosted model. Subject access requests start from searchable logs, not inbox archaeology.
UK GDPR & DPA 2018
DPIAs where processing is likely to be high risk, Article 22 checks for solely automated decisions with legal or similarly serious effects, lawful basis recorded per source. We follow the ICO's AI and data protection guidance.
Making Tax Digital
From 6 April 2026, MTD for Income Tax applies to sole traders and landlords with more than £50,000 in qualifying income. HMRC requires compatible software to create digital records of business income and expenses.
Consumer Duty & accounts rules
For financial services firms and law firms: review queues for customer-facing decisions, evidence for Consumer Duty outcome monitoring, and records that match the SRA's accounts-rule expectation for accurate chronological records.
Signatures & seals
Signature detection, advanced and qualified electronic signature support, plus an audit trail aligned with UK eIDAS trust-service concepts for signatures, seals and timestamps.
When off-the-shelf tools fall short
There are public examples of what goes wrong when documents and AI meet without proper controls. Three worth knowing.
Samsung's three AI leaks.
Samsung semiconductor staff reportedly pasted source code, test sequences for identifying defects and meeting content into ChatGPT. Media reports put the three incidents inside twenty days. Samsung restricted generative AI on company devices in May 2023.
$12.88 per invoice. Still.
Ardent Partners' AP Metrics That Matter in 2025 puts invoice processing cost at $12.88 for all others and $2.78 for its top 20% group. Processing time is 17.4 days for all others and 3.1 days for that top group.
ICO AI guidance, in writing.
The ICO's AI and data protection guidance says AI projects need DPIA thinking, lawful basis, transparency, fairness and accuracy work. The ICO also flags Article 22 checks when a system makes solely automated decisions with legal or similarly serious effects.
Sources checked: Ardent Partners' AP Metrics That Matter in 2025, ICO guidance on AI and data protection, GOV.UK MTD guidance, FCA Consumer Duty guidance, SRA Accounts Rules, GOV.UK UK eIDAS guidance, CNBC / Bloomberg and trade press coverage of the Samsung incident.
Document processing already sits inside our client systems
Leo Associates extracts supplier quotes into project and finance records. Crystal keeps compliance findings and evidence with each deal. The extraction only matters because the next team receives controlled data.
When this is worth discussing
We work best when there is a real operating problem, enough volume to measure and people from the affected teams who can make decisions.
Usually a good fit
- An established UK business, usually with annual revenue above £10m
- A repeated process with a known cost, delay, error rate or capacity problem
- A senior sponsor and a day-to-day owner who understand the work
- Access to the relevant staff, systems, sample records and security requirements
We may point you elsewhere
- A standard product already covers the process well
- The requirement is a one-off small build with no wider operating case
- There is no owner or access to the people and data needed to test the result
- The plan relies on AI making high-impact decisions with nobody responsible for review
Questions before connecting the systems
What about hallucinations? I can't have made-up totals on an invoice.
Right. Two things stop it. First, we extract with a confidence score per field and bounce anything low into the review queue. Second, we run deterministic checks: line totals add up, VAT matches the rate, PO exists, supplier on file. If a number doesn't reconcile, the pipeline holds the document for a human. The AI never gets the last word on money.
Would Xero, Dext, Hubdoc, Rossum or Klippa cover this?
For standard supplier invoices entering a supported accounting package, an established product may be enough. Custom work is justified when document types, required fields, review rules or downstream systems fall outside the product's supported flow.
Where does the document data go? Who sees it?
You decide, document type by document type. Sensitive ones run through model endpoints in the UK or EU under a data processing agreement, or against a self-hosted open-weight model. Less sensitive ones can use a hosted frontier model under agreed processing terms. We write it into the DPIA before we touch your data.
How long until it's live and earning back?
Timing depends on document variation, validation rules and downstream systems. The pipeline runs alongside the manual process until the operational owner accepts the extraction and exception results.
What does it cost per document?
We price it after benchmarking your documents. Model cost, review time, failure rate and downstream integration work all matter. Ardent's 2025 accounts payable report puts invoice processing cost at $12.88 for all others and $2.78 for its top 20% group, which is the gap we use for the first business case.
What about handwriting? Stamps? Foreign-language invoices?
Sometimes handled, sometimes not. Handwriting, stamps and foreign-language invoices vary wildly by scan quality and format, so we benchmark on your real inputs before promising a number. The bad ones go to the review queue; nothing posts on a guess.
Does my team need to use a new app?
Almost never. The intake stays where it is (email inbox, shared drive, portal upload). The data lands in your existing systems. The only new thing is a small review screen for the documents that need a human eye.
Who owns it once it's built?
The commercial proposal states ownership of source code, prompts, evaluations and extracted data. Model, document-processing, storage and support costs are shown separately.
Talk to us about the documents
Send us representative documents, volumes, exceptions and the systems that receive the data. We will assess which document class has the strongest case for automation and what a safe pilot requires.