CashMatch reads your bank statements in any format, matches each deposit against the premiums you expect to collect, and scores every match against rules your own team defines. What is certain is applied. What is not goes to a person, with the evidence attached.
Built for insurance & reinsurance premium collections · Deployed under your data governance
Not a faster way to open files. A different way to decide: every deposit reaches a policy through rules you can read, change and defend.
Hundreds of statements per cycle in PDF, Excel, Word, native or scanned. No template per bank, no re-keying, no pre-formatting by anyone on your team.
Weighted rules built from how your executives already decide: tolerances, payment windows, authorized payers, FX scenarios. Change a weight and the outcome changes with it.
Rule-by-rule scoring plus a written argument attached to each item — the amount, the name, the reference recovered, the behaviour this payer has shown before. Audit reads what the analyst reads.
Above your threshold it applies on its own. Below it, the exception arrives with the evidence already assembled — so an executive confirms in seconds instead of investigating for an hour.
Premium collections is a matching problem disguised as an accounting problem. Every deposit that lands in the bank has to be tied back to a policy, a receipt and a due date — and almost nothing arrives in a shape that makes that easy.
One statement is a PDF, the next is an Excel export, the next is a scan. Hundreds of files per cycle, none of them shaped the same way.
A single global payment covers several policies and receipts. The amount only makes sense once you know which receivables it was meant to cover.
The lead coinsurer pays. The reinsurance intermediary pays. The cedent pays. An affiliate pays under a name that isn't the full legal entity.
Bank fees taken at source, intermediary commission and VAT withheld, netted receipts, partial and advance payments. The difference has to be explained before it can be called a difference.
A USD policy paid in pesos, a peso policy paid in dollars, and a rate that may be Banxico's, the FIX, the closing rate, or whatever the payer's own bank applied that morning.
Checks with nothing attached. SPID payments from abroad with no reference and no proof. The clue an experienced executive uses is the one no rigid system reads.
The cost isn't the effort — it's the delay. Cash sits unapplied, receivables age past the terms you sold, and the close waits on a spreadsheet only two people know how to read.
See how CashMatch closes itCashMatch is a pipeline, not a black box. Each stage leaves something you can inspect — the files read, the transactions normalized, the candidates proposed, the score, and the reasoning behind it. This is the same sequence you will see live, on your data.
Connected to the source, not waiting for an upload.
In a live session we upload files so you can watch the process. In production CashMatch reads from wherever the information already lives — core system, statement inbox, party catalogs, rate feeds — and writes back into the places your close depends on.
APIs into the systems that hold policies and receivables, a monitored inbox for statements that already arrive by email, or a watched folder. The run starts on its own.
Broker, cedent and policyholder data is confidential by default. We implement the access, retention and segregation controls your security team defines, in the environment they approve.
Connect a published feed and CashMatch converts at run time, or reconstruct the rate the payer's own bank applied from the statement itself. Both are rules, and both are yours.
Most reconciliation tools ship with someone else's logic and ask you to adapt. CashMatch works the other way around: we interview your executives, map how they actually decide today, and encode that as weighted rules. Change a weight and the outcome changes with it — no release, no re-implementation.
Move the weights on the right. Every rule is a lever your team controls: switch one off, make another decisive, and watch the same transaction change verdict. This is the exact behaviour we configure during discovery — with your rules, your tolerances and your thresholds.
payer identity
Fuzzy matching between the name on the proof of payment and the full legal entity on record.
On follower contracts the settlement comes from the lead. We need the lead coinsurer catalog to recognise those payers.
The intermediary settles instead of the client. The intermediary catalog turns that into an authorized-payer rule.
Cedent catalogs let the engine tie the deposit to the treaty and receipt instead of flagging an unknown payer.
amount integrity
Incoming funds can land short by anything from USD 12 to 36 or more. With your typical fee ranges this becomes a tolerance band, not an exception.
The payment arrives net and the invoice is issued afterwards. Commission types and structures let the engine explain the exact gap.
How does your team identify them today? That answer becomes the rule that separates the components.
Money arrives before the policy exists. We need to see how it is held today and how underwriter data can be consumed.
currency & FX
Conversion applied at match time, with the rate rule you choose driving the score.
When the applied rate differs from Banxico, the engine reconstructs the scenario from the statement itself.
Payers pick different references. We need to know which ones your team accepts today to build the scenario set.
reference & evidence
Resolved by combining amount, exchange rate, references, date and the payer's history into one allocation proposal.
How are they identified today, and what information travels with the check? That is what the rule will read.
We map how your team relates them today — corridor, amount pattern, timing — and encode it.
receipt & reporting
The three lines are consolidated into a single receipt premium before the comparison happens.
They have to be applied together with the main receipt. We need the mapping that links them.
Settlement is processed in Germany. A routing rule keeps them out of the local unmatched pile.
How are they detected today? The engine can flag them at ingestion instead of at the close.
differentiated treatment
Cash Call from Germany, salvage, recoveries and subrogation land in the same account. How are they told apart today?
These items are not tied to a policy premium, so they need their own identification, treatment and accounting route.
Every "discovery question" above is an agenda item, not a limitation. What is already in the engine runs on day one. What needs your catalogs or your current practice is exactly what the domain-driven design sessions are for — and each answer becomes a rule that never has to be remembered by a person again.
See the path to productionEvery match carries its reasoning: the amount that lined up, the name that reconciled, the reference that was recovered, the payment behaviour this payer has shown in past cycles. An auditor reads the same explanation your executive does.
How many points each rule contributed, and which one held the score back.
The statement row that produced the match stays attached to it — no jumping back to the original file.
The reasoning is generated in the same language your team uses to justify a match today.
Three payments from the same intermediary did not resolve.Their clearing account changed on 3 MAR — update the authorized-payer rule?
Deposit of USD 71,430.00 scored 60%: currency converted, reference partial.Confirm the rate applied, or enter the payer's own.
One global payment covers 14 receipts with a single total.Allocation proposed — review before applying.
415 items applied automatically.Ready to export or post to your system.
Human in the loop, where a human actually adds something.
Real figures from live operations. Identities are under NDA — the full detail, including reference calls, is available in a private session. rocket code operates with 47+ carriers and brokers across LATAM.
Cross-border premium settlements arriving from a dozen jurisdictions, each with its own bank, format and currency.
A mixed MXN/USD/EUR book where deposits landed faster than anyone could tie them to a policy.
per document reconciled, from 15 min — a 97% cut
held in the suspense account, down from weeks
policy application errors, from 3.42%
evidence assembled on demand, from 3 days
No phase starts with a blank page. Each one takes something you already have — how your executives decide, your catalogs, one closed month — and turns it into behaviour the engine repeats every cycle.
Domain-driven design sessions with the people who reconcile today. We map every scenario, including the ones only one person knows how to solve.
Payer directories, commission structures and fee ranges are loaded. Rules, weights, tolerances and thresholds are configured and versioned.
We reprocess a period you have already reconciled and compare the engine's result against yours, line by line. Disagreements are the useful output.
The exceptions the pilot produced become rule adjustments. The threshold is set where your team is comfortable letting the engine decide alone.
APIs, inbox or SFTP replace the upload. Runs are scheduled, results post back, and the debtor report comes out of the same engine.
Bank reconciliation is where CashMatch starts because it is where the pain is loudest. The underlying process — read, structure, apply weighted rules, explain, escalate — works anywhere two sources of truth are supposed to agree and don't.
Bring us your hardest reconciliationTheir ledger against yours, line by line, with every difference explained.
Shares, retentions and balances between carriers on the same risk.
What was calculated against what was actually withheld and paid.
Authorized amounts against payments and supporting documents.
The session is a working one. We open the platform, start a run, and stay in it until you have seen the cases that matter to you — including the ones designed to be hard.
Hundreds of statement files in mixed formats, read and matched against a receivables file while you watch the pipeline advance.
We alter a weight or a tolerance in front of you and re-score the same transaction, so "configurable" stops being a claim.
Every transaction of the month, no clean reference and a payer nobody recognizes. That is where the scoring earns its place.
What lands on an executive's desk at the end, why it landed there, and what confirming it actually takes.
Optional and recommended: send one month of your own statements beforehand. We run yours instead of ours.
book a session
Tell us how you collect premiums today and how many statements a cycle brings in. We will come back with a session agenda built around your cases.