OpenChainGraph Suite · ART-508 · Delegated Authority · Coverholder Oversight

Delegated Authority Bordereau Recomputation

Foots the bordereau your coverholder sent, from that same file, and tells you what it actually adds up to. Where you also paste the totals they assert, the two are compared figure by figure. Exact agreement on a footing is a weak result and this page says so, because both sides added the same column. The check that carries weight is the one underneath it: utilisation of the binding authority, measured against the limits you hold as the carrier and which are nowhere on the bordereau.

Caller supplied column mapping Carrier held limits Fixed-point money math No field list bundled

Basis: your own column mapping · standard pinned as you declare it · no field list, schema, rate or commission table is bundled or read · field set v1.0.0

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

⚠ This is the highest risk family on this site for personal data. Real bordereaux carry insured names, addresses and claim narratives, and none of them is needed here. Only the columns you name in the mapping are ever read; every other column is dropped before anything is computed or exported, and where a mapped cell is unusable it is reported by column name and type, never by its contents. Supply anonymised or synthetic data. A difference against the asserted totals means the two arithmetics disagree on the rows supplied, which can equally be an incomplete extract or a wrong mapping. It is not a finding that the coverholder misreported, and whether authority was properly exercised is a conclusion for the delegated authority audit. This page computes once when you press the button, stores nothing, runs on no schedule, and retains nothing.

Submission and the standard you are working to

The demo book below is synthetic. It is not a copy of any real coverholder file, any real book of business or any real market data standard, and it is already loaded so you can press Run without entering anything of your own. It deliberately carries an insured name column that the mapping does not name, so you can see that nothing from it reaches the result.

Period label (your input, never a clock read)

Bordereau class

Standard label (free text, pinned into the artifact)

Standard version (free text, pinned into the artifact)

Amounts are written as

Currency when no currency column is mapped

Column mapping

JSON object. Name which of YOUR columns carries each measure. Nothing is read from a column you do not name here. taxes takes a list.

Bordereau lines

JSON array, one object per line. Paste your own extract here. Columns the mapping does not name are dropped before anything is computed or exported.

[
  { "Unique Market Reference": "B1234SYN0001", "Reporting Period": "2025-07", "Risk Inception Date": "2025-07-04",
    "Settlement Currency": "GBP", "Gross Written Premium": "10000.00", "Brokerage Amount": "1000.00",
    "Coverholder Commission Amount": "1500.00", "Reinsurance Ceded Premium": "2000.00",
    "IPT Amount": "1200.00", "Levy Amount": "35.00", "Net Premium Due To Carrier": "4265.00",
    "Limit Of Liability": "500000.00", "Insured Name": "SYNTHETIC NAME, NOT MAPPED, NEVER READ" },
  { "Unique Market Reference": "B1234SYN0002", "Reporting Period": "2025-07", "Risk Inception Date": "2025-07-19",
    "Settlement Currency": "GBP", "Gross Written Premium": "2500.55", "Brokerage Amount": "250.05",
    "Coverholder Commission Amount": "375.00", "Reinsurance Ceded Premium": "0.00",
    "IPT Amount": "300.07", "Levy Amount": "8.75", "Net Premium Due To Carrier": "1566.68",
    "Limit Of Liability": "250000.00", "Insured Name": "SYNTHETIC NAME, NOT MAPPED, NEVER READ" },
  { "Unique Market Reference": "B1234SYN0003", "Reporting Period": "2025-07", "Risk Inception Date": "2025-07-22",
    "Settlement Currency": "EUR", "Gross Written Premium": "4000.00", "Brokerage Amount": "400.00",
    "Coverholder Commission Amount": "600.00", "Reinsurance Ceded Premium": "0.00",
    "IPT Amount": "0.00", "Levy Amount": "0.00", "Net Premium Due To Carrier": "3000.00",
    "Limit Of Liability": "100000.00", "Insured Name": "SYNTHETIC NAME, NOT MAPPED, NEVER READ" }
]

Binding authority, as the carrier holds it

JSON object, optional. These limits are yours and are not on the bordereau, which is exactly why they are declared here and never derived from the file under review.

Totals the coverholder asserts

JSON array, optional, one object per currency. Leave this empty and the run is reported as recompute only, which is not a pass.

Expected periods

JSON array, optional. Periods you expect to see on the file, so an absent one is reported.

Footing by currency

Authority utilisation

Limit observations

Lines outside the declared scope

Against the asserted totals

Population

Rejected inputs

Rationale

Execution Hash (SHA-256)

What this does not do

It validates conformance with no data standard, because bundling a field list would be a set of fields somebody has to keep current, and a stale one would be worse than none. It holds no rate table and no commission table, screens no sanctions list, assesses no terms of business, and performs no reserving or pricing adequacy work. It does not judge whether authority was properly exercised: it reports arithmetic and limit facts about the rows you supplied, and the audit reaches the conclusion. It does not verify that the file is complete, so a total that agrees says the rows present add up, not that the right rows are present. It makes no claim that its output is acceptable to any regulator or to Lloyd's.

See also ART-509 Securitisation Payment Waterfall Recomputation, which applies the same independent recomputation idea to a priority of payments, and the ChainGraph Hub for the rest of the suite.