This scorecard is part of environment reproducibility, which walks one inventory mismatch through an ERP sandbox. Here the job is narrower: deciding whether a particular client is worth introducing for this kind of record, and stating how strong the fit looks before anyone at SourceX reviews it.
How the reproducibility scorecard is scored
Each criterion earns 2 points when strong, 1 when borderline and 0 when weak, for a maximum of 14. Three criteria are gates: if headcount, rights or the authorized contact scores 0, the total does not matter until that is fixed.
| Total | Zone | What it means for the introduction |
|---|---|---|
| 11 to 14 | Strong | Past states look rebuildable and answerable; introduce with the open items named |
| 6 to 10 | Borderline | Real inventory history, but cut-off, versions or outcomes need confirming |
| 0 to 5 | Weak | The opportunity is mostly theoretical; resolve the gaps before taking an owner's time |
Why these criteria rather than a general data screen: a rebuilt state is only useful if its starting conditions match the original and its ending is known. Microsoft's Business Central documentation makes the first point in plain terms. The Calculate Inventory action creates journal lines with a calculated quantity, posting a different counted quantity adjusts stock, and users are told to keep the originally calculated lines and not recalculate, because expected inventory might change. A recalculated "expected" figure quietly changes the case.
Seven criteria, applied to rebuilding a past inventory state
The general screen lives in the company qualification checklist. This version applies it to ERP inventory history.
| Criterion | Strong (2) | Borderline (1) | Weak (0) | Who answers it |
|---|---|---|---|---|
| Company size (gate) | Well over 50 full-time employees at peak | Near 50; needs confirming | Under 50 full-time, or mostly contractors | CEO or HR lead |
| Operating history | Several years of postings in one ERP | Years split by a migration | Recent ERP with no prior history | Controller |
| Rights to license (gate) | Company owns its ERP records; vendor terms known | A logistics provider or parent holds part of the data | Records belong to a client or 3PL | CFO or counsel |
| Expected figure kept | Count journals archived as posted | Kept for some sites or years | Recalculated or deleted after posting | Controller |
| Date cut-off | Dated backups, dated sandbox copies or filterable postings | One method, not tested | No way to stop history at a date | ERP administrator |
| Recorded cause and change log | Reason codes or correcting entries name the cause; changes logged by named user | Causes noted in free text; change log partly on | Investigations end with no recorded outcome | Operations director |
| Authorized contact (gate) | Named executive over the ERP records | Senior contact, authority unconfirmed | Nobody identified | CEO |
Two notes on the middle rows. A dated copy only fixes a starting point if it was made at the right moment: Microsoft says a copied Business Central environment keeps the source's version and extensions but does not sync with the source afterwards, so a copy made five days late carries five days of later postings. And "who posted what" depends on configuration: Business Central's change log tracks direct modifications users make, but only for tables and fields an administrator has chosen and only once it is activated. Ask, rather than assume either way.
English share works as an extra gate outside the U.S., Canada and the EU. 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.
Strong, borderline and weak: three Illustrative distributors
All three companies are fictional. The same seven questions separate a ready introduction from a long shot.
| Criterion | 420-person food distributor | 160-person online retailer using a 3PL | 90-person spare-parts wholesaler, South Africa |
|---|---|---|---|
| Company size | 2 | 2 | 2 |
| Operating history | 2 | 1 | 1 |
| Rights to license | 2 | 1 | 2 |
| Expected figure kept | 2 | 1 | 0 |
| Date cut-off | 2 | 1 | 1 |
| Recorded cause and change log | 1 | 0 | 0 |
| Authorized contact | 1 | 2 | 1 |
| Total | 12 of 14, strong | 8 of 14, borderline | 7 of 14, borderline on paper, weak in practice |
The food distributor archives every count journal as posted, keeps nightly dated backups and closes each variance with a reason code. It loses a point because the change log was switched on only for item and location tables two years ago, and another because the COO, not yet the CFO, is the contact. Both are questions, not blockers.
The online retailer owns its sales records, but its warehouse is run by a third-party logistics provider whose system holds the counts. Ask whose records those are before anything else; the rights row moves the whole score.
The spare-parts wholesaler passes every gate, but it migrated ERPs in 2024 and recalculated opening balances, so older expected figures are gone, and variance write-offs carry no cause. Its records are almost all in English, which keeps it eligible on geography. A borderline total can hide a weak core: if the two middle criteria are both 0, treat the fit as weak.
Five discovery questions that move the score
Put these to the controller, the operations director or the ERP administrator, in this order. The early answers decide whether the later ones matter.
- When a count finds a difference, is the system's expected figure kept as it was on that day? Moves the expected-figure row. A kept journal line or a saved report counts; a figure recalculated later does not.
- Can the company stop its history at a date? Moves the cut-off row. Dated sandbox copies, dated backups or posted entries filterable to a cut-off all work.
- Are upgrades, extension installs and integration changes logged with dates? Moves the cut-off row up or down, because an undated version change spoils a replay.
- How do investigations end? Moves the recorded-cause row. Look for a reason code, a closing note or a correcting entry, plus a rough count per month.
- Who owns the ERP records, and who can approve a licensing discussion? Moves both gates. The CFO or COO usually owns them, and the CEO can authorize the discussion; if a 3PL runs the warehouse, ask whose records they are.
Before any introduction, the owner may want to read questions to ask before licensing company data. Keep a note of the owner's agreement to be introduced, as described in how to document client consent for a referral.
What the score leaves for SourceX's review
The scorecard records what the company says it holds. It cannot show how many past mismatches would actually rebuild and pass a fixed acceptance check, how supplier and customer names would be de-identified, whether an ERP vendor's or logistics provider's terms limit use, or whether any buyer wants this task type. Interest in repeatable agent tasks, explained in what RL environments are, does not mean every ERP archive qualifies.
Your role stops at metadata: which ERP, which years, roughly how many investigations a month, who owns the records. The evidence gaps analysis shows how to describe weak rows honestly, and the review packet lists what the company prepares later. Other record families are listed under 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 your client lands in the strong or borderline zone with all three gates passed, register as a partner, confirm the basics on who qualifies and read the program terms before you introduce the CFO or COO.