GST returns and annual reconciliation in one register
From GSTR-1 data entry to portal-ready JSON, everything a practice needs for monthly GST compliance — plus the year-end reconciliation that usually happens in a spreadsheet.
GSTR-1 end to end
Outward supplies captured at invoice level where it matters and summary level where it does not, validated before the return leaves your hands.
GSTR-3B auto-filled
Populated from the GSTR-1 you just prepared, with every field still editable before you file.
GSTR-1A amendments
Prefilled from the filed return so an amendment starts from what was actually submitted.
Annual return and 9C
GSTR-9 across its part-tabs with auto-population, plus the reconciliation statement and certification.
Portal-compliant JSON
Download in the exact format the GST portal accepts — no reformatting, no rejected uploads.
GST portal connect
Fetch taxpayer details, return history and cash or ITC ledger balances directly from the portal.
2A and 2B inward register
Invoice-level inward supply by financial year, with a last-fetched marker so you know what you are looking at.
Notices and orders
A register of every notice across the firm and per client, so nothing sits unopened in a portal inbox.
Excel and CSV import
A guided GSTR-1 import wizard — upload, map, preview, import — across all sections in one pass.
Filed here, or on the portal
Every period shows how it was filed — through taxfilo or directly on the portal — and fetched returns are marked as such, so the register never lies to you.
Annual reconciliation
Books against the portal across the full year, with matched, mismatched and missing separated and the ITC impact priced in rupees.
Filed-return locking
Once a return is filed it opens read-only, so a filed period cannot be quietly edited after the fact.
Income tax returns with a genuine computation engine
Not a data-entry form with a total at the bottom. Tax liability recalculates as income goes in, with both regimes computed side by side the entire way.
Every ITR form
ITR-1 Sahaj, ITR-2, ITR-3 and ITR-4 Sugam today, with the remaining forms following — each with the full schedule set rather than a subset.
Regime comparison in rupees
Both computations run side by side with the difference stated, so the advice you give a client is a number rather than a judgement call.
Prior-year roll-forward
Last year’s return opens as this year’s starting point — master data, schedules and brought-forward figures carried, not retyped.
Foreign assets and income
Schedule FA, FSI and TR handled properly — the schedules most software leaves you to fight with on the portal.
AIS and TIS auto-pull
The annual information statement comes from the portal and is reconciled against what you entered, so mismatches surface before the department raises them.
Interest computation
Sections 234A, 234B and 234C computed as you go, not discovered when the portal rejects the return.
Portal-ready JSON
Generated in seconds and uploadable directly to incometax.gov.in without any intermediate tool.
Presumptive taxation
Sections 44AD, 44ADA and 44AE handled with the threshold checks built in.
Capital gains detail
Scrip-level entry with grandfathering under 112A and the indexation treatment applied per asset class.
Carry-forward losses
Brought-forward losses tracked across years so set-off is applied correctly without a side spreadsheet.
Client-wise ITR register
Every client, every assessment year, with status and filing acknowledgement in one view.
Tax audit alongside the return
Form 26 under Section 63 will sit inside this module rather than beside it, cross-referenced with the client’s ITR data where the clauses overlap.
Challan-first TDS, aligned to the Income Tax Act 2025
Built around how deductors actually work: create the challan first, then attach deductee rows underneath it. The new statute is the starting point, not a retrofit.
Form 138 — salary
Salary TDS statements under the Income Tax Act 2025, replacing the legacy 24Q workflow.
Form 140 — non-salary
Non-salary deductions with the full payment-code set and deductee-level detail.
Form 141 — contractor
Contractor and specified-payment deductions, quarter by quarter.
Challan-first structure
Deductee rows are linked to the challan that paid them, so coverage is verifiable at a glance.
Payment codes 1001–1092
The four-digit code set that replaces the legacy 194-series, with descriptions inline.
Deductor profile
TAN, deductor category and branch details held once and reused across every statement.
Quarter-level validation
Section totals and challan coverage checked before you file, not after a rejection.
TRACES 2.0 aligned
Built against the regime effective April 2026 rather than patched onto the old one.
Cross-client register
Every deductor and every quarter on one board, so nothing slips between clients.
Form 16 and 16A
Certificate generation from filed statements — on the near-term roadmap.
Conso file import
Bring in the consolidated file to correct or continue a previously filed statement.
Late-deduction flags
Interest exposure on late deduction or late payment surfaced before the statement goes out.
Company secretarial without the spreadsheet chaos
Board meetings, director KYC, annual filings and penalty accrual for Private Limited, Public Limited and LLP clients — with MCA data pulled in at onboarding.
MCA V3 data pull
Entity master and director list fetched at onboarding so the record starts accurate.
Annual filing tracker
AOC-4, MGT-7 and ADT-1 with due dates computed from the AGM date rather than typed in.
Board meeting scheduler
Quorum checks and the seven-day notice gap tracked, with the calendar entry created for you.
Resolutions and minutes
Draft board resolutions and minutes from the meeting record instead of a Word template.
DIR-3 KYC reminders
The triennial cycle under G.S.R. 943(E) tracked per director, effective March 31, 2026.
LLP compliance
LLPIN, partner contribution and audit threshold alerts handled on the LLP track, not bolted onto company rules.
Penalty accrual
The ₹100 per day exposure computed automatically so a delay has a visible cost.
DSC expiry register
Every director certificate with its expiry date, so a filing is never blocked on a dead DSC.
Registers and records
Statutory registers maintained alongside the filings that draw on them.
INC-20A and DPT-3
Commencement of business and deposit returns tracked with the rest of the annual cycle.
Director master
DIN, appointment dates and directorships held per person across all your client entities.
Charge management
Charge creation and satisfaction filings kept with the entity they belong to.
Form 26 — arriving inside the ITR module
Tax audit is not a separate product here — it belongs with the return it supports, so Form 26 lives inside the ITR module and draws on the client's ITR data directly. The audit report under Section 63 of the Income Tax Act 2025 replaces the 3CA / 3CB / 3CD framework entirely, and we ship it once CBDT notifies the final schema.
The layer that holds
the modules together.
Filing is only part of running a practice. These are the tools that manage the clients, the team and the calendar around it.
Compliance calendar
Every due date, every client, every module — generated, not entered. Seven-day advance alerts.
Work queue
Firm-wide pending work with assignment, status and overdue flags on one board.
One client record
PAN, GSTIN, TAN, DIN, engagement terms and group structure in a single record that serves every module — entered once, never again.
Auto-fetch at creation
Type a GSTIN, PAN or CIN and the master fills itself — legal name, address, constitution, directors — from the portal and MCA V3.
Task management
Work that is not a statutory return still has to happen. Create tasks, assign them, date them, and close them from the phone.
Notes everywhere
Notes on every return and on the client record itself, so the reasoning behind a figure survives to next year.
Legacy data import
Coming off older desktop software? Send a sample export and we will tell you honestly how much we can bring across.
Client groups
Related entities and family groups linked, so a promoter and his companies sit together.
Enquiry register
Capture a prospect at first phone call and send a document checklist before onboarding.
Client status link
A public link showing where a return stands — fewer follow-up calls during season.
User controls
Granular permissions per role and per client. A junior sees their assigned book, a manager the team, a partner the firm.
Audit log
Every material change recorded with who did it and when.
Practice analytics
Filing volumes, staff load and revenue by module across the year.
Import wizard
Client CSV, ITR XML, TDS conso file and Form 16 brought in through a guided flow.
Notifications
In-app and email alerts for deadlines, assignments and status changes.
Mobile app
Client status, due dates and details in your pocket for the 3pm call.
The practice runs from your pocket
Not a cut-down viewer bolted on at the end. Task management, deadlines, client records and notes are all first-class on the phone, because the questions that matter arrive when you are away from the desk.
Tasks in your hand
Create, assign, reassign and close tasks between meetings. The owner gets a notification rather than a message in a group.
Deadlines with you
What is due this week, per client, with the seven-day alerts arriving on the phone instead of an inbox you open at night.
The client record
PAN, GSTIN, contacts, filing history and current status — enough to answer properly while you are still on the call.
Notes on the spot
Leave a note against the client or the return the moment the conversation happens, so it is not lost by the time you reach a desk.
Approvals and alerts
A partner can review and release work from the phone, so filing does not wait on someone reaching the office.
Your queue, filtered
Only what is assigned to you, in due-date order, with overdue at the top — the same board the desk shows.
A mini CRM for work that is not a client yet
Every practice loses work between the first phone call and the engagement letter. Existing tax software has no concept of that stage at all — the enquiry module holds it properly, from the call to the converted client.
Capture on the call
Log the enquiry while the person is still on the line — service asked for, entity type, who referred them, what they were quoted.
Send the checklist
Fire off the document list for the service in question before the call ends, so the client starts collecting the same day.
Follow up on time
Reminders against every open enquiry, so a quote does not go cold because nobody chased it in week three.
Convert without retyping
When they say yes, the enquiry becomes a client record and everything captured carries straight across — no second data entry.
See where work comes from
Source, service and conversion rate per enquiry, so you know which referrals are actually worth the time.
Nothing lost in between
The stage between first call and engagement letter finally has a home, instead of living in a notebook.
What changes against
desktop software.
Not a features war — the differences that actually show up in how a practice runs day to day.
Your clients’ data,
handled properly.
A practice holds PANs, bank details and books for hundreds of people. That obligation shaped how the platform was built.
Data resident in India
Client records are stored on infrastructure in India, in line with how a practice is expected to hold them.
Encrypted end to end
Data is encrypted in transit and at rest. Portal credentials are held separately from client records.
DPDP-aligned handling
Consent, retention and access follow the Digital Personal Data Protection framework.
Role-based access
Staff see only the clients assigned to them. Partner-level access is explicit, not assumed.
Full audit trail
Material changes are recorded with the user and timestamp, which matters when a filing is questioned.
Your data is exportable
Client master, returns and documents can be exported at any time. There is no lock-in by hostage.