The GST console

The GST Console behavior is implemented by the first-party TaxCenterWidget. When a tenant AppPage embeds that widget, it answers a narrow operational question: for the selected GST registration and financial year, which return records exist and what state do their stored values indicate? It links to return records and scoped lists; it does not process, reconcile or file a return by itself.

The widget's route is not universal because AppPage provisioning is tenant configuration. This page is therefore intentionally text-only rather than showing a route that may not exist for the reader's tenant. If a Tax Center URL returns Not Found, use the underlying GSTR entity lists and actions until an administrator provisions and grants the AppPage.

Choose the scope

The console uses three coordinates:

• GST registration. The picker loads GSTRegistration records and keeps those that are active and have a nonblank GSTIN. The current query does not separately prove that a registration is the tenant's own filing registration, so administrators must keep the registration master accurate and select the filer GSTIN deliberately.
• Financial year. The picker is built from your stored GST fiscal periods, grouped into Indian April-to-March financial years and ordered newest first. It is not a fixed current-year-plus-or-minus list. If no fiscal-period rows exist, the control falls back to the current financial year.
• Filing period. The timeline shows the annual row first and available months in descending order. When no stored periods exist for the selected year, the console generates a twelve-month navigation scaffold; that scaffold does not mean return records have been provisioned.

Changing any coordinate refreshes the filing cards. Always confirm the GSTIN and displayed period before opening a card, particularly in a tenant with several registrations.

Read the filing cards

For a regular monthly period, the console presents:

For an active registration flagged as an Input Service Distributor, the monthly set is GSTR-6 instead of the regular trio. The annual row presents GSTR-9.

When exactly matching records exist, a card opens the corresponding record. If no exact record can be resolved, it opens the entity list scoped to the selected GSTIN and period so the absence is visible rather than silently inventing a record.

GSTR-2B is a statement GSTN drafts, not a return you file, so its card shows a sync state rather than a filing state, and it reads the portal side of the statement:

• Synced once the statement has been pulled from GSTN. The card shows the statement's invoice value, with its taxable value and tax beneath.
• Awaiting GSTN Data before the statement's expected Generation Date, with "GSTN releases it on …".
• Not Synced after that date if the statement has not been pulled yet. No amount is shown rather than a misleading ₹0.00.

See GSTR-2B for pulling the statement.

The filing activity table has one row per return the period files — GSTR-1 and GSTR-3B (GSTR-6 for an ISD, GSTR-9 on the annual row) — with due date, last update, filed-on date, ARN and status. The ARN is the acknowledgment GSTN returned: GSTR-3B's acknowledgment number, and GSTR-1's ARN when it was filed through the GSP. A return with no record yet shows Not created.

Where records come from

Return provisioning is available in two places, both existence-checked, so repeating it for the same registration and period does not create duplicate headers:

• Provision GST Returns on a GST registration — that registration, for the current month.
• The scheduled Provision GST returns job — every active registration, for the current month unless a {"month","year"} payload names another. This is the way to provision an earlier month.

The standard GST fiscal period page has no provisioning button, and creating a period with New does not create any returns. See GST fiscal periods for how periods are created and what their status controls.

• A regular monthly period provisions GSTR-1, GSTR-2B and GSTR-3B.
• An ISD monthly period provisions GSTR-6.
• Provisioning any normal-filer month also ensures that one GSTR-9 exists for that financial year; repeated months are no-ops for the annual header.
• "Current month" is the month in India time. Returns for a month are filed in the next one, but they open with the month so that GSTR-1 builds up while it runs and a bad buyer GSTIN or missing HSN surfaces while it can still be fixed. Nothing pre-creates every month and year merely because the console was opened.

There is one current edge case to understand: the widget presents an annual GSTR-9 card even for an ISD registration, while the provisioning service does not create GSTR-9 for an ISD. That card can therefore lead to an empty scoped list. Treat that as absence of a provisioned annual record, not as a completed filing.

Recommended workflow

1. Select the filer registration and verify its GSTIN and registration type.
2. Select a financial year derived from the stored fiscal periods.
3. Select the annual row or the required month; do not mistake a generated timeline scaffold for provisioned returns.
4. Read each card as a summary only, then open it and verify the record's own GSTIN and period.
5. Run processing, reconciliation and filing-record actions from the return surface described on that return's documentation page.
6. Return to the console and refresh to confirm the summary changed as expected.

Common questions

Why is the GSTIN picker empty?

No active GSTRegistration record with a nonblank GSTIN was returned. Correct or create the registration master and verify the user's permission to read it.

Why is a financial year missing?

The normal choices come from stored GST fiscal periods. Provision or create the required fiscal periods; the single fallback year shown when no rows exist is only a navigation default.

Why do I see months but no return record?

The console can synthesize the twelve-month timeline when fiscal-period data is absent, and a card can fall back to a scoped list when no exact header exists. Run the appropriate provisioning action or scheduled job for the required registration and period.

Why does GSTR-2B say Not Synced when the statement has rows?

The card counts only the portal side: documents pulled from GSTN with Pull From GSTIN. Rows built from your own purchases by Process GSTR2B are the books side and do not make the card Synced. Open the statement, run Pull From GSTIN, and refresh the console.

Related topics

• GSTR-1 — outward supplies
• GSTR-2B — inward supplies and ITC
• GSTR-3B — the summary return
• Annual returns