Bordereaux management that maps every delegate’s file, checks every row and explains every rejection
Every bordereau in your layout on arrival, each rejected row with its reason.
See one case, screen by screen ↓Software that takes the risk, premium and claims bordereaux your MGAs and coverholders send, turns each one into a single standard layout and checks it against the binding authority agreement. Bordereaux Management adds agents that read any delegate’s spreadsheet, map it from that delegate’s remembered mapping, check every row and draft the return of rejected rows.
How to choose AI solutions for insurance →
Updated
Every MGA and coverholder sends its risk and premium bordereau in its own columns, its own codes and its own date formats — often late, often with rows missing. Before a single row can be checked against the binder, a bordereaux analyst re-maps the file by hand, usually the same file she mapped last month.
The checking itself then turns into sampling, because there are not enough hours to test every row for territory, limits, commission, tax, dates and duplicates. And when a delegate renames a column without saying so, the check that read it quietly stops working: a location over the per-location limit loads with no warning, and the head of delegated authority finds out at audit.
Estimated split for one analyst loading a month’s risk and premium bordereaux, by hand and with the solution.
Six agents read, map, check and return every delegate's file; the analyst confirms changes and the DA manager decides breaches.
Pellworth Specialty Insurance Company delegates to 14 MGAs and coverholders. Northmarch Underwriting’s September risk and premium bordereau arrived on Friday, six days early. Here is what happens next, screen by screen, in the working solution.
Hannah opens the mapper on NM_Sep2026_RiskPremium.xlsx: 1,284 rows, 38 columns, $6,419,448 gross premium under binder B0841NM26PRP. On Friday the file reader found the header on row 3 and tied gross premium to the cover sheet; the column mapper placed 36 of 38 columns from Northmarch’s August mapping. Two columns wait on her.
36 columns remembered · 1 renamed · 1 new · 18 rows rejected so far · 1,266 accepted
“TIV” is gone. “Total Insured Value (USD)” sits in its place — same position, numbers, no blanks, a median of $882,000 against August’s $874,000. The mapper scores the profile match at 0.97 and proposes the rename to Sum insured — total for the location. It does not apply it.
“TIV”, mapped every month since February, is missing. “Total Insured Value (USD)” sits in its place.
Below the mapping, a strip shows all 1,284 rows against 12 binder checks. Ten have run on every row: 18 rows rejected, 41 warnings. Click a mark to open the row — Row 643, Hill Country Plaza Ltd in Lafayette, LA, passes everything that has run, with the per-location limit and windstorm deductible checks waiting on a confirm.
Per-location limit: “waits on the rename”. Windstorm deductible: “waits on new column”.
Hannah clicks Confirm. The column lands on Sum insured — total for the location and is remembered for October. The per-location limit check runs straight away on all 1,284 rows and finds five locations above $5,000,000 with no referral approval on file.
“Per-location limit run on 1,284 rows: 5 locations above $5,000,000 with no referral — rejected and referred to Graham Tulley.”
“Wind/Hail Ded %” has never been sent before. Its nearest field, Deductible — windstorm %, matches at 0.88 — below 0.90, so the mapper waited for her. She maps it, the windstorm deductible check runs, and every coastal location meets the 2% minimum. All 38 columns are placed and the mapping is saved for October.
23 of 1,284 rows go back — $219,897 of gross premium held back. Seven are in Florida, outside the binder’s territory of TX, LA, OK, AR and MS; five are over the per-location limit; four were already on the August bordereau; four take commission above 22.5%; three are effective in October. Each row says why in a sentence and cites its binder clause, or the earlier bordereau it repeats.
“Commission taken at 25%; the binder allows 22.5% — $71.88 over-deducted.” Binder §7.1
The return writer drafts the note to Megan Castell at Northmarch: the 23 rows grouped by reason, each clause cited, the column changes explained, and NM_Sep2026_returned_rows.xlsx attached with the original values. Under binder §9.2 corrections are due on the October bordereau or within 10 business days, whichever is sooner. Hannah reads it and sends it.
The return writer drafts; it never sends and never corrects the delegate’s data.
Twelve of the rows are not just wrong data — the Florida risks and the over-limit locations are outside Northmarch’s authority. Territory and limit failures are both returned and referred to Graham Tulley as possible breaches. Under §4.1 Pellworth must hear within 5 business days; Graham refers them to underwriting or asks Northmarch for referral evidence.
The accepted rows sit in the Coverholder Reporting Standards v5.2 layout — the same layout for all 14 delegates — with all 39 fields placed: 1,261 accepted, 41 with warnings, 23 rejected. Gross premium $6,199,551.00, commission $1,394,902.15, net to Pellworth $4,804,648.85, ready to send to oversight and finance.
Northmarch’s September goes on its record: six days early, 98.2% of rows clean, 12 of its last 12 bordereaux on time. Sable Creek Transport is the other story — late on 10 of its last 11, by seven days on average, and two days late today, chased at 08:00.
Graham Tulley is told when a delegate is late three months running.
The same September file, seen by the four people who carry it — what their month looked like, and what it looks like now.
Six agents read, map, check and return every delegate's file; the analyst confirms changes and the DA manager decides breaches.
Opens each delegate’s bordereau — any spreadsheet or CSV, any sheet — finds the header row, counts the rows and ties the totals to the cover sheet.
Places each column on the standard layout from the delegate’s remembered mapping, and spots renamed, new, moved and dropped columns by their values, not just their names.
Turns each delegate’s dates, amounts, codes and yes/no flags into the standard formats and code lists.
Runs every row against the binder in force on its inception date: reference, month, territory, class, limits, commission, tax, dates, duplicates and deductibles.
Drafts the return to the delegate: the rows grouped by reason, each with its clause, and the spreadsheet of returned rows.
Scores each delegate every month on timeliness and the share of clean rows, keeps the 12-month record, and tells the DA manager when a delegate is late three months running or clean rows fall below 97%.
Confirm changes, decide breaches. The agents propose; a named person decides.
Ask about a delegate’s file, a rejected row, a check or who is late. Every answer cites the file, the binder, the mapping record or an earlier bordereau.
What changed in Northmarch’s file this month?
Three things. Column 22 “TIV” is now “Total Insured Value (USD)” — same position, same values, profile match 0.97 against August. A new column 24 “Wind/Hail Ded %” arrived; its nearest field is Deductible — windstorm %. And “Agent Code” is gone; it is optional, so Producer code is left blank. Until you confirm the rename, the per-location limit check cannot run.
Why were the Florida rows rejected?
Seven locations — Pensacola, Destin, Panama City, Fort Walton Beach, Milton, Navarre and Crestview — are in Florida. The binder only lets Northmarch bind in Texas, Louisiana, Oklahoma, Arkansas and Mississippi. They are rejected back to Northmarch and, because a risk bound outside the territory is a breach of authority, also referred to Graham Tulley, who must hear within 5 business days.
Is Northmarch taking the right commission?
On 1,280 of 1,284 rows, yes — 22.5% of gross premium. Four rows take more: three at 25% and one at 27.5%, $529.41 deducted beyond the binder in all. Those rows are rejected with the amount, and the premium due to Pellworth is held at the binder rate.
Which delegates are late this month?
One. Sable Creek Transport was due Saturday 10 October under its 10-day clause and has not sent its file; it was chased this morning at 08:00. It was late on 10 of its last 11 bordereaux, by seven days on average. Quillon Professional Risks is not in yet but is not due until Thursday.
13 screens from the working solution, on its sample data. Pick one to see it large.
What Pellworth’s delegated authority team configures. Changes are drafts until the head of delegated authority approves them.
| Setting | Default | Choose from |
|---|---|---|
| Apply a remembered mapping on its own at | 0.90 | Any match threshold |
| Spot a renamed column at | 0.95 | Any match threshold |
| A rename always needs a person | On | On · Off |
| Layout delegates are mapped to | Coverholder Reporting Standards v5.2 | Coverholder Reporting Standards v5.2 · Pellworth carrier template |
| Optional fields left blank, not guessed | On | On · Off |
| Delegate correction deadline | 10 business days | The sooner of the next bordereau or this |
| Rows outside authority go to | Graham Tulley | Any named person |
| Bordereau due | 15 days after month end | Unless the binder says otherwise |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample delegate data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (SwiftCase, 2026 — 3–5 working days a month on bordereaux for a mid-sized MGA). Lloyd’s Y5311 Conditions of Trade for Delegated Authorities Data. People, companies and insureds named on this page are fictional — characters and sample data in the working solution.
Software that takes the risk, premium and claims bordereaux your MGAs and coverholders send, turns each one into a single standard layout and checks it against the binding authority agreement. Bordereaux Management adds agents that read any delegate’s spreadsheet, map it from that delegate’s remembered mapping, check every row and draft the return of rejected rows.
The column mapper compares the missing column with the new one by position, type, range, blanks and median. When they match — “TIV” and “Total Insured Value (USD)” at 0.97 in the demo — it proposes the rename with that evidence. One confirm places it, remembers it for next month and runs the check that depended on it.
Every row. The binder checker runs each check on every row of every file, against the binder in force on the row’s inception date: territory, class, per-location limit, commission, surplus lines tax, dates, duplicates against earlier bordereaux, deductibles and required fields.
Yes. Every delegate’s file can be mapped to Coverholder Reporting Standards v5.2 or to your own carrier template — it is a setting. Lloyd’s conditions of trade for delegated authorities data expect risk, premium and claims data to meet those standards.
They are not loaded. Each goes back to the delegate with its reason and binder clause, grouped by reason in a drafted note with the returned rows attached in their original values. The analyst reads and sends it, and the correction deadline comes from the binder.
No. Territory and limit failures are referred to the head of delegated authority as possible breaches, and he decides. The agents never apply a renamed or new column without the analyst, never send a return and never guess a value.
Yes. The match needed to apply a remembered mapping or offer a rename, the standard layout, the correction deadline, who receives breach referrals, when bordereaux are due and late reminders are all settings, and changes are drafts until approved.
The Agentic Solution Engine builds and deploys it from your requirements — your binders, standard layout and a month of your delegates’ files — and it goes live once every quality gate has passed. We will walk you through it on your own bordereaux first.
Breaches flagged the day the risk is bound, not months later at audit.
1-min demoBinder Guidelines SearchFewer needless referrals, and every answer shows the clause that decides it.
1-min demoPremium Bordereaux ReconciliationEvery difference between bordereau and cash given a cause before settlement.
1-min demoWe’ll run Bordereaux Management on a month of your own delegates’ files.