Premium, claims, and risk bordereaux generated from live policy data in capacity-provider formats. Delivered on a schedule. Audit-trailed in Timeline. Built for the delegated-authority audit you have not had yet.
Why It Breaks
Spreadsheets, exports, manual reconciliation, format-of-the-month emails, and a one-person bottleneck. None of which scale, and none of which audit cleanly.
Premium and claims bordereaux assembled from spreadsheets and exports. The same person, the same days, every month or every quarter. The cost compounds.
Policy admin says one number. Finance says another. Bordereaux says a third. By the time the discrepancy surfaces, the carrier has already received the wrong file.
Manual bordereaux means manual edits to data the regulator expects to be tamper-evident. A delegated-authority audit catches the gap, and you spend a quarter explaining the spreadsheet history.
Each capacity provider wants a different layout. Templates rot, version control slips, and someone always sends last quarter's format on the day of the deadline.
How SwiftCase Does It
Four steps from policy ledger to the capacity provider, with the data behind them recorded in Timeline.
SwiftCase already holds the policy lifecycle, premium movements, claims reserves, and settlement events as structured records. Bordereaux generation reads from that source, not from a re-keyed export.
Each capacity provider's required layout (premium, claims, and risk bordereaux) is set up as a report in SwiftCase: the fields it wants, in its order, with calculated fields where it needs them.
The bordereau and the policy book read the same records, so their totals start from the same place, and a discrepancy gets fixed in the data it came from.
Files generated on a schedule and delivered by SFTP or email.
Three Bordereaux Types
All three generated from the same underlying SwiftCase data, just different views, templates, and schedules.
Per-policy premium movements: new business, MTAs, renewals, cancellations. Built from the policy ledger.
Per-claim reserve and settlement movements. Status lifecycle tracked. Outstanding reserves and case-level detail included.
Risk-by-risk reporting for binding-authority arrangements. Coverage detail, exposure, and underwriting rationale captured.
Delegated-Authority Defensibility
Capacity providers and the FCA both want the same thing: reported numbers that trace back, cleanly, to operational records.
Each change to the policy and claims records a bordereau reads from is a Timeline entry with who made it and when.
Every row in a bordereaux ties back to the underlying SwiftCase case file. The auditor asks “why is this premium reported here?” and you open the policy.
The file is produced from the case records with no copy-and-paste step, so what the capacity provider receives is what your system holds.
Carrier audits expect to see how reported numbers map back to operational records. Timeline + bordereaux generation produces that mapping as a side-effect of normal operation.
FAQ
Each capacity provider's layout is set up as its own report, so an MGA writing to several capacity providers can produce each one's preferred layout from the same underlying data. Bring the layouts you send today and we set them up.
Field mappings and template structure are configured by our implementation team during onboarding. Once a template is defined, adjustments to the layout are configurable by your operations team without engineering involvement.
There is no separate reconciliation engine. The bordereau reads the same policy and claims records as the rest of SwiftCase, so its totals and your book start from the same data, and the pivot tables let you check the totals by period before the file goes.
Correct the records, run the report again for the period and send the new file. Each correction is in Timeline with who made it, so the carrier can see what changed.
Delegated-authority audits expect to see (a) that operational data is captured at source, (b) that bordereaux are produced from that data without manual change, and (c) that changes to that data are logged. SwiftCase's reports and Timeline cover all three.
SwiftCase runs at insurer scale: over 11.8 million cases on a single tenant, 384 active workflows, with its policy and claims data structured for capacity-provider reporting. The detailed deployment pattern is in the specialist motor insurer case study.
Pick one binder. We generate the next bordereaux from your live data, alongside your manual process. Compare. Decide. No platform migration. No long lock-in.
