This list belongs to reward hacking in a month-end close. It comes after the introducer's part: the evidence gaps analysis explains which weaknesses the packet should state openly. Partners never assemble or handle the packet; the company prepares it for SourceX under its own agreement.
The packet in order
Each document depends on the one before it. The acceptance check, for example, refers to the scoring rule and the item-level fields, so it cannot be written until those are described.
| Order | Document | What it shows | Prepared by |
|---|---|---|---|
| 1 | Task statement | The real task each case represents, in one sentence | Controller |
| 2 | Scoring rule description | What the sign-off actually checked at the time | Controller |
| 3 | Item-level retention note | Which match-level records survive, for which periods | ERP or reconciliation tool administrator |
| 4 | Adjustment and permission summary | How manual entries are recorded and who could post them | ERP administrator with accounting manager |
| 5 | Review trail description | Where reviewer notes, rejections and reversals are kept | Controller |
| 6 | Acceptance check | The test a correct case must pass, written before review | Controller with CFO |
| 7 | Volume, span and rights note | Counts, years, systems, third-party terms and the authorizer | Accounting manager, then CFO or counsel |
Documents 1 and 2: the task and the narrow check
1. Task statement. One sentence that defines the work, not the total. For the bank reconciliation on the main guide: "Reconcile the operating account: match every bank line, explain every exception, post no unsupported adjustment." The wording matters because a reward hack is measured against it.
2. Scoring rule description. What the sign-off form or close checklist asked the reviewer to confirm in each period: often just "reconciled balance equals bank balance" and a preparer signature. Note when the checklist changed. A rule that only checks the tie is the reason a forced total could pass, so describing it plainly is the most useful sentence in the packet.
Documents 3 to 5: the layer beneath the score
3. Item-level retention note. Whether matched and unmatched lines are kept with their match type, for how many years, and in which tool. Microsoft's documentation for advanced bank reconciliation shows the level of detail to describe: lines matched one-to-one, many-to-one or many-to-many, or left unmatched and moved to the next worksheet. Say where a tool replacement cut the history.
4. Adjustment and permission summary. How manual journal entries are recorded (amount, user, timestamp, attached support) and whether user roles and posting limits can be shown for past periods. State whether corrections are posted as reversals or made by editing the original entry, since only reversals keep the attempt.
5. Review trail description. Where controller notes, items returned to the preparer and reversal entries live, and whether they are tied to the reconciliation they concern. Notes kept only in email are worth stating as a limitation rather than leaving out.
Document 6: the acceptance check, fixed before review
Without a fixed check, "the preparer forced it" is an opinion. With one, anyone holding the case can test it. Illustrative, using the main guide's example:
- ☐Every bank line is matched or listed as an explained exception.
- ☐No manual adjustment lacks supporting documentation.
- ☐Open items carried forward equal the unmatched lines exactly.
- ☐The next period shows each carried item resolved.
The preparer's version, with its $9,600 adjustment, fails the second and third conditions even though its total ties. The controller's corrected version, which reverses the adjustment and carries the $6,120 and $3,480 invoices as open exceptions, passes all four once next month shows them cleared. A check written this way cannot be met by forcing the total. Companies do not need to write such checks for AI developers; this one only tells SourceX which cases the records can support.
Why AI developers care is documented. OpenAI reports using a monitor model to flag reward hacking on agentic coding tasks, and Anthropic reports that models which learn to reward hack in production training environments can generalize to broader misaligned behavior. Real cases where a shortcut was caught and corrected show what the correct end state looks like.
Document 7: volume, span and rights
Give counts as ranges if exact numbers would take a project: accounts reconciled per month, years of close files, the share of periods with line-level detail, and roughly how many reversals of manual adjustments per year. Name the systems in plain words (an ERP, a reconciliation tool, a document store). Then the rights side: bank and vendor names appear throughout, some bank agreements limit reuse of statement data, and a named executive must be able to authorize a licensing discussion. Owners often ask how money flows if a license happens; the guide on telling a referral reward apart from the company's licensing proceeds answers that, and what happens after data delivery covers the later steps.
Illustrative cover sheet
Fictional, for a 240-person specialty food distributor. It shows the expected level of detail.
| Field | Entry |
|---|---|
| Task | Reconcile operating and payroll accounts monthly, no unsupported adjustments |
| Scoring rule | Tie to bank balance plus preparer signature until 2024; reviewer checklist added since |
| Item-level detail | Kept for the last four years in the reconciliation tool |
| Corrections | Posted as reversals; roughly 20 reversed manual adjustments per year |
| Review notes | In the tool since 2023; email before that |
| Identifiers present | Bank names, vendor names, employee names on payroll lines |
| Authorizer | Owner-CEO, with the CFO preparing the case |
The same habit of tracing a summary figure to its source runs through MCP for CFO dashboards. Eligibility still applies: 50 or more full-time employees at peak, 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. 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 the controller could fill most of the seven slots from what the finance team already keeps, register as a partner, confirm the company against who qualifies and read the terms, then introduce the CEO and let the company prepare the packet with SourceX.