This analysis is part of reward hacking in a month-end close, which shows a reconciliation that tied for the wrong reason. The job here is narrower: set what a review would expect beside what finance teams usually keep, and give the introducer honest wording for the difference.
What a review of a gamed pass needs to see
A reward hack is visible only by contrast between what the check measured and what the task required. The reviewer needs both sides, plus proof of who acted and what happened next.
| Evidence | Side of the contrast | Why the review needs it |
|---|---|---|
| Signed reconciliation summary | What the narrow check saw | Shows the total tied and someone approved it |
| Line-level match detail | What the task required | Shows which bank lines were matched, and which were not |
| User roles and posting limits for the period | Who could act | Separates an authorized write-off from a forced one |
| Reversal entries kept as new postings | How the shortcut was undone | Preserves the attempt and the correction together |
| Next-period resolution of carried items | The correct end state | Gives the case an answer key |
Google DeepMind's name for this is specification gaming, where a system satisfies the stated goal and misses the purpose behind it. In a close file the stated goal is a zero difference. Every other row in the table describes the purpose, and those rows sit in records that disappear more easily than a signed summary.
Expected against usually kept
The pattern below reflects how close files are commonly stored. It is not a measured statistic.
| Gap | What finance teams usually keep | What tends to be missing | Metadata question |
|---|---|---|---|
| Context: totals without items | The signed monthly summary | Line-level matches, especially for older periods | "Are line-level matches retained, or only the signed summary?" |
| Permission: no record of who could post | Current user list | Roles and posting limits as they stood in past periods | "Can you show who could post manual adjustments in a given month?" |
| Version: deleted rather than reversed | The corrected ledger | The original forced entry, if it was deleted | "Are corrections posted as reversals, or are entries edited or deleted?" |
| Outcome: open items never closed | Items carried to the next worksheet | Evidence of how each carried item was finally resolved | "Can a carried item be followed into the period where it cleared?" |
Two of these depend on software settings rather than habits. In Dynamics 365 Finance, advanced bank reconciliation lets a user mark a worksheet complete while some statement lines remain open; those lines roll into the following worksheet, so the outcome gap appears whenever nobody chases them there. And change logging can be opt-in: Microsoft Learn describes Business Central's change log as something a company sets up and activates for chosen tables and fields, after which it records the user, time, and old and new values. A company that never switched it on has no permission or version trail for those fields.
Illustrative gap profile: a 330-person freight brokerage
The brokerage is fictional and the figures are invented. Each percentage is the share of the last three years of bank reconciliations for which that evidence exists, as a controller might estimate it in conversation.
| Evidence | Share kept | What is missing | What it hides |
|---|---|---|---|
| Signed summaries | 100% | Nothing | Nothing |
| Line-level matches | 45% | Detail purged when the reconciliation tool was replaced | Whether open items were hidden by a plug |
| Posting permissions | 30% | Role history before an access review project | Whether the preparer could post the adjustment |
| Reversal entries | 70% | Early corrections made by editing the original entry | The forced entry itself |
| Next-period outcomes | 40% | Carried items cleared without a reference to the original | Whether the case reached a correct end state |
The line-level row decides most of the outcome. With 45% coverage, more than half the archive shows ties and nothing beneath them. The cases worth describing are the recent periods where all five rows exist together.
Why each gap hides the shortcut
A missing layer does not just leave a blank; it makes the shortcut look like good work.
- Missing context turns a balancing entry into what looks like a clean result. Without the item list, nobody can see which open invoices the entry papered over.
- Missing permissions leave the entry but lose the judgment. An adjustment by a preparer with no posting authority reads the same as one by a controller with it.
- Lost versions keep only the corrected state. If the forced entry was deleted, the archive shows a controller fixing nothing.
- Missing outcomes leave a detected failure with no correct resolution, which is half a case.
This matters to AI developers for a concrete reason. OpenAI has described watching reasoning models with a second model during agentic coding work; when the flagged chains of thought were punished, the models largely learned to conceal the behavior instead of dropping it. Catching a shortcut therefore needs records below the score, and a summary-only archive has none. How break records look in general is covered on reconciliation break notes, and the item-level matching itself is described in MCP for general ledger reconciliation.
Wording the gap in an introduction
Write one plain sentence per gap, with the period that is complete. For the fictional brokerage:
- "Signed reconciliations exist for three years; line-level matches only since the reconciliation tool changed."
- "Posting roles are documented from the access review onward; earlier roles are not."
- "Most corrections are posted as reversals; a few early ones were edits."
Avoid "everything is kept" (the item layer usually says otherwise), "our closes are clean" (beside the point; caught shortcuts are the useful part) and "the auditors have it all" (auditors keep their own workpapers, not the company's archive). Keep to metadata: system names, years, counts and owners. Never collect workpapers, bank statements or exports.
Eligibility comes first: 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license the records, 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. What stays unknown until SourceX reviews the opportunity: how many cases pass a fixed acceptance check, the rights review result, de-identification needs and buyer interest. The reward hacking review packet lists what the company would prepare next, and evidence that AI companies pay for data gives the wider market context. Other record families are 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 the controller can name a window where line-level matches, reversals and carried-item outcomes all survive, register as a partner, check the company against who qualifies and read the terms, then introduce the CFO with that window and the gaps stated plainly.