Our tool

One platform for receiving, cleansing and tracking bordereaux

Border-Io is a browser-based portal. Cleansing runs on your machine, the original upload is never altered, and every decision is written to an audit trail you can export. Below is what each module does.

Cleanse wizard

Six guided steps from upload to download.

Multi-file and multi-sheet import with compatibility scoring before sheets are merged
Auto-mapping against the Lloyd's template with confidence scores and a review gate on weak matches
Column defaults suggested from the binder, so known values pass without manual entry
Before and after previews with a cell-level diff of every change
Cleanse report, mapping report and activity log issued with the output file

BDX tracker

One register for everything received.

Filter and sort on any field: UMR, internal reference, coverholder, underwriter, division, risk code or date
Add or remove columns and save the arrangement as a view for the team
Status per submission: geocoded, sanctions checked, passed or failed
Retry failed uploads and repository scans without reconfiguring anything

Overdue and expectations

Chasing that runs itself.

Expectation rules per contract set frequency, due dates and grace periods
Ageing bands from one to five months, with the chart clickable straight through to the detail
Chase emails on your own templates and tokens, previewed exactly as the recipient sees them
Audit log of every rule change and every chase sent

Nil returns

A nil is still a return.

Driven by the reporting channels configured on the binder
Month and year selection, with risk codes only where the binder uses them as an identifier
Review queue so extracted fields are approved before a period is marked complete

Reference data and standards

Your definitions, held centrally.

Coverholders, risk codes, TPAs and contract registers with a full import audit trail
Saved standards: pinned filters and stats widgets, created by experienced users for everyone else
Naming conventions and storage destinations driven by tokens, never hard-coded

Control and access

Administered per portal.

Role groups with individual permissions across every page and cleansing stage
Admins choose the default cleansing view for a person or a group
Cleansing features can be switched on per portal as chargeable options
Settings, API and email changes recorded with a field-level diff

See it against your own data

The fastest way to judge the tool is to put a real bordereau through it. Send us one and we will show you the mapping, the exceptions it raises and the file it produces.

Arrange a walkthrough