How Border-Io works
Border-Io is built for delegated authority operations teams handling bordereaux across binders, lineslips, consortia, master policies and portfolio underwriting. The working portal sits behind a login.
Step 1
Onboarding
A new company completes a guided setup: logo and brand accent, the minimum standards a submission must meet, the validation rules and thresholds, the mailboxes used for submissions, queries and data-quality receipts, and the SharePoint site, library and folder pattern files are written to.
- Logo and brand accent
- Minimum standards
- Validation rules and thresholds
- Mailboxes
- SharePoint destination
Step 2
Receipt
Submissions arrive in the shared operations mailbox. Message metadata, body content and spreadsheet attachments are pulled through, key attributes are extracted with a confidence score per field, and the file is linked to a delegated contract — auto-suggested, then confirmed by an operator.
- Shared mailbox sync
- UMR, UCR and period extraction
- Contract linking with confirmation
Step 3
Cleansing
Files and tabs are merged where compatible, columns are mapped to the Lloyd's template for the class and bordereau type, and a cleansing routine specific to the bordereau type runs. Nothing destructive happens without being asked for, and the original upload is never altered.
- Multi-file and multi-tab merge
- Confidence-scored column mapping
- Premium chain derivation
- Before and after diffs
Step 4
Assurance and filing
Validations, transaction-type checks, sanctions screening and address geocoding run against your rules. The output is named by your naming convention and filed to the SharePoint location, with a cleanse report, mapping and quality workbook and a tracked audit record for every submission.
- Sanctions screening
- Geocoding with confidence
- Cleanse and quality reports
- Full BDX tracker