One payment can have several truthful states

A receipt can say paid while a processor says pending, a bank says returned, or a ledger still shows an open balance. The evidence ladder gives each state a distinct proof requirement so teams stop treating an authorization, submission, settlement, return, correction, and refund as interchangeable events.

An IRS fact sheet published in July says eligible business-account users can view recently processed payments and see whether a payment was returned or refused. On July 27, Ofgem reported that proactive monitoring, system alerts, strong governance, and reconciliation improve billing performance. Together, these current public signals reinforce a basic control: status labels should be observable and reconcilable.

Connect receipt, tender, location, and operating context through the ServingIntel Genesis operating record.

Define the seven rungs

  1. Authorized: permission exists, but funds may not have moved.
  2. Submitted: the payment instruction entered the expected channel.
  3. Processed: the receiving system accepted and recorded the event.
  4. Settled: an independent account or settlement record proves movement.
  5. Returned or refused: the original instruction did not remain effective.
  6. Corrected or refunded: a linked reversal or replacement was issued.
  7. Reconciled: receipt, settlement, ledger, and customer-visible status agree.

The IRS Summer 2026 Business Tax Account fact sheet illustrates why processed, returned, and refused deserve separate visible states.

Attach evidence to every transition

Store the transaction identifier, prior state, new state, event timestamp, source system, amount, tender, location, initiator, approver, reason, external reference, and reconciliation owner. Preserve the original record; never overwrite it to make the latest screen appear consistent.

Use the ServingIntel solutions overview to assign system and operating owners. For web checkout, pair the ledger with the POS Websites checkout price proof.

Reconcile with independent proof

Do not confirm settlement using the same interface that submitted the payment. Compare the receipt, processor event, deposit or account record, general ledger, tax record, loyalty adjustment, and customer notice. The Federal Reserve's payment-systems explainer provides neutral context for the distinct roles involved in payment processing and settlement.

Build an exception query with the ServingIQ three-table evidence framework so every unresolved rung has an owner and source.

Run the daily exception queue

  • Authorized or submitted payments that never become processed.
  • Processed payments that lack independent settlement evidence.
  • Returned or refused payments still shown as paid.
  • Refunds without a linked original transaction or verified destination.
  • Ledger, tax, loyalty, and customer-notice amounts that disagree.

Ofgem's July billing-performance assessment is a current regulatory example of monitoring and reconciliation as operating controls. Track recurring exception patterns through ServingIntel News & Insights and route unresolved incidents through ServingIntel support resources.

The closeout test

Close the exception only when the original event remains intact, the state sequence is explainable, independent evidence proves the final state, every dependent record agrees, and the customer-facing message matches the books.

The bottom line: a payment status is a claim. The evidence ladder makes finance prove that claim before the exception disappears from view.