One platform for the whole bordereau lifecycle.

From the file a coverholder sends to the data a carrier books, with the automation, integration points and infrastructure that enterprise delegated authority needs. Every capability says whether it is available today, in development, or planned.

Upload first. Map once. Validate every time.

A bordereau goes in as it arrives, in the sender's own layout. Isovara asks only for what it needs to process that file and keeps the answer with the Feed, so the next delivery from the same coverholder needs nothing.
  • Available

    Flexible intake. CSV in any column order with any header names; Excel is planned.

  • Available

    Feeds, Templates and Core Configurations. Your standard fields, and a saved mapping per Feed; one source column can feed several fields.

  • Available

    Readiness and next actions. A file that cannot run yet says why (Mapping required, Context required) and who does what next.

  • In development

    Validation runs. Required fields, formats, dates, currencies and reconciling totals on every delivery, each issue naming its rows.

  • Planned

    Issue-led correction. Fix from the list as a new revision, revalidated; or send the list back to the sender.

  • Planned

    High-volume processing. Streamed upload to about 100 MB per file, processed by a separate worker.

  • In development

    History and traceability. Source versions, configuration versions, runs and actors kept per submission.

Feed mapping · Property premium · Halden Underwriting

  • Assured NameInsured name
  • Gross PremGross written premium
  • InceptInception date
  • Pol RefPolicy reference

Seen from other coverholders:InsuredPolicyholderGWP

24 of 24 columns mapped · saved as revision 3

Issues in plain words, with the rows they affect

Blocking issues hold a file. Warnings let it through with a flag. Every issue says what is wrong, which rows, and what to do, so the person who can fix it does not have to open the spreadsheet to find out.

Gross written premium > 0 when Transaction type = New

March 2026 premium bordereau In development

Halden Underwriting · B0999XYZ2026001 · run 2 of 2

Issues found
Rows
2,418
Passed
2,401
Need attention
17
  • Blocking12 rows need a policy numberRows 118–129
  • Warning3 inception dates fall outside March 20263 rows
  • Warning2 premiums are not in GBP2 rows
  • PassedPremium total reconciles to the binder summary: £1,248,400.00

Automation that proposes. People who approve.

The repetitive parts of bordereaux work are suggested by the platform and approved by a person. Every suggestion shows its reasoning; every accepted change is a revision that is revalidated. Nothing changes your data on its own.
  • Planned

    AI-assisted onboarding and schema discovery. A new Feed’s columns suggested from the file and your Core Configuration.

  • Planned

    Intelligent mapping suggestions. Renamed or moved columns matched to the saved mapping, with confidence shown.

  • Planned

    Automated anomaly detection. Movements that break a Feed’s pattern, run to run, flagged before they reach a report.

  • Planned

    Natural-language data exploration. Ask a question of validated data in plain words.

  • Planned

    Intelligent workflow recommendations. The next action suggested from what usually resolves this kind of issue.

  • Planned

    Human-in-the-loop approvals. Accept, reject, or edit a suggestion; recorded with who, when and why.

Suggested fixPlanned

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.

AnomalyPlanned

Claims monthly · Marlow & Finch · March 2026

Paid indemnity is 4.1× the six-month average for this Feed (£312,900.00 vs £76,400.00). 3 claims account for 88% of the movement. Flagged for a check; the file is not held.

API-first, so Isovara fits the systems you already run.

Everything the interface does will be reachable from your own code: submit files, read results, subscribe to events, and connect the policy administration, claims and data systems that bordereaux come from and go to.

Senders and sources

Email mailboxAttachments picked up on the due date
SFTP dropCoverholder or TPA folders
Policy admin / claims systemExport pulled over API
Manual uploadIn the interface, today

Isovara

ConnectorsEmail, SFTP, API intake · Planned
REST APISubmissions, Feeds, results · Planned
Webhooks and eventssubmission.validated, issue.raised · Planned
SDKsTyped clients, local testing · Planned

Onward

Carrier data teamStandard extract
Data warehouseValidated tables
Market reportingIn the shape each expects

What exists for engineers today

Built

The data model is small and named in plain words. A Channel is a business relationship (an MGA and a carrier). A Feed is one recurring delivery on that relationship (Halden's monthly property premium file). ACore Configuration is your standard set of fields. A Template is the saved mapping from a Feed's columns to that standard. A Submission is one file received, with its versions, runs and actors.

A fictional sample CSV and the mapping it needs are available on request, so your team can see the shape before any API exists.

  • Planned

    Integration endpoints and webhooks. Submit a file, query a result, get told when something changes.

  • Planned

    Event-driven workflows. React to a validated submission or a raised issue in your own systems.

  • Planned

    Extensible processing. Your own validation rules and transformations, versioned with the Core Configuration.

  • Planned

    Existing insurance systems. Policy administration, claims and broking platforms as sources and destinations.

Isolated by design, scalable by default.

A control plane that knows which organisation you are and routes you to your own data plane. Nothing is shared between customers below that line.
  • In development

    Multi-tenant architecture. A control plane with authorised routing to each tenant’s own PostgreSQL database.

  • In development

    Isolated customer data environments. A database and a file container per organisation; workspaces as prefixes within it.

  • Planned

    Scalable ingestion and processing. A separate worker for validation runs; streamed uploads to about 100 MB per file.

  • Available

    Configurable workflows. Channels, Feeds, Templates and Core Configurations set per organisation.

  • Planned

    Enterprise deployment flexibility. Selectable UK and EU regions, dedicated infrastructure, or a customer-owned database.

Control planeSign-in, organisations, routing

  • Halden Underwriting

    DatabasePostgreSQL
    File containerBlob storage

  • Marlow & Finch

    DatabasePostgreSQL
    File containerBlob storage

  • Tern & Weald MGA

    DatabasePostgreSQL
    File containerBlob storage
In developmentTarget architecture. Fictional organisations. Dedicated servers and customer-owned databases are planned tiers.

For coverholders and TPAs

Been asked to send your bordereaux through Isovara?

Do I need an account?
Only if the MGA or carrier invites you. Then you sign in with your email or your company account; nothing to install.
What do I send?
The same file you send today, in your own layout. Isovara maps it; you do not reformat it.
Does it cost me anything?
No. The organisation that invited you holds the subscription.
What happens to my file?
It is kept, unchanged, in the inviting organisation’s own store; if something needs fixing you get a short list, not the whole file back.

See it on one of your bordereaux.

Thirty minutes, your file shape, fictional data. Design partners get early access and a say in what gets built next.

Request early accessSee the roadmap