Statutory filing and tax credit review

Compliance Status is the first read because it tells the team whether filing work is ready, blocked, overdue, or waiting on operational evidence. Users should not jump straight into a return tab without knowing which statutory obligation is under review.

The status view should point finance toward the right follow-up: sales return preparation, purchase credit review, annual reconciliation, document generation, or movement-document completion.

Evidence should come from source transactions, journals, receivables, payables, bank reconciliation, tax review, close tasks, trial balance, registers, or reporting outputs. For Status before filing detail, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

GSTR-1, GSTR-3B, GSTR-2A, and GSTR-9 are separate review surfaces because each answers a different statutory question. Sales outward supply, periodic tax summary, purchase-side reconciliation, and annual consolidation should not be collapsed into one generic compliance step.

Teach users to confirm the source period, source documents, exception rows, and reviewer ownership before they treat a return as filing-ready. A statutory tab is trustworthy only when it explains the business records behind the numbers.

For GST return surfaces, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

The ITC tab is where purchase-side tax credit becomes a review decision rather than an assumption. Finance should confirm supplier document quality, eligible credit, blocked credit, mismatch state, and follow-up ownership before relying on the credit position.

E-Invoice and E-Way Bill tabs complete the operational compliance picture. They show whether regulated sales and movement documents are generated, cancelled, pending, or blocked before finance signs off tax settlement or close posture.

Use this section to confirm the learner understands more than the page label. They should connect ITC and document controls to the business state, owner, and consequence behind it.

Run the lesson as a finance-control walkthrough. Start with the practical task: use compliance status to decide which statutory area needs attention first. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from source transactions, journals, receivables, payables, bank reconciliation, tax review, close tasks, trial balance, registers, or reporting outputs. The practice should end with the learner connecting the action back to the lesson summary: teach finance and compliance users to read statutory filing state, GST return tabs, ITC review, e-invoice, and e-way bill controls as one compliance workflow.

Close the exercise by asking the learner to restate the objective in operational terms: use compliance status to decide which statutory area needs attention first. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let finance learners treat reports as isolated totals. They should tie balances and close status back to source workflows, blockers, and review evidence. In this lesson, watch for that risk while learners work on this objective: use compliance status to decide which statutory area needs attention first.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain why compliance status should be checked before a specific return tab and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain why compliance status should be checked before a specific return tab, keep the lesson in practice mode before marking it complete.