# W/ Finance — The Missing Settlement

**Room:** ROOM-03 · **Portfolio stage:** Next  
**Audience:** Finance teams, accounting students, controllership, internal audit, reconciliation owners, and revenue operations

> The payment story does not end when authorization succeeds.

## Consequential question

Can finance and security reconstruct the same transaction exception from authorization through settlement, ledger, dispute, and evidence?

## Fictional scenario

A fictional authorized payment has a provider reference, no expected settlement line, a manual refund note, and two dashboards that disagree.

**Pressure:** Month-end closes tomorrow while security and finance use different identifiers and different definitions of complete.

## Five working artifacts

- [ ] Transaction-to-ledger lineage
- [ ] Five-state reconciliation record
- [ ] Exception ownership map
- [ ] Claims ledger entry
- [ ] Reopening and retention rule

# Four practice moves

## 1. Join

**Prompt:** Link authorization, token or reference, settlement, ledger, refund, dispute, and evidence identifiers.

**Output:** Lineage record

## 2. Reconcile

**Prompt:** Separate expected, observed, documented, asserted, and validated states.

**Output:** State comparison

## 3. Own

**Prompt:** Assign the exception, decision, evidence, and correction to named roles.

**Output:** Responsibility handoff

## 4. Close

**Prompt:** Record the bounded conclusion, limitation, retention, and reopening event.

**Output:** Claim disposition

## Bounded decision output

One cross-functional exception record that finance and security can independently reconstruct.

## Pilot format

A finance reader and security reader work the same fictional exception separately, then reconcile only from retained artifacts.

## Stop rule

Stop if the room produces an accounting opinion, audit conclusion, financial advice, or uses live transaction or customer data.

## Reviewed reading route

- WACK-CONTENT-0107
- WACK-CONTENT-0129
- WACK-CONTENT-0095
- WACK-CONTENT-0104
- WACK-CONTENT-0142

## Program boundary

W/ Practice Rooms is practitioner-developed commissioning material. It is not PCI SSC guidance, not an assessment, not a compliance result, not an accredited curriculum, not professional certification, and not legal, financial, healthcare, public-sector, employment, or product-validation advice. Every room uses fictional facts and requires its named pilot before expansion.