Three calculators, one consistent set of numbers
For a ₹56,100 basic pay, X-classified city, and 55% DA rate: the standalone DA calculator reports ₹30,855, and the standalone HRA calculator reports ₹16,830. Running the identical inputs through the gross salary calculator reports those exact same two figures internally — ₹30,855 DA and ₹16,830 HRA — before adding a ₹3,600 transport allowance to reach a gross salary of ₹1,07,385 (₹56,100 + ₹30,855 + ₹16,830 + ₹3,600, which sums to exactly that reported total).
Why this consistency isn't automatic
The gross salary calculator doesn't call the standalone DA and HRA formulas internally — it recomputes both from its own copy of the same rate tables. Getting identical results confirms both independent implementations agree, rather than one having a stale rate table or a different rounding convention that the other doesn't share.
What a mismatch would have revealed
If the gross salary calculator's internal DA or HRA figures had differed from the standalone calculators' outputs for the same inputs, that would point to one of the two HRA rate tables being out of date relative to the other — exactly the kind of drift that can happen when the same real-world rule is implemented twice in different places.
Why this matters for trusting a gross salary estimate
A central government employee estimating their gross salary can cross-check the individual DA and HRA components against the dedicated calculators for each — getting matching numbers is a useful confirmation that the combined gross-salary figure isn't silently using a different (and possibly outdated) assumption for either allowance.