A credit balance is a state to investigate, not an automatic refund instruction. Start with account reference, balance date, transaction history, payments, adjustments, reversals, transfers, and prior review. The goal is to explain how the credit arose and identify the decision that remains with the owner.

Compare like with like

A statement balance, account ledger, remittance line, and payment batch may use different dates. Preserve original values and label calculations. Amount and date alone are weak evidence when payments are split, batched, reversed, or posted late. Keep the opening population and exclusions visible.

Use supported credit, duplicate-risk, source missing, transfer candidate, refund review, access limited, and unresolved as separate states. A support specialist can reconstruct chronology and prepare a packet. The role must not refund, transfer, write off, change an account, or resolve identity and privacy questions outside the assigned boundary.

Preserve alternatives

For each candidate, show originating event, current balance, competing explanations, and missing proof. If a payment could belong to two accounts, preserve both histories and ask which approved evidence establishes the destination. Do not remove an incomplete item because it makes a report untidy.

Close with an approved reference, documented hold, or next review. Retain rejected matches and reasons. If a later reversal changes the state, append it rather than erasing the earlier observation. This creates a usable trail across shifts.

### Control points

  • Preserve account and transaction versions.
  • Compare the same unit and date convention.
  • Label observed, calculated, and unresolved amounts.
  • Keep competing destinations visible.
  • Never refund from a candidate match.
  • Reconcile every starting record.
  • Link approval to the resulting event.
  • ## Operating notes

+1. Write the operating purpose in one sentence before naming a metric, because a number without a decision context can invite the wrong action.

+2. Use the smallest stable identifier available and record where it came from, while keeping unnecessary personal or account details inside approved systems.

+3. Preserve the source wording beside any summary so a later reviewer can distinguish an observed fact from a preparer's interpretation.

+4. Record the date an event occurred, the date it was received, and the date it was reviewed when those moments have different operational meanings.

+5. State the timezone and business-day convention before comparing records created by people or systems working in different locations.

+6. Keep a missing source separate from a source that was not searched, and keep both separate from a source that was found but access-limited.

+7. Describe a calculation with its inputs and formula so another specialist can reproduce it without trusting an unexplained remainder.

+8. Do not borrow a field from a similar record merely because the target record is incomplete; similarity is a search clue, not evidence.

+9. Give every exception a named owner and one bounded question, rather than sending a broad request that hides several unrelated decisions.

+10. Set a next review date that follows the evidence or deadline, and record why that date is appropriate to the source.

+11. Use a carry-forward state when work is incomplete at a cutoff, and preserve the reason instead of counting it as silently finished.

+12. Retain rejected candidate matches because they explain why a plausible alternative was not accepted by the reviewer.

+13. Keep preparation, approval, posting, correction, communication, and release as distinct events in the record.

+14. Make clear which role may inspect, calculate, draft, approve, change, or communicate each part of the workflow.

+15. Treat a later event as an addition to history; do not erase an earlier observation simply because the current state looks cleaner.

+16. Compare periods only after checking that the source population, filter, definitions, and exclusion rules are materially the same.

+17. Report excluded, duplicate-risk, access-blocked, and unresolved items beside completed items so the denominator remains understandable.

+18. Explain a changed category or filter before describing a lower queue count as improvement or a higher count as deterioration.

+19. Use a specific exception status that tells the next person what evidence is missing and what action is permitted next.

+20. Do not use a generic pending label when the queue is waiting for different people, sources, or decisions.

+21. Preserve the source path and capture time for portal checks, exports, correspondence, and generated reports.

+22. Limit copied information to what the next reviewer needs, particularly when a working note could otherwise expose protected data.

+23. Route permission questions through the approved owner path and never use another person's account to complete a check.

+24. Keep a version link when a report, invoice, claim, statement, or source document changes after the first review.

+25. Record the exact event that caused a row to reopen, rather than describing the reopening as a general correction.

+26. Close a row only when its approved result, documented hold, or accountable carry-forward is visible.

+27. Use a short final reconciliation to prove that the opening population did not lose records between intake and disposition.

+28. Review a sample of completed rows for source traceability, boundary compliance, and clear next action before trusting an aggregate measure.

+29. Escalate contradictions early, because a confident summary built on conflicting sources is harder to repair than an explicit unresolved state.

+30. Make the handoff useful to a new shift: source, current state, evidence, owner, question, deadline, and next review should be findable together.

Add a stop point before disposition

Before a credit balance is refunded, transferred, or left open, perform a separate stop-point review. Confirm the balance is tied to the correct account, that every payment and adjustment is represented, and that no pending reversal or duplicate transaction could change the result. The preparer can assemble this packet and show the arithmetic. The authorized owner decides the disposition and records the reason. Keeping that final choice separate from investigation prevents a plausible explanation from becoming an unreviewed financial action.