Receipts and invoices compared at period end. Your controller approves each entry.
The agent compares what the ERP says arrived with what accounting says was billed, types each difference and drafts the adjusting entries. Nothing posts until the controller approves it, and nothing posts to a closed period.
DesignedThe steps and approvals are designed. It has not run yet.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent for reconciliation does the comparison your finance team rebuilds every period. Goods arrive and are received in the ERP. Invoices arrive and are posted in accounting. At period end someone exports both, lines them up in a workbook, and works out why the two do not agree: an invoice not yet in, a price that differs, a short delivery billed in full.
This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet.
How it differs from invoice matching
Invoice matching checks one invoice before it is paid. Reconciliation looks back over a whole period and one account, and finds what the day-to-day checks left open.
What the controller gets
- Every difference, typed as timing, price, quantity or no invoice, with both documents attached.
- A draft adjusting entry for each difference that needs one.
- A list of receipts with no invoice at all, with the query to the buyer drafted.
The rest of the library is on the workflows page.
One account, one period, every receipt matched or named.
The account, the period and the suppliers are examples. The approval sits on the posting. The refusal protects the period your team has already reported.
- 01Ticketing
Take the reconciliation task from the close checklist and receive a credential for this account and this period only.
- Who approves
- No approval on this step
- On the record
- credential issued · one account, one period
- 02ERP
Read the goods receipts for the period that are not yet matched to an invoice.
- Who approves
- No approval on this step
- On the record
- read-receipts · allowed
- 03Accounting
Read the supplier invoices posted against the same orders.
- Who approves
- No approval on this step
- On the record
- read-invoices · allowed
- 04Office suite
Match by order line in the reconciliation workbook. Type each difference: timing, price, quantity or no invoice.
- Who approves
- No approval on this step
- On the record
- match-lines · allowed · differences typed
- 05Accounting
Draft an adjusting entry for each difference that needs one, with the receipt and the invoice attached.
- Who approves
- No approval on this step
- On the record
- draft-adjustments · allowed
- 06Accounting
Try to date one adjustment in the previous period, where its receipt belongs. That period is closed, and posting to a closed period is outside the permission, so the step is refused. The entry is drafted in the open period with a note.
- Who approves
- No approval on this step
- On the record
- post-closed-period · refused · period closed
- 07Accounting
Post the adjusting entries. The step waits until the controller approves each one.
- Who approves
- Controller
- On the record
- post-adjustments · approved by controller
- 08Email
Draft the query to the buyer for each receipt with no invoice on file.
- Who approves
- No approval on this step
- On the record
- query-buyer · allowed
- 09Ticketing
Attach the finished workbook to the close checklist and mark the task ready for review.
- Who approves
- No approval on this step
- On the record
- ready-for-review · allowed
The systems, by type
We name systems by type. Yours are named in the assessment.
Ticketing
Holds the close checklist. The agent takes one task and returns it with the workbook attached.
ERP
Holds the goods receipts and the orders behind them. The agent reads them and changes nothing.
Accounting
Holds the invoices and the ledger. The agent drafts entries there, and posts only after the approval.
Office suite
Holds the reconciliation workbook your team already uses, if you keep it in a spreadsheet.
Carries the drafted queries to buyers about receipts with no invoice.
The approval, the refusal, the record
- A person approves: Post the adjusting entries. The step waits until the controller approves each one.An adjusting entry changes what the books say for the period, so the controller who signs the close approves each one.
- Refused: Try to date one adjustment in the previous period, where its receipt belongs. That period is closed, and posting to a closed period is outside the permission, so the step is refused. The entry is drafted in the open period with a note.A closed period has already been reported, and a late entry would change figures others rely on, so the job drafts into the open period and leaves any reopening to a person.
- On the recordEach receipt and invoice read, each difference and its type, the refused entry with its reason, each posting with the controller’s name, and each query sent.
What goes on the record
- credential issued · one account, one period
- read-receipts · allowed
- read-invoices · allowed
- match-lines · allowed · differences typed
- draft-adjustments · allowed
- post-adjustments · approved by controller
- query-buyer · allowed
- ready-for-review · allowed
One record per step, as designed. This workflow has not run yet.
What it does not do
- It does not decide how a difference is treated. It types it and drafts an entry, and the controller decides.
- It does not reopen a period or post an entry without approval.
- It reconciles the accounts named in the assessment. Bank and intercompany accounts are scoped on their own.
Questions and answers
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.