Broker Reference Mapping for Treaties: Crosswalk Guide
On this page
- Key Takeaways
- What Is Broker Reference Mapping for Treaties?
- How Do Broker, Cedent and Reinsurer References Line Up in One Crosswalk?
- How Should Reinsurers Map Broker References to Treaty Records?
- How Is an Unmatched Treaty Cash Receipt Traced Through the Crosswalk?
- Where Does Broker Reference Mapping Break Down?
- How Does Insurnest Relate to Broker Reference Mapping?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
USD 182,500 lands from the broker with a remittance line of "B1234 PRXL25 01 L2 Q1". No treaty in your system carries that string.
The cash goes to suspense. Six weeks later the cedent asks why its premium is still shown as unpaid.
Broker reference mapping for treaties is a crosswalk linking broker references, such as a UMR, to cedent codes and your contract numbers.
It matters because cash, statements, claims and signings arrive under the broker's reference, while your books run on yours.
This guide gives you a reference crosswalk, matching rules in priority order, a worked unmatched cash case and the common failure points.
Key Takeaways
- One row per section and year. Not one row per programme.
- Normalise before matching. Strip spaces and hyphens, then upper-case.
- Exact UMR first. Weaker matches go to a person, not to auto-posting.
- New year, new row. Renewals never inherit last year's mapping.
What Is Broker Reference Mapping for Treaties?
Broker reference mapping for treaties is the crosswalk between the references each party gives the same contract.
Life business needs the same at policy level; see policy number mapping between cedent and reinsurer. This guide works at treaty level.
What format does a Lloyd's Unique Market Reference follow?
A Lloyd's Unique Market Reference follows a fixed pattern: the letter B, the 4-digit Lloyd's broker number, then up to 12 letters or digits.
Buckhill's key concepts guide gives a 17-character maximum with A–Z and 0–9 only. No spaces or hyphens.
So "B1234 PRXL25 01" is a human retyping of B1234PRXL2501. Your matcher must undo that.
How Do Broker, Cedent and Reinsurer References Line Up in One Crosswalk?
Broker, cedent and reinsurer references line up in one crosswalk row per treaty section and underwriting year. Values are illustrative.
| Crosswalk field | Issued by | Example | Granularity | Changes when |
|---|---|---|---|---|
| UMR | Broker | B1234PRXL2501 | Contract (whole MRC) | Each new placement |
| Main broker code | Embedded in UMR | 1234 | Contract | Rarely |
| Additional broker codes | Recorded in MRC body | 5678 | Contract | Mid-term broker change |
| Cedent treaty code | Cedent | NWP-CAT-25-L2 | Layer | Each renewal |
| Reinsurer contract number | Reinsurer | R25-004812 | Contract | Each renewal |
| Reinsurer section | Reinsurer | 2 (of 3) | Layer | Layer added or removed |
| Layer token used by broker | Broker remittance | L2 | Layer | Broker practice |
| Underwriting year | All | 2025 | Year | Each renewal |
The UMR is contract-level, so one UMR often feeds several sections. That is where most mis-postings start.
How Should Reinsurers Map Broker References to Treaty Records?
Reinsurers should map broker references to treaty records with fixed rules, applied in this order.
| Priority | Rule | Result |
|---|---|---|
| 1 | Normalise: remove spaces, hyphens and dots; upper-case | Clean key |
| 2 | Exact UMR match, plus layer token to section | Auto-match |
| 3 | Exact cedent treaty code + year + layer | Auto-match |
| 4 | UMR found but no layer token | Match contract; route section to a person |
| 5 | Cedent name + inception + currency only | Suggest; human confirms |
| 6 | Nothing above | Suspense with reason code |
Amount alone never decides a match. Two layers can carry similar instalments.
Use these normalisation and format tests in Excel or SQL before rule 2 runs.
Normalised key (Excel):
=UPPER(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(A2," ",""),"-",""),".",""))
UMR shape test (regular expression):
^B[0-9]{4}[A-Z0-9]{1,12}$
Layer token: first match of L[0-9]+ in the remittance text
A key that fails the shape test is not a UMR. Route it to rule 3 instead of forcing a match.
Log every rule 4 to 6 outcome with the person who confirmed it. Those confirmations become tomorrow's aliases and cut suspense volume over time.
Which other references should sit on the treaty crosswalk?
Other references that should sit on the treaty crosswalk are those that arrive on later documents for the same contract section.
- Signing number and date. Buckhill's underwriting lifecycle guide says each underwriter receives one after signing.
- Claim references. Claims carry their own references; map each to the contract section it hits.
- Statement numbers. Broker account statements often quote their own number beside the UMR.
Why can cash arrive under a broker code that differs from the UMR?
Cash can arrive under a broker code that differs from the UMR because one Market Reform Contract can involve several Lloyd's broker codes.
Lloyd's Market Bulletin Y5364 says the UMR reflects a main broker code. Additional codes are recorded in the MRC body.
Those codes "should not be used to generate additional UMRs". Do not reject cash because the paying broker code is not the one inside the UMR.
How Is an Unmatched Treaty Cash Receipt Traced Through the Crosswalk?
An unmatched treaty cash receipt is traced through the crosswalk in five steps. This case is illustrative.
- Normalise. "B1234 PRXL25 01 L2 Q1" becomes tokens: B1234PRXL2501, L2, Q1.
- Find the UMR. B1234PRXL2501 exists, contract R25-004812, sections 1–3.
- Map the layer. Token L2 maps to section 2, cedent code NWP-CAT-25-L2.
- Test the amount. Q1 deposit at 100% is 0.5m; signed line 40% gives 200,000; less 8.75% brokerage is 182,500.
- Post and record. Post to section 2 Q1 and add "B1234 PRXL25 01" as a known alias.
The exact amount confirms the mapping; it did not create it. Broker balances then tie out, as in reinsurance broker balance reconciliation.
Where Does Broker Reference Mapping Break Down?
Broker reference mapping breaks down at a few predictable points.
- Retyped references. Spaces, hyphens or a dropped character defeat exact matching.
- One UMR, many sections. Cash posts to section 1 by default.
- Mid-term broker change. A new broker code appears; the UMR does not change.
- Cedent recodes. The cedent renames its programme codes after a merger.
- Lost aliases. Known variants live in one person's spreadsheet.
Record where each mapping came from and who confirmed it; reinsurance data lineage covers the wider practice.
Should a renewed treaty keep the same broker reference mapping row?
A renewed treaty should not keep the same broker reference mapping row, even when the cedent code looks unchanged.
Create a new row per renewal with its own year and references. Link it to the prior row so loss history and late cash still find the right year.
How Does Insurnest Relate to Broker Reference Mapping?
Reinsurance Treaty Management does not hold a broker reference crosswalk, match cash or manage placement with brokers.
It gives each treaty a controlled record of structure, participation share, limits and terms, and calculates premium and settlement from them.
Key your crosswalk to that record. Step 4 above then tests cash against a calculated figure, not a remembered one.
Key Terms
- UMR (Unique Market Reference): The broker-issued contract reference used across London market systems.
- Crosswalk: A table linking each party's reference for the same treaty section and year.
- Alias: A known variant of a reference, stored so it matches next time.
Sources
- Buckhill: Key Concepts (UMR format)
- Lloyd's: Market Bulletin Y5364, UMRs and Broker Codes on MRCs
- Insurnest: Reinsurance Treaty Management
Frequently Asked Questions
What is broker reference mapping for treaties?
Broker reference mapping for treaties is a crosswalk linking each broker reference, such as a UMR, to the cedent's treaty code and the reinsurer's contract and section numbers.
What format does a Lloyd's Unique Market Reference follow?
A Lloyd's Unique Market Reference starts with B, then the 4-digit Lloyd's broker number, then up to 12 letters or digits, with a maximum of 17 characters.
How do broker, cedent and reinsurer references line up in one crosswalk?
Broker, cedent and reinsurer references line up in one crosswalk row per treaty section and year, holding UMR, broker code, cedent code, contract number, section and layer.
How should reinsurers map broker references to treaty records?
Reinsurers should map broker references to treaty records by normalising the reference, matching UMR exactly first, then cedent code with year and layer, then reviewing anything weaker by hand.
Why can cash arrive under a broker code that differs from the UMR?
Cash can arrive under a broker code that differs from the UMR because one MRC can use several Lloyd's broker codes, while the UMR reflects only the main broker code.
How is an unmatched treaty cash receipt traced through the crosswalk?
An unmatched treaty cash receipt is traced through the crosswalk by normalising the remittance, finding the UMR, mapping the layer token to a section and testing the amount.
Where does broker reference mapping break down?
Broker reference mapping breaks down when references are retyped with spaces, one UMR covers several sections, broker codes change mid-term or renewals reuse last year's row.
Should a renewed treaty keep the same broker reference mapping row?
A renewed treaty should not keep the same broker reference mapping row. Each renewal gets a new row with its own year, references and sections, linked to the prior row.

Hitul Mistry
CEO, Insurnest
An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.
View LinkedIn profile →