Payment reconciliation
Payment reconciliation platform. Every payment matched or explained.
Flominzo Recon matches every payment to provider, settlement and bank evidence with deterministic rules. AI investigates and explains the exceptions.
Last updated:
Book a Recon demoAgentic payments
Payments, built for agents.
One chapter of Kwame’s day, run through a chat. The same limits, approvals and evidence govern it as every other payment.
RecononlineWhatsApp- Payment
- TX-20418
- Provider API
- Paid 14:02
- Partner file, 23 Sep
- Not listed
The provider says PAID, but the 23 September partner file doesn’t list Mum’s payout.
That file closes at 14:00 and the payout landed at 14:02. It’s in the 24 September file: same reference, same amount.
- Action
- Match to the 24 September file
- Evidence
- 2 records attached
Approve.
Recorded your decision. TX-20418 is reconciled, with the evidence and your approval in its history.
An agent that works your exception queue. It correlates evidence across providers, partner files and bank statements, explains what it found in plain language, and recommends a resolution. You approve what happens next.
The Recon Agent never moves money and never changes a state. A person approves every resolution. Chat channels are agreed for your deployment.
Early-bird offer
Flominzo AgentPay
$3,999 setup + $999 a month
Early-bird for the first 20 customers: integration with your providers and bank or settlement files by the Flominzo team, every payment reconciled to closure, and the operations console. Month to month, no minimum term.
On this page 13 sections
What Flominzo Recon is
Flominzo Recon is a payment reconciliation platform for payment businesses, fintechs, and finance teams. It compares what your systems say happened with independent evidence from providers, settlement files, and bank statements. Every payment is matched or explained, with evidence, and each payment and each financial day closes only when that evidence agrees.
Matching is deterministic; AI explains the exceptions. Versioned rules, tolerances and expectations decide every match, so the same evidence always gives the same result and every match shows the rule behind it. AI agents investigate what the rules could not match and draft an explanation; they never decide a match.
Recon works with payments made through Flominzo and with transactions from your existing payment platform. It can start read-only, alongside the systems you already run.
The questions Recon answers
- What should have happened, and what does our application say happened?
- What do the payout partner, the settlement report, and the bank say?
- Where is the difference, and why is there a difference?
- Who owns it, and what should happen next?
- Can this payment, or this business day, be financially closed?
How Recon works
- Connect sources: Read-only transaction records, provider APIs, verified webhooks, settlement files, and bank statements.
- Preserve evidence: Raw files and callbacks are stored with a hash and their provenance before they are interpreted.
- Match: Records are matched on agreed identifiers, amounts, currencies, and business dates. Evidence is graded
CASH,SETTLEMENT,CLAIM, orINTERNAL, and a higher grade outranks a lower one. - Raise exceptions: Each difference gets a type, an owner, and a due-by time.
- Investigate: Agents correlate the evidence and draft an explanation. A person or an approved rule makes the decision.
- Close: A payment and a business day close when no blocker remains. Late evidence reopens them, with the history preserved.
Evidence Recon reads
| Source | Examples | What it proves |
|---|---|---|
| Your transaction database | Read-only replica with an agreed mapping | What your systems instructed and believe |
| Provider APIs and webhooks | Status lookups, signed callbacks | What the provider claims happened |
| Settlement files and partner reports | Settlement CSVs, payout partner reports | What the provider will settle with you |
| Bank statements and feeds | ISO 20022 camt.053 and camt.052, SWIFT MT940 | Whether cash actually moved |
Capabilities
- API, CSV, and bank-feed reconciliation.
- Payout, collection, and settlement reconciliation.
- Fee and FX reconciliation against the booked quote.
- Duplicate, orphan, and missing-evidence detection.
- Status disagreement detection between API, webhook, and file.
- Cut-off and business-day handling.
- Exception management with owners and due-by times, and evidence packs for each decision.
- Daily and per-payment financial closure, reopened by late evidence.
What 100% reconciliation means
Every payment ends either matched against independent evidence (provider, settlement file, bank statement) or as an open exception with an owner and a reason - none is silently assumed paid.
Recon does not report a match rate and leave the remainder in a spreadsheet. The unmatched remainder is the exception queue: each item typed, owned, and due. See the exception types.
Agents investigate. People decide.
Matching itself never depends on a model. The Recon Agent reads, correlates, and drafts an explanation for each exception. It can request a deterministic action, such as a status lookup or a file re-fetch, through the same controlled commands a person would use.
It never closes an exception, accepts a settlement, or writes off a difference on its own. Those decisions stay with the people and rules you approve, and every agent action is recorded with the agent as the actor.
What agents can and cannot doWho Recon is for
- Remittance and payout operators reconciling provider claims with settlement and bank evidence.
- PSPs and fintechs running several providers for the same corridor.
- Finance and treasury teams closing the business day.
- Teams with an ageing reconciliation backlog. Read the use case.
Start alongside your current systems
A Recon deployment can start with read-only access and one payment flow. Run it in parallel with your current process for a representative financial day, including late records and adjustments, before relying on it to close a day.
See the integration approachMarkets
Rails, statement formats, and regulation differ in each market. Flominzo is connected through rail adapters to the providers you use; markets, rails, and activation are agreed for your deployment.
Questions
Do we need to make payments through Flominzo to use Recon?
No. Recon can read transactions from your existing payment platform, alongside provider and bank evidence, while your current systems keep running.
Which bank statement formats does Recon read?
The integration modules include parsers for ISO 20022 camt.053 and camt.052, SWIFT MT940, and configured CSV layouts. Each format is validated against your actual files before activation.
Can we read reconciliation results through an API?
Yes. The REST API reads payment state, events, evidence, positions, settlements, and exceptions in your integration environment.
What happens if a reversal arrives after a payment was closed?
The payment reopens with a POST_CLOSURE_EVIDENCE exception. The earlier closure decision stays in the history, and the new evidence is visible next to it.
Related guides
Let’s make it specific to you.
Bring your systems, payment flows, and questions. We’ll help define the next step.
Talk to the team