
- RULESDate and amount tolerance, fees and duplicates live in Knowledge.
- FILESStatement and entries for the period go in as CSV, with no bank data.CSV only
- COMPARISONBoth sides are matched using only the rules in the base.rule cited
- DIFFERENCESEach difference comes out with its type, rule and source records.
- REVIEWThe list goes to the treasury queue through an n8n flow.awaiting approval
- DECISIONThe team decides; the agent does not settle or pay.human decision
How it works
During setup, the reconciliation rules (date and amount tolerance, fees, duplicates) go into Knowledge, and the statement and the ledger report for the period are uploaded as CSV; to check a few lines, just paste them into the conversation. The assistant matches both sides using only the rules in the base and lists each difference with the statement item and the ledger item (file and record), the rule applied with its source document, and the type: "statement only", "ledger only", "amount differs", "date outside tolerance" or "possible duplicate". With no rule in the base, it uses the exact amount and the same date and says so. A foreign currency entry follows the rate the rule specifies; if the rule says to use PTAX, the assistant queries the Central Bank of Brazil rate on the entry date and shows the rate used, and an exchange difference becomes a difference for review, never an adjustment. Nothing is declared reconciled: what matches comes out as "matched by rule". Sending the list to treasury for review is an n8n flow that runs only after a person approves.



