12 May 2026
When matching tolerances quietly rewrite your control story
Tolerance bands look like configuration trivia until they decide which differences never reach a human eye.
Most reconciliation policies still speak in human language: differences above a threshold require review; forced clears need dual approval. Inside the application, a tolerance band may already be clearing those differences before anyone sees them.
During a recent full application audit, we found a bank module whose tolerance had been widened after a noisy month of FX noise. The policy document was never updated. Exception volume fell; so did the trail of who had looked at mid-size differences.
What to check before you widen a band
- List the difference amounts that will newly auto-clear.
- Confirm whether the audit trail still records a human decision or only a system clear.
- Ask who owns the decision to widen — and who reviews it after the next close.
If your reconciliation management application lets tolerances differ by ledger or entity, map them side by side. Mergers especially leave mismatched bands that nobody intended to keep.
Space Reason’s configuration & control review is built for exactly this moment: before the change goes live, not after the auditor asks why the queue went quiet.