Skip to content

Reconciliation & Balancing — GRH

Scope

Document late transactions, automated rechecks, cross-day matching, and balancing. GRH may use additional state beyond Google Sheets; verify before committing any implementation description.

Required safety rules

  • Do not mutate a transaction record based on amount alone.
  • Use stable API transaction identifiers and compare relevant fields.
  • Distinguish OPEN, REOPENED, and RESOLVED conditions if present in the actual implementation.
  • Define who can transition an issue to RESOLVED and avoid silent status rewriting.
  • Prevent balancing and live recording from competing over the same date section.

Questions to verify

Exact source-of-truth, audit windows, lock ownership, daily cutoffs, historical state persistence, and recovery from partial writes.