Reconciliation — PW¶
Reconciliation compares API records to Sheet records, keeps an auditable issue history, and separates diagnosis from data repair.
Typical results¶
| Result | Interpretation |
|---|---|
| MATCHED | Matching eligible API and Sheet records |
| API_ONLY | Eligible API record absent from Sheet |
| SHEET_ONLY | Sheet record not found in eligible API data |
| MISMATCH | Relevant transaction fields differ |
Historical operational constraints to verify¶
- Certain API-only records may be intentionally excluded by rule. Exclusions should be documented explicitly and reviewed periodically.
- Distinguish
OPEN,REOPENED,RESOLVEDfor issue lifecycle, where the current system supports them. - A repair/backfill process must not silently claim an issue resolved: only the reconciliation process should confirm that the discrepancy has disappeared.
- Balancing must coordinate through the same effective lock as transaction writing, with rechecks before any writes.
- Review the currently deployed date-section and ledger/cursor rules before enabling auto-balancing.
Report checklist¶
Date, vendor, total approved API count, eligible count, Sheet count, matched count, API_ONLY, SHEET_ONLY, ignored cases, unresolved issues, and sanitized references to run logs.