A complete GST desk, from registration to resolution.

A useful dashboard shows more than filed-versus-pending returns. It connects registration status, state footprint, turnover bridges, output liability, credit quality, cash tax, vendor exceptions, refunds, demands, notices and material business changes. Each exception should have a value, reason, evidence status, owner and next date. Management should be able to distinguish a routine timing difference from a legal exposure or missing record. The dashboard supports decisions; it does not replace document-level review or current-law verification.

Standardise source data, roles, close dates, reconciliations, approval thresholds and evidence retention before transaction volume rises. Central policy can define masters and minimum controls, while each GST registration still needs state-specific records, portal access and accountability. Automate repeatable matching and validation, but keep human review for unusual supplies, classification, place of supply, restricted credit, exports, refunds and authority matters. Measure ageing and root cause so the same exception is not manually repaired every month.

It should identify the registered person, GSTIN, periods, filing status, returns and acknowledgements, tax payments, reconciliations, ledgers, open exceptions, credit positions, refund matters, notices, portal access owners and the next scheduled actions. Working papers should connect figures to source data and explain material judgments. The business should receive documents in usable formats rather than depend on one person's email or device. Passwords and authentication controls should be transferred securely, with access reviewed after the handover.

Both views serve different controls. Period folders support return preparation, payment and acknowledgement tracking. Transaction or matter files support contracts, invoices, shipping, remittance, credit eligibility, refunds and notices across periods. A strong system uses stable document identifiers so the same source record can be located from either view without uncontrolled duplication. The retention design should follow current statutory requirements and any longer commercial, litigation or audit need applicable to the record.

Operations owns commercial facts: what moved, where, why, under which contract and with which evidence. Finance owns recording, reconciliation, tax computation and ledger integrity. Procurement supports vendor and receipt evidence; sales supports customer and credit-note facts; technology controls master data and interfaces; management approves material positions; advisers interpret difficult rules and filings within scope. The responsibility matrix should name people and deadlines. Calling every issue a tax-team problem usually delays fact collection until after the filing date.

No. Software can validate fields, calculate configured rules, create documents, reconcile populations and preserve workflow evidence, but configuration and source facts can still be wrong. It cannot independently decide every classification, place-of-supply, composite-supply, credit-restriction or legal-remedy question. Controls should document who approves tax logic, how changes are tested, what exceptions are reviewed and how portal results reconcile back to books. Automation increases consistency only when governance over data and rules is equally strong.

It is especially useful before fundraising, diligence, an audit, a refund, expansion into a new state, a major system migration, launch of a new channel, change in supply model, business transfer or closure. A periodic review is also useful when returns appear timely but reconciliations, vendor exceptions or notices are accumulating. The scope should state periods, registrations, data availability and materiality. A health check identifies and prioritises issues; correction must follow the legally available route and current time limits.

Record the date and manner of service, exact form, section, tax period, issuing authority, response or hearing date and any portal instructions. Read whether the communication seeks information, proposes a liability, communicates an order or begins another statutory process. Do not assume that an email reminder and a portal order have the same effect. If the deadline or service is unclear, obtain appropriate advice immediately while preserving the document and preparing the factual record. Silence can materially restrict later options.

Filing evidence proves what was submitted or paid: return copy, ARN, challan, ledger and acknowledgement. Decision evidence explains why the numbers and treatment were chosen: contract analysis, reconciliation, classification note, credit test, approval and supporting documents. A complete file needs both. Filing evidence without reasoning makes later review difficult; reasoning without submission proof cannot establish completion. Material or unusual positions deserve a concise dated note connected to the actual transaction population and current authority relied on.

Map every legal entity and GST registration, the goods, services, employees, assets, guarantees, management support and shared costs moving between them. Review distinct-person, related-party, valuation, invoice, place-of-supply, credit and documentation requirements. Define recurring allocation drivers and approval rather than creating year-end invoices without operational evidence. Reconcile both sides of each transaction and explain differences in timing or value. Transfer-pricing, accounting and company-law questions may also apply and should be coordinated rather than conflated.

Confirm that business has actually ceased or the legal ground is available, then review pending returns, tax, interest, stock and capital goods, input credit, refunds, demands, notices, amendments, e-way or e-invoice activity and books. Preserve portal access and records after cancellation. A cancellation application can trigger queries or require final reporting, and cancellation does not erase earlier-period liabilities or record-retention duties. The effective date and consequences should be chosen from verified facts, not only the last sales invoice.

The page separates durable control principles from dates, rates, thresholds and portal steps that can change. It links to CBIC, the GST portal, GST Council material, official tutorials and other authority sources where appropriate, and it displays a review date for current-awareness sections. Before an engagement or filing, the relevant Act, rules, notification, circular, order, portal guidance and effective date are checked against the taxpayer and transaction. Editorial depth improves issue spotting; it cannot convert a general web page into transaction-specific professional advice.