Use the specified fifty-paise rule
Section 170 of the CGST Act requires the covered amount to be rounded to the nearest rupee. A fractional rupee of fifty paise or more is increased to one rupee; a smaller fraction is ignored. The wording covers tax, interest, penalty, fine and other sums payable, and refunds or other sums due under the Act. A software function that rounds every exact half to an even number can therefore produce the wrong result at that boundary.
Identify the amount being rounded before doing arithmetic
Section 170 in ICAI’s April 2026 statutory compilation supplies the rounding rule, not a complete instruction for identifying every taxable value, return field or invoice line. Determine the legally relevant sum and its governing return or payment requirement first. Do not infer that every unit price, inventory value or invoice line must lose its paise because a statutory amount is eventually rounded. Nor should section 170 alone be used to pool different liabilities, tax heads, periods or persons.
Keep precision until the appropriate step
Maintain the unrounded calculation and a distinct rounded-output column. Reconcile the rounding adjustment to the same amount and period, using decimal arithmetic that reproduces the fifty-paise test. This is especially important when an accounting system and a return extract use different precision. A rounding adjustment is not an unexplained discount, tax-rate change or missing invoice. Preserve the base and rate calculation rather than changing them to make the rounded total fit.
Refunds and charges are within the wording too
Do not apply nearest-rupee treatment only to output tax while truncating every interest or refund amount downward. The statutory description includes both payable and due amounts. The examples below assume each specified figure is already the correctly computed, positive, legally relevant amount under the CGST Act. They do not establish entitlement to a refund, impose a penalty, extend the provision to a different Act or invent current portal behaviour.
Investigate the source of a mismatch
An amount differing by a rupee can arise from rounding, but that is not proof. First reconcile transaction scope, dates, tax heads and credit notes. Where an aggregate is the relevant statutory sum, premature rounding of its components may produce a different total. Where the law instead requires separate sums, do not merge them just to obtain a preferred answer. Record that legal unit alongside the calculation; the aggregate example is expressly conditional on that determination.
Six worked illustrations
All facts and amounts below are fictional. Assumptions describe the model, not additional statutory rules.
Illustrative example 1: Tax fraction below fifty paise
Assume the correctly determined statutory tax amount is ₹15,432.49. The fraction is below ₹0.50, so section 170 gives ₹15,432. The adjustment is minus ₹0.49, not an unexplained reduction in taxable turnover.
Illustrative example 2: Interest at exactly fifty paise
A properly computed interest amount is ₹254.50. It rounds to ₹255, an increase of ₹0.50. A half-to-even function producing ₹254 at this boundary would not reproduce the specified rule.
Illustrative example 3: Penalty near the next rupee
Assume a penalty amount lawfully determined before rounding is ₹999.99. The rounded amount is ₹1,000 and the adjustment ₹0.01. This example only applies rounding and does not create a substantive penalty.
Illustrative example 4: Refund boundary
An otherwise admissible refund sum is ₹6,500.50. Section 170’s upward fraction rule produces ₹6,501, a ₹0.50 adjustment. It is not a rule that all refund fractions are discarded in favour of the Government.
Illustrative example 5: Already whole rupees
A covered amount is exactly ₹12,500.00. The rounded result remains ₹12,500 and adjustment is zero. Rounding is not permission to add a blanket extra rupee to every payment.
Illustrative example 6: Premature component rounding
Assume four computed components of ₹100.49 form one legally established statutory amount to be rounded at the aggregate stage. The aggregate is ₹401.96 and rounds to ₹402. Rounding each component first gives ₹100 × 4 = ₹400, a ₹2 difference. This example does not say that unrelated tax heads or separate statutory liabilities may be combined.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Identify the Act | Confirm that the sum is covered by section 170. |
| 2 | Identify the legal amount | Record person, period, head and aggregation basis. |
| 3 | Verify the underlying computation | Check bases, rates and entitlement before rounding. |
| 4 | Retain decimal precision | Keep the source calculation rather than editing it to whole rupees. |
| 5 | Apply the fifty-paise test | Distinguish below ₹0.50 from exactly ₹0.50 or above. |
| 6 | Test software behaviour | Check exact-half cases rather than assuming the default rounding mode. |
| 7 | Record the adjustment | Show rounded minus unrounded amount. |
| 8 | Reconcile component treatment | Avoid premature rounding or unsupported pooling. |
| 9 | Match return and payment output | Verify the applicable field and workflow separately. |
| 10 | Resolve discrepancies | Separate genuine rounding differences from omitted transactions. |
Sixteen practitioner FAQs
1. Which basic method does section 170 use?
Nearest rupee, with the expressly stated fifty-paise rule.
2. What happens at exactly fifty paise?
The fractional part is increased to one rupee.
3. What happens below fifty paise?
The fractional part is ignored for the covered amount.
4. Is half-to-even always suitable?
No. It can give the wrong answer at an exact half; test the mode.
5. Does the text include interest?
Yes. Interest is expressly listed among the covered amounts.
6. Are penalties and fines mentioned?
Yes. Their substantive imposition must still be independently valid.
7. Are refunds also covered?
Yes. The text includes refunds and other sums due under the Act.
8. Does rounding establish refund eligibility?
No. Determine admissibility before rounding the relevant amount.
9. Must every underlying unit price be rounded to rupees under this section?
That does not follow from the section alone. Identify the legally relevant sum and other requirements.
10. Can different taxpayers’ liabilities be pooled?
No such permission is supplied by this rounding rule.
11. Can all tax heads automatically be merged?
Do not assume so. Apply each governing liability and return requirement.
12. Why keep unrounded workings?
They explain the base, precision and resulting adjustment without altering source facts.
13. Is every one-rupee mismatch a rounding issue?
No. Reconcile scope, timing and transaction completeness first.
14. Does a whole-rupee amount change?
It remains the same under this operation.
15. Does the aggregate illustration mandate aggregate rounding in every situation?
No. It expressly assumes an already established aggregate statutory sum.
16. Does this guide assert a current portal precision setting?
No. Verify the actual return/payment workflow independently.
Conclusion
Section 170 rounds covered statutory amounts to the nearest rupee, with fifty paise rounded upward. Retain the underlying precision and identify the legal amount before applying the rounding step.