Invoice Intake with Human Review

About this design

This is a design walkthrough, not a completed client implementation or a report of measured results. It describes how I would approach this workflow and the checks needed before launch.

Receive and identify the document

An email trigger collects the attachment and records its source. A document fingerprint helps detect a repeated attachment before a second draft is created. File types and size limits are agreed as part of the implementation.

Extract into a draft

The extractor returns supplier, invoice number, dates, line items, and totals in a defined structure. Rules check required fields and whether the amounts reconcile. A model confidence score alone is not treated as proof that a value is correct.

Make review practical

A reviewer sees the source document alongside the draft and the fields that need attention. They can correct a value, approve the record, or reject the document. No payment is initiated by this design.

Write the approved version

The destination receives the reviewed fields and a reference to the source. A stable record key makes retries safe; delivery status remains separate from review status so a temporary outage does not lose an approved invoice.

Adapting it to your team

The first conversation establishes your tools, data access, review responsibilities, and expected workload. The scope should include representative examples and acceptance checks before a production rollout.