
Tax Filing Systems Keep Getting Smarter, Until Cross-Department Reconciliation Shows Their True Colors
Last week I helped a client go through the payroll side; they had just brought in the Integral tax and payroll service. Looking at tax calculation alone, it's quite clean — pre-tax and post-tax, social insurance and housing fund, year-end bonus simulation, all out in a few clicks, no more digging through Excel pulling formulas.
But the problem is in reconciliation. Finance added a VAT withholding task for external individual labor fees under the new rules. The tax module calculates it correctly, but the payroll module doesn't recognize that basis, and the numbers exported from the two sides don't match. From my testing, in the end someone still has to manually list the differences and fill them in again.
Putting payroll and tax in the same product doesn't mean both sides are calculating the same set of books.
From a product perspective, it's more like two mature modules stuffed into one shell, with the interface layer not truly connected. This is very common in enterprise software — do feature coverage first, then go back and fix data consistency, but this catch-up round is often what costs clients the most time. My advice: if your team doesn't have someone specifically watching the calculation basis, don't switch everything at once. Let payroll run first, and keep a manual review buffer on the tax side, otherwise month-end closing will be very passive.
By the way, on your side, calculating individual income tax and calculating labor remuneration — is it one system outputting both now, or two systems each doing their own?
Physix Frontier