Do I legally need to keep GST invoice PDFs together for ITR filing?

You are required to retain GST invoices for 72 months from the due date of furnishing the annual return for that financial year (Section 36 of the CGST Act, 2017). The format is not specified — paper, individual PDFs, or a single merged PDF are all acceptable. A merged PDF is the practical choice for audit response: GST officers ask for tax-period bundles, not individual invoice files.

Why merge GST invoices instead of zipping them?

A merged PDF preserves the invoice order, makes the bundle searchable as a single document, and is the format auditors and accountants expect. A zip needs unzipping plus a viewer; a single PDF opens with one click. Most CAs and tax consultants explicitly ask for the merged PDF with serial-numbered invoices so they can cross-reference against your GSTR-2B / GSTR-3B in one window.

Will GST invoice PDFs be uploaded to PDF Mavericks servers?

No. PDF Mavericks processes everything inside your browser using pdf-lib and WebAssembly. The invoices never leave your device. There is no upload step, no server-side storage, no temporary cache. You can verify by disconnecting from the internet after the page loads — the merge tool keeps working because all computation happens locally.

How many invoice PDFs can be merged at once?

Practical limit is browser memory, not a server quota. Tested up to 500 invoice PDFs (~150MB combined input) on a 16GB laptop with Chrome — completes in under 90 seconds. For very large bundles, split by tax period (one merged PDF per month or per GSTR-3B filing) to keep individual PDFs under 50MB for easy email attachment to your CA.

What about e-invoice PDFs with IRN and signed QR codes?

Merging preserves the IRN, the signed QR code, and the digital signature on each individual invoice — pdf-lib's merge operation copies pages as-is without re-rendering. The digital signature on each page remains valid. Auditors can scan the QR code on any page of the merged PDF and verify the invoice against the IRP exactly as they would with the standalone PDF.

How should I name and order the merged file for ITC reconciliation?

Recommended convention: GSTIN_TAXPERIOD_PURCHASES.pdf (e.g., 27ABCDE1234F1Z5_AY2026-27-Q1_PURCHASES.pdf). Order invoices by supplier GSTIN, then by invoice date within each supplier. This matches how GSTR-2B groups data, so when your CA reconciles ITC claims against IMS-fed GSTR-2B entries, they can find the source invoice in seconds.

What if a supplier sends invoices in WhatsApp or email — can I merge those too?

Yes. Most WhatsApp Business invoices are JPGs; convert them to PDF first using /jpg-to-pdf, then add to the merge queue. Email PDFs are already in the right format. If your supplier sends Excel or images of receipts, convert each to PDF before merging — pdf-lib needs PDF inputs for the merge operation. The whole conversion pipeline runs locally in the browser.

Merge GST Invoices PDF for ITR Filing (Browser-Local)

Why merge GST invoices for ITR filing

Three things drive the need for a single merged PDF of GST invoices during ITR filing season:

CA handover. Your accountant reconciles your GSTR-3B input tax credit claims against the IMS-fed GSTR-2B entries (auto-populated from supplier GSTR-1 filings). Cross-checking 30–200 individual invoice files against 30–200 GSTR-2B line items in two separate windows is slow and error- prone. One merged PDF in invoice-date order lets the CA scroll a single document while the GSTR-2B sits open in another tab.
Audit response. A GST officer issues notices tax-period-wise (typically quarterly or yearly). The standard ask is "produce all purchase invoices for Q3 FY 2025-26." Sending 47 separate PDF attachments by email triggers attachment-limit issues and looks disorganised. Sending one merged PDF named `27ABCDE1234F1Z5_AY2025-26-Q3_PURCHASES.pdf` looks professional and answers the notice in one attachment.
Retention. Section 36 of the CGST Act, 2017 mandates 72-month retention of GST invoices from the due date of furnishing the annual return. Sixty months of individual PDFs across 24 quarters becomes thousands of files. Twenty-four merged PDFs (one per quarter) is the practical archival format — and you can compress each merged PDF using /compress to fit under 25MB email attachment limits without losing the originals.

The five-step GST-period merge workflow

This is the workflow that fits cleanly with the IMS-based ITC reconciliation introduced in the 2025 GST budget:

Gather invoices for one tax period. Pull every supplier purchase invoice for the GSTR-3B period you are reconciling. Most come by email; some arrive on WhatsApp Business; a few are downloaded from supplier portals. Sort them into one folder per period.
Convert non-PDF inputs. WhatsApp invoices are usually JPG; Excel-format purchase orders may also have made it into your records. Convert JPGs to PDF via /jpg-to-pdf; convert Excel to PDF in the original tool. Everything in the merge queue must be a PDF.
Reorder by supplier GSTIN, then by invoice date. This matches how GSTR-2B groups data. When your CA scrolls the merged PDF and finds a discrepancy on, say, supplier `06AABCS1234N1Z3`, they can spot the invoice cluster in seconds instead of grepping a flat file list.
Open /merge. Drag every PDF in the chosen order onto the page. The page loads the documents into a canvas inside your browser. Reorder by drag-and-drop if needed.
Merge + name + archive. Click "Merge". The file downloads directly. Use the naming convention from the § "Naming and ordering" section below. Store in a folder per financial year per quarter.

