A bordereau is written once by the MGA, checked by the capacity provider that carries the risk, and settled on again by the reinsurer behind them. Each party keeps its own system of record, and each one rebuilds the same file by hand. Brisc produces, checks, matches to cash and updates your systems at each handoff, beside the systems you already run. Your systems stay the system of record, and payments stay on your banking rails.
Premium and claims bordereaux, technical accounts and cash calls from cedants and their brokers.
Where Brisc fits for a reinsurer → You receive and sendBordereaux in from MGAs and TPAs, a cession report out to your reinsurers, from the same figures.
Where Brisc fits for a carrier → You sendThe bordereaux your capacity requires every month, and the paid bordereau once the cash is in.
Where Brisc fits for an MGA →Bordereaux move up the chain from the MGA that writes the risk to the reinsurer that shares it. Each party keeps its own system of record. Brisc works at five points along the chain, reading the files you send and updating your systems by API or file.
Most treaty business reaches the reinsurer through the broker that placed it. The broker checks the cedant’s account against the slip, splits it by each reinsurer’s signed line, and sends each reinsurer a technical account in its own template with the cedant’s bordereau attached. Premium, claims and cash calls move through the broker’s client account. Direct placements go cedant to reinsurer in the cedant’s layout.
MGAs say BDX or border row. Brokers say statement or technical account. Reinsurers say treaty account, statement of account or cash call. Finance teams at carriers call it the reinsurer export, or just the month-end file. If a file lists risks, premiums, claims or payments line by line and goes to the party that carries or shares the risk, Brisc reads it, checks it and produces it.
Brisc sits beside them, reads what you send it, and updates them after your team has reviewed. Brisc hands the result to your systems three ways: by API integration into your policy administration system, broking system or reinsurance system, such as Insurity, BindHQ, NOVUS or DXC SICS; as a file in the layout the system loads; or through Brisc’s API and MCP agent access, so your own tools and agents pull what they need.
Where a managing agent already runs a bordereaux management platform, Brisc takes its validated output as the expected side and ties each line to the cash that settled it. Where there is none, Brisc runs the checks. Either way the platform, the policy system and the ledger stay the record; Brisc is how checked data reaches them.
A Canadian carrier that takes programs from MGAs and brokers. Premium and claims bordereaux arrive in each partner’s layout; Brisc checks them on arrival, tracks each version against the last, and delivers the data to Fortress’s own data lake, which stays the system of record.
For carriers →An MGA whose finance team matches broker remittances to its own bordereaux in Brisc and posts cash applied to its policy system. The payment allocation report to each capacity provider comes from matched cash, not from a rebuilt spreadsheet.
Read the Helix case study →Four years of cedant bordereaux rebalanced, then run monthly, with cash matched by contract layer across multiple currency accounts.
Read the reinsurer case study →Yes. A cession statement, a treaty report, a monthly export to your reinsurer: if it lists premiums, claims or payments line by line and goes to the party that shares the risk, it is the file Brisc produces and checks. The name on the tab does not matter.
No. Brisc reads what you send it and updates them by API or file after your team has reviewed. The policy system, the lake and the ledger remain the system of record. Brisc keeps the record of every version it has received and the trail of who decided what.
Both. On the sending side it produces the bordereau from your policy data or warehouse in the layout the receiving party requires, and the paid bordereau once cash is matched. On the receiving side it reads whatever arrives, in any layout, and checks it row by row.
Yes. Brisc integrates with your system by API, as it does with a customer’s policy administration system today, or delivers a file in the layout it loads. Your own tools and agents can also pull from Brisc’s API or through MCP agent access. The system itself stays as it is.
In the middle of the cash flow. Cedants pay you, you pay the markets, and the bordereau is the map of what is owed to whom. Brisc matches incoming cash to the open items in your broking ledger with the evidence attached. Paying out to markets stays with your treasury.
No. Brisc records payments against what they settle and tells you what to remit to each capacity provider. The payment itself goes through the banking rails you already use.
On How bordereaux move through Brisc: intake channels, column drift, the validation library, review and how your systems are updated.
30 minutes, no slide deck. We run both through Brisc and show you where each figure came from, what the checks flag, and what would update in your systems.
Book the walkthroughNot ready for a call? Get the MGA operations report →