AI proposes, you approve
No payment is applied without a person confirming it. A design decision, not a limitation.
Pacunex automatic bank reconciliation reviews your statement against your receivables and proposes the match. You approve the obvious in bulk; you decide the doubtful.
AI proposes, you approve · no payment is applied on its own.
Matching the bank against the ERP means manually hunting which invoice each deposit paid. And it rarely matches cleanly: withholdings lower the amount, there are partial payments, and single transfers covering five invoices at once. Detective work, repeated every month, done by people who should be collecting.
A spreadsheet only its author understands — and that breaks when that person leaves.
Payments left unapplied for weeks, while the customer still shows as overdue.
Month-end closes that drag because nobody finishes matching on time.
The system recognizes your bank's format and loads the movements. Each bank is configured once.
It compares each movement against your receivables and builds the proposal. It runs on its own as soon as the import finishes.
It separates exact matches from those with withholding, partial payment, multi-invoice payment, or no match at all.
You accept the obvious in bulk, review the doubtful and discard what should not be reconciled.
It is not an amount comparator. It understands the real cases of a LATAM company: withholdings, partial payments, payments covering several invoices, and receipts sent as photos. And it never moves money on its own.
No payment is applied without a person confirming it. A design decision, not a limitation.
Exact matches are accepted at once. Tick what you want and confirm in one click.
It recognizes when a deposit comes in lower due to a withholding, or when it is a partial payment of a larger invoice.
It detects the transfer covering a set of invoices and applies them in order.
The customer sends a photo of the transfer and the system extracts the data to validate it.
Statement lines that will not be reconciled leave the view and stop getting in the way.
Your bank on one side, your management system on the other. Pacunex sits in between.
Honest projections — Pacunex is in open beta.
The obvious is bulk-approved the same day the statement arrives; the team only looks at exceptions.
The payment is applied on time, so the customer stops showing as overdue and gets no collection message.
The criteria live in the system, not in the head of whoever built the spreadsheet. Every run is logged.
Guided implementation, special beta conditions and a direct voice in the roadmap.
No, and that is on purpose. The AI proposes the match and a person approves it. You can bulk-accept exact matches, but nothing moves without someone confirming.
Yes. It is one of the most time-consuming cases when reconciling by hand: the deposit arrives for less than the invoice amount. The system recognizes it and proposes it as such, instead of flagging it as unmatched.
The system detects that the movement covers a set of invoices and proposes applying them in order. You do not have to break the payment apart by hand.
It is separated into its own group for you to review. And if a statement line should not be reconciled, you mark it as ignored and it stops appearing.
With the file your bank gives you. We support the usual statement formats, including MT940, and each bank is set up once. Tell us which one you use and we will confirm.
No. The AI agent queries what it needs each turn via database, REST API or MCP and does not copy your database. Chat sessions and operational logs are stored encrypted in our infrastructure, isolated per company.
Let's chat on WhatsApp, look at a real statement of yours and show you what would match on its own and what would not.