How to document a GST portal workflow with web page screenshots

To document a GST Portal workflow, choose one task and tax period, follow the current official manual for that task, and capture only the screens that show its start, meaningful transitions, review, and final result. Add a short caption to each screenshot explaining what changed and what the reader should confirm. Keep credentials, OTPs, and unnecessary taxpayer or commercial information out of every public image.

For a return filing guide, distinguish a draft from a submitted or filed return. The documented GSTR-1 workflow identifies successful filing by an Application Reference Number (ARN) and Filed status; conceal the ARN in public examples unless disclosure is authorized. GSTN advises users not to share their GST Portal credentials. Use the current GST Portal help manual for the exact form and period, because labels and steps can change.

1. Choose the task and verify the official workflow

Write down the portal function, form (if applicable), and tax period before you capture anything. A guide for GSTR-1 should not be presented as a universal path for other returns, refund applications, appeals, or ledger tasks.

GSTN’s Welcome Kit points users to help manuals and FAQs with screenshots for portal functions including payments, return filing, refund applications, appeals, offline tools, ITC forms, and ledgers. The GSTR-1 FAQ describes the statement of outward supplies for eligible registered taxpayers and points to the portal help section for detailed filing instructions. Start at the GST Portal help area and locate the manual that matches the task. The official return manuals are the authority for current steps and labels.

Before publishing, verify the manual’s current screen sequence and authentication requirements. The detailed manual can specify steps that a general article cannot safely assume. Treat this page as a documentation method, not individualized tax advice or a substitute for checking entries against the taxpayer’s own records.

2. Plan a concise screenshot sequence

Capture a sequence that explains the workflow without reproducing every click. The following is an editorial template synthesized from official workflow stages, not a formal GSTN screenshot standard.

Frame	What to capture	Caption should explain
1. Find the task	The relevant dashboard or menu, only if it helps readers locate the function.	Which task and period the guide covers.
2. Starting point	The task or form before entering or changing information.	What page the reader should be on and what state it represents.
3. Meaningful transition	A page after a consequential action, such as saving a section or generating a summary.	What changed and what status or content to confirm.
4. Review	The draft or consolidated summary, with sensitive values concealed.	That readers should compare their own entries with their source records before proceeding.
5. Completion	The final Filed status or success message when documenting a filing workflow.	What confirms completion. For GSTR-1, successful filing produces an ARN and Filed status; hide the ARN in a public example unless authorized.

Skip duplicate screens that add no information. If a screen differs by return type, period, or current portal version, say so in its caption. Do not imply a screenshot is the only valid route if the official guidance describes other preparation methods.

3. Capture screenshots safely

1. Prepare the browser. Close unrelated tabs and windows. Check browser tabs, bookmarks, notifications, autofill suggestions, and the surrounding desktop for information that should not appear.
2. Sign in yourself. Do not give your username, password, or OTP to a photographer, editor, or helper. GSTN’s Welcome Kit says: “You are strongly advised not to share your GST Portal credentials (Username and Password) with anyone.” See the GSTN Welcome Kit.
3. Capture each meaningful state. Take the screenshot after the page has loaded and the relevant state is visible. Avoid capturing a live password or OTP entry.
4. Redact before publication. Conceal credentials and OTPs, and minimize exposure of GSTINs, PANs, contact details, bank details, customer names, invoice numbers, amounts, and other identifying or commercial data. These minimization steps are practical privacy guidance; the retrieved GSTN material does not establish a formal public screenshot redaction standard.
5. Inspect the exported image. Review it at full size, including browser chrome and image edges. Use opaque redaction that cannot be removed by editing a layer or changing image settings. Publish a minimized copy; if retaining an original is necessary, keep it in an access-controlled location.

Prefer fabricated example data or a test environment if one is available for your purpose, but do not assume the GST Portal provides a demo mode. Never use real taxpayer data in a public example without clear authorization and a genuine need.

4. Write captions that make the evidence useful

Give each image a sequence number and a short action label. State what changed and what the reader should confirm. Avoid captions that merely repeat a button label or claim more than the screenshot proves.

Step 3 — Review the consolidated summary
The portal has generated a summary for the selected period. Compare the entries with your source records before continuing. This example conceals taxpayer and transaction details.

For a completion frame, describe the visible state precisely. For example: “The portal shows Filed status. An ARN is generated on successful GSTR-1 filing; the identifier is concealed in this public example.” Do not label a draft or an intermediate submission state as filed.

5. GSTR-1 details to represent accurately