Total time for a 60-invoice merge: under 2 minutes including ordering. No account creation, no upload progress bar — the file never leaves your device.

Why GSTIN data should never touch a third-party server

Smallpdf, iLovePDF, and Adobe Online all offer a PDF merge tool. They are fast and easy to use. They also upload your invoice files to their servers, process the merge there, and serve back the result. For a document set containing your GSTIN, supplier GSTINs, transaction amounts, and HSN codes, that is a regulatory and commercial risk you do not need to take.

The data on a GST invoice is enough to reverse-engineer your supplier relationships, monthly purchase volumes, vendor pricing, and effective gross margins. For a competitor, it is a treasure trove. For a fraudster, the GSTIN + invoice details enable fake ITC claims. The 2024 Star Health and 2025 India Post breaches both started from internal access at supposedly trusted entities — the same risk applies to PDF tool servers, whose security posture you cannot audit.

Uploading GSTIN data to third-party PDF tools is avoidable risk

Once the unmerged invoices reach a third-party server, the privacy and commercial-confidentiality benefit is already lost. The merged output protects no one if the inputs leaked en route.

Browser-local processing closes that exposure. PDF Mavericks uses pdf-lib and WebAssembly to run the merge entirely on your device. The page loads the JavaScript, you drop the invoices, the merge happens in memory, the file downloads. No network request carries your invoice content. You can verify in DevTools Network tab: zero outbound transfers of file data.

Naming and ordering for ITC reconciliation

The file name is the index. A consistent naming convention saves hours during audit response and CA handover:

File name: <GSTIN>_AY<FY>-<Q>_PURCHASES.pdf
Example: 27ABCDE1234F1Z5_AY2025-26-Q3_PURCHASES.pdf
Internal order: primary sort by supplier GSTIN (alphanumeric), secondary sort by invoice date within each supplier.
Cover page (optional but recommended): a single page listing supplier name, GSTIN, invoice count, and total taxable value per supplier, with the totals matching your GSTR-3B. Use /pdf-to-csv to extract invoice metadata first if you want to generate this table programmatically.
Bookmarks: if your merge tool supports it, add a bookmark per supplier so the auditor can jump to any GSTIN-cluster in one click. Optional, but a big win for audit-heavy industries.
Backup: keep the individual invoice PDFs alongside the merged file. The merge does not destroy the originals; reconcilable data is safer.

Common situations: CA handover, audit response, retention

CA handover for ITR filing: at the end of each quarter or financial year, your CA wants two PDF bundles — one for purchases (matched against GSTR-2B) and one for sales (your outward supplies). Each bundle is one merged PDF per period. Skip the email-attachment-limit headache by compressing each merged PDF via /compress to under 25MB.

GST audit response: when an audit notice arrives, the standard ask is "produce all purchase invoices for tax period X." A merged PDF in the naming convention above is the professional response. Officers typically accept it as the primary submission and only ask for individual originals if a specific entry triggers a deeper inquiry.

Retention: 72 months × 4 quarters = 24 merged PDFs per FY. Across multiple FYs, you end up with a clean archive indexed by file name. A USB drive, an encrypted external HDD, or a private cloud bucket (only if encrypted at rest) all work for cold storage.

ITR-1 / ITR-4 submission: as of AY 2026-27, the CBDT-notified ITR-1, ITR-4, and ITR-V forms are live on the e-Filing portal. The portal does not require you to upload the merged invoice PDF — but you need it on file for any post-filing scrutiny notice (Section 143(2)) which can arrive up to 12 months after the assessment year ends.

E-invoices with IRN and signed QR codes

E-invoicing is mandatory for B2B supplies above prescribed turnover thresholds. Each e-invoice carries an IRN (Invoice Reference Number, a 64-character hash) and a digitally signed QR code generated by the NIC's Invoice Registration Portal (IRP).

A common worry: does merging the PDFs break the IRN or the digital signature? Answer: no. PDF Mavericks' merge operation (powered by pdf-lib) copies each page as-is into the output PDF. The IRN text remains intact. The QR code image remains scannable and decodable. The page-level digital signature embedded by the IRP issuer also remains valid; the merge does not re-render or re-sign the page content.

Verify after merge: open the merged PDF, scan any QR code with a phone, and check that the decoded IRN matches the IRP database. If a downstream consumer needs to verify a single invoice from the merged bundle, the QR code on that page is still self-authenticating against the IRP.