Implementing Cloud Financials: From Empty Pod to Go-Live · Module 6 · Banks, Branches and Cash Management
Reconciliation rules and tolerances
Lesson 62 of 153 · 11 min
The statement says 4,182.60 out on the fourteenth. The system has a payment for 4,182.60 issued on the twelfth. Same thing? Probably. How does the system know? Four match types: one-to-one, one-to-many, many-to-one, many-to-many. One-to-many is a single bank debit covering a payment batch, and it is extremely common — which is why a rule set that only handles one-to-one matches almost nothing in a real estate. Then tolerances. Date tolerance handles clearing lag. Amount tolerance handles bank fees deducted at source and FX rounding. Both need a number, and the number is a business decision rather than a technical default. Two failure modes, and they are opposites. Tight tolerances mean more manual matching. Loose tolerances mean the system confidently matches things that are not the same. Start tight and loosen based on evidence from the first two months. Then the walkthrough: build a rule set with two rules, set…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Cloud Financials: From Empty Pod to Go-Live, with a certificate on completion and a fourteen-day refund window.