# Partner statement evidence worksheet

Fictional worked example and reusable blank card. No payment, refund or collection action. This file explains supplied records; it is not a provider export specification, earnings-completeness audit or proof of an account balance.

## Files and fixed rule

[Download the fictional receipt journal](/learn/resources/partner-statement-events.csv) and [Download the proposed statement](/learn/resources/partner-statement-proposed.csv). Both use UTF-8 CSV. Preserve the original bytes before making a separate review copy.

Select source `fictional-provider`, partner `P-A`, currency `USD`, cutoff `2026-11-15T15:00:00Z` inclusive. Both an event's occurrence and receipt times must be at or before cutoff. Amounts are integer minor units: `amount_minor=1500` with `currency=USD` means USD15.00; `amount_minor=1000` with `currency=EUR` means EUR10.00 in this fixture. Do not total across currencies or assume every currency has two minor-unit digits.

A receipt ID records one arrival. The source+event ID identifies evidence: identical payload replay counts once; different payloads under that same key put every named record on hold. Exclude receipt ID and receipt time when comparing payloads. Group keys as separate fields, not a concatenated string. For an unconflicted source+record kind+record ID, use the greatest eligible revision; conflicting greatest revisions remain on hold. Receipt arrival order cannot promote a payment status.

An approved commission without a linked payment is approved/unsettled in this snapshot. A paid claim requires a matching, unconflicted, eligible payment with status `settled`, the same source, partner, currency, commission reference and full amount. Processing, missing and mismatched evidence stays on hold. These statuses are invented for this exercise, not a provider's API contract. Partial and grouped payments need a separate allocation policy.

## Completed statement card

Owner: fictional operator. Statement selection: P-A / USD. Review cutoff: November 15, 2026, 15:00 UTC. Overall result: **unresolved — six selected lines on hold and one separate unresolved adjustment**.

| Line / source commission | Proposed amount and label | Evidence at cutoff | Review disposition |
| --- | --- | --- | --- |
| S01 / C101 | USD15.00 approved | E-C101: approved, 1500; no payment reference | Approved/unsettled; no linked settlement evidence |
| S02 / C102 | USD8.00 pending | E-C102: pending, 800 | Pending; exclude from settled money |
| S03 / C103 | USD16.00 approved | E-C103: approved, 1500 | Hold; proposed minus source = USD1.00 |
| S04 / C104 | USD22.00 paid | M104 revision 1 is processing; revision 2 occurs after cutoff | Hold; processing is not settled |
| S05 / C105 | USD30.00 paid | M105: settled, 3000; A105 later records unresolved -500 | Retain historical settled evidence; show separate adjustment |
| S06 / C106 | USD12.00 paid | M106: settled, 1200; repeated as R16/R17 under one event ID | Evidenced settled once; second receipt adds nothing |
| S07 / C107 | USD9.00 paid | Approved 900 exists; M107 does not | Hold; payment evidence unknown, not zero |
| S08 / C108 | USD7.00 approved | E-C108 occurs with 700 and 900 payloads | Hold both payloads; no winning source amount |
| S09 / C109 | USD11.00 approved | Partner P-B | Excluded from P-A statement and partner-visible output |
| S10 / C110 | EUR10.00 approved | Currency EUR | Excluded from USD subtotal; no conversion |
| S11 / C999 | USD6.00 approved | No source commission | Hold; unknown source evidence |
| S12 / C112 | USD5.00 paid | M112 occurred 14:59 but arrived 15:01 | Hold at 15:00 cutoff; later arrival cannot repair that snapshot |

The two excluded rows remain in this fictional operator review so the exclusion can be checked. A real partner-facing page must not reveal another partner's rows.

| P-A / USD evidence section | Count | Amount |
| --- | --- | --- |
| Pending | 1 line | USD8.00 |
| Approved/unsettled | 1 line | USD15.00 |
| Evidenced settled | 2 lines | USD42.00 |
| Hold | 6 lines | Not a reconciled subtotal |
| Separate unresolved adjustment A105 | 1 adjustment | USD-5.00 |

Keep M105's USD30.00 historical evidence intact. Do not relabel USD42.00 minus USD5.00 as a newly verified USD37.00 payment; no corresponding payment exists. Do not sum pending+approved+settled into a payable total. A105 is linked to C105 and remains a question for the authoritative source, not an instruction to take money back.

Receipt audit: 19 arrivals; 2 after cutoff; 17 eligible receipts; 15 distinct source/event keys; 1 exact extra receipt; 1 conflicting event key with 2 payloads; 14 accepted unique events. These counts describe evidence receipts, not commissions, partners or payments. Proposed-row partition: 12 = 10 selected + 2 excluded; 10 selected = 1 pending + 1 approved/unsettled + 2 evidenced settled + 6 hold.

## Blank statement card

- Statement owner and review date:
- Authoritative source and evidence location (no secret credentials):
- Partner identifier / access owner:
- Currency / documented minor-unit exponent:
- Period and cutoff / timezone:
- Do occurrence AND receipt times bound this snapshot? State exact rule:
- Event identity / duplicate and conflict rule:
- Record revision / ordering rule:
- Declared settlement evidence requirement:
- Partial/grouped payment allocation policy, or explicitly excluded:
- Complete export evidence available? Unknowns and omitted-scope limits:
- Intended reader: operator or the one authorized partner:

| Statement line | Source commission ID/revision | Claimed amount/status | Payment reference and evidence | Difference or missing evidence | Disposition / next evidence needed |
| --- | --- | --- | --- | --- | --- |
| | | | | | |

### Separate adjustments

| Adjustment ID and source event | Linked commission / historical payment | Signed amount and currency | Status / evidence needed | Action actually authorized |
| --- | --- | --- | --- | --- |
| | | | | None from this worksheet |

### Review before using the explanation

- Every selected line has an owner, currency, source lineage and one disposition; a blank is not zero.
- Duplicate events cannot add payments; conflicts remain visible rather than choosing the larger or later-arriving value.
- Another partner's records and currencies do not enter this statement.
- Historical payment evidence and later unresolved adjustments remain separate.
- A clean supplied-line result is not proof the source export included every earning or payment.
- Partner access is tested across detail, list, search and export; operator-only receipts and internal notes stay private.
- Only the source system can authorize the payment decisions. This explanation view has no pay/refund/approve/clawback action.

## Carry the requirements into Overskill

For native affiliate setup, read [the existing help](https://www.overskill.com/help/articles/paying-affiliates-to-promote-your-app) first. If a separate read-only explanation view is useful, open [the partner-statement app brief](https://www.overskill.com/learn?recipe=reconcile-a-partner-statement#brief-builder), edit its fields, and keep **Use this guide’s access rules** selected. Inspect the generated prompt before using **Start build**. **Copy brief** is available if you are still comparing options. The link imports no file or data.

State the one-partner permission boundary, unresolved evidence, separate adjustments and absence of payment controls explicitly. Keep sensitive partner information out of the initial brief. Supply the fictional files separately only where supported, and test source mapping and privacy before using real records.