The Reinsurance Accounting Analyst reads each cash call as it arrives by email or drag and drop, assesses it against the contract on file, and shows your reviewer every figure with its source. Approved calls are filed against their contract, so next month you can see what each layer has paid and what is left.
| Field | Value |
|---|---|
| Contract ref (UMR) | B0823XL2026014 |
| Date of loss | 29 Aug 2026 |
| Layer | USD 10M xs 5M |
| Currency | USD |
| Share applied | 13.00% |
| Amount requested | 412,000.00 |
| Check | Contract | Cash call |
|---|---|---|
| Contract match | UMR found | B0823XL2026014 |
| Date of loss in period | 1 Jan to 31 Dec 2026 | 29 Aug 2026 |
| Layer | USD 10M xs 5M | USD 10M xs 5M |
| Currency | USD | USD |
| Share applied | Discrepancy: 1.37% on the slip | |
| Arithmetic | 10 checks | all agree |
Approved calls are filed against their contract and the version they were assessed against, so paid-to-date and limit remaining stay current. The payment request itself stays in your system.
A 13% applied where the signed line is 1.37% is a nine-figure difference on a large loss, and it is caught only if the reviewer remembers the contract.
Long-tail books still receive cash calls on contracts a decade old. Finding the slip to check a layer or an attachment point takes longer than the review.
Paid less retention, amount due at 100%, our share, reinstatement premium, net payment: five figures re-keyed into a list, with no check that they add up.
Once a cash call is paid it is gone. Paid to date on a layer, limit remaining, which cedant keeps sending the wrong share: finance answers these by hand, if at all.
Forward the cash call to a Brisc address, or drop the PDF or email on the screen. Attachments stay together as one cash call.
Every field is extracted with its source. The cash call is matched to the contract on file by policy reference, UMR or broker risk reference, then cedant and period, and checked: our share, share applied, parties, date of loss, layer, currency, underwriting year, contract status and ten arithmetic checks.
The reviewer sees the assessment first, then every field with its source. Correct a value and the assessment re-runs. Approve, reject with a reason, or archive. Approving a discrepancy asks for a note.
| Assessment | What it means |
|---|---|
| Looks correct | Contract found, and every check that ran agrees. |
| Discrepancy | Contract found, and at least one check differs. A Brisc insight sets out what the contract says, what the cash call says, the difference and the likely cause. |
| No contract found | Nothing on file matches. The references tried are listed. |
| Could not fully assess | Contract found, but a field a check needs is missing. The missing fields are named. |
The assessment is advisory. Brisc flags; your team decides. Every figure in an insight comes from a check, never from a model.
Cedant, loss, contract, amount at our share, due date and the assessment. Filter by assessment, or search by cedant or reference.
“The contract share is 1.37% (slip, signed lines, p.3). The cash call applies 13.00%. At 1.37% the amount due would be USD 43,418.46, USD 368,581.54 less than requested.” One click copies it for your email back to the broker.
Seven tabs of extracted fields, each value with the excerpt it came from. Unconfirmed extracted values are marked.
The terms the cash call was assessed against, with the version and the date they last changed. Nobody trusts an assessment against terms they cannot see.
By contract: calls, approved to date at 100% and at our share, limit remaining and last call. Also by loss across layers, by cedant and broker with discrepancy rate, by period and currency, and an exceptions view. Export any view to Excel, and mark calls paid with a date and reference.
| Old way | With Brisc | |
|---|---|---|
| Share check | Reviewer recalls the line, or looks for the slip | Signed line, basis of the line and order % on file; share and share applied checked on every call |
| Arithmetic | Re-keyed, unchecked | Ten checks, each with expected, observed and difference |
| Contract terms | Slip in a folder | Entered once per contract, layer and year; every term carries its clause or page |
| Period and status | Not checked | Date of loss tested against the period on the contract’s loss basis; commuted contracts flagged |
| The difference, in writing | Drafted by hand | Written up from the checks, ready to copy |
| History | A shared list | A ledger by contract, loss, counterparty and period that cannot be edited after approval; Excel export |
| Approval | Keyed into a list | Approved with name, time and, for discrepancies, a note |
Today Brisc enters the contract terms for you. Send the slip and endorsements, and we record the reference and UMR, the reinsured and broker, year and period, type and layer, currency, limit and attachment, and your share. Once a contract is on file, every cash call on it is assessed against it.
Uploading and editing contracts yourself is on the roadmap. The payment request process stays exactly where it is: Brisc sits in front of it.
Working on the inbound side? The same Analyst handles cession statements, classifying cedant statements into your ledger’s entry codes.
No. The payment request stays in your own system and your own approval process. Brisc checks the cash call against the contract and files it once your reviewer approves it. Approval in Brisc means checked, and you are content.
Today Brisc enters them for you. Send the slip and endorsements, and we record the terms each cash call is checked against. Uploading and editing contracts yourself is on the roadmap.
The cash call is marked No contract found, and the references Brisc tried are listed. Nothing is guessed. Once the contract is entered, the cash call is assessed against it.
No. Brisc writes up the difference, and a Copy button puts it on your clipboard for your own email. Brisc never sends it.
Send us two or three contracts and a handful of cash calls. We'll show you every assessment, figure by figure, against your own terms.
Book a demo