Reading payment schedules before you open the ledger
How to extract contractual payment triggers so ledger testing does not chase the wrong invoice dates.
Most payment disputes start with a calendar mismatch. The contract names a trigger — delivery acceptance, month-end, or architect’s certificate — while the ledger keys on invoice date. Before sampling remittances, rebuild the payment schedule on paper.
Start with the executed PDF
Pull the payment clause, every amendment, and any side letter that changes timing. Note grace periods and weekend rules. Hong Kong banking cut-offs often explain why a “late” remittance is still within a contractual business-day window.
Build a trigger table
For each obligation, record:
- Trigger event
- Number of days to pay
- Currency and any FX reference
- Document that proves the trigger occurred
Only then export AP/AR detail. If the trigger table is incomplete, ledger testing will produce noise rather than findings.
Common traps
- Price lists attached as schedules that were replaced mid-year
- Retainage release dates tied to defects liability, not practical completion
- Offset rights buried in set-off clauses that AP never applied
When Digital Toolset begins a contract compliance verification audit, this schedule is the first working paper we clear with the client coordinator.