Form 16 / 24Q preparer
Checks the quarterly TDS statement on salary before it's due and prepares the Form 16 data after the year.
How it works
Before each quarterly statement of TDS on salary is due (Form 138, which replaces Form 24Q: 31 July, 31 October, 31 January and 31 May), the agent puts together the deductee rows from approved pay runs and the TDS challans recorded on the Compliance page, and in Q4 the yearly salary details (Annexure II: salary, exemptions, Chapter VI-A deductions, regime, tax). It checks every row in code: missing or invalid PANs and where the higher no-PAN rate applies, challans that don't cover the TDS deducted, rows not mapped to a challan, late deposits, regime mismatches and whether Annexure II adds up. After Q4 it reviews each employee's Part B (Part C of Form 130, which replaces Form 16) and flags deductions declared but not backed by approved proofs. It prepares the data files (payroll's FVU text file for Q1 to Q3, CSV where no official format exists yet) and, when you confirm, saves them in payroll's filing tracker as prepared. It never files anything: your CA runs the utility and files on the portal; Part A comes from TRACES.
Free: no AI model is used, every check is done on payroll's figures
What it reads
- Approved pay runs, TDS challans, tax computations, declarations and proofs (needs the permission to view employee payroll details and to run or approve payroll)
- The filing tracker and Form 130 certificates on the Compliance page
When it starts
- When payroll runs it, in Agents or through the Employee assistant
What it can do
- List each problem with who it affects and what to do
- Save the prepared files in the filing tracker (after you confirm)
What it never does
- File a return, issue certificates or change pay runs and challans
Safe by design
- One assistant, many agents. Ask the Employee assistant in the app or on WhatsApp; it calls the agents your company has hired that you may use.
- Hired, not switched on. Your admin hires each agent from the catalogue and chooses who can use it.
- Agents propose, people confirm. Anything that changes data, like a leave request, waits for a person to confirm it.
- Same access as the user. An agent sees only what the person asking is allowed to see.
- AI processing in India. Agents run on models hosted in India (AWS Mumbai).
- Budgets and a hard stop. Set a monthly credit limit per agent; agents stop when credits run out.
- Every run recorded. Admins see each run, the credits it used and what it did.
Frequently asked questions
What does the Form 16 / 24Q preparer do?
Before each quarterly statement of TDS on salary is due (Form 138, which replaces Form 24Q: 31 July, 31 October, 31 January and 31 May), the agent puts together the deductee rows from approved pay runs and the TDS challans recorded on the Compliance page, and in Q4 the yearly salary details (Annexure II: salary, exemptions, Chapter VI-A deductions, regime, tax). It checks every row in code: missing or invalid PANs and where the higher no-PAN rate applies, challans that don't cover the TDS deducted, rows not mapped to a challan, late deposits, regime mismatches and whether Annexure II adds up. After Q4 it reviews each employee's Part B (Part C of Form 130, which replaces Form 16) and flags deductions declared but not backed by approved proofs. It prepares the data files (payroll's FVU text file for Q1 to Q3, CSV where no official format exists yet) and, when you confirm, saves them in payroll's filing tracker as prepared. It never files anything: your CA runs the utility and files on the portal; Part A comes from TRACES.
Can the Form 16 / 24Q preparer change data on its own?
No. It asks a person to confirm before it will: save the prepared files in the filing tracker. It never does the following: file a return, issue certificates or change pay runs and challans.
How much does the Form 16 / 24Q preparer cost?
Free: no AI model is used, every check is done on payroll's figures. Hiring it uses none of your AI credits; it only needs a flowwork.ai plan.
Where is the data processed?
Agents run on AI models hosted in India and see only what the person using them is allowed to see. Admins see every run and the credits it used.
Other agents
Before a pay run is approved, compares it with the last one and lists what stands out: missing bank details or PAN, zero pay, big net pay changes, LOP spikes, joiners and leavers.
Answers “why is my pay lower this month?” by comparing payslips line by line.
Checks a full and final settlement against your own rules before payroll approves it.