Match, validate and reconcile with a record
Invoices against purchase orders, receipts against policy, accounts against statements. Mismatches stop and go to an approver instead of being posted.
The playbook in 54 seconds
What each agent checks and who decides the exceptions. All videos
What you can build for accounting
Invoice and PO matching
Invoice and PO matching reads a supplier invoice and its purchase order. It checks the PO numbers, supplier and line quantities match and the totals differ by 2 percent or less, then holds any mismatch for an accounts payable approver.
Tested: clean set completed; 3 of 3 planted errors flagged.
View on the Docy AI marketplace →See the brief
Build an agent that matches a supplier invoice to its purchase order. From the invoice and the PO, extract the supplier name on each, the invoice number, the PO number quoted on the invoice and the PO number on the PO, each line item with its quantity on both, and the two totals. Also have the extractor work out the difference between the totals as a percentage of the PO total, and state whether all line quantities match (Yes or No). Check that the PO numbers match, the supplier matches, the quantities match, and the total difference is 2 percent or less. If any check fails, hold the invoice for an accounts payable approver to approve or reject. Then write a matching result showing each check and the outcome.
Receipt validation
Receipt validation reads an expense claim and its receipts. It checks each receipt is dated within 60 days of the claim, is under 500 and has an allowed category, then sends exceptions to a finance approver and writes a validation record.
Tested: clean set completed; 3 of 3 planted errors flagged.
View on the Docy AI marketplace →See the brief
Build an agent that validates an expense claim against our expense policy. From the claim form, extract the submission date, and from each receipt the merchant, date, amount, currency and category. Also have the extractor work out how many days before the submission date each receipt is dated, and state whether every category is an allowed type: meals, travel, accommodation, taxis or office supplies (Yes or No). Check that every receipt is dated 60 days or less before submission, every amount is under 500, and every category is allowed. If any check fails, send it to a finance approver to approve or reject. Then write a short validation record for the claim.
Account reconciliation
Account reconciliation reads a ledger report and a bank or supplier statement. It checks the closing balances agree within 0.5 percent, every ledger transaction appears on the statement and the periods match, then sends differences to the finance manager.
Tested: clean set completed; 3 of 3 planted errors flagged.
View on the Docy AI marketplace →See the brief
Build an agent that reconciles a ledger to a statement. From the ledger report and the bank or supplier statement, extract the period and closing balance of each, and the ledger transactions with date, reference and amount. Also have the extractor work out the difference between the two closing balances as a percentage of the statement closing balance, and list any ledger transactions that do not appear on the statement (or None). Check that the difference is 0.5 percent or less, no ledger transactions are missing, and the two periods match. If any check fails, send the differences to the finance manager for review. Then write a short reconciliation note.
The brief is what you type into the Docy AI assistant. Agents tagged Open Docy can also be built by hand on the open-source canvas. Agents tagged Docy AI may need custom code, a knowledge list or a policy node, which Open Docy does not include.
Your rules. A person's decision. A record.
Send the documents
Upload an invoice with its purchase order, an expense claim with its receipts, or a ledger with its statement.
Apply your rules
Your tolerances and policies are checked the same way every time. Mismatches are held, not posted.
Keep the record
Each run records the check, the values found and who approved the exception.
Be clear about the limits
- No accounting-system connection. Agents read the documents you give them and export a result; they don't post to your ledger.
- They apply your tolerances and policy; they don't decide what is correct accounting treatment.
- These agents check documents against rules you set. They do not replace the people who make the decision.
- We have tested these: each completed a clean test set and flagged the errors we planted in a flawed one. Test on your own files before relying on them.
Want to try one on your own accounting documents?
Tell us which documents you work with and which check would save you the most time.