# Claims completeness records across systems | SourceX

Canonical: https://refer.sourcex.si/guides/claims-document-completeness-review-records-across-systems
Last updated: 2026-11-04

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.

This system map is part of the [claims document completeness review hub](/guides/workflow-claims-document-completeness-review). 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.

| Record | System | Linking key it carries | Typical owner |
|---|---|---|---|
| Claim and its revision history | Claims system | Claim number, version or revision date | Claims operations |
| Checklist template by line and loss type | Claims system or claims standards library | Template ID and version | Claims standards team |
| Checklist instance for one file | Claims system, sometimes a spreadsheet | Claim number, template version, reviewer, sign-off date | Completeness reviewers |
| Missing-item request | Claims system activity; letter in correspondence | Claim number, request ID, sent date | Adjusters |
| Request letter copy | Document repository or correspondence module | Claim number, letter date | Records management |
| Received document | Document repository | Claim number, upload date, sometimes received date | Records management |
| Receipt log entry | Claims system activity | Claim number, request ID, received date | Completeness reviewers |
| Claim decision | Claims system | Claim number, version, decision date | Adjusters |

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

| Key | What it answers | Where it usually lives | How it fails |
|---|---|---|---|
| Claim number | Which claim | Every system | Typed by hand into folder names; changed at migration |
| Claim version or revision date | Which scope the document supported | Claims system only | Repository stores the claim, not the revision |
| Request ID | Which requirement a receipt satisfied | Claims system activity | Request sent from email with no system record |
| Received date | When the gap closed | Claims activity; repository metadata | Upload 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](/guides/claims-document-completeness-review-exception-examples), 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.

| Step | System | Record | Keys present | Join to next step |
|---|---|---|---|---|
| Day 2 | Claims system | Checklist instance from the auto physical damage template | Claim number, template version | Claim number |
| Day 6 | Claims system | Revision to version 2: total loss | Claim number, version 2, date | Version date, if the reviewer can see it |
| Day 10 | Claims system | Checklist signed off with the body shop's repair quote on file | Claim number, reviewer, date | None to the quote's version: the gap |
| Day 14 | Claims system and correspondence | Request REQ-7 for a salvage valuation and the title copy | Claim number, request ID, sent date | Request ID |
| Day 20 | Document repository and claims system | Valuation and title received; receipt entries | Claim number, request ID, received date | Request 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](/guides/how-to-identify-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](/questions/what-records-to-keep-after-selling-a-business) and [data quality due diligence](/resources/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](/resources/claims-document-completeness-review-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](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing the head of claims operations.

## Sources

- https://docs.guidewire.com/cloud/cc/202511/apiref/generated/Claim%20API/claims--claimId--documents--post/
- https://docs.guidewire.com/cloud/cc/202511/cloudapibf/cloudAPI/topics/141-Framework/01_activities/c_creating-activities.html
- https://refer.sourcex.si/terms
