Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A company processing 2,000 GSTR-2B matches per month finds that 180 of them — 9% — have variances of ₹1–₹5 between the purchase invoice amount and the GSTR-2B entry. These are GST rounding differences. Without tolerance rules, a reviewer must manually inspect all 180 items and confirm they are rounding differences. With a ₹5 tolerance rule, they are auto-resolved — and the reviewer’s time is spent on the 50 items with genuine discrepancies.
Tolerance matching is a standard reconciliation practice. The risk is in setting thresholds that are too high — which can mask genuine variances — or too low — which eliminates no exceptions.
Types of Tolerance Rules
Absolute Amount Tolerance
Auto-resolve variances where the difference does not exceed a fixed rupee amount. Examples:
| Reconciliation type | Suggested absolute tolerance | Rationale |
|---|---|---|
| GST amount rounding | ₹2 per invoice line | CGST Act rounding creates ₹1–₹2 differences |
| TDS deduction rounding | ₹5 per transaction | Percentage calculation rounding at low values |
| Bank charge variance | ₹50 per charge | Monthly bank charges vary within a small range |
| MDR fee calculation | ₹10 per transaction | MDR rates applied to varying transaction sizes |
| NACH EMI amount | ₹1 per mandate | EMI amounts rounded at mandate creation |
Percentage Tolerance
Auto-resolve variances where the difference does not exceed a percentage of the transaction value. Examples:
- TDS on high-value invoices: 0.1% of TDS amount (prevents ₹200+ rounding items from manual review)
- Platform commission: 0.05% of gross transaction value (for MDR rate fluctuations)
- Bank balance: 0.01% of account balance (for large accounts where even ₹1,000 is immaterial)
Percentage tolerances are better suited to high-value transactions where a fixed rupee amount is too restrictive.
Combined Tolerance (Amount AND Percentage)
The safest tolerance design: auto-resolve only when the variance is below both the absolute threshold AND the percentage threshold. This prevents a large percentage variance on a small transaction from being auto-resolved when the amount threshold alone would pass it.
Example: 5% OR ₹50, whichever is smaller. A ₹100 transaction with a ₹6 variance (6%) is NOT auto-resolved (exceeds 5% even though ₹6 < ₹50). A ₹10,000 transaction with a ₹30 variance (0.3%) IS auto-resolved (below both thresholds).
India-Specific Tolerance Scenarios
TDS Rounding Differences
TDS is calculated as: Invoice Amount × Rate ÷ 100. When the result is a fraction, banks round differently than the income tax calculation system. Example:
- Invoice: ₹45,750
- Section 194J rate: 10%
- Exact TDS: ₹4,575.00
- Bank credit: ₹41,175 (₹45,750 − ₹4,575)
For this invoice, no rounding occurs. But at ₹45,763:
- Exact TDS: ₹4,576.30
- Deductor may round to ₹4,576 — bank credit ₹41,187
- Or round to ₹4,577 — bank credit ₹41,186
- Form 26AS shows what the deductor actually deposited
A ₹1–₹2 tolerance handles this correctly.
MDR Fee Calculation Differences
MDR is calculated as a percentage of transaction value, rounded to the nearest paisa (or rupee, depending on acquirer). At 2% MDR:
- Transaction: ₹8,750 → MDR: ₹175.00 → no rounding issue
- Transaction: ₹8,763 → MDR: ₹175.26 → rounded to ₹175 or ₹176
The ₹1 difference between expected MDR (₹175.26) and applied MDR (₹175.00) generates an exception unless a tolerance rule is applied.
GST Rounding under CGST Act
The CGST Act provides that GST amounts are rounded to the nearest rupee. Invoices raised in the accounting system may calculate GST to two decimal places; GSTR-2B reflects the rounded value. A ₹2 tolerance per invoice line handles this consistently.
Governance of Tolerance Rules
Tolerance rules require formal governance:
- Approval: CFO or controller must approve the tolerance thresholds before they are applied in production
- Documentation: Tolerance rules are documented in the reconciliation policy with the rationale for each threshold
- Monthly reporting: A monthly report shows the volume and total value of exceptions auto-resolved under tolerance rules — reviewed by the CFO
- Annual review: Tolerance thresholds are reviewed annually against the distribution of actual variances
The key control: tolerance rules should never be changed to accommodate a growing exception queue. If the exception queue is growing because more items exceed the tolerance, the root cause must be investigated — not the tolerance widened.
What Tolerance Should Not Cover
Tolerance matching should explicitly exclude:
- GSTIN mismatches: A wrong GSTIN with a ₹1 amount difference is a compliance error, not a rounding error
- PAN/TAN mismatches: Any mismatch involving identity fields requires human review regardless of amount
- Unexplained bank credits or debits: Unknown transactions are never auto-resolved on tolerance
- Negative tolerance items: Credits where a debit was expected (or vice versa) require investigation
Reconciliation software India that supports configurable tolerance rules — separate thresholds by reconciliation type, with combined amount-and-percentage logic — enables finance teams to reduce exception queues without weakening controls.
Bank reconciliation software with built-in bank charge tolerance rules handles the most common bank reconciliation tolerance scenario (varying bank service charges) without requiring custom configuration for each account.
The Institute of Chartered Accountants of India publishes guidance on materiality thresholds in auditing — which inform the tolerance levels that statutory auditors consider appropriate for auto-resolution in reconciliation processes.