The official FAQ describes GSTR-1 as the monthly or quarterly statement of outward supplies for eligible registered taxpayers. It identifies three preparation routes: online portal entry, the Returns Offline Tool, and third-party application software through GSPs. Which route is suitable depends on the taxpayer’s workflow and current portal instructions; do not imply that every route is interchangeable in every case. See the official GSTR-1 help and FAQ.

The FAQ lists prerequisites including an active GSTIN for the period, valid login credentials, and, where applicable, a valid DSC or access to the authorized signatory’s registered mobile for EVC. The official login manual describes portal login with credentials and OTP authentication. Keep these authentication details out of screenshots. Confirm requirements in the current manual before documenting a specific filing.

When your guide covers filing, make the state distinctions explicit:

• Draft or review: information is being prepared or checked; this does not establish that filing is complete.
• Submitted or in progress: describe only the state the portal actually displays; do not equate it with Filed.
• Filed: the documented successful GSTR-1 workflow identifies an ARN and Filed status. Conceal the ARN in a public example unless disclosure is authorized.

Or skip the browser setup

If you already have an authorized, public page to document, ScreenshotNeo can return a webpage screenshot from one API request. See the ScreenshotNeo API documentation before using it. Do not send GST Portal credentials, authenticated pages, or taxpayer data to a screenshot service; use it only for pages you are authorized to capture and that do not expose sensitive information.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
with open("shot.webp", "wb") as image:
    image.write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

Replace the example URL with an authorized, non-sensitive page. The API supports PNG, JPEG, WebP, and PDF output; consult the docs for request options and response handling. Cookie banners, popups, and chat widgets are removed before the shot; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. An MCP server lets AI agents, including Claude and Cursor, use screenshot tools. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card.

Troubleshooting

Problem	Likely cause	What to do
The guide’s buttons or page order do not match the portal.	The portal layout, labels, task, or period differs from the guide.	Recheck the current official manual for the exact form and period, then update the screenshots and date or version context.
A screenshot contains an OTP, identifier, or transaction detail.	The capture included authentication or live taxpayer data.	Do not publish it. Make an opaque redacted copy, inspect it at full size, and remove unnecessary details. If a credential was exposed, follow the account’s applicable security steps.
The image appears to prove filing, but the return was only saved or reviewed.	A draft or intermediate state was mistaken for completion.	Capture the actual completion state. For GSTR-1, document Filed status and conceal the ARN unless disclosure is authorized.
The screen is cluttered or too small to read.	The capture includes irrelevant browser or desktop content, or the page is scaled down.	Close unrelated windows, capture the relevant area at readable size, and crop only if the crop preserves necessary context.
A helper asks for login credentials to capture the workflow.	The capture process would require sharing account access.	Do not share credentials. Capture the screen yourself and provide only a minimized, redacted image for editorial review.
The screenshot sequence is long and repetitive.	Every click was captured instead of meaningful state changes.	Keep the starting point, consequential transitions, review, and result; remove frames that do not teach or confirm anything new.

Performance, reliability, and evidence limits

For a manual guide, capture only the frames needed to explain distinct states. This keeps the article readable and reduces the number of sensitive images that must be reviewed. Capture after a page reaches a stable state, and recheck the sequence whenever the official manual or portal changes.

A screenshot is evidence of what was visible at capture time; it does not independently validate the underlying return data or establish that every required action was completed. Keep captions tied to visible facts and official workflow guidance. The retrieved GSTN sources establish that official manuals and FAQs include screenshots, and that successful GSTR-1 filing yields an ARN and Filed status. They do not set a formal screenshot editing, redaction, annotation, or retention standard.

FAQ

Where can I find GST Portal manuals with screenshots?

GSTN directs users to the portal help section for detailed manuals and FAQs. Start with the official GST Portal user guides and choose the guide for the task you are documenting.

What should I hide in a GST Portal screenshot?

Always keep passwords and OTPs out. As a privacy practice, also conceal unnecessary GSTINs, PANs, contact details, bank details, customer and invoice information, amounts, and other identifiers before publication.

How can I show that a GSTR-1 return was filed?

Show the portal’s Filed status. Successful filing generates an ARN; conceal that identifier in a public example unless disclosure is authorized.

Does GSTN specify a screenshot redaction standard?

The materials reviewed for this guide do not establish a formal public standard for redaction, annotation, or screenshot retention. Use careful data minimization and opaque redaction as practical privacy measures.

Sources

• GSTN Welcome Kit — help manuals and FAQs, and credential guidance.
• GST Portal return user guides and GSTR-1 FAQ — GSTR-1 overview, prerequisites, preparation methods, and filing outcome.
• GST Portal login user guide — login and OTP authentication guidance.