# Recovery loops review packet contents | SourceX

Canonical: https://refer.sourcex.si/resources/recovery-loops-review-packet
Last updated: 2026-11-04

A recovery loops review packet holds nine metadata documents, assembled in this order: a cover sheet, the task specification, a description of the control, a run log map, a diagnosis notes map, a fix record map, the authority record, the pass condition with sign-off, and rights notes. Together they let a reviewer replay a migration's retries, such as an import revised until reconciliation passes, without receiving a single invoice or error file. Finance, IT and legal staff prepare them.

This contents list belongs to the guide on [recovery loops: five questions for introducers](/guides/concept-recovery-loops). It tells an owner what their team would be asked to assemble once a licensing discussion starts. It does not ask partners to build anything: it describes what the company's records would need to support later, under SourceX's agreement with the company.

## The packet in assembly order

| Order | Document | What it shows | Prepared by |
|---|---|---|---|
| 1 | Cover sheet | Systems, migrations and integrations covered, years, owner | Controller or CIO |
| 2 | Task specification | One loop's job and pass condition in plain words | Controller |
| 3 | Control description | Which report served as the target, and what it recorded | Controller |
| 4 | Run log map | Where each attempt's counts, totals and errors are kept | ERP or integration administrator |
| 5 | Diagnosis notes map | Where analysts wrote down why each run failed | Migration project manager |
| 6 | Fix record map | Where changes between runs are recorded, with user and time | ERP administrator |
| 7 | Authority record | Who was allowed to change master data, mappings and approve cutover | Controller with IT security |
| 8 | Pass condition and sign-off | The exact check, and where the signed result lives | Controller, refined with SourceX |
| 9 | Rights and sensitivity notes | Customer data, implementer contracts, lender or parent consent | General counsel |

## Documents 1 to 3: the frame

**1. Cover sheet.** One page: each migration or integration in the covered years, the systems on both sides, cutover dates, rough record volumes, whether an outside implementer ran the work, and the executive who owns the records.

**2. Task specification.** Illustrative wording for one loop: "Load all open receivables from the legacy aging report into the new ERP. The import passes when the item count and total match the legacy control exactly and every aging bucket matches. Do not post adjusting entries to force a match." One paragraph per loop type is enough.

**3. Control description.** What the target was (an aging report, a trial balance, a bank file total), when it was run, and whether it is still kept. Without a control, no attempt can be judged short or over.

## Documents 4 to 7: the loop itself

These four maps describe where the middle of each loop is recorded. They name fields and locations, never contents.

**4. Run log map.** For each attempt: timestamp, rows submitted, rows loaded, rows rejected, imported total and the tool's error output, and where each is kept. Microsoft's documentation for Dynamics 365 Finance and Operations import jobs says each run records succeeded and failed counts per entity and an execution log, and that by default job history and staging data older than 90 days are deleted. So this map must say whether error reports were exported before that happened.

**5. Diagnosis notes map.** Where the analyst's explanation of each failure lives: a ticket, a note on the error report, a project log. The Reflexion paper's agents keep written reflections on failures to guide the next attempt; a company's diagnosis notes play the same role, and without them a series of runs is only repetition.

**6. Fix record map.** Where the specific change between runs is recorded: master data entries, versioned mapping files, change tickets. Each needs a user and a time.

**7. Authority record.** The cutover plan, access approvals or RACI showing who was allowed to make each type of fix and who could approve the cutover.

## Documents 8 and 9: the test and the limits

**8. Pass condition and sign-off.** The exact outcome check, fixed in advance. An Illustrative version passes a loop only if all of these hold:

- [ ] The final count and total equal the control.
- [ ] Each aging bucket matches.
- [ ] No manual adjustment was posted to the receivables control account during the cutover window.
- [ ] Every run between the first failure and the pass is accounted for.

A loop that reaches $0 through an adjusting entry fails. So does one where the second run is missing, because the reviewer cannot confirm that its fix was diagnosed rather than stumbled on. The [worked import example](/guides/recovery-loops-workflow-example) shows a loop of three runs that passes.

**9. Rights and sensitivity notes.** Categories only: customer names and balances in error files, implementer engagement terms covering working files, and any parent company or lender consent needed.

## An Illustrative cover sheet (document 1)

**Illustrative and fictional.** A 520-person specialty chemicals distributor fills in document 1:

| Field | Entry |
|---|---|
| Projects covered | ERP migration 2020; e-commerce order integration 2022; bank file format change 2024 |
| Systems | Legacy accounting package to cloud ERP; web store to ERP; ERP to two banks |
| Implementer | Outside partner for the 2020 migration; in-house since |
| Error reports kept outside the tool | 2020 in the implementer's project folder; 2022 and 2024 in an IT shared drive |
| Mapping versions | Saved as dated files from 2022 |
| Signed reconciliations | All three projects |
| Records owner | CFO; CIO for integration logs |

Nothing here is an invoice, a customer or an error message. The table shows one point to flag honestly: the 2020 files sit with the implementer, so access depends on that engagement contract. Project tools and shared drives can hold some of this too: the [Asana system page](/systems/asana) covers project histories kept in a work management tool, and the note on [Microsoft 365 data after a subscription ends](/systems/microsoft-365-data-after-subscription-ends) covers what to check before a lapsed subscription takes shared project files with it.

## What the packet leaves open

The packet frames the archive. It does not decide whether the records qualify or are wanted. The company must have 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.

Vendors such as Appen market agent data built on failure-mode taxonomies and verifiers, which shows the category exists. It does not show demand for any particular company's retries, and SourceX does not claim to have purchased this type of data. Whether generated failures can replace real ones is discussed in [will synthetic data replace real data](/questions/will-synthetic-data-replace-real-data). In a sale or wind-down, establish who holds the systems first; see [special-situations investors and data assets](/for/special-situations-investor-data-assets) and [ABC assignee intangible asset recovery](/guides/abc-assignee-intangible-asset-recovery). The [evidence gaps analysis](/questions/recovery-loops-evidence-gaps) shows what usually goes missing. More record families are in [data types](/data-types).

## 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 the controller can picture the team filling in these nine documents for at least one past migration, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [program terms](/terms) before making the introduction.

## Sources

- https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/data-entities/data-import-export-job
- https://papers.nips.cc/paper_files/paper/2023/hash/1b44b878bb782e6954cd888628510e90-Abstract-Conference.html
- https://www.appen.com/agentic-ai
- https://refer.sourcex.si/terms
