AI-assisted mapping
Column headers and sample values are matched against the canonical schema for your bordereaux kind, with a confidence score per proposed mapping.
Bordereaux processing
Your bordereaux intake, normalized in minutes — with a human sign-off before anything commits.
Upload premium or claims bordereaux from your brokers as CSV or XLSX. InsureGuardAI proposes a column mapping, you approve or adjust it, and the records are validated and normalized into a clean, tenant-scoped format you can export.
How mapping works
Header names vary by broker — "Premium" one week, "Gross Premium (EUR)" the next. InsureGuardAI reads your headers and a sample row, then proposes a mapping using Workers AI (Llama 3.1 8B) with a confidence score per column. If AI mapping is unavailable, a deterministic fuzzy-match fallback proposes mappings from known field aliases instead — a mapping suggestion is always produced.
Human sign-off
No mapping is applied without explicit confirmation. Every canonical field is shown with sample values so the reviewer knows exactly what the system will normalize before it runs.
Mappings remember your brokers
Once confirmed, a mapping is saved per counterparty and bordereaux kind, so the next file from the same broker starts from your last approved mapping.
Validation and export
Once a mapping is confirmed, every row is normalized and validated against the canonical schema — required fields, date formats, and currency codes are checked row by row. Issues are surfaced in full, never truncated, so your team can fix the source file or decide how to handle each row. Normalized records export as CSV on demand.
Canonical fields
Two bordereaux kinds are supported today, each with its own canonical schema.
Premium bordereaux
- policy_number required
Policy or contract reference number
- insured_name required
Name of the insured party
- inception_date required
Policy start date
- gross_premium required
Gross premium amount
- currency required
ISO 4217 currency code
- commission optional
Broker commission amount
Claims bordereaux
- claim_number required
Claim reference number
- policy_number required
Policy or contract reference number
- loss_date required
Date of loss
- paid_amount required
Amount already paid
- currency required
ISO 4217 currency code
- reserved_amount optional
Outstanding reserve amount
Where this fits
Bordereaux intake runs in the same InsureGuardAI workspace as sanctions and PEP screening, on the shared Spot Suite identity plane. Bought through the Spot Suite marketplace; customer workspaces run on InsureGuardAI hostnames.