One product covers premium and claims bordereaux and cession statements. Brisc reads the layout each partner actually sends, validates every row at ingestion, versions it against the last file you accepted, and generates the bordereau back out in the format the receiving party requires.
Row 214, delegated binder program, June bordereau. Commission billed at 30.0% against a contracted binder rate of 22.5%. Gross less commission, brokerage, taxes and fees doesn’t add up to the stated net premium; the difference is 18,406.12. Flagged for review, with the row left untouched.
Three vantages on the same engine.
Monthly files from coverholders and brokers: validated against the binder, reconciled to the cash.
Explore bordereaux reconciliation →Every version tracked, financials reconciled row by row, exceptions queued with evidence.
Explore claims bordereaux →The reinsurer and cedent vantage: cession statements read and checked by the same rule library.
Explore the cession vantage →Validation runs the moment a file lands. A sample of what runs:
Every file diffed against the last one you accepted, so nothing changes silently between periods.
Totals recomputed on every row, so the file balances before it moves anywhere.
Rates validated against the binder, row by row, not sampled.
Repeats flagged before they inflate the month.
Rows present last period and missing this one, surfaced instead of silently gone.
Every check is named and explained in the validation check library.
Ingestion is half the job. The other half is producing the file the other end needs, in their format, on their deadline.
Normalised to one schema, then generated back out to the layout the receiving party requires: a carrier template, a syndicate layout, your own.
A partner file, a PAS extract, or a feed straight from your data warehouse. Whatever holds the written premium record.
Generated from matched cash and validated line items once the reconciliation balances.
Golden-schema export, or posted to your PAS, general ledger or data lake. Your systems of record stay canonical.
Both. The Analyst reads source data in whatever form it arrives, a partner file, a PAS extract, or a feed straight from your data warehouse, normalises it to one schema, and generates the bordereau back out in the format the receiving party requires, whether that is a carrier template or a syndicate layout. After cash is applied, it generates the premium bordereau you report up to capacity from validated line items. Brisc reads bordereaux and writes them.
No. That is the work, not the prerequisite. The Analyst takes the layout each partner actually sends, maps it once with your operations team, and reuses that mapping every month. A validated file is a good input, but nothing has to be cleaned up before you start.
Whatever your partners send: Excel, CSV, PDF, any layout, market-standard and not-remotely-standard alike. The Analyst maps a partner’s layout once and the mapping persists per program, so month two isn’t month one again. No new templates, no format mandates.
At ingestion. Every row is checked as the file lands, so by the time anyone opens it the exceptions are already queued with their evidence. There’s no separate validation step to schedule, and none to forget.
No. Anything that fails a check is flagged with the reason and the source attached, queued for your team’s judgment. Nothing is silently corrected, and nothing changes without a person deciding it should.
30 minutes, no slide deck. We run your real files, any format. Your book is specific; the walkthrough should be too.
Book the walkthrough