Build a reinsurance treaty bordereau generation and submission pipeline for facultative and treaty accounts
domain: insurance-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Query the policy admin system for all in-force policies subject to treaty cession, filtering by treaty number, inception date range, and cession basis
Aggregate cession data per risk: policy number, insured name, risk address, line of business, TIV, premium, cession percentage, and reinsurer share
Format the bordereau according to the reinsurer's agreed template (typically a structured spreadsheet or delimited file with mandatory columns)
Calculate treaty-level summary statistics: total ceded premium, total ceded TIV, number of risks, and any profit commission adjustments
Transmit the bordereau to the reinsurer's bordereau portal or via agreed SFTP channel with appropriate encryption
Reconcile the reinsurer's acknowledgment or settlement statement against the submitted bordereau and flag discrepancies
Known gotchas
Cession calculations must account for mid-term endorsements, cancellations, and reinstatements; using inception-to-date earned premium rather than written premium is a common source of bordereau disputes
Some treaty agreements require separate bordereaux for new business, renewals, and cancellations; verify the treaty wording before building a combined output
Reinsurer-specific column naming and date format requirements vary; a generic template engine that maps internal field names to reinsurer templates reduces maintenance burden
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?