# Environment reproducibility gap analysis | SourceX

Canonical: https://refer.sourcex.si/questions/environment-reproducibility-evidence-gaps
Last updated: 2026-11-04

Six gaps make environment reproducibility hard to assess in an ERP inventory archive: an expected figure that was recalculated, no way to stop history at a date, undated software and extension changes, integrations nobody listed, shared logins that hide who posted an adjustment, and investigations that never recorded a cause. Each can be spotted from metadata, without opening a record. None rules a company out; each narrows which past situations could be rebuilt and checked.

This page is part of [environment reproducibility](/guides/concept-environment-reproducibility). Its job is a gap analysis: set what a replay review would expect beside what ordinary distributors and manufacturers keep, then show how to describe the difference plainly in an introduction.

## The six things a replay review looks for

A reviewer judging whether past stock mismatches can be rebuilt asks two questions of each case: will the rebuilt state match the original, and is the right answer on record? Builders of agent environments frame the first question the same way. Toloka (on a page checked October 18, 2026) describes versioned environments, deterministic resets and controlled seeds as what allows exact replay. A company archive has no seeds, so dated records have to play that role.

| Evidence | What it proves in a replay |
|---|---|
| Expected figure kept as posted | The "system said" side of the mismatch is the original one |
| Date cut-off | The rebuild contains nothing posted after the count |
| Version and extension log | The same postings will behave the same way |
| Integration list | Nothing the live system received is silently missing from the copy |
| Named posting accounts | Each adjustment can be tied to a role and its authority |
| Recorded cause | The case has an answer key, so a replay can be scored |

## Typical holdings against the review's expectations

Companies rarely hold all six cleanly. The pattern below describes ordinary operating archives; it is not a statistic.

| Evidence | What companies usually have | What tends to be missing | What a partner can ask |
|---|---|---|---|
| Expected figure kept | Posted count journals in the ERP | Journals deleted and recalculated before posting, or older years purged | "Are count journals archived as posted?" |
| Date cut-off | Nightly backups kept for weeks | Backups older than the retention window; no dated sandbox copies | "How far back do dated backups go?" |
| Version and extension log | Current version and extension list | Dates of past upgrades and installs | "Is there a log of upgrade and extension install dates?" |
| Integration list | Knowledge in the ERP administrator's head | A written register of feeds active on each date | "Which feeds post into the ERP, and are they listed anywhere?" |
| Named posting accounts | Named users for office staff | Shared scanner or warehouse logins; change log never activated | "Do warehouse staff post under their own accounts?" |
| Recorded cause | Write-off entries with amounts | A reason code or closing note naming why | "Do variance investigations end with a reason code?" |

Microsoft's documentation explains why two of these matter more than they look. It tells Business Central users to keep originally calculated journal lines rather than recalculate, because expected inventory might change. And it describes a copied environment as keeping version and extensions while clearing base-application integration settings and not syncing with the source afterwards. A copy, in other words, carries some starting conditions for you and drops others; only a written integration list says which.

## Illustrative gap profile: a 230-person building-supplies distributor

This company is fictional, and the percentages are invented to show how a profile reads. Each figure is the share of the last three years for which that evidence exists, as the controller and ERP administrator estimated it in conversation.

| Evidence | Share of history covered | What is missing | Effect on a replay |
|---|---|---|---|
| Expected figure kept | 90% | Journals for one warehouse recalculated during a 2024 stock take | That warehouse's mismatches from that period lose their original gap |
| Date cut-off | 60% | Backups older than 14 months were rotated out | Older cases can only be cut off by filtering postings, which the reviewer must test |
| Version and extension log | 45% | Upgrade dates before last year were never written down | Cases before the log starts carry a version question |
| Integration list | 35% | An EDI feed and a scanner app were added without a register | Postings from those feeds may be missing from any rebuild |
| Named posting accounts | 70% | Two yard scanners shared one login | Adjustments from the yard cannot be tied to a person or role |
| Recorded cause | 50% | Half of write-offs closed with an amount only | Half the cases have no answer key |

Read across the rows, not down the column. The strongest cases are those where all six exist for the same date range: here, roughly the last twelve months at the main warehouse. That overlap, not any single percentage, is what an introduction should describe.

## Why a start without an outcome, or an outcome without a start, falls short

The last row decides value. A rebuildable starting state without a recorded cause gives a reviewer a puzzle with no answer key: any explanation a person or a model produces cannot be marked right or wrong. A recorded cause without a rebuildable start gives a story nobody can check, because the figures it explains may have moved since.

The workflow that produces the cause, a cycle count variance investigation, is covered on its own [data type page](/data-types/cycle-count-variance-investigation). Where an owner is reluctant to let records leave its systems at all, [compute-to-data](/questions/compute-to-data) explains an arrangement some buyers use, which is a matter for the agreement, not the introduction. For the demand side, see the evidence that [AI companies pay for data](/proof/ai-companies-pay-for-data).

## Wording the gap honestly in an introduction

Describe each gap in one line, with who could close it. Three examples, written for the fictional distributor above:

- "Count journals are kept as posted, except one warehouse in 2024; the controller can identify the dates."
- "Dated backups cover the last 14 months; older history can only be cut off by filtering postings."
- "About half of variance write-offs record a cause; the operations director says the share has risen since a reason-code list was introduced."

Avoid three phrasings: "all our history is reproducible" (untested), "we can rebuild anything" (versions and feeds say otherwise), and "the data is clean" (cleanliness is not the question). The eligibility gates still come first: 50 or more 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.

To turn these answers into a fit rating, use the [qualification scorecard](/questions/does-environment-reproducibility-data-qualify); once the owner agrees to proceed, the [review packet](/resources/environment-reproducibility-review-packet) lists what the company prepares. More record families sit under [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 gaps you found leave at least one date range where all six kinds of evidence overlap, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [terms](/terms), then introduce the owner with the gaps written down.

## Sources

- https://learn.microsoft.com/en-us/dynamics365/business-central/inventory-how-count-adjust-reclassify
- https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/tenant-admin-center-environments-copy
- https://learn.microsoft.com/en-us/dynamics365/business-central/across-log-changes
- https://toloka.ai/virtual-environments-rl-gyms
- https://refer.sourcex.si/terms
