Premium, claims, and risk bordereaux generated from live policy data in capacity-provider formats. Reconciled before submission. 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 capacity-provider portal — and every transition 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 format — premium, claims, and risk bordereaux — is configured as a template in SwiftCase. Field mappings, calculated fields, summary rows, schema validation. Changes are versioned.
Bordereaux totals reconciled against the policy book and finance ledger before the file is finalised. Discrepancies flagged for handler review. No surprises after submission.
Files generated on schedule, delivered via SFTP or capacity-provider portal where supported. Submission timestamps and acknowledgements logged in Timeline.
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. Reconciled against 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.
Bordereaux file generated → reconciliation outcome → scheduled delivery → carrier acknowledgement. Each step a Timeline entry with actor, timestamp, and outcome.
Every row in a bordereaux ties back to the underlying SwiftCase case file. The auditor asks “why is this premium reported here?” and you click through to the policy.
Bordereaux outputs are cryptographically hashed against the underlying data state. Any post-submission edit is visible. Capacity providers see clean files; auditors see clean provenance.
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
We support the formats used by every major UK capacity provider, plus standard Lloyd's bordereaux structures. Format templates are configured per binder, so an MGA writing to multiple capacity providers can produce each provider's preferred layout from the same underlying data.
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. New capacity providers added during the relationship are typically configured within a few days.
Before a bordereaux is finalised, SwiftCase compares the file totals against three sources: the policy ledger (premium movements over the period), the claims register (reserve movements and settlements), and any finance system integration (payments processed). Discrepancies are surfaced as a structured list — by case, by amount, by type — for handler review before the file is locked.
Revisions are handled as a new versioned file with a delta record showing what changed and why. Both the original and the revision live in Timeline with explicit links between them. Carrier audits get the full revision history, not a quietly-edited original.
Delegated-authority audits expect to see (a) that operational data is captured at source, (b) that bordereaux are produced from that data without manual transformation, and (c) that submission and acknowledgement events are logged. SwiftCase's bordereaux pipeline + Timeline produces all three by default. Auditors typically work through the audit pack we generate from Timeline.
SwiftCase runs at insurer scale — over 11.8 million cases on a single tenant, 384 active workflows including bordereaux generation. 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.
