Skip to content

Filing: guide

Help release c4e6d48f22a45602 · Generated 22 November 2026. Online at docs.mycadesk.in/modules/filing/.

Help explains how the software works and is not professional advice; refer to the statute or notification.

Direct filing of GST and income-tax returns

Filing builds a return from imported data or a final computation, takes it through review, client approval and pre-filing checks, and files it through the provider or records a manual filing.

The Filing area (menu: Filing) prepares, approves and files a client's returns from inside the app. It works with two kinds of return:

  • GST returns (GSTR-1, IFF and GSTR-3B), built from the client's imported data for one GSTIN and period.
  • Income-tax returns, built from the client's final income computation (see Income computation).

How a return moves

  1. Prepare and validate. The app builds the return, seals its contents and runs the validation rules. Blocking issues must be fixed before anything else.
  2. Review (GST only). Someone other than the person who built or last changed the return reviews it for the period.
  3. Client approval. The client approves a summary of these exact contents in the portal, or a partner records an approval the client gave outside the portal. See How the client approves a return.
  4. Pre-filing checks. The app re-checks the return just before submitting (already filed, computation final, reconciliations current, signatory valid and so on). Some checks can be overridden by a partner.
  5. Submit. A member at or above the firm's minimum role, who did not prepare the return, submits it with a fresh identity check (Step-up). The filing runs in the background.
  6. OTP, DSC and verification. A GST return is filed with an EVC OTP. An income-tax return is uploaded first and then e-verified (EVC, Aadhaar OTP or DSC); see .

If the provider does not answer, the app never resends blindly: see When the provider does not answer a filing step. When the provider is unavailable, you can file on the portal yourself and record the proof (the manual fallback).

Pages

PageUse it to
Read the filing dashboardsee returns by form, period and status, and what needs attention
Find returns and start a new onefind returns, start a new one, prepare a bulk filing
Take a return from draft to filedvalidate, send for approval, submit, enter the OTP, verify
file many approved returns in chunks
pair the connector agent that signs with your DSC token
Filing settingsthe firm's filing rules

Features switched on per firm

Parts of Filing are rolled out gradually. Your firm sees a part only when it is switched on: income-tax filing through the e-return intermediary (ff.filing.itr_eri), GST filing through the GST suvidha provider (ff.filing.gst_gsp), the GSTR-1/IFF and GSTR-3B builders (ff.filing.gst_builders), bulk filing (ff.filing.bulk), DSC signing (ff.filing.dsc), OTP entry by the client in the portal (ff.filing.portal_otp), the filed-return status sync (ff.filing.status_sync), the manual filing fallback (ff.filing.manual) and staff entry of a client's Aadhaar OTP (ff.filing.staff_aadhaar_otp, see Enter a client's Aadhaar OTP for them).

For the fee shown with a return filed after its original time limit, see .

How the client approves a return

The client approves a summary of the exact contents of the return. Any later change, or an approval older than the firm allows, needs a new approval before submit.

Before a return is submitted, the client approves it.

In the portal

Send for client approval files a summary PDF in the client's Documents (the figures and masked bank accounts) and asks the contacts you choose to approve it in the portal. The approval is bound to these exact bytes: the app compares a fingerprint of the approved contents with the return at submit.

Outside the portal

When the client approved by other means (for example a signed summary), a partner chooses Record an offline approval, names an evidence document of this client in Documents and gives a reason. A fresh identity check is needed. The override is visible on the return, and the partner who recorded it cannot also be the one who submits, unless the firm is a solo practice. Your firm can switch this off (Filing settings).

When an approval no longer counts

  • The return changed after approval (a new version, a rebuilt payload): ask again.
  • The approval is older than the firm's limit (default 15 days): ask again.
  • The client declined: the return goes back to Valid (income-tax) or Reviewed (GST).

The app then refuses submit with or .

When the provider does not answer a filing step

If the provider does not answer, the return shows Outcome unknown. The app queries the status for a settle time and never resends on its own; a partner then decides to retry after a fresh check or to record the filing with proof.

A filing call can time out with no answer. The provider may or may not have received it, so sending it again could file the return twice. The app therefore:

  1. marks the return Outcome unknown and opens a case on the return (Unknown outcome);
  2. queries the provider's status every five minutes until a settle time passes (30 minutes for income-tax returns, 15 minutes for GST returns, at most a few queries);
  3. if a query finds the filing, records it as filed; otherwise it lists the case on the dashboard under Unknown outcomes (a partner decides).

