Capture records once, then review what matters.

Client and staff intake

The client upload route is intentionally simple. The client chooses the record type and uploads the source file; staff then review it in the accounting workflow.

Required classification

Use Sales, Purchase or Expense for documents so the capture engine has the right accounting context. Bank statements follow the dedicated banking route. Clients do not post entries into the ledgers themselves.

OCR and uncertain fields

OCR should reduce re-keying, not remove review. Check supplier/customer identity, date, gross/net/VAT, document number and any field that is uncertain or conflicts with the source.

Bank statements

Bank statement uploads belong to the banking workflow. The bank engine should protect against duplicate lines, identify gaps/overlaps where possible and preserve the source statement context.

See Bank import & reconciliation →.

Duplicates and evidence

Duplicate control should focus on the underlying document or statement lines, not merely the uploaded filename. Keep source evidence attached so a reviewer can understand why an accounting entry exists.

Missing information

Where a source document is missing, request it from the client. For a Document-Led client, use the controlled bank-only coding action only after the missing documents have been confirmed as unavailable and the practice is ready to code those bank entries from the bank evidence.