Every source row accounted for
Each row becomes a claim or a recorded exclusion with its reason. The report shows the reconciliation.
Bordereaux intelligence
Insurance data,
finally in motion.
TrueBind takes the bordereaux your partners actually send — any layout, any number of sheets — and turns them into validated, reconciled, explainable data your team can act on.
The engine
From a messy workbook to a decision, in five steps.
- 01
Receive
Upload any workbook — one sheet or twenty. File checks run first: type, size, structure. Macros never run.
- xlsx · xlsm · xls · csv
- sender and programme recorded
- sha-256 fingerprint
- 02
Understand
Every sheet is inspected, header rows found below titles, and each source column matched to a Lloyd’s CRS field.
- alias rules first
- AI sees headers only
- confidence per column
- 03
Validate
Required data, arithmetic to total incurred, dates, currency and status — row by row, with every source row reconciled.
- paid + expenses + reserve
- no silent row loss
- currencies never mixed
- 04
Investigate
Each finding says what happened, where it came from, the evidence and why it matters. Duplicates are told apart from development.
- exact vs probable
- development ≠ duplicate
- source row for every finding
- 05
Act
Decide, assign, follow up and export — every decision written to a hash-chained audit trail.
- work queue
- claims / exceptions / audit CSV
- verifiable audit chain
The product
One file in. A health report you can defend.
Below is the report TrueBind produced for a synthetic 450-row, three-sheet test workbook we use to exercise the engine. The numbers are the engine’s real output for that file. They are not customer data.
Truebind_StressTest_450rows_replica.xlsx · synthetic test file
99/100
Grade 5 / 5 · Excellent
450 claim rows across 3 of 3 sheets were assessed and every source row is accounted for. 6 exact resubmissions found. 6 claims show development from a previous period and are not treated as duplicates.
Every source row reconciles6 exact resubmissions6 development
Total incurred · GBP£81,631,049
Paid to date£45,950,455
Paid expenses / ALAE£2,050,145
Reserve£33,630,449
high6 exact resubmissions of a claimSame claim reference, same reporting period and identical amounts — confirm each pair and ask the sender to withdraw the repeat.
info6 source columns were not mappedKept on every row and included in the claims export; not validated.
Measured in our test environment: that workbook went from upload to a rendered report in 3–5 seconds, including the mapping confirmation.
Trust
Built for people who have to defend the number.
Nothing merged automatically
Duplicates are flagged for a person to confirm, dismiss or send back. Source data is never altered.
AI reads headers, not your data
Column mapping may ask a model about header text only. Cell values are never sent. Calls are capped and time-boxed.
Tamper-evident audit trail
Every mapping, decision and export is hash-chained. Anyone can verify the chain is intact.
Isolated by organisation
Tenant isolation in the application and PostgreSQL row-level security underneath it.
Safe outputs
CSV exports are guarded against formula injection; uploads are checked before anything reads them.
Automation
From inbox to outbound, without the copy-paste.
The same audited pipeline runs for every file. Web upload and API intake work today; e-mail intake is planned and marked as such.
- 01E-mail arrivesplanned
- 02Attachment detectedplanned
- 03Workbook ingestedlive
- 04Mapping proposedlive
- 05Validatedlive
- 06Exceptions raisedlive
- 07Report builtlive
- 08Output sentlive
Bring your next bordereau.
Create an organisation, upload a workbook and walk through mapping, validation and the report yourself.