For MGAs

Report once to every carrier, from the data you already have.

Your bordereaux and binders go into Cork as they stand. Cork checks every policy against its binder, reports to each carrier in its own format, and answers their queries from the record.

See the flowGet in touch

The month-end today

  1. The same data, rebuilt for every carrier. Each carrier wants its bordereau in its own layout, with its own codes.
  2. Errors found weeks late. Few teams check every policy against the binder, so a problem surfaces when the carrier queries it.
  3. Queries answered by hand. Each carrier query means digging through filings, binders and spreadsheets to explain one figure.

With Cork, you send your data once. Cork checks it, reports it to every carrier and answers their queries from the same record.

The flow

Your month-end, without the spreadsheet work.

1 · Data in, every way

Send your data as it is, from wherever it lives.

By upload, through your AI or straight from your own systems. Each way files the same bordereau, runs the same checks and waits for your signature.

Upload

Drop the file

Drag your policy system's export, Excel or CSV, onto Bordereaux imports. One file can carry business for several carriers, and each policy goes to its carrier.

The bordereau drop zone
Your AI

Ask in plain words

Hand the file to the AI assistant your team already uses. It connects to Cork through MCP, files the bordereau and brings back what needs your eye.

File this month's bordereau for Northgate.

Done. 41 policies read with your saved mapping. 39 are ready to sign, and 2 need a look: HUA-WH-2026-0203 is a flood risk under a fire-only binder.

Your systems

Send it automatically

Your policy system sends its data straight to Cork through the Cork API: the month-end export, or each policy as it is written. Your IT team connects it once.

  • Month-end export, on a schedule
  • Each policy as it is bound
  • Each claim as it is notified

2 · Connected to the binder

Show your carrier every policy sits within its binder

Drop your binder documents for all your carriers at once. Cork reads each term with its clause, and asks only what the documents leave open.

Each policy you bind, in a bordereau or one at a time, is then checked against the binder in force on its date. A policy outside it is refused, with the clause named.

3 · Your whole book

Know where you stand at any moment, and so does your carrier.

Every binder, policy, endorsement and claim you file lands in one book: capacity used, limits, claims and premium. Each carrier sees the same figures for its own business.

Bound policies214
Written premiumUSD 1.28M
Open claims7
Outstanding reservesUSD 520K

Capacity used under each binder

Northgate Mutual
68%USD 8.2M of 12M
Kingsbridge Insurance
41%USD 2.5M of 6M
Orwell General
87%USD 4.4M of 5M

Limits by peril

USD 9Mtotal
  • Flood6.1M
  • Fire2.0M
  • Windstorm0.9M

Claims

HUA-2026-0007 · floodReservedUSD 320K
HUA-WH-2026-0201 · floodSettledUSD 85K
HUA-2026-0012 · fireNotified—

Premium by month

JanFebMarApr
Each carrier sees the same figures for the business written under its binders.

4 · Carrier reporting

Every carrier gets its report, in its format, with no rework.

Cork builds each carrier's format once, from its template or a report it accepted before. Every period after that, Cork fills it from your book.

Cork builds the format

Give Cork the carrier's template, its instructions or a report it accepted before. Cork works out each column, where its value comes from and the carrier's codes, and shows you the source of each choice. You approve the format once.

Cork finds the gaps

Before a report goes out, Cork lists anything the carrier needs that your data lacks, such as a postcode or a peril code. Fill it in on the policy, and every carrier's report picks it up.

Cork tracks each report

Each report goes out as Excel, CSV or JSON with a reference. Cork records whether the carrier accepted or queried it, and keeps each corrected version with its reason.

Monthly risk bordereauFormat version 2 · applies from 1 April
ColumnFilled fromSource
CertificatePolicy referenceTemplate · column A
PostcodeRisk postcodeInstructions · page 2
Peril codePeril, in the carrier's code listBinder · schedule 3
Sum insuredCoverage limitAccepted example · March
Gross premiumWritten premium, rounded half upBinder · clause 7.2
  1. Revision 1 released in CorkApril · 214 policies · USD 1,284,500
  2. Queried by the carrierPostcode missing on 2 policies
  3. Revision 2 replaces itPostcodes completed on the policies
  4. AcceptedRevision 2 is the report of record

5 · Reconciliation requests

Answer carrier queries without the digging

Drop a carrier's email or statement into Cork. Cork splits it into points and checks each one against your filings, binders and statements.

Each point gets an answer with its source, and any fix on your side is prepared for your approval. You review the drafted reply and send it.

6 · Balances

Settle each month with each carrier in one payment

Every premium and commission is an amount owed, tied to its policy and its due date. Cork nets them against each other, so one statement and one payment settle the month with each carrier.

Each signed filing stays on record with its files and mapping, so you can always show what you filed and when.

AI integration

Hand the routine work to your AI.

Connect the AI tool your team already uses. It files the monthly bordereau, prepares each carrier's report and works through the actions waiting on you. It sees only what your firm sees.

  • Claude
  • OpenAI Codex
  • Cursor
  • VS Code
  • Any tool that supports MCP
You approve your AI prepares each change, and a person on your team approves itOr it acts your AI makes routine changes itself
Harbour Underwriting Agency · you approve

Get in touch

See Cork run on your own bordereaux and binders.

Contact us