// Bank reconciliation
Reconcile incoming payments automatically
An example of matching bank transactions to invoices and orders, with a confidence check that sends uncertain matches to the accountant.
Automation Example. Example workflow, not a customer case study.
The situation
Payments arrive in one or several bank accounts. An accountant opens the bank, downloads the transactions, reads each payment reference, finds the invoice and the customer, updates the accounting system and the CRM, and tells sales that the money has arrived.
Before automation
- SystemA payment arrives in the bank
- PersonAccountant downloads the transactions
- PersonAccountant reads the payment reference
- PersonAccountant searches for the invoice and the customer
- PersonAccountant updates the accounting system
- PersonAccountant updates the CRM and tells sales
Where the work breaks
- Sales learn about a payment hours or days later.
- References with typos or missing invoice numbers take the most time.
- The same payment is recorded in two systems by hand.
- Partial and combined payments are easy to mismatch.
- Month-end reconciliation becomes a separate project.
What Agentoriq automates
- TriggerA bank transaction arrives
- AutomatedThe counterparty is matched to a customer
- AIThe payment reference is parsed for invoice and order numbers
- AutomatedThe payment is matched to an invoice or order
- AutomatedA confidence check compares the amount, the payer and the reference
- AutomatedHigh confidence: the match is recorded automatically
- Requires approvalLow confidence: the accountant reviews the suggested match
- SystemThe accounting system and the CRM are updated
- ResultSales are notified that the payment arrived
Systems connected
Each system is connected through its available API, webhooks, database access or a custom connector. The approach is confirmed during the audit.
- Bank
- monobank
- PrivatBank
- BAS / 1C
- CRM
- Excel / Google Sheets
Human control
Not every payment can be matched reliably, and the workflow is designed to say so. An example of what the accountant receives: “Payment received: 48,500 UAH. Two invoices may match. Please confirm.”
- AutomatedPayments that match one invoice exactly
- Requires approvalPayments that could match several invoices
- Requires approvalPartial payments and overpayments
- Human decisionUnknown payers and disputed amounts
After automation
- TriggerA payment arrives
- AutomatedClear matches are recorded in accounting and the CRM
- Requires approvalThe accountant confirms the uncertain ones
- ResultSales see the payment status without asking
Expected outcomes
- Less manual reconciliation work.
- Payment status reaches sales sooner.
- Accounting and the CRM stay in sync.
- Uncertain matches are reviewed instead of guessed.
- A calmer month end.
Show us the workflow your team still handles manually.