The problem it solves: Payroll admins could create multiple tax challans for a month (for example India Challan 138 / TDS), but there was no way to say which employees belonged to which challan – and challan records had no dedicated home for bulk management. Employee-to-challan mapping was effectively manual, and challan data had nowhere to live, making accurate Form 138 reporting and auditing harder than it should have been.
What we built: Two additions in Reports. A full-screen employee selector assigns employees to each challan individually, with a bulk Excel upload for large numbers – challan serial numbers come from a live dropdown, so you map exactly the right employees to each challan. And a new Challan Data page (top-right of Reports) gives challan records a dedicated home – upload, validate, save, edit, download and delete them in one place.
What this means for your team
Accurate Form 138 reporting
every challan reports exactly the employees it should
Bulk, not manual
map large employee populations to challans with one Excel upload instead of one at a time
One home for challan data
manage and retain all challan records in a single place, ready for audit
How it works
Assign employees to challans
In Reports, use the employee selector (or the bulk Excel upload) to map employees to each challan. Challan serial numbers are chosen from a live dropdown. Confirm the mapping, then generate Form 138 with each challan reporting the right people.
Manage challan records on the Challan Data page
Open the Challan Data page from the top-right of Reports to upload, validate, save, edit, download and delete challan records – keeping challan data complete and current for Form 138 reporting.
Audience at a glance
| Role | Primary action |
|---|---|
| Payroll Administrator (India) | Map employees to challans (individually or via bulk Excel); manage challan records on the Challan Data page; generate accurate Form 138. |