# Claim question to closure record chain | SourceX

Canonical: https://refer.sourcex.si/guides/claim-question-to-closure-record-linkage
Last updated: 2026-11-04

A company connects claim-question-to-closure records by following five keys in order: the policy number and endorsement dates in the policy system, the claim number and loss date in the claims system, the conversation ID on each email thread, the claim-number folder in the document library, and the version number on each coverage letter. The links usually hold inside each system and fail at the hand-offs. The weakest is the policy copy, which can be taken before a late endorsement is processed.

This record chain is part of the [claim-question-to-closure records guide](/guides/chain-claim-question-to-closure), which covers what a partner can learn about the archive as a whole. Here the job is narrower: step, record, key and system, one row at a time.

## The chain, step by step

Illustrative. A 450-person regional property insurer, fictional. A bakery's commercial property policy gains a spoilage endorsement effective March 1; underwriting processes it on March 18. A freezer fails on March 9, and the bakery's broker reports the claim the next day.

| Step | Record | Key that joins it to the next step | System |
|---|---|---|---|
| 1. Policy change | Spoilage endorsement, effective March 1, processed March 18 | Policy number; effective and processed dates | Policy administration system |
| 2. Claim opened | Draft claim with a copy of the policy as of the March 9 loss date | Claim number, policy number, loss date | Claims system (ClaimCenter) |
| 3. Coverage question | Broker email asking whether spoiled stock is covered | Claim number in the subject; conversation ID | Mail server |
| 4. Evidence request and receipt | Handler asks for temperature logs and stock invoices; files arrive | Same conversation ID; claim-number folder | Mail, then the document library |
| 5. Coverage position | Letter version 1.0 declining spoilage; version 2.0 confirming it | Claim-number folder; major version number | Document library |
| 6. Closure | Payment issued and claim closed | Claim number | Claims system |

Illustrative. The insurer, bakery, dates and letters are fictional.

Read the key column downwards. Steps 2 to 6 share the claim number, directly or through a folder. Step 1 does not: it joins only through the policy number and the dates, which is why it is the link most likely to fail.

## Where the links break, and how each is repaired

| Link | How it breaks | What repairs it | Question for the claims team |
|---|---|---|---|
| Policy to claim | Endorsement processed after the policy copy was taken | A logged policy refresh or re-check on the claim | "When a policy changes after a claim opens, how does the claim learn about it?" |
| Claim to email | Broker starts a new thread without the claim number | Conversation ID, or a shared inbox filed by claim | "Is broker email filed to the claim, or left in personal mailboxes?" |
| Email to documents | Attachments never saved to the claim folder | A filing rule or a records team that files them | "Where does an attachment go if the adjuster does not file it?" |
| Letter to letter | Version 2.0 saved as a new file, or version 1.0 overwritten | Library versioning switched on, with enough versions kept | "If a coverage position changes, is the first letter still there?" |
| Letter to payment | Payment recorded only in a finance system | Payment status mirrored in the claims system | "Where would I see that this claim was paid?" |

In the Illustrative bakery claim, the first row is the weak link. The copy taken on March 10 predates the March 18 processing, so the adjuster's case view shows no spoilage coverage and version 1.0 declines. The broker's reply, in the same conversation, attaches the endorsement; the adjuster re-checks the policy, and version 2.0 reverses the position. The chain holds only if the re-check left a dated trace and version 1.0 survived. [What the case view alone leaves out](/guides/claim-question-to-closure-missing-context) reads the same kind of claim with and without that context.

## What each key is, according to the vendors

- **Policy copy (step 1 to 2).** Guidewire documents that ClaimCenter copies the policy from the policy administration system when a draft claim is created, that the copy reflects the policy as of the loss date, and that the policy system remains the system of record. The copy is a snapshot. If an endorsement is processed after the snapshot, the claim does not show it until someone refreshes or re-checks the policy.
- **Claims opened before the policy is confirmed.** Guidewire also covers the case where first notice of loss arrives before the policy can be matched, so the claim starts on a placeholder policy keyed from what the caller said. Payments stay blocked until that placeholder is replaced from the policy system. In such setups a policy pull is already a routine step on the claim; whether it carries a date is for the carrier to say.
- **Email thread (step 3 to 4).** In Microsoft Graph, an Outlook message carries a conversationId for the thread it belongs to and an internetMessageId in RFC 5322 format. A broker reply that drops the claim number from the subject can still be tied to the thread.
- **Letter versions (step 5).** SharePoint libraries can keep major versions (1.0, 2.0) and minor versions of a file, with version history for each. The default organization setting in SharePoint in Microsoft 365 is a manual limit of 500 major versions with no expiration; libraries set up differently may keep fewer.

None of this proves a given insurer kept the trail. It shows which keys can exist, so a partner knows what to ask.

## Joining the chain without moving any record

A partner does not test links; the insurer describes them. The useful answers are short: which identifier each system uses, since which year each link has held, and which link is known to fail. "Claim number on email since 2019, folders since 2017, letters versioned since the 2020 migration, policy refresh not logged" is a complete description of a chain. For scoring each link pass, partial or fail, use the [claim-question-to-closure completeness checklist](/resources/claim-question-to-closure-completeness-checklist).

How records would ever move is decided after SourceX's review and a signed agreement with the insurer. Naming vendor products here does not imply SourceX has a connector for any of them; any export field nobody has checked should be marked unknown. [Microsoft Outlook records](/systems/microsoft-outlook) and [Microsoft SharePoint records](/systems/microsoft-sharepoint) describe those systems in more detail.

## Who can authorize the introduction

Claim records hold policyholder and claimant information, so the sponsor is senior: the chief claims officer with general counsel or the chief privacy officer, or the CEO at a smaller carrier, MGA or TPA. Where a TPA handles the claims, ownership of the records may sit with the carrier; [who owns claims data at a TPA](/questions/who-owns-claims-data-tpa) explains why that matters before anyone is introduced.

The company has to clear the same bar as any referral: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Unknown until SourceX reviews it: whether claimant data can be de-identified to a buyer's standard, which lines of business and years would be in scope, regulatory and reinsurance limits on reuse, and what the insurer would be paid. Partners never ask for or handle claim files, letters or emails, and sign the Channel Partner Agreement before submitting introductions. The [insurance industry page](/industries/insurance) covers the wider fit.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If an insurer you advise can name the key for each link and the year each one started holding, [register as a partner](/register), check the insurer against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its claims or legal sponsor.

## Sources

- https://docs.guidewire.com/cloud/cc/202411/cloudapibf/cloudAPI/topics/111-CCFNOL/02-claims/c_retrieving-policy-information.html
- https://docs.guidewire.com/cloud/cc/202507/cloudapibf/cloudAPI/topics/111-CCFNOL/01-executing-FNOL/c_creating-claims-with-unverified-policies.html
- https://learn.microsoft.com/en-us/graph/api/resources/message?view=graph-rest-1.0
- https://support.microsoft.com/en-us/sharepoint/lists/documents-and-library/how-versioning-works-in-lists-and-libraries
- https://learn.microsoft.com/en-us/sharepoint/set-default-org-version-limits
- https://refer.sourcex.si/terms
