Upload a bordereau as it arrives, map it to your standard once, and validate every delivery the same way, with the evidence an auditor will ask for.
Bordereaux carry the premium, claims and exposure of a binder from the people who write the business to the people who carry the risk. The files are critical and the process is still manual.
Forty binders, forty layouts. "Insured", "Assured Name" and "Policyholder" are the same column, and someone reconciles them by hand every month.
A missing policy number surfaces in the carrier’s report, weeks after the file arrived, and the fix lives in an email thread nobody can audit.
The original file is on a shared drive, the corrected one in someone’s downloads, the rules in a macro. Explaining a figure means archaeology.
Spreadsheets, generic ETL and legacy BDX portals each solve a corner of the job and leave the people in the middle to glue them together.
The file arrives as it is
Available is in the product today. In development is being built. Planned is where we are going, and we would like design partners to shape it.
A CSV in the sender's own layout goes in before anything is set up. Map each source column to your Core Configuration once; the Feed keeps it for every later delivery, and one source column can feed several fields.
A file that cannot be processed yet says why (Mapping required, Context required) and who does what next.
Fix from the list, not the whole file. Every change is a revision that is revalidated.
Organisations and access
Invite your team, set admin and member roles, connect your company sign-in.
Database per tenant
Each organisation’s data in its own database and file store behind a separate control plane.
APIs, webhooks and connectors
Submit and subscribe from your systems; files picked up from mailboxes and SFTP.
Required fields, formats, dates, currencies and reconciling totals, with each issue naming the rows it affects.
Fictional data
Source versions, configuration versions, runs and actors kept together per submission, so a figure can be traced back later.
2 premiums are not in GBP · POL-2026-008242, POL-2026-008251
Convert from USD at the binder's agreed rate (1.27): $14,200.00 → £11,181.10. The same pattern was accepted on 4 earlier files from this Feed.
Reviewed by a person before anything changes. Recorded with who, when and why.
Security and trust
Your organisation’s data in its own database and its own file container, never a shared table.
Sign-in and organisation membership already live apart from customer data; routing each request to its tenant’s own database is being built.
Email or your company’s identity provider through a brokered sign-in; one SSO connection per organisation.
Bordereaux and business data in Azure UK South; sign-in identity data in Microsoft’s Europe geography.
TLS on every connection; Azure-managed encryption for databases and file storage; secrets in Key Vault with managed identities.
Every submission keeps its source versions, runs and actors; an exportable audit record is being added.
NowFoundation
Intake, Feeds and mappings, readiness checks and sign-in are available; validation runs, traceability and tenant isolation are in development.
NextAutomation and integration
AI-assisted mapping, email, SFTP and API intake, developer APIs and webhooks, enterprise identity, an exportable audit trail.
LaterIntelligent insurance infrastructure
Anomaly detection, reconciliation, natural-language analytics, SDKs, selectable residency and dedicated deployments, delivery onward.
Early stage, on purpose. We are choosing a small number of MGAs, coverholders and insurers to shape Isovara around their real monthly files. Design partners get early access, a direct line to the team, and a say in what gets built next.