Decide the case

A partner chooses Decide the unknown outcome and confirms it's them:

  • Retry (after a fresh check): the app first runs a fresh receipt and status check. The retry is released only when the provider confirms it never received the filing. Otherwise the app refuses with .
  • It was filed: record the proof: enter the acknowledgement or ARN and the filing date from the portal.

Every decision is recorded in the audit log with the case and the return.

Enter a client's Aadhaar OTP for them

When the firm allows it, partners, CA assistants and roles the firm authorised may type a client's Aadhaar OTP for them, each time with a fresh identity check and an attestation.

By default only the taxpayer enters an Aadhaar OTP, in the portal. Your firm can let members relay it instead, for example when the taxpayer reads it out on a recorded call.

Who may relay

  • The firm setting Staff may enter a client's Aadhaar OTP must be on. Only the owner or a partner changes it, with a fresh identity check and a reason of at least 20 characters (Filing settings).
  • The member holds the relay permission: partners and CA assistants by default, and members of a role the firm authorised.

Relay the OTP

Steps

  1. On the return, while it waits for the Aadhaar OTP, choose Enter the OTP for the taxpayer.
  2. Tick to confirm the client this OTP is for.
  3. Give the Reason and how you received it (20 characters or more).
  4. Enter the OTP (4 to 10 characters) and confirm it's you.

The OTP goes to the provider in one call and is kept nowhere. The app records who relayed it, for which client and a fingerprint of the reason in the audit log; the reason itself is not kept in readable form.

Warning

Relay an OTP only when the taxpayer gave it to you for this return. Never ask for an OTP by e-mail or message.

Find returns and start a new one

The returns list shows the returns of clients you can see. Start a GST return from imported data or an income-tax return from a final computation, and select approved returns for bulk filing.

Filter the list by Form, Status and Client; the filters stay in the page address, so you can bookmark or share a view. Open a return to work on it (Take a return from draft to filed).

Start a return

Steps

  1. Choose New return.
  2. Pick the Form: GSTR-1, IFF, GSTR-3B or Income-tax return.
  3. Pick the Client.
  4. For a GST return, pick the GSTIN, the Return period (for example M:2026-09) and the imported data to build from (under Imported data, only published datasets of this client are listed).
  5. For an income-tax return, pick the client's Final computation. A draft computation cannot be used: finalise it first (Choose the regime and finalise a computation).
  6. Optionally link the Engagement. It is needed before the return is submitted and can be linked later.
  7. Create the return. The app builds it, seals its contents and runs the validation rules.

The contents are committed to the exact bytes the client will approve. If the imported data or the computation changes afterwards, the return shows that its source changed; see .

Prepare a bulk filing

Managers and partners can select client-approved returns with the tick boxes and choose Prepare bulk filing. Each return is checked as a single submit would be (approval, pre-filing checks, separation of duties); refused returns are listed on the batch with their reason. See .

Take a return from draft to filed

On a return you see its progress and its next step (review the period, send it for client approval, run the pre-filing checks, submit, enter the EVC OTP and, for an income-tax return, e-verify it).

The return page shows the Client, Engagement, Form and version (the schema the return is built on, for example current value: see your app for ITR-3), the Payload commitment (a short fingerprint of the exact contents), a Progress track and the Next step. Only the buttons you are allowed to use are shown.

Progress

StageGST returnIncome-tax return
Prepared and validatedyesyes
Reviewed for the periodyes—
Client approvalyesyes
Thensaved and checked on the portal, EVC OTP, filed with an ARNuploaded to the e-filing portal, e-verified, filed

Validation issues

Every rule that failed is listed with its Severity, Rule, Where and Message. A block issue stops the return; fix the source (the imported data or the computation) and build a new return. A warn issue is for your judgement.

Steps

Steps

  1. Review the period (GST). A member other than the person who built or last changed the return reviews it. A solo practice may review its own return; this is logged.
  2. Send for client approval. Choose the client's portal contacts. A summary PDF with the figures and masked bank accounts is filed in Documents and sent to them. See How the client approves a return.
  3. If the client approved outside the portal, a partner may Record an offline approval with an evidence document and a reason (when the firm allows it).
  4. Check Pre-filing checks. A blocked check that can be overridden shows Override to a partner; others show Cannot be overridden and must be resolved at the source.
  5. Choose Submit, pick the Signatory and the Verification mode, and confirm it's you. The filing runs in the background inside the five-minute step-up window; the portal summary is compared with what the client approved before anything is filed.
  6. For a GST return, when the status is Waiting for the EVC OTP, choose Enter the EVC OTP and type the OTP the signatory received. If your firm takes OTPs only in the portal, the client enters it there.
  7. For an income-tax return, when the status is Uploaded, verify, use E-verification: choose the mode and Start verification, or Sign with my DSC agent. See .

