Cash application in insurance is matching money received from brokers to the policies, layers, or treaties it pays for, then posting it as settled. Done well, every payment lands on the right obligation with the evidence for why.
Because the money rarely arrives looking like the obligation it settles. Four patterns do most of the damage.
Brokers remit in bulk. A single credit can settle dozens of policies bound across different months.
The amount on the statement rarely equals the amount booked. The shortfall is the broker’s commission.
Subsidiaries, trading names, and abbreviations mean the payer on the statement rarely matches the record.
The statement line often carries a truncated policy reference, or none at all. The context lives elsewhere.
Whether it runs in a spreadsheet or a system, cash application is five steps, in order.
Bank statements, broker remittance advices, and bordereaux arrive in whatever shape they are sent.
Each credit is read for payer, reference, amount, and currency, including references buried in free-text narrative.
The payment is matched to the open obligations it settles: a policy, a layer, a treaty, or a remittance’s list of line items.
Anything that cannot be matched with confidence goes to a person for judgment, with the reason attached.
Matched cash posts to the PAS and GL as applied. The unallocated balance shrinks instead of growing.
Unallocated cash is money that has arrived in the bank but hasn’t been matched to the obligation it settles. It misstates the debtor position, hides genuine credit risk, and consumes the team: in delegated-authority operations, matching and exception-chasing absorbs 45–60% of credit-control hours.
Yes, and the reliable way is deterministic: a ladder of explainable matching rules, with every match recording the rule that made it. AI reads the documents and argues the borderline cases; it never decides a match. The workhorse rule is the three-way match: bank credit, broker remittance, and bordereau in agreement.
Brisc’s Reconciliation Analyst ingests statements, remittances, and bordereaux, matches them by rule, and posts reconciled cash back to your PAS and GL. Your team reviews the exceptions, not the volume.
Match rate on day one, climbing over roughly 90 days as rules and aliases accumulate.
Roughly the share of rows that need human review at steady state. The rest clears itself.
To live. Day one needs no PAS integration: uploads in, evidenced CSV out.
See the full matching ladder on bank reconciliation for insurance, or browse all guides.
Cash application is one half of bank reconciliation: applying money received to the obligations it settles. Reconciliation is the wider discipline, which also clears bank fees and internal transfers, and proves the bank position against the ledger. In insurance operations the two run together, on the same files.
The single credit has to be split across every policy it settles, usually by working back from the remittance advice that lists the lines. This is the case manual processes handle worst, and the main reason unallocated cash accumulates.
A broker often remits premium with their commission already deducted, so the bank amount doesn’t equal the booked obligation. Correct cash application recognises the shortfall against gross as commission and records gross, net, and the implied rate rather than leaving the line unmatched.
No. Automation absorbs the volume matching; the team keeps the judgment. Exceptions still route to a person, with the reasoning and source documents attached. At steady state that review queue is roughly one row in twenty, not the whole workbook.
No. You cannot make brokers send clean remittances or banks send parseable narratives, so the mess isn’t yours to fix. A system built for insurance reads the files as they actually arrive and documents the mess while it works it.
30 minutes, no slide deck, your real files: a bordereau, a statement, a submission. Your business is specific; the walkthrough should be too.
Book the walkthrough