Bordereau MGA Meridiana — April 2026. 2,400 lines processed. Reconciliation complete. 2,350 lines compliant (97.9%). Anomalies: 40 premium lines with variance above threshold (total €34,000 excess in favour of the MGA). 8 claim lines absent from management system. 2 duplicate premium lines.
AGENT · BORDEREAU RECONCILIATION
Bordereaux reconciled with anomalies already highlighted.
Bordereau Reconciliation reads the periodic bordereaux from the company's MGAs and brokers, reconciles premiums and claims against internal management systems, identifies anomalies and variances, and prepares the summary for the technical accounting team. Every decision is traced for IVASS audit.
Bordereau Reconciliation at work.
For the 40 variance lines, prepare the clarification request to the MGA.
Request ready with the list of the 40 lines, bordereau vs management system amounts, internal record reference. For the 8 claim lines I opened a check with the MGA's claims manager. For the 2 duplicates: notification for correction. The full event is in the audit registry for IVASS.
Why it exists.
Insurance companies working with MGAs or delegated brokers receive periodic bordereaux that summarise premiums collected and claims settled on the company's behalf. Reconciliation is a large-scale technical accounting job: every line must be compared against internal management systems, anomalies identified, material variances managed with the counterparty.
How it reconciles each bordereau.
Bordereau Reconciliation activates on receipt of each bordereau. It extracts structured data from the specific MGA or broker format, reconciles line by line against the company's management system, identifies anomalies (unreconcilable premiums, claims with differing amounts, duplicate lines, missing lines), and prepares the summary for the team with the variance detail.
The decision stays with the accounting team.
The decision on how to manage variances — clarification request to the MGA, acceptance within tolerance, contractual escalation — stays with the technical accounting team. Each MGA or broker format requires a dedicated extraction schema, configured during the project by the Exelab team.
Who it serves and where it applies.
Head of technical accounting
Reclaims the time of manual reconciliation, one of the most consumed jobs for the team. Capacity focuses on managing anomalies and contractual decisions, not on line-by-line reconciliation of thousands of entries.
fnol.receive 09:14:22 ALLOW
triage.classify 09:14:25 ALLOW
idd.check 09:14:31 WARN
liquidation.propose 09:15:02 ALLOW
SELECT * FROM audit_log WHERE claim_id = '2024-0847'
Head of MGA relationships
Sees the quality of bordereaux received in a structured way — frequency of anomalies, type of errors per MGA. Contractual relationship management moves from anecdotal perception to structured evidence.
Claim type Auto liability
Severity Medium
Adjuster Dr. Ferrari · Northeast
Initial reserve € 4,200
Routed ✓
Compliance manager
Has an inspectable trace of the reconciliation for IVASS audit on the quality of MGA relationships. The registry is queryable with a standard SQL client and available at the first audit.
fnol.receive 09:14:22 ALLOW
triage.classify 09:14:25 ALLOW
idd.check 09:14:31 WARN
liquidation.propose 09:15:02 ALLOW
SELECT * FROM audit_log WHERE claim_id = '2024-0847'
A concrete example.
An MGA sends the April bordereau.
For an insurance company with 12 MGA partners sending monthly bordereaux, the agent is scheduled on the trigger of each new bordereau arriving. An MGA sends the April bordereau on the first Monday of May. The agent receives the bordereau in the MGA's proprietary CSV format and extracts 2,400 structured lines.
97% compliant, 50 anomalous lines identified.
It reconciles against the company's management system. Identifies the anomalies: 1,760 premium lines reconciled without material variances (97%). 40 premium lines with an amount variance above the 1% tolerance threshold (total €34,000 excess in favour of the MGA). 8 claim lines not present in the management system. 2 duplicate premium lines.
The manager decides case by case.
The summary reaches the head of technical accounting on the work channel with the detail of the 50 anomalous lines. For the 40 variance lines, the manager triggers the clarification request to the MGA with the summary already prepared. For the 8 claim lines, triggers the check with the claims manager. For the 2 duplicates, notifies the MGA for correction. The event stays in the audit registry for IVASS.
Configuration and technical resources.
The Bordereau Reconciliation rules are declarative. The company's technical accounting team defines in a readable format the extraction schemas for each MGA (CSV format, column mapping), the tolerance thresholds for variances, the pattern anomaly rules, and the summary format. The rules live in the company's repository, versioned, validated at agent startup.
- Language
- TypeScript (Node.js)
- LLM model
- customer's choice: Anthropic, OpenAI, Mistral, open source models hosted internally, AWS Bedrock for a private model
- Built-in controls used
- pii-detector, credential-detector, tool-param-validator
- Native intake channels
- OpenAI-compatible HTTP (upload webhook)
- Corporate email as intake channel
- integration delivered during the project
- Company management system integration
- dedicated adapter delivered during the project
- Extraction schemas for MGAs/brokers
- declarative, one per counterparty, versioned — each new format requires configuration during the project
- Memory
- persistent per instance, pgvector + PostgreSQL FTS on historical bordereau patterns
- Registry
- immutable, queryable with a standard SQL client (IVASS audit inspectable)
Frequently asked questions about the agent.
Every MGA sends bordereaux in their own format. The extraction rules are declarative, configured per MGA. When a new MGA enters a contractual relationship with the company, the team configures a new extraction schema in the repository. The onboarding curve for a new MGA is measured in days of configuration.
No. The agent identifies the anomalies and prepares the detail for the head of technical accounting. The decision on how to handle them — clarification request, acceptance within tolerance, contractual escalation — stays with the manager according to the customer's procedures and contracts.
Systematic anomaly patterns — an MGA with an error rate above threshold across multiple consecutive months — are identified by the agent in the bordereau summary. The head of MGA relationships decides whether to trigger contractual procedures (formal warning, authority suspension, contract termination) according to the company's rules.
The typical pattern for Bordereau Reconciliation is 10-14 weeks. Discovery 2 weeks, configuration of extraction schemas for the main MGAs 3-5 weeks, company management system integration 3-4 weeks, hand-off to the technical accounting team 1-2 weeks.
From a 30-minute conversation to the squad in production.
A 30-45 minute conversation to understand how Bordereau Reconciliation would configure to the company's structure. How many MGAs, what monthly bordereau volume, which management system.