Keep a recorded payment that has not cleared the statement from being selected to force a match. Preparation only, not an account action.
Download the free skill
One complete Markdown file. No subscription or fabricated setup files.
Download SKILL.mdWhat to provide
Payment IDs, register dates, bank statement period, clearing evidence and next-period coverage.
How it works
- Match transaction IDs and amounts to the actual statement.
- Separate recorded payments from statement-cleared payments.
- Carry unmatched payments as evidence questions rather than selecting them for a zero difference.
- Return a timing register without changing checkmarks or ledger entries.
The output
payment | recorded_date | statement_match | cleared_evidence | next_period | hold
Worked fictional example
Fictional payment 100 is in the ledger but absent from the supplied bank statement. Its date alone is not clearing proof. Do not select it solely to remove a 100 difference.
Checks and limits
Keep source versions and original values. Unknowns stay unknown. Use qualified review for regulated, legal or hiring decisions. No live account compatibility test, send, share, schedule, ledger change or payment is authorized.
More bookkeepers workflows · How-to guides
Method: reviewed source. Demand lead: Oct12 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude38, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia100. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured. Checked October 12, 2026.