Reinsurance Email Filing: Link Emails to Treaty and Claim
On this page
- Key Takeaways
- What Is Reinsurance Email Filing?
- Which Link Keys Should Reinsurance Emails Be Filed Against?
- How Should a Reinsurance Email Filing Taxonomy Be Structured?
- Where Does Reinsurance Email Filing Break Down?
- What Escalation Rules Stop Reinsurance Emails Sitting Unfiled?
- How Does Insurnest Support Reinsurance Email Filing?
- What Should Operations Heads Fix First in Reinsurance Email Filing?
- Key Terms
- Sources
- Frequently Asked Questions
Last reviewed: November 2026
A cedent's loss advice arrives on a Friday, addressed to an underwriter who left the company in the summer.
It is found three weeks later in a shared folder, filed under the wrong year, after the cedent chases for a reply.
Reinsurance email filing is the practice of linking every broker and cedent email, with its attachments, to the treaty, year, account or claim it concerns.
Doing it reliably needs a fixed taxonomy: each email type, the key that links it, where it goes and who owns it.
Key Takeaways
- File by record, not by person. An email belongs to a treaty or claim, not to an inbox.
- Every email type needs one link key. Without a key, filing becomes guesswork.
- Loss advices need the date first. The attachment basis decides which treaty year applies.
- Ownership follows email type. Claims, accounts and underwriting each own their own queue.
- Unfiled email is a risk queue. It needs an owner, a clock and escalation.
What Is Reinsurance Email Filing?
Reinsurance email filing is the link between a message and the contract record it affects. It covers far more than submissions.
Accounts, cash calls, claims, endorsements and queries all arrive by email. Each one carries an action and, often, a deadline.
Submission inbox pressure is a separate problem, covered in reinsurance underwriter email overload. Filing is about everything that follows.
Which Link Keys Should Reinsurance Emails Be Filed Against?
Reinsurance emails should be filed against a key that never changes for the life of the record. External references help, but they must map to it.
| Link key | Issued by | Best used for | Watch for |
|---|---|---|---|
| Reinsurer contract reference | Reinsurer | Every treaty or fac email | Must exist in the reinsurance treaty register |
| Underwriting year | Contract terms | Accounts, renewals, wordings | A renewal is a new year, not an update |
| Unique Market Reference (UMR) | Broker, London market | Matching broker emails to placements | Contains a broker code, so check after broker changes |
| Cedent treaty number | Cedent | Matching cedent emails | Cedents may reuse numbers across years |
| Claim reference | Cedent and reinsurer | Loss advices, updates, settlements | Cedent and reinsurer numbers differ |
| Account period | Contract terms | Statements, bordereaux, cash | Quarter vs underwriting year confusion |
| Event code | Reinsurer | Cat losses across many treaties | Assign it once, centrally |
Lloyd's market bulletin Y5364 confirms that the Lloyd's broker code is a component of the UMR.
How Should a Reinsurance Email Filing Taxonomy Be Structured?
A reinsurance email filing taxonomy should be structured by email type, because the type tells you the key, the place and the owner.
| Email type | Link key | Filed to | Owner | File within |
|---|---|---|---|---|
| New or renewal submission | Cedent, class, underwriting year | Submission record | Underwriting | Same day |
| Broker query and answer | Submission or contract reference | Same submission or contract | Underwriting | Same day |
| Firm order and binding confirmation | Contract reference, year | Contract record | Underwriting and operations | Same day |
| Wording, endorsement, addendum | Contract reference, year | Contract documents, version noted | Wordings or operations | 1 business day |
| Technical account or statement | Contract, year, account period | Accounts record | Technical accounting | 1 business day |
| Bordereau | Contract, year, period | Bordereau log | Technical accounting | 1 business day |
| Cash call | Contract, year, claim reference | Claim and cash record | Claims and finance | Same day |
| Loss advice or update | Claim reference, contract, year | Claim record | Claims | Same day |
| Collateral or letter of credit | Contract, year | Security record | Finance | 2 business days |
| General market news | None | Reference folder | Recipient | No deadline |
The times above are illustrative. Set your own by the deadline each email type usually carries.
Who owns filing when one email covers two treaties?
Filing of one email that covers two treaties is owned by the team for that email type, and the email is linked to both records.
A broker statement for four treaties is stored once, with four links. Copies create four versions, and only one gets updated.
What happens to an email that carries no link key?
An email that carries no link key goes to an unfiled queue with a named owner, and the sender is asked for the reference.
It must not stay in a personal inbox. That is where the cedent's chaser ends up being the first alert.
Where Does Reinsurance Email Filing Break Down?
Reinsurance email filing breaks down where the email looks routine but the key is ambiguous.
| Misfiling | How it happens | Consequence |
|---|---|---|
| Loss advice under the wrong year | Filed by date received, not date of loss | Wrong treaty reserved, wrong layer checked |
| Renewal endorsement on the expiring contract | Same cedent treaty number both years | Expiring wording appears amended |
| Cash call filed only to accounts | Treated as a statement item | Claims team misses the payment deadline |
| Statement filed under one treaty | Multi-treaty statement, one link | Other treaties show no account received |
| Group entity mix-up | Two cedent entities share a name | Exposure and claims land on the wrong entity |
| Reply-all thread drift | Topic changes mid-thread | New claim hidden inside an old query thread |
Why does a loss advice need the date of loss before filing?
A loss advice needs the date of loss before filing because the treaty's attachment basis decides which underwriting year responds.
The Reinsurance Association of America glossary defines losses occurring during as cover for losses that happen during the reinsurance term.
It defines policies attaching as cover for losses under original policies issued during the reinsurance term.
Take an illustrative loss on 10 February 2027 under a policy that incepted on 1 October 2026. The cedent renews both treaties each 1 January.
Under a losses occurring treaty, the email files to the 2027 year, because the loss happened in 2027.
Under a policies attaching treaty, it files to the 2026 year, because the policy incepted in 2026.
If a team files by the date received, both cases look like 2027, and the policies attaching claim is booked to the wrong year.
What Escalation Rules Stop Reinsurance Emails Sitting Unfiled?
Escalation rules stop reinsurance emails sitting unfiled by giving each queue a clock and a named person above the owner.
| Trigger | Escalate to | Action |
|---|---|---|
| Loss advice unfiled at end of day | Head of claims | File and acknowledge to cedent |
| Cash call unfiled at end of day | Head of claims and finance | Confirm payment due date |
| Email with no key after 2 business days | Head of operations | Chase sender, file provisionally to cedent |
| Endorsement unfiled after 3 business days | Head of wordings | Check version against contract record |
| Email to a leaver's inbox | Team leader | Redirect and refile all open items |
The thresholds are illustrative. What matters is that each trigger has an owner and a deadline.
Our case study on a claims notice that gets lost shows what happens when no rule applies.
How Does Insurnest Support Reinsurance Email Filing?
Insurnest supports one part of reinsurance email filing: the submission email. Accounts, claims and general correspondence stay with your existing process.
Reinsurance Email Intelligence reads a submission email with its PDFs, spreadsheets and claims files, and works out which attachments belong to it.
It extracts cedent, broker and contact, treaty structure, premium, inception and expiry into one structured submission view, which gives the submission its keys.
It does not file statements, cash calls, loss advices or endorsements, and it does not track filing deadlines.
Those taxonomy rows stay manual or in your own systems.
For terms buried in attachments, see treaty terms trapped in email and PDF attachments.
What Should Operations Heads Fix First in Reinsurance Email Filing?
Operations heads should fix the email types that carry money or deadlines first, then the rest.
- Sample last quarter's loss advices. Check each against the date of loss and the treaty's attachment basis.
- List every shared mailbox and its owner. Remove inboxes nobody watches.
- Map external references to contract references. Start with cedent treaty numbers that repeat across years.
- Count emails still in leavers' inboxes. Refile open items before the next renewal.
- Publish the taxonomy table. One page, agreed by claims, accounts and underwriting.
For endorsements, pair this with change control for contract amendments.
Key Terms
- Link key: The stable reference an email is filed against, such as a contract reference.
- Unique Market Reference (UMR): The London market placement reference, which embeds a broker code.
- Losses occurring during: Cover for losses that happen during the reinsurance term.
- Policies attaching: Cover for losses under original policies issued during the reinsurance term.
- Cash call: A cedent's request for early payment of a large claim before the next account.
Sources
- Lloyd's: Market Bulletin Y5364, Operational Guidance for UMRs and Broker Codes on MRCs (22 December 2021)
- Reinsurance Association of America: Glossary of Reinsurance Terms
- Insurnest: Reinsurance Email Intelligence
Frequently Asked Questions
What is reinsurance email filing?
Reinsurance email filing is the practice of linking every broker and cedent email, with its attachments, to the record it concerns. That record may be a treaty, an underwriting year, an account period or a claim, so the email can be found and acted on later.
Which references should reinsurance emails be filed against?
Reinsurance emails should be filed against a stable link key: the reinsurer's contract reference, the underwriting year, the claim reference or the account period. A London market Unique Market Reference or the cedent's treaty number helps match the email but should map to the internal key.
Why is filing a loss advice harder than filing other reinsurance emails?
Filing a loss advice is harder because the right treaty depends on the date of loss and the treaty's attachment basis. Under losses occurring, the loss date picks the treaty year. Under policies attaching, the original policy's inception date picks it, which can point to an earlier year.
Who should own reinsurance email filing?
Ownership of reinsurance email filing should follow the email type, not the inbox it arrived in. Underwriting owns submissions and wordings, technical accounting owns statements and cash, and claims owns loss advices, with operations owning the taxonomy and the unfiled queue.
How do you file reinsurance emails to the right treaty?
To file reinsurance emails to the right treaty, classify the email type first, then find the link key in the subject, body or attachments. Map any broker or cedent reference to your contract reference, confirm the year from the relevant date, and queue anything unclear for review.
What happens when a reinsurance email is misfiled?
When a reinsurance email is misfiled, the action it carries is missed or done against the wrong contract. Typical results are a late claims response, a cash call paid on the wrong year, or an endorsement that never reaches the treaty record.
How quickly should reinsurance emails be filed?
Reinsurance emails should be filed within a time set by their type. Loss advices and cash calls need same-day filing because they carry deadlines, while general market correspondence can wait longer. Each firm should set and publish its own filing times.
Should one reinsurance email be filed in two places?
One reinsurance email should be filed in two places when it truly concerns two records, such as a broker statement covering several treaties. The email is stored once and linked to each record, so nobody keeps conflicting copies.

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 →