How It Works
The FVA integration works in three steps:1. Automated Report Generation
Every day at midnight, an automated job generates a report listing all vehicles whose insurance coverage changed during the previous day (started, stopped, suspended, reactivated, or first payment received). The report includes:- Vehicle registration number
- Insurer code
- Broker code
- Asset id (internal reference)
- Coverage start and end dates
- Operation type (see below)
- A CSV file for internal review
- An XML file in a ZIP ready for submission to the FVA
2. Automatic Submission
Once generated, the report is automatically uploaded to the FVA API via the upload-to-connector mechanism using the FVA connector (ConnectorType.FVA in tenant configuration).
The submission uses the tenant’s secure certificate.
If the file is accepted, a scheduled job is automatically created to retrieve the integration report one hour later.
3. Report Retrieval
One hour after the file is accepted, a scheduled job automatically retrieves the integration report from the FVA API. This report lists:- Accepted vehicles: Successfully registered in the FVA file. For each accepted vehicle, the system marks the corresponding asset as declared to FVA.
- Rejections: Vehicles that were rejected, with error codes and reasons.
Operation Types
Each line in the FVA report indicates what happened to the vehicle’s coverage:C - Coverage Creation
When: A vehicle’s coverage is declared as active. This happens in two cases:- Standard: The asset started during the reporting period and at least one invoice has been paid.
- Deferred (first payment): The asset started in a previous period but its first invoice was paid during the current reporting period (see First Payment Gating below).
M - Coverage Modification
When: A policy is suspended or reactivated during the reporting period. Suspension: The policy is suspended → One M line with end date = suspension date (coverage is paused). Reactivation: The policy is reactivated → One M line with end date = empty (coverage is active again). Example: A policy is suspended on January 18th → One line with operation type M, start date = original start date, end date = 18/01. Then reactivated on January 25th → One line with operation type M, start date = original start date, end date = empty.R - Coverage Termination
When: A vehicle’s coverage was stopped during the reporting period. Example: An asset coverage stops on January 20th → One line with operation type R, end date = 20/01.Multiple Operations in the Same Period
A single vehicle can generate multiple lines in the same report if several events occur in the same period. For example:- Started and stopped → C line + R line
- Suspended and reactivated → Two M lines
First Payment Gating
The FVA declaration of a new coverage (C line) is not sent when the asset starts. Instead, it is deferred until the first invoice is paid. Why: A vehicle should only be declared as insured in the FVA once the policyholder has actually paid. This avoids declaring vehicles where the coverage was never effectively activated. How it works:- An asset starts on January 10th but no invoice has been paid yet → No C line is generated.
- The first invoice is paid on January 20th → A C line is generated in the January 20th report, with start date = January 10th (the original start date).
Related Documentation
- Reports: How reports are configured and run
- Third-Party Integrations Overview: Overview of all external system integrations

