Skip to content

Resolve bordereaux gaps before the reporting handoff

A coverholder report can arrive with missing risk references or changed columns. Duvo would check the agreed reporting rules and prepare corrections for the delegated authority team.

Get a demo

Proposed application

This proposed workflow coordinates reporting data exceptions and approved correction requests. The managing agent retains reporting acceptance, authority-breach findings and formal market submissions. It does not bind risks, settle claims or reconcile premium cash.

Delegated authority bordereaux · Illustrative

Illustrative review

Bordereau DA-201 · Synthetic

Report status
Held
Missing field
Risk reference
Owner
Delegated authority team

A reported location has no risk reference, so the row cannot be linked reliably to the binding authority’s risk records.

Next action

Request risk reference: route the approved row-level query to the coverholder and keep the report open until the revised file is checked.

Refer reporting exception: send the evidence to the managing agent’s reporting owner; formal acceptance remains pending.

Delegated authority owner approval

The delegated authority owner approves each correction request or internal reporting handoff before Duvo routes it.

Illustrative workflow example
View the wider product queue

Delegated authority bordereaux · Illustrative

Proposed workflow using synthetic records.

Adds cases
Coverholder bordereau
Processes cases
Delegated authority bordereaux
Total

24

Pending

5

Postponed

2

In progress

4

Needs input

3

Failed

0

Completed

10

Add filter
Case
Case Status
Reporting gap
Scope
Decision
Exceptions
Next action
Bordereau DA-201
Needs Input
Risk ID missing
Property binder
Request risk reference
1
Bordereau DA-202
In Progress
Period conflicts
Liability binder
Check reporting period
0
Bordereau DA-203
Completed
Reply recorded
Claims report
Handoff recorded
0
Bordereau DA-204
Pending
Column changed
Property binder
Review field mapping
1
Bordereau DA-205
Postponed
Revision awaited
Risk report
Await coverholder
0

Showing 5 of 24 cases

  1. 1

    Approval

    Exceptions pause for the named owner

    Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.

  2. 2

    Reporting gap

    Reporting gap is visible before the action

    A reported location has no risk reference, so the row cannot be linked reliably to the binding authority’s risk records.

Illustrative workflow example

Review a coverholder reporting cycle

A monthly bordereau may use a new column layout, omit a risk identifier or mix reporting periods. The reporting team must resolve those issues with the coverholder before it can accept the data for the relevant binding authority.

  1. 0101

    Match the report to its authority

    Duvo would link the bordereau, binding authority reference and reporting period using the supplied contract register.

  2. 0202

    Check the agreed reporting fields

    Duvo would check mandatory fields, duplicate risk references and reporting periods against the managing agent’s selected rules, preserving the original values.

  3. 0303

    Prepare the correction request

    Duvo would group the affected rows by issue and draft a request that identifies the missing field and responsible coverholder.

  4. 0404

    Your team decides

    Approve the reporting follow-up

    The delegated authority owner would approve the correction request or internal reporting handoff. Reporting acceptance and any authority-breach determination remain with the managing agent.

  5. 0505

    Track the revised file

    Duvo would route the approved correction request, compare the returned version and update the agreed reporting case. It would retain request delivery evidence and case-update confirmation, with acceptance still pending the managing agent’s decision.

Match each report to its authority and period

Systems and control details

Start with one binding authority, its current reporting rules and a sample of submitted files. Agree field mappings, reporting periods and permitted contacts before evaluating system access.

Coverholder bordereau, Binding authority register, Reporting field rules, Prior report versions

  • Delegated authority owner approval

    The delegated authority owner approves each correction request or internal reporting handoff before Duvo routes it.

  • Hold unresolved reporting fields

    Missing mandatory data, uncertain authority matches and conflicting periods remain open. Only the managing agent can accept the report or decide whether an authority breach occurred.

  • Retain every file version

    Keep original rows, applied mapping version, changed values and the owner’s instruction linked. A corrected file is recorded separately from formal reporting acceptance.

Contracted guarantee

5x ROI, guaranteed

If measured results fall below 5x the total proposal price, the whole contract is free.

What teams ask about Delegated authority bordereaux

  • When does Delegated authority bordereaux run?

    A coverholder submits a risk or claims bordereau for a reporting period.

  • Who owns Delegated authority bordereaux?

    Delegated authority operations and managing agent reporting teams

Related processes