Recovery loops workflow example: three import runs from a $143,580 shortfall to a signed reconciliation

Short answer

A recovery loop is a run of attempts in which each failure is checked, diagnosed and fixed before the next try, until a defined check passes. In an ordinary business, it looks like a migration team importing open receivables three times: the first run lands $143,580 short, the second $18,400 over, and the third matches the legacy control exactly before the controller signs off. The valuable record is the whole sequence, not the clean final number.

Visual briefFull-size diagram
A workflow plays through an Illustrative receivables import: control, run 1 ($143,580 short), a fix creating 31 customers, run 2 ($18,400 over), a fix to mapping v2, run 3 at a $0 difference and sign-off; each step drops its record, from the aging report and three job logs to the signed reconciliation.
Illustrative figures for a fictional 240-person distributor. Each dropped record is one the AI-data review would look for.

This worked example is part of the guide on recovery loops: five questions for introducers. That guide helps you ask whether a client kept these records. This page walks through one loop end to end so you can recognise one when a controller describes it.

The task and its control (Illustrative)

Illustrative and fictional. A 240-person building-products distributor is cutting over from a legacy accounting package to a new ERP. One cutover task is loading every open customer invoice. The legacy aging report is the control: 3,412 open items totaling $1,846,220.

The pass condition is written before the first run: the item count and total must equal the control, every aging bucket must match, and no adjusting entry may be posted to force a match. That last clause matters later.

AI research has a name for this pattern of attempt, feedback and retry. Reflexion, a NeurIPS 2023 paper, describes language agents that improve across attempts by writing reflections on feedback into a memory that guides the next try, rather than by retraining. Here the import error report is the feedback, the analyst's note is the reflection and the next run is the retry.

Step by step: three runs, two fixes, one sign-off

StepWhat happensDecision takenRecord left behind
1. Extract controlLegacy aging report run as of cutoverAccept 3,412 items, $1,846,220 as the targetAging report with count and total
2. Run 13,200 of 3,412 rows load; imported total $1,702,640Stop: $143,580 shortImport job log with succeeded and failed counts
3. Diagnose run 1212 rows rejected: customer IDs missing from the new customer masterFix master data, not the fileAnalyst note on the rejection report
4. Fix 131 missing customers created, approved by the master data ownerRerun the full fileCustomer creation entries with user and time
5. Run 23,412 of 3,412 rows load; imported total $1,864,620Stop: $18,400 overSecond import job log
6. Diagnose run 223 credit memos worth $9,200 loaded as positive invoicesRepair the mapping, do not post an adjustmentAnalyst note naming the document type
7. Fix 2Sign reversed for the credit memo document typeRerunVersioned mapping file or change ticket
8. Run 33,412 of 3,412 rows; imported total $1,846,220Difference $0; compare bucketsThird import job log
9. Sign-offController compares aging buckets, all matchApprove cutover of receivablesSigned reconciliation workbook

Microsoft's documentation for Dynamics 365 data import jobs describes this tooling: each run records execution details, including records that succeeded and failed per entity, and an execution log, and failing records can be fixed and reimported. Other ERPs differ in detail, but most leave a per-run trace of some kind.

Reading the numbers: why run 2 is the instructive one

Read down the differences: $143,580 short, then $18,400 over, then $0. Two details reward a closer look.

First, the run 1 shortfall hid part of the problem. The 23 credit memos were already loading as positive amounts in run 1. So the 212 rejected rows were actually worth $161,980, partly masked by the $18,400 overstatement: $1,846,220 minus $161,980 plus $18,400 gives the $1,702,640 that run 1 reported. An analyst who stopped at "load the missing customers" would have been surprised by run 2.

Second, a $9,200 credit loaded as a positive amount moves the total by twice that, which is why run 2 is over by $18,400 rather than $9,200. An analyst under time pressure could have posted an $18,400 adjusting entry and reached zero without repairing the mapping. The pass condition forbids that, and the reason it matters is the reason the loop has value: the fix itself, not just the final total, belongs in the record. A reviewer must be able to tell a repaired mapping from a forced balance. Our page on why AI agents fail describes the same risk in software agents: reaching the right-looking answer by the wrong route.

Which records carry the signal

Not every record above is equally useful to an AI-data review. The ones that carry signal are those that connect a failure to its cause and its fix.

RecordSignal it carriesStrength if missing
Aging report (control)Defines the target the loop is judged againstLoop cannot be judged at all
Run 1 and run 2 job logsShow each failure and its sizeLoop collapses to a single successful run
Analyst diagnosis notesExplain why each run failed, in plain languageFixes look like guesses
Customer creation entries and mapping versionShow exactly what changed between runs, and who changed itCannot tell repair from luck
Run 3 job logShows the passWeak: the final ERP balance also shows it
Signed reconciliationConfirms the bucket check and a named approverEnd point is unverified

The middle rows, diagnoses and fixes, are the heart of it, and they are the most likely to be lost. Microsoft's documentation notes that by default, Dynamics 365 deletes job history and related staging data older than 90 days. A company that migrated years ago on default settings may have no runs 1 and 2 in the tool, only in exported error files or project folders. The evidence gaps page covers those losses in detail.

Why real loops differ from generated ones

Vendors such as Appen market agentic AI data services built around failure-mode taxonomies, golden trajectories and verifiers. That shows the category exists. It does not show demand for any particular company's migration records, and SourceX does not claim to have bought this type of data. What a real loop offers that a generated one may not is the odd, compound failure, like a missing master record masking a sign error, discovered and fixed by people working to a deadline. Whether generated failures can stand in for that is part of the debate over whether synthetic data will replace real data.

Similar retry trails appear in month-end loads, bank file changes and integrations. Process mining shows how event logs reveal such patterns across a business, and the software workflow example pack covers software workflow records more broadly. Reconciliation breaks more broadly are under reconciliation exceptions.

Who owns the loop, and does the company qualify?

Migration records usually belong to the operating company, though an outside implementation partner may hold copies under its engagement contract. The controller or CIO typically owns them, and the CEO can authorize a licensing discussion.

The 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.

Unknown until SourceX reviews it: how many loops survive intact, how customer details are de-identified, buyer interest and any offer. Partners stay at metadata level: which systems, how many migrations, how many years, who owns the files. The review packet contents list shows what the company would assemble later. More record families are in 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 a client's controller can describe a migration like this one with the failed runs and fixes still on file, register as a partner, check who qualifies, and read the program terms before introducing the CFO.

  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 this example based on a real migration?

No. The company, counts and amounts are invented to show the shape of a recovery loop. The import tool behavior it relies on, such as per-run success and failure counts, comes from Microsoft's published documentation.

Would a single loop like this be worth anything on its own?

Unlikely. Value, if any, comes from many loops across years and projects, each with its runs, fixes and sign-off intact. One example shows what to look for, not what an archive is worth.

Do I need to understand accounting to spot this in a client?

No. Ask whether failed loads were kept, whether fixes between attempts were written down, and whether someone signed a final reconciliation. The controller will know.

Sources

  1. papers.nips.cc/paper_files/paper/2023/hash/1b44b878bb782e69…
  2. learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/data-…
  3. appen.com/agentic-ai
  4. 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