Replacing paper with a PDF reduces handling, but it does not by itself create a controlled billing process. A digital file can still be detached from its source, reviewer, delivery state and payment outcome.
The stronger target is one inspectable invoice record. It keeps the document and the decisions around it connected while preserving the accounting system's role as ledger authority.
Capture structured facts, not only an image
Retain the customer, issuing entity, line sources, currency, dates, terms and identifiers as structured facts that can be checked and reused.
A scan or attachment may remain supporting evidence, but it should not be the only place finance can discover the amount or due date.
Control versions and approval
Distinguish draft, ready for review, returned, approved and sent. A file named final does not explain who approved it or whether a later change occurred.
When a document changes after review, create a visible new version and route the affected decision again.
Make delivery and collection visible
Record where and when the invoice was delivered. Use that state alongside the agreed due date to plan reminders and collection ownership.
If the customer reports missing information or disputes a charge, attach the issue and next action to the same record instead of starting a separate inbox history.
Connect payment without erasing history
Match receipts to the issued invoice and retain partial payments, allocations and open balances. Payment status is part of the invoice lifecycle, not a replacement for the invoice.
Send the supported billing output to the accounting system with stable identifiers so finance can reconcile the operating and ledger records.
Define the source record before scanning
Moving a paper invoice into a digital workflow begins with identity, not image capture. Record the document type, supplier or customer, issuing entity, invoice number, issue date, currency, amount, received channel and physical custodian. Decide whether the paper is an original customer invoice, a copy, supporting evidence or an internal worksheet before creating a digital record.
Apply the organisation's approved retention and document policy. This workflow can preserve provenance, access and processing history, but it should not invent legal status for a scan. Route uncertain originals, signatures, stamps or jurisdiction-specific requirements to the responsible specialist while keeping the operational record held and visible.
Capture a faithful, inspectable image
Scan every relevant page at a readable resolution and in the correct order. Preserve colour where marks or annotations carry meaning. Check edges, folds, reverse sides, attachments and faint print. Do not crop identifiers or improve an amount manually. If the document cannot be read faithfully, record the defect and request a better source.
Create a stable file reference, capture time, operator and source-location note. Keep the raw capture unchanged and make any derivative for search or presentation separately. This allows a reviewer to compare extracted fields with what was actually received instead of trusting an edited image that has lost its origin.
Extract fields without treating extraction as approval
Enter or extract the invoice number, dates, customer, entity, currency, line descriptions, quantities, rates, tax-document inputs, terms and total. Flag low-confidence or missing fields for human review. Character recognition can accelerate entry, but it does not prove that a charge is supported, correctly calculated or assigned to the right account.
Retain a link from every material field to the source page or region where practical. Record corrections to extracted values with actor and reason. Never change the source image to agree with a preferred field value. The digital record should explain both what the document shows and what the governed workflow subsequently decided.
Detect duplicates before creating an obligation
Compare issuing entity, counterparty, invoice number, date, currency, amount and source channel with existing records. Use a match as a review signal rather than an automatic deletion rule because corrected documents and reused references can require investigation. Keep potential duplicates held until an authorised person classifies them.
If two captures represent the same paper document, retain one governed record and link or close the duplicate intake event with its reason. If they are distinct obligations, document the differentiating evidence. A digital queue should not turn repeated email, portal and postal delivery into repeated invoices.
Work a multi-page intake case
Assume finance receives a three-page invoice by post and the same document later by email. The first scan omits the page containing payment terms; the email PDF is complete. Keep both intake events, identify the same invoice, replace neither source silently and designate the complete file as the processing reference under the approved policy.
Verify the amount, entity, invoice number and line set against all pages. Close the incomplete capture as linked supporting history, not a second obligation. Record why the email file became the governed working source and retain the physical document location or approved disposition.
Route review, exceptions and access
Send the complete digital record through the appropriate verification and approval path. Name missing purchase references, unreadable fields, entity conflicts, duplicate suspicion and unsupported lines as specific exceptions with owners and next dates. Avoid a generic scan failed state that forces the next reviewer to repeat discovery.
Restrict access to the document and extracted data according to role. Do not expose bank, address or personal information more broadly merely because the file is now searchable. Record downloads, material edits and administrative interventions where the approved control requires them.
Close with a provenance and reconciliation check
Reconcile received items to digitised records, held exceptions and approved dispositions. For a sample, retrieve the source channel, raw capture, extracted values, corrections, duplicate decision, approval and downstream identifier. A second authorised person should understand what was received and how it became the current record.
Review recurring scan defects, missing pages, duplicate channels and correction patterns. Improve intake guidance and capture equipment without publishing unsupported accuracy claims. The objective is not a paperless label; it is a traceable digital record that preserves the evidence and decisions the paper once carried.
Decision summary
Identify the source document before capture.
Preserve an unchanged raw image and its provenance.
Treat extraction as data entry, not approval.
Resolve duplicates and unreadable fields through owned exceptions.
Reconcile every received item to an explainable digital outcome.
Verify the record before physical disposition
Before returning, archiving or disposing of the paper under the approved policy, confirm the digital record contains every page, readable identifiers, attachments and the intake reference. Ask a second authorised person to compare a sample with the source. Record the check and any recapture so later users do not discover that the only complete evidence has already left controlled custody.
Put the control into practice
Choose one paper-heavy workflow and follow it from source to payment. Digitise the facts and ownership at every hand-off, not merely the page that reaches the customer.
Run the review on a real case
Scanning a paper invoice creates a digital image, not a controlled invoice record. Capture customer, entity, number, dates, terms, lines, currency and source references as structured facts, then retain the scan only as supporting evidence.
Test retrieval using one issued invoice, its approval, delivery event, customer question, correction and payment allocation. A complete digital process should surface the chain without depending on a filing cabinet or personal inbox.
Case-review checklist
Required invoice facts are structured
Original evidence remains available
Versions and corrections are linked
Delivery outcome is recorded
Payment closes the right balance
Digitisation should not alter the legal or accounting status of the document. Retention periods, electronic-invoice rules and record formats must follow applicable policy and jurisdiction.
Evidence
Sources and scope
- GOV.UK: invoices and required information
Supports the example that an invoice must retain required information; it does not establish global requirements or product capability.
Continue in context
