Preparing PDF Documents for Tax, GST, and Official Filings: A Practitioner's Checklist

Last updated: July 2026

Anyone who deals with tax departments, registrars, banks, or courts learns the same lesson quickly: the substance of your submission matters, but so does its packaging. A reply to a notice that arrives as one clean, ordered, bookmarkable PDF gets processed; a zip of seventeen photos named IMG_2041.jpg invites queries, delays, and rejection. This checklist is written from the perspective of a small accounting practice that assembles these bundles every week.

The Golden Rule: One Matter, One File

Whatever the submission — an income tax notice reply, a GST registration application, a loan file, a tender — the goal is a single PDF in which the pages appear in the exact order a reviewer would want to read them. Typically:

1. Covering letter or index stating what is enclosed and in what order.
2. The primary document (the reply, the application form, the computation).
3. Supporting evidence in the order it is referenced — annexure 1, annexure 2, and so on.
4. Identity and authority documents last (PAN, registration certificates, authorisation letters).

When a covering letter says "the bank statement for April 2026 is at Annexure 3", the officer should be able to scroll straight to it. That single courtesy shortens processing more than almost anything else you can do.

Assembling the Bundle

1. Collect everything as PDF first

Convert every item to PDF before you think about order: export letters from Word, download statements from bank portals, and scan paper originals with a phone scanning app (see our phone scanning guide). Never insert raw photos into a submission.

2. Unlock protected files

Bank statements and salary slips usually arrive password-protected and will break any merge. Remove the protection from your own documents first — the safe methods are covered in this guide. Do this on your own device, not on an upload-based website: these are exactly the documents you don't want on a stranger's server.

3. Name files in reading order

Prefix each file with a two-digit number: 01-covering-letter.pdf, 02-reply.pdf, 03-annexure-1-ledger.pdf. The numbering is your table of contents and your insurance against mis-ordering.

4. Merge locally

Combine the files with a browser-based merger so client financial data never leaves the machine. Arrange, merge, download, and then — non-negotiable — open the output and page through it once, checking against your index.

5. Meet the portal's constraints

Check the size and format limits before the deadline day. Common constraints: 1–5 MB per attachment, PDF-only, sometimes a page limit. If your bundle is too large, rescan supporting documents at 200 dpi black-and-white or compress the merged file — see reducing PDF file size. If the portal enforces a per-file limit smaller than your bundle, split at logical boundaries (reply in one file, annexures in another) and say so in the covering letter.

Quality Standards Reviewers Notice

• Straight, right-way-up pages throughout. One sideways page signals a bundle nobody proofread.
• Legible figures. Amounts, dates, GSTIN/PAN digits, and signatures must survive zooming. If a seal or stamp matters, that page — and only that page — should be scanned in colour.
• No duplicates or stray pages. Duplicated annexures make page references wrong from that point onward.
• Self-explanatory filename. reply-142-1-notice-ay2018-19-jhl-trading.pdf tells everyone — including you, two years later — exactly what the file is.

A Note on Confidentiality

Tax and financial bundles are among the most sensitive documents a person or business owns: they contain identity numbers, bank balances, turnover, and signatures, all in one convenient package. Two habits protect them: process files locally rather than uploading to conversion websites, and when emailing a bundle, confirm the recipient address character-by-character — misdirected email is the most common data breach in small practice, and no software fixes it.