How an AI agent can prepare a reconciliation queue for finance review
This workflow gives an AI agent a defined job, a bounded set of records, and a result a person can review. The agent reads the relevant Brex context and matches it with Xero, applies the rules in the prompt, and keeps the source behind every recommendation. It returns a proposed handoff rather than taking consequential actions on its own.
Can an AI agent prepare a reconciliation queue for finance review using Brex?
Yes. Start with the scope, date range, decision rules, and fields that identify the right records. The agent can collect the evidence, compare states or sources, mark conflicts and missing data, and organize the result around the outcome above. A reviewer then checks the matches and judgment calls before approving messages, record updates, bookings, purchases, publishing, or other write actions. The guide below shows the records, boundaries, prompt, and handoff needed for this specific workflow.
Match the transaction before checking the coding
Brex contains the card transaction, cardholder, merchant, memo, receipt, and spend context. Xero contains the bank or card-feed item, account, tax treatment, contact, and reconciliation state. Match on a stable external ID when available, then use amount, currency, date, and merchant as supporting evidence.
Keep one-to-many charges, refunds, fees, and foreign-exchange differences in separate exception groups. A forced one-to-one match can hide the real accounting treatment.
Example starter prompt
Compare Brex transactions for [scope and dates] with Xero records in [account]. Match by external ID first, then amount, currency, date window, and merchant.
Show unmatched items, duplicate candidates, amount or currency differences, missing receipts, account-code differences, tax differences, and reconciliation-state conflicts. Cite both records and explain the match method. Draft proposed corrections, but do not post or reconcile entries.Leave accounting judgment with the accountant
The agent can show that a transaction’s Brex category differs from the Xero account, but it should not choose tax treatment or final coding without the organization’s rules. It should also preserve the original values and identify whether the difference came from a source update after export.
Questions this workflow answers
Why do our card transactions and accounting records disagree, and which differences require an accountant?
An agent can match Brex spend with Xero ledger records before evaluating coding or evidence. Give it the card accounts, ledger account, date range, and matching rules. A stable external identifier takes precedence. Amount, currency, transaction and posting dates, merchant, cardholder, and reference fields provide supporting evidence. One-to-many settlements, refunds, fees, and foreign exchange belong in explicit exception patterns rather than being forced into one-to-one pairs.
After matching, the agent compares current values: receipt presence, memo, contact, account code, tax field, amount, currency, and reconciliation state. It should preserve both source records and the method used to connect them. A date difference caused by settlement may be expected; a card charge with no ledger entry is a different problem from a ledger entry coded to another account.
Accounting judgment remains with the accountant. The agent can say that the spend category and ledger code differ, quote the organization’s mapping rule if supplied, and draft a proposed correction. It cannot choose tax treatment from merchant name alone or assume that a reconciled entry is correct. If a source changed after export, the timeline should show which value came first.
The resulting queue separates confident matches, unmatched items, duplicates, amount or currency differences, coding questions, tax questions, and missing evidence. An accountant reviews proposed changes and decides whether to post, reconcile, reverse, or request information. Keeping the original and proposed values side by side makes the review fast while preserving an audit trail. The agent never posts a journal, changes a card transaction, or marks an item reconciled during this comparison.
Expected handoff
Return matched pairs, unmatched records, duplicates, coding and tax discrepancies, missing evidence, and proposed owner actions. Each correction needs the Brex transaction, Xero record, current value, proposed value, and reason. An accountant approves all ledger changes.