The OTP goes to the provider in one call and is kept nowhere.

Submission timeline

Each provider call is listed with its Step, Attempt, Outcome and Code. A step that failed shows the error code; open the error's help for what to do.

When something goes wrong

  • Outcome unknown: the provider did not answer. A partner chooses Decide the unknown outcome once the app has finished checking: see When the provider does not answer a filing step.
  • Failed, can retry: the provider rejected a step. Read the code in the timeline, correct the cause and Submit again.
  • The provider is unavailable: file the return on the portal by hand and choose Record a manual filing with the acknowledgement or ARN, the filing date and the proof. The same approval and separation-of-duties rules apply.
  • Withdraw stops a return that should not be filed, for example one built on the wrong data.

Warning

Do not file the same return on the portal while it is being submitted here. If you already filed it elsewhere, the status sync records it and the return here is withdrawn.

Filing settings

The firm's filing rules - who may submit, how long a client approval lasts, where OTPs are entered, what blocks a submission and how long a return waits for the EVC OTP.

Open Filing → Settings. Partners change these settings; other members see them read-only. Each change asks for a reason and is recorded in the firm's audit log.

Submitting

SettingKeyDefaultWhat it does
Lowest role that may submitfiling.submit.min_roleManagerSenior or manager. Below it, Submit is refused.
Changed source data blocks submit until re-validatedfiling.block_on_source_changeYesA return whose imported data or computation changed after it was built cannot be submitted until it is rebuilt or re-validated.
High and critical reconciliation exceptions block GST filingfiling.gst.block_on_blocking_exceptionsYesOpen high or critical reconciliation exceptions for the period block a GST return. A partner may override the check.

Client approval

SettingKeyDefaultWhat it does
Client approval valid for (days)filing.approval.max_age_days151 to 60. An older approval is stale at submit.
Partners may record offline approvalsfiling.approval.offline_override_allowedYesA partner may record an approval the client gave outside the portal, with evidence and a reason.

OTP and verification

SettingKeyDefaultWhat it does
OTPs only from the client in the portalfiling.otp.portal_onlyNoWhen on, staff may not enter EVC or session OTPs; the client enters them in the portal.
Hours an approved return waits for the EVC OTPfiling.evc.max_wait_hours241 to 72. After this, a return waiting for the OTP goes back to Client approved; submit it again.
Staff may enter a client's Aadhaar OTPfiling.aadhaar_otp.staff_relayNoPartners, CA assistants and roles you authorise may relay the taxpayer's Aadhaar OTP, each time with step-up and an attestation. Only the owner or a partner changes this, with a reason of at least 20 characters. See Enter a client's Aadhaar OTP for them.

Status sync

SettingKeyDefaultWhat it does
Complete filings found elsewhere without confirmationfiling.sync.complete_externalNoOff: staff confirm each return the status sync finds filed outside the app before the compliance calendar completes it. On: it completes at once.

Read the filing dashboard

The filing dashboard counts your returns by form, period and status and lists the returns that need someone to act now.

The dashboard shows only the returns of clients you can see. Filter it by Form (GSTR-1, GSTR-3B, IFF or income-tax returns) and Period.

Returns by form, period and status

A grid of counts. Choose a count to open the matching list on Find returns and start a new one.

Needs attention

ListWhat to do
Unknown outcomes (a partner decides)The provider did not answer a filing step. A partner decides once the settle time has passed: see When the provider does not answer a filing step.
Waiting for the EVC OTPThe return was saved on the portal and an OTP was sent. Enter it on the return before the wait ends (Filing settings).
E-verification dueIncome-tax returns uploaded but not yet verified. Verify them before their verification date ().
Failed or sent backSubmissions the provider rejected, and returns the client did not approve. Open the return to see the reason.
Filed elsewhere, not confirmedThe status sync found a return filed outside the app. The compliance calendar completes once a member allowed to run the status sync confirms it, or at once when the firm completes such filings without confirmation (Filing settings).

When every list is empty, nothing is waiting for your firm.