Foundation 03 · Reconciliation and disputes

Make exceptions
operable.

A transaction is not complete when a system emits a success code. Reconciliation compares records across parties; disputes, refunds, reversals, duplicate requests, partial delivery, and missing evidence determine whether the commercial state can be trusted.

Learning boundary. This lesson is an educational operating model, not dispute, banking, accounting, legal, or consumer-finance advice. A matching identifier or terminal state does not prove that two counterparties agree, that a refund was received, or that an external obligation was resolved.

Learning objective

Design the recovery work around a disagreement.

By the end of this lesson, you should be able to model internal and external records, duplicate and reversal conditions, dispute ownership, evidence windows, partial delivery, and the action that must remain blocked until reconciliation completes.

01 · Match

Which records agree?

Compare request, authorization, capture, settlement, delivery, refund, and ledger records by stable references, amount, currency, time, and counterparty.

02 · Duplicate

Did work repeat?

Track idempotency keys, retries, duplicate charges, and repeated fulfillment requests. A retry is not proof that the first attempt failed.

03 · Dispute

Who owns the case?

Name the resolver, evidence packet, response window, hold, and escalation path. Do not let an agent adjudicate a dispute merely because it can read the records.

04 · Repair

What can be reversed?

Separate refund, reversal, replacement, credit, cancellation, and manual correction. Preserve the original record rather than overwriting the disputed history.

Practice lab

Reconcile the split record.

A client sees one settled payment, the merchant ledger shows two authorization attempts, and the fulfillment system reports only one delivered item. The agent proposes a refund but cannot determine which record owns the customer’s acceptance.

  1. Build a cross-system record table using IDs, amount, time, status, and source.
  2. Mark the duplicate, the delivered unit, the unresolved acceptance, and the dispute owner.
  3. Define which automated actions must pause until the records are reconciled.
  4. Write the evidence packet required for a refund, replacement, or escalation decision.

Source shelf

Study records, messaging, and payment-data scope.

  1. ISO 20022 message definitionsUse structured financial-message definitions to study the data needed to compare payment events and counterparties, without treating a message as a full commercial ledger.
  2. JSON-RPC 2.0 specificationReview request IDs, errors, notifications, and batch behavior as a parallel lesson in correlating retries and failures.
  3. PCI Security Standards Council: PCI DSSStudy payment-account data protection and responsibility boundaries. It does not define a universal dispute or agent-commerce operating model.

Continue the pathway

Next: map the
incentives.