Every business that takes online payments hits the same wall: matching what the bank says arrived against what the system says was ordered. A finance manager opens the Monobank statement, opens the order list, and spends the morning ticking off transactions by hand. Multiply that across hundreds of orders and the cost is real — hours lost, payments missed, refunds delayed, and a ledger that is always a day behind.
The deeper problem is not the volume. It is that the data already exists in two places that never talk to each other. Monobank knows the exact amount, time, and reference of every incoming transfer. Your store or CRM knows which order is waiting for that payment. The gap between them is filled by a person copying numbers — and people make mistakes that compound over a month-end close.
The solution: an n8n reconciliation workflow
We close that gap with n8n, a self-hosted automation platform that connects the Monobank API directly to your back office. Instead of a manual match, a workflow runs on a schedule, pulls every new transaction, finds the matching order by amount and payment reference, and updates the order status — or flags the exceptions a human actually needs to look at.
Monobank's corporate API exposes a statement endpoint and supports webhooks for real-time events. n8n consumes both: a webhook for instant confirmation of a single payment, and a scheduled pull to catch anything the webhook missed. The result is a ledger that reconciles continuously instead of once a day.
How we build it
- Connect the API. We register a Monobank corporate token and configure an HTTP Request node in n8n to read the account statement, respecting Monobank's rate limits with retry logic.
- Normalise the data. A Function node maps each transaction's amount, timestamp, and comment field to a clean structure your system can query.
- Match against orders. n8n queries your Laravel, WordPress, or OpenCart database — or its REST API — to find the order matching the payment reference and amount.
- Update and notify. Matched orders are marked paid automatically; the workflow posts a Telegram or email alert for any payment without a clear match.
- Log everything. Each run writes to a reconciliation log, so finance has a full audit trail instead of a spreadsheet from memory.
For one OpenCart client, this replaced roughly two hours of daily manual matching with a workflow that runs every fifteen minutes and surfaces only the handful of edge cases — duplicate transfers, partial payments, wrong references — that genuinely need a person. The reconciliation backlog went from a day to minutes.
What it means for the business
Automated reconciliation is not just about saving time, though it does that. It gives you a payment status you can trust in real time: orders ship faster because confirmation is instant, accounting closes the month without a frantic catch-up, and disputes are easier to resolve because every transaction is logged with its source. The same pattern extends to LiqPay, Privat24, and Nova Poshta COD settlements — once the workflow exists, adding a second payment source is a configuration change, not a new project.
If your team still reconciles Monobank payments by hand, we can build the workflow that does it for you — designed around your stack and your accounting rules. Talk to MaxiMoruM about automating your payment reconciliation.