Premium and claims bordereaux, technical accounts and cash calls arrive from cedants and their brokers, in the broker’s layout as often as the cedant’s. Someone keys them into a ledger, in your reinsurance system or in Excel, and checks what there is time to check. Brisc reads each file as it lands, checks it against the treaty terms you configure and the last version you accepted, matches cash by contract and layer, and updates your reinsurance system and general ledger, by API or as a file they load, after your team signs off.
Most files reach you through the broker that placed the treaty. The cedant sends its account to the broker; the broker splits it by signed line and sends you a technical account in its own template showing your share, with the cedant’s bordereau attached in the cedant’s layout, and the cash through its client account. Direct placements arrive in the cedant’s layout. Three documents, one ledger: the premium bordereau, the claims bordereau, and the cash call or statement that settles them. Some cedants report inception to date, others report movements; the checks need to know which.
The same cedant arrives differently through different brokers. Brisc reads the broker’s statement and the cedant’s bordereau as one package, applies your signed line, and maps each layout once. Excel and CSV, by email, upload or a scheduled pull from your storage.
Commission rate against the contracted rate, tax and levies by jurisdiction, currency and FX, policy validity against the period, sign against transaction type, duplicates, and others set up per treaty. A check whose fields are not in the file says so instead of passing by default.
Silent premium changes, disappearing rows, status regression on claims, indemnity drops, claims that close silently, big losses the day they arrive, each with before and after side by side.
Bank lines and broker remittances matched to the expected items per contract layer, with the evidence attached. Three buckets become visible: clean, received but unconfirmed, ageing with no cash.
Every row of every file, in every version, with what changed and when, and who acknowledged what. The history stops living in a run of quarterly spreadsheets.
Validated lines and the cash-call ledger into your reinsurance administration system and general ledger, by API integration or as a file they load, after your team signs off. Your own tools and agents can also pull from Brisc’s API or through MCP agent access.
The checks that run. More than 50 checks sit in the catalog. The named ones on the validation library run on every cedant file and every version: the premium family (silent premium change, disappearing rows, cross-version diff, commission rate vs contract, tax and levy correctness, sign vs transaction type, duplicate transaction, premium outlier, policy validity, currency and FX, bank-reconciliation readiness, structural checks on request) and the claims family (status regression, indemnity drop, recovery netting, closed vs silent drop, the footing checks, reported after loss, big loss, master-drift where a master record exists). Others are set up per treaty with your team.
Your systems. DXC SICS, Sequel Re, Sapiens, a bespoke system with a spreadsheet beside it, or Excel as the ledger today. Brisc reads the files you receive and updates your system by API integration or a file it loads; your own tools can also pull from Brisc’s API or through MCP agent access. Bank statements are read; nothing is written to the bank. For the cedants who send structured data through ADEPT, nothing changes. Brisc is for the files that still arrive by email and PDF.
Four years of cedant bordereaux rebalanced, then run monthly.
Read the reinsurer case study →Cash applied by contract layer against statements and remittances across multiple currency accounts. The three buckets, clean, received but unconfirmed, and ageing with no cash, visible for the first time.
How cash application works →For brokers who hold the cash flow, Brisc matches incoming cash to the open items in the broking ledger. Paying out to markets stays with treasury.
Where a broker fits →Downstream of them, or in their place. Brisc can take the processor’s standardised output as the expected side and match cash to it, or read the raw cedant files and run the checks itself. Either way the history is kept in one program record.
No. The Excel ledger is the layout Brisc produces into until you move to a reinsurance system, and the files Brisc reads are the ones already arriving.
No. The cession pages describe the ceding side. For assumed reinsurance you are the receiver: the premium and claims bordereaux, technical accounts and cash calls from reinsureds and brokers are the files Brisc reads, checks and matches cash to.
No. They send what they send today. Brisc maps each layout once and applies the usual template changes on its own. A change that needs a decision pauses the file with the reason in plain English; Brisc updates the mapping and the same file resumes.
No. Brisc matches what arrived to what was expected and shows the result with its evidence. Settlement stays on the banking rails you already use.
30 minutes, no slide deck. We run both through Brisc and show you what moved, what the checks flag, and what would update in your ledger.
Book the walkthroughNot ready for a call? Get the MGA operations report →