Claims document completeness review records across systems: a system map with linking keys

Short answer

Four keys rebuild a claims document completeness review across systems: the claim number, the claim version or revision date, the request identifier and the date each document was received. The claims system holds the checklist and the revision history; the document repository holds what arrived; correspondence holds what was asked for. The claim version is the join that usually fails, because many repositories file a document against the claim and nothing finer. Below is the map, then one Illustrative file joined end to end.

Visual briefFull-size diagram
A system map with four nodes, claims system, document repository, correspondence and the receipt log, joined to one claim file at the center by four keys: claim number, claim version, request ID and received date; the claim version link is marked amber as the join most often missing.
Illustrative: four systems, four keys, one claim file. The amber link is the join most repositories never store.

This system map is part of the claims document completeness review hub. It does one job: show where each record lives, which key links it to the next, and who owns each system.

Where each completeness record lives

The table is the evidence asset: one row per record, with the system, the key it carries and the person who can answer questions about it. Owners vary by company; these are typical.

RecordSystemLinking key it carriesTypical owner
Claim and its revision historyClaims systemClaim number, version or revision dateClaims operations
Checklist template by line and loss typeClaims system or claims standards libraryTemplate ID and versionClaims standards team
Checklist instance for one fileClaims system, sometimes a spreadsheetClaim number, template version, reviewer, sign-off dateCompleteness reviewers
Missing-item requestClaims system activity; letter in correspondenceClaim number, request ID, sent dateAdjusters
Request letter copyDocument repository or correspondence moduleClaim number, letter dateRecords management
Received documentDocument repositoryClaim number, upload date, sometimes received dateRecords management
Receipt log entryClaims system activityClaim number, request ID, received dateCompleteness reviewers
Claim decisionClaims systemClaim number, version, decision dateAdjusters

Two details from one widely used platform show why the keys matter. In Guidewire ClaimCenter's Cloud API, documents are created against a claim identifier through POST /claims/{claimId}/documents. Activities, the natural home for a missing-item request, are likewise created from an existing claim and require an activity pattern code. Both hang off the claim. Whether a company also records which revision a document or request relates to depends on its configuration, so it is a question to ask, not an assumption.

The four keys, and how each one fails

KeyWhat it answersWhere it usually livesHow it fails
Claim numberWhich claimEvery systemTyped by hand into folder names; changed at migration
Claim version or revision dateWhich scope the document supportedClaims system onlyRepository stores the claim, not the revision
Request IDWhich requirement a receipt satisfiedClaims system activityRequest sent from email with no system record
Received dateWhen the gap closedClaims activity; repository metadataUpload or scan date used instead of the date the claimant sent it

The first key is almost always present. The other three decide whether the review can be reconstructed or only summarized.

One file joined end to end (Illustrative)

A different fictional file from the one on the exception examples page, so the join stands on its own: a commercial auto claim at a 600-person fleet insurer. On day 6 the van is declared a total loss, which turns claim version 1 (repair) into version 2 (total loss). Every value is invented.

StepSystemRecordKeys presentJoin to next step
Day 2Claims systemChecklist instance from the auto physical damage templateClaim number, template versionClaim number
Day 6Claims systemRevision to version 2: total lossClaim number, version 2, dateVersion date, if the reviewer can see it
Day 10Claims systemChecklist signed off with the body shop's repair quote on fileClaim number, reviewer, dateNone to the quote's version: the gap
Day 14Claims system and correspondenceRequest REQ-7 for a salvage valuation and the title copyClaim number, request ID, sent dateRequest ID
Day 20Document repository and claims systemValuation and title received; receipt entriesClaim number, request ID, received dateRequest ID back to day 14

With all four keys, a reviewer years later can read the file as a sequence: the loss type changed, a quote for the old version was accepted, the gap was caught and closed. With only the claim number, the same records look like a pile of documents on one claim.

Where the joins break, and what to ask

Most breaks happen at the edges between systems:

  1. Checklist outside the platform. Some teams keep checklists in spreadsheets. Ask whether sign-offs are in the claims system or elsewhere.
  2. Requests sent by email. A letter without an activity has no request ID. Ask whether every missing-item request creates a system entry.
  3. Repository metadata. Ask whether the repository stores a received date distinct from the upload date, and any field for claim version.
  4. Migration. Ask whether claim identifiers change at migration and who re-points repository links.

The cross-system logic is the same in other sectors; logistics exceptions and their documented resolutions shows it for freight files.

Confirming coverage without opening a file

Export capability varies by platform, version and contract, so the company should confirm with its own administrators what history each system can produce and how far back. Legal retention periods vary by state and line, and many insurers keep far more than the minimum in an old platform. A partner collects answers, not data: the systems, the years, whether each key exists, and who owns each system. What records to keep after selling a business and data quality due diligence give useful framing.

Qualification follows the program rules: the introduced company needs 50+ full-time employees at peak (contractors excluded), 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. Claim files hold claimant personal data, so de-identification and exclusions are part of SourceX's rights review, along with buyer interest and any offer, all unknown until that review. The referral brief template turns the map into a one-page introduction.

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's administrators confirm that requests, receipts and claim versions can still be joined, register as a partner, check the company on who qualifies and read the program terms before introducing the head of claims operations.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is the claim number enough to join everything?

It joins records to the claim, not to the moment. Without the claim version and the request identifier, you can see that a document arrived but not which requirement it satisfied or which scope it supported.

Can a partner test the joins without seeing the data?

Yes, by asking the administrators yes-or-no questions: does the repository store a claim version, does each request have an identifier, are received dates kept separately from upload dates. The answers describe the joins without anyone sharing a record.

Does a platform migration always break the links?

Not always, but it often changes claim identifiers or leaves the repository behind. Whether links are re-pointed is a question for the project plan, and the company should confirm it with its own team.

Sources

  1. docs.guidewire.com/cloud/cc/202511/apiref/generated/Claim API/c…
  2. docs.guidewire.com/cloud/cc/202511/cloudapibf/cloudAPI/topics/1…
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment