Payroll
The numbers were already correct. Somebody rebuilds them anyway.
In most companies the payroll run produces the right figures, and then a person spends two days each month reassembling those same figures into what actually has to be filed — from an export, in a spreadsheet, by hand.
That second assembly is where the errors are, and it is entirely avoidable.
What is produced
Six returns, and most of them without being asked.
Contribution files, the monthly returns, the quarterly tax return and the annual per-employee certificate come out of approved runs — not from an export of them, and not from a second pass over the same data.
They generate on their own schedule, for every legal entity that actually had an approved run in that period. An entity with nothing to report does not produce an empty filing, and a return that already exists is not duplicated.
- Provident fund contribution fileon schedulemonthly
- State insurance monthly returnon schedulemonthly
- Professional tax returnon schedulemonthly
- Quarterly tax returnon schedulequarterly
- Annual tax certificateon requestone per employee
- Only entities that actually ran payroll —
A scheduler sweeps for legal entities with an approved run in the period. An entity with nothing to report produces nothing, rather than an empty filing somebody has to explain.
- It will not duplicate one —
A return that already exists for a period is not generated again by a later sweep.
- The certificate is on request, deliberately —
It is one per employee per year. A scheduled job producing thousands of personal tax certificates unasked is a bad idea wearing the costume of automation.
- Byte-for-byte reproducible —
The same approved run produces the same file every time, and its fingerprint is stored — so what did we file in March is answerable, and provable.
- Readable before you upload it —
The file carries a header and its own summary lines, so the person responsible can look at it rather than trust it.
- Per legal entity —
Filings follow the entity that employed the person, which is the only way a multi-entity group can file at all.
What this is not
It produces the return. It does not file it for you.
The output is a structured file containing exactly what the return needs, which you upload to the relevant portal. There is no direct submission to a government system and we are not going to imply one.
That distinction matters more than it sounds. A product that claims to file on your behalf owns a failure that lands on you — and the portals change without notice. What is worth automating is the assembly, which is the part that consumes two days and produces the mistakes.
Asked by whoever signs the return
Precise answers, including two noes.
›Does it submit the return to the government portal?
No. It produces the file; you upload it. Nobody should hand a product the ability to file on their behalf without being able to read what went.
›What if we correct payroll after a return was generated?
Regenerate it. Because generation is deterministic, the new file reflects the corrected run exactly, and the stored fingerprints show you which version was which.
›Which returns are covered?
Contribution and state insurance filings, professional tax, labour welfare fund, the quarterly tax return, and the annual per-employee certificate. All of them within the one statutory regime that is built.
›Does professional tax cover every state?
The states that levy it and are built — not a blanket claim. Ask us for the specific ones you operate in rather than taking a yes from a website.
›What produces a return — the payroll run or a separate entry?
An approved run. Nothing is re-entered, which is the entire point, and an entity with no approved run in a period produces nothing rather than an empty file.
›Can we prove what we filed?
Yes. Each generated file has a stored fingerprint, and regenerating from the same run reproduces it exactly — so a challenge about a past filing is a lookup rather than an argument.
Book a demo
Bring last quarter's returns.
If the comparison matches what your team assembled by hand, that is two days a month you get back.
- Generate them from the approved runs and compare
- Correct a run, regenerate, and look at both fingerprints
- Open a file and read it before it would be uploaded
- Ask for the states we have professional tax built for