Skip to content

Resolve bordereau exceptions before the reporting handoff

Duvo matches each coverholder bordereau to its binding authority, checks every row against the agreed reporting rules and groups the exceptions into one correction request.

Book a process call

Delegated authority bordereaux

Needs review

Bordereau DA-201

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: the coverholder gets a row-level query and the report is held until the revised file passes the checks.

Refer reporting exception: the managing agent’s reporting owner receives the row and its evidence for review.

Delegated authority owner approval

The delegated authority owner approves each correction request and internal referral before Duvo sends it.

View the wider product queue

Delegated authority bordereaux

Risk bordereau with a row missing its risk reference.

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 reference missing
Property binder risk report
Request risk reference
1
Bordereau DA-202
In Progress
Inception after binder expiry
Liability binder
Refer to owner
0
Bordereau DA-203
Completed
Reply recorded
Claims bordereau
Handoff recorded
0
Bordereau DA-204
Pending
Column order changed
Property binder
Review field mapping
1
Bordereau DA-205
Postponed
Revision awaited
Risk bordereau
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 tied reliably to the binder’s risk records and the report is held.

Review a coverholder reporting cycle

A coverholder sends this month’s risk bordereau with a new column order, a handful of rows without a risk reference and some policies that incept after the binder expired. The delegated authority team has to find those rows, separate data errors from anything that needs a closer look and go back to the coverholder before it can accept the report.

  1. 0101

    Match the report to its authority

    Duvo links the bordereau to its binding authority reference and reporting period from the contract register, and applies the agreed column mapping.

  2. 0202

    Check each row

    Duvo checks mandatory fields, duplicate risk references, inception dates, class of business, territory and limits against the agreed rules. The coverholder’s original values are never overwritten.

  3. 0303

    Group the corrections

    Duvo groups the affected rows by issue and drafts a correction request naming the missing or conflicting field for the coverholder.

  4. 0404

    Your team decides

    Approve the follow-up

    The delegated authority owner approves the correction request, or refers rows that may point to an authority breach for closer review.

  5. 0505

    Check the revised file

    The coverholder receives the approved correction request. When a revised bordereau arrives, Duvo compares it with the original and updates the reporting record; acceptance still waits on the delegated authority owner.

Match each report to its authority and period

Systems and control details

Bordereau checks follow the reporting rules of each binding authority, tested first on a sample of submitted bordereaux for one binder. Field mappings, reporting periods and permitted coverholder contacts are agreed before any 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 and internal referral before Duvo sends it.

  • No authority or acceptance decisions

    Duvo does not accept reports, decide whether a coverholder breached its authority, bind risks, settle claims, reconcile premium cash or make market submissions.

  • Retain every file version

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

What teams ask about Delegated authority bordereaux

  • Can Duvo cope with coverholders who change their bordereau layout?

    Yes. Duvo maps each file to the agreed reporting fields and flags a changed layout for review before applying a mapping. The original values are kept.

  • Does Duvo decide whether a coverholder has breached its authority?

    No. Duvo flags rows that fall outside the agreed limits, dates or territory. The insurer or managing agent decides whether a breach occurred and what follows.

  • Does this cover claims bordereaux as well as risk bordereaux?

    Yes. Both are checked against the rules agreed for each binding authority. Premium cash reconciliation is outside this scope.

Related processes