Reward hacking review packet: the seven metadata documents a finance team prepares, in order

Short answer

A reward hacking review packet holds seven metadata-only documents, assembled in this order: a task statement, a description of the scoring rule, an item-level retention note, an adjustment and permission summary, a review trail description, an acceptance check fixed in advance, and a volume, span and rights note. Together they let SourceX judge whether a company's close records show both the shortcut and its correction. The controller usually leads. No ledgers, bank statements or workpapers go in before an agreement.

Visual briefFull-size diagram
Seven numbered documents slide one by one into an open folder: task statement, scoring rule, item-level retention, adjustment and permission summary, review trail, acceptance check, and volume and rights note, each tagged with the role that prepares it; the folder is labelled descriptions only, no ledgers.
Illustrative packet order for a finance team. The packet describes close records; it never contains ledgers, bank statements or workpapers.

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.

OrderDocumentWhat it showsPrepared by
1Task statementThe real task each case represents, in one sentenceController
2Scoring rule descriptionWhat the sign-off actually checked at the timeController
3Item-level retention noteWhich match-level records survive, for which periodsERP or reconciliation tool administrator
4Adjustment and permission summaryHow manual entries are recorded and who could post themERP administrator with accounting manager
5Review trail descriptionWhere reviewer notes, rejections and reversals are keptController
6Acceptance checkThe test a correct case must pass, written before reviewController with CFO
7Volume, span and rights noteCounts, years, systems, third-party terms and the authorizerAccounting 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.

FieldEntry
TaskReconcile operating and payroll accounts monthly, no unsupported adjustments
Scoring ruleTie to bank balance plus preparer signature until 2024; reviewer checklist added since
Item-level detailKept for the last four years in the reconciliation tool
CorrectionsPosted as reversals; roughly 20 reversed manual adjustments per year
Review notesIn the tool since 2023; email before that
Identifiers presentBank names, vendor names, employee names on payroll lines
AuthorizerOwner-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.

  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

Who leads the packet inside the company?

Usually the controller, because the scoring rule, the review trail and the acceptance check all sit with the close process. The ERP administrator supplies retention and permission facts, and the CFO or counsel signs the rights note.

Does the introducer assemble or read the packet?

No. The introducer's part ends with the introduction. Sharing this list with the CEO simply shows the work involved before they decide to talk to SourceX.

Can the packet include one redacted reconciliation as an example?

Not before an agreement. The packet describes the class of cases in words, dates and counts. Any example record is exchanged later under SourceX's process and the agreed de-identification.

Sources

  1. anthropic.com/research/emergent-misalignment-reward-hacking
  2. openai.com/index/chain-of-thought-monitoring
  3. learn.microsoft.com/en-us/dynamics365/finance/cash-bank-manageme…
  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