What we do

Delegated authority data, handled from the inbox to the market submission

Bordereaux arrive late, in the wrong format, with columns that shift month to month. The work of chasing, reformatting and checking them absorbs the time that should be spent on oversight. Border-Io takes that work on, applies the same standard every month, and leaves a record of everything it did.

The services we cover

Receipt and capture

Submissions arrive in a monitored mailbox or a shared repository. Border-Io reads the message, extracts the UMR, coverholder, period and premium figures, and matches the attachment to the right contract before anyone opens it.

Cleansing to standard

Columns are mapped to the Lloyd's Coverholder Reporting Standards template for the class of business, transaction and premium types are normalised, and the premium chain is derived where a figure is missing.

Validation and screening

Mandatory fields, sign conventions, period coverage and identifier consistency are checked. Insured and location names are screened against sanctions lists and addresses are quality scored and geocoded.

Naming and filing

Cleansed files are named to your convention from contract data — UMR, coverholder, year of account, bordereau type, period and identifier — and written to the SharePoint or OneDrive location you nominate.

Chasing and exceptions

Expectation rules per contract set what is due and when. Missing returns age into bands, chase emails go out on your wording, and nil returns are captured through the same reporting channels.

Oversight and reporting

Every upload, mapping decision, override and delivery is logged. Tracker views, saved standards and exportable reports give underwriters and compliance a defensible record.

Who it is for

Managing agents
Evidence that delegated data is complete, screened and filed on time, ahead of the next audit.
Coverholders and MGAs
Submit once, in your own format, and let the mapping engine reconcile it to the market template.
Brokers
Fewer rejected submissions and clear, itemised data quality feedback to pass back to the source.
TPAs
Claims bordereaux handled to the same standard as premium, with paid and outstanding kept apart.

Every class of business

Written, premium, paid and claims bordereaux are treated as separate processes with their own template variants, so gross written premium never appears in a paid return and paid figures never appear in a written one. Territory and class of business route each file to the correct template variant.