Missing policy information
A blank policy number or premium leaves reviewers without the context needed to investigate a row.
Bordereaux data quality for insurance teams
Better data starts with better validation.
Bordex helps insurance teams identify missing information, inconsistencies and business-rule exceptions in their bordereaux data before those issues affect downstream processes.
Built for practical review by insurance operations and data teams.
VALIDATION SUMMARY
Synthetic example
Monthly bordereaux
Records checked124
Findings4
Affected rows3
Duplicate policyPolicy BRX-0048 · row 49Error
Premium is not numericPolicy BRX-0072 · row 73Error
Currency uses lowercasePolicy BRX-0091 · row 92Warning
Designed around insurance bordereaux
CSV · XLSX · XLS
Excel exception reports
The problem
Small data issues can create a lot of follow-up.
Bordereaux often pass between insurers, underwriting managers and service teams. Missing values or inconsistent records can be hard to spot in a large spreadsheet and slow down the next review.
Repeated records
A policy can appear more than once. The right duplicate key depends on the selected profile and the data available.
Values that do not line up
Dates out of sequence, non-numeric premiums or unexpected currency formats can be easy to miss by eye.
Configured rules to check
Where an insurer provides product or binder rules, Bordex can check rows against those configured relationships.
How Bordex works
From spreadsheet to clear next steps.
A focused workflow that helps teams find and review issues in the bordereaux they receive.
- 1
Upload a bordereaux
Work with a CSV, Excel workbook or legacy XLS file. Policy identifiers are handled as text where the source preserves them.
- 2
Choose a validation profile
Bordex checks the file structure and values using the selected profile, including the insurer rules configured for that profile.
- 3
Review an Excel report
Inspect the summary, rule breakdown, exceptions and original data, then investigate the relevant rows with your team.
What it does
Useful checks, presented for investigation.
Bordex is a data-quality aid. Teams review findings in context and decide what needs correction.
Explore the synthetic demonstrationFlexible validation profiles
Select the available profile, such as Bordex Default or UMA1, to apply its configured checks.
Automated data-quality checks
Find missing values, duplicate keys, date problems, numeric issues, currency problems and structural gaps.
Insurer-configured rules
Where profile configuration is supplied, check numeric thresholds and binder or product relationships.
Clear Excel exception reports
Use four sheets: Summary, Rule Breakdown, Exceptions and OriginalData.
Validation history
Review completed validation runs and download their available reports from the authenticated application.
Who it is for
Made for teams that work with insurance data.
Life insurers
Review incoming policy and premium bordereaux before downstream use.
Funeral insurers
Surface missing information and inconsistent records in policy data.
Underwriting managers
Apply available programme profiles and configured binder or product checks.
Insurance operations
Give reviewers a structured exception list with links back to source rows.
Actuarial and data-quality teams
Investigate data quality issues before relying on a bordereaux for analysis.
Example results
Each finding points reviewers back to the data.
These fictional examples show the kinds of issues a selected profile can report. A warning calls for review; it does not by itself mean a policy is incorrect.
| Row | Field | Finding | Severity |
|---|---|---|---|
| 18 | PolicyNumber | Policy number appears more than once under this profile. | Error |
| 42 | Premium | Value could not be read as a number. | Error |
| 73 | Currency | Currency code contains lowercase letters. | Warning |
| 91 | ExpiryDate | Date sequence needs investigation. | Warning |
Synthetic examples only. Findings depend on the selected profile and available fields.
Questions and answers
Before you book a demonstration.
What file formats can I use?
The application accepts CSV, XLSX and XLS files. CSV headers must be present and valid. For spreadsheet identifiers already stored as numbers, leading zeros removed by the spreadsheet cannot be recovered.
What does a validation profile do?
A profile selects the available checks and insurer-specific configuration. Bordex Default and UMA1 are included. Additional thresholds and binder or product relationships depend on configuration provided for the profile.
What is in the Excel report?
The report includes Summary, Rule Breakdown, Exceptions and OriginalData sheets. It helps a reviewer locate and investigate findings while retaining the uploaded rows for reference.
Does every rejected file appear in History?
No. History records completed validation runs. Files rejected before validation, such as malformed CSV files, are not currently recorded as validation runs.
How is the application accessed?
Real file validation and History use an API key. The public synthetic demonstration does not upload files, call validation endpoints or show stored customer reports.
How do I arrange a demonstration?
Email info@bordex.co.za to arrange a conversation about your team's bordereaux workflow.
A practical next step
See what Bordex can identify in your bordereaux.
Arrange a demonstration using fictional sample data, then discuss the checks your team needs.