PDF to PDF/A for India: MCA, GST and Court Filing

What "pdf to pdf/a india mca" actually means

If you have hit a "file not in PDF/A format" rejection while attaching a document to an MCA21 form, the e-filing portal's validator has refused your file at the byte level. The PDF you generated from Word, Excel, or a scanner output is a regular PDF. The regulator wants an archival PDF — specifically PDF/A-1b, the format standardised as ISO 19005-1. The difference is not visible when you open the file. It is structural: which fonts are embedded, which color profile is declared, whether scripts exist inside the PDF, whether transparency layers are present. Pdf to pdf/a india mca filings is a one-way checkpoint at the portal — the validator either accepts the file or rejects it, and the rejection message rarely tells you which specific rule failed.

This guide walks through what India's three big regulator portals — MCA21, GST, and the courts — actually require, the five common reasons your file gets rejected, and how to check your PDF in the browser before you waste an upload attempt. The pre-check runs entirely in your browser. The PDF never leaves your device, which matters when you are uploading audited financials, GSTR-9C reconciliations, or sealed court pleadings.

MCA21: which forms require PDF/A and why

The MCA21 portal at mca.gov.in is the filing system for the Ministry of Corporate Affairs. Every form attachment — board resolutions on AOC-4, director KYC supporting documents on DIR-3 KYC, share-transfer evidences on PAS-3, audit reports on MGT-7 — passes through the portal's document validator. The MCA21 help portal documents the requirement plainly: attachments must be in PDF format, must be searchable, and must not contain encryption, scripts, or multimedia. In practice this collapses to PDF/A-1b conformance. A scanned image PDF without OCR will be rejected for not being searchable. A Word-exported PDF without font embedding will be rejected. A PDF with a password set will be rejected even if the password is empty.

The cost of a rejection at MCA21 is concrete. AOC-4 has a hard filing window — 30 days from the AGM date for most companies. If your PDF fails validation on day 29 at 11 PM, you may have to pay late fees of Rs. 100 per day of delay under section 403 of the Companies Act, 2013. DIR-3 KYC has an even tighter annual window each September, and missing it deactivates the DIN. Form INC-22A (active company tagging) had a one-shot window where rejected filings often meant struck-off status. The pattern: the portal is strict, the deadline is fixed, and the rejection message is generic. The fix has to happen before you click upload.

GST portal: PDF format rules per attachment slot

The GST portal at gst.gov.in is more permissive than MCA21 on attachment format but still rejects four categories of files. One: encrypted PDFs — common with bank-statement exports for GSTR-9 reconciliations, where SBI and HDFC password-protect statements by default. Two: PDFs with embedded multimedia — happens when you save a Word document containing a screenshot of a YouTube embed. Three: files above the slot-specific size cap, typically 5 MB but as low as 1 MB on some form attachments. Four: image-only scans where the portal asks for searchable text — common on GSTR-9C reconciliation statements signed by a Chartered Accountant.

The slots that explicitly require PDF/A or PDF/A-like conformance include the supporting-document upload on the GST refund forms (RFD-01 series), the proof-of-payment slot on DRC-03 voluntary tax payment, and most appeal and revision form attachments. The slot validator accepts plain PDF/A-1b. Submitting a PDF/A-2b file works most of the time but is not guaranteed.

For bank-statement attachments on GST refunds, the workflow gets thornier. Most Indian banks deliver statements as password-protected PDFs. The GST portal refuses the encrypted file, but you cannot legally distribute the unlocked file to a third-party server for conversion. The browser-local path: unlock the statement on your laptop using our unlock-pdf tool (the unlock runs in your browser, the statement never uploads anywhere), then run the pre-check, then upload to the portal.

eCourts, NCLT, ITAT and High Court e-filing

The court e-filing landscape in India is fragmented across the Supreme Court's e-Filing 3.0 portal, the eCourts platform for district and subordinate courts, NCLT for company law matters, ITAT for income tax appeals, and individual High Court e-filing portals. The common requirement across all of them: case documents must be in searchable PDF format, with no encryption, no embedded scripts, file size below the court-specific cap (5 MB on most High Court portals, 10 MB on Supreme Court), and OCR-applied if any page is a scan.

Delhi High Court's e-filing rules document specifies PDF/A as the required format for case documents. The portal validator runs at upload, and the rejection bounces back the same generic "invalid PDF format" message. The Supreme Court's e-Filing 3.0 manual published on the court's website is explicit that pleadings must be searchable — in practice this means PDF/A with an OCR text layer for any scanned exhibits. NCLT and ITAT both require PDF/A for case-document uploads under their respective procedure rules. Bombay High Court and Karnataka High Court e-filing platforms accept PDF/A and reject encrypted or image-only files.

The pattern: every court portal does upload-time validation. You get one rejection message, no diagnostic. The pre-check is the only honest way to know the failure reason before you submit. For redacted exhibits — common in matrimonial, IBC, and writ petitions — use the browser-local redaction tool first, then the pre-check, then upload. Redaction has to be byte-level (the underlying text removed, not just covered with a black rectangle), which our tool handles. A black-rectangle "redaction" in a PDF still ships the original text underneath.

Five common rejection reasons

Across MCA21, GST, and court portals, five rejection causes account for the bulk of failures.

1. Fonts not embedded. The most frequent cause. Word for older Windows installs has the "embed fonts in the file" option off by default. When you Save As PDF, the font references stay symbolic — Arial, Times New Roman — without the actual glyphs. PDF/A requires every font used in the document to be fully embedded so the file renders identically on a system without that font installed. Fix: in Word, File → Options → Save → check "Embed fonts in the file." In LibreOffice, Tools → Options → LibreOffice Writer → Print → uncheck "Use only standard fonts"; the PDF export embeds fonts by default. In Acrobat, the Preflight tool can re-embed missing fonts on an existing PDF.

2. No ICC color profile. The PDF references device-RGB or device-CMYK colors without declaring which exact color space those device values map to. PDF/A forbids ambiguous color. Fix: the source application has to embed an output intent — typically the sRGB IEC61966-2.1 profile, a 3 KB ICC blob. Word does this automatically when PDF/A export is enabled. Manual fix: Acrobat Pro's "Convert to PDF/A" action, or the Ghostscript command in the next section.

3. JavaScript or form scripts present. Common with PDFs derived from interactive forms, even when the form is no longer being filled. PDF/A bans all JavaScript. Fix: open in Acrobat, Tools → JavaScript → Remove All JavaScript. Or re-export from the source document without form-fill enabled.

4. Transparency layers. PDF/A-1b bans transparency completely. Watermarks, semi-transparent stamps, and some logos introduce transparency. Fix: flatten transparency before export — in Word and Acrobat, the "Flatten Layers" or PDF/A export option handles this. Manual fix: Ghostscript's pdfwrite device flattens transparency when PDF/A mode is set.

5. Encryption or password protection. Even an empty password counts. The portal validator refuses any encrypted file. Fix: open the PDF, enter the password if any, Save As without encryption. For bank statements where you do not own the encryption key, the bank's online portal usually offers a non-password version on request, or you use the browser-local unlock tool with the password you received.

The pre-check flow before you upload

The pdfmavericks PDF/A pre-check runs as a single browser tab. Drop the PDF on the drop zone, wait 5 to 15 seconds depending on file size, read the report. The report covers font embedding status per font used in the file, declared ICC color profile, presence of JavaScript, presence of transparency, encryption state, XMP metadata validity, and the searchability check for OCR text layers. Each check returns PASS, WARN, or FAIL with a one-line explanation and a recommended fix.

What the pre-check does not do is convert. Browser JavaScript cannot embed a complete ICC profile, subset fonts byte-correctly, or write a valid PDF/A XMP packet without rasterising. The pre-check tells you what is wrong; the fix has to happen in Word, Acrobat, LibreOffice, or Ghostscript. The pre-check exports a JSON report you can attach to a compliance audit log.

The privacy story matters here. An MCA filing attachment for a Schedule-IV related-party transaction, a GST refund supporting statement, or a sealed court exhibit are documents you do not want passing through a third-party server. The pre-check runs in your browser; the PDF stays on your machine. Server-side PDF/A converter tools sit between you and the regulator's validator and add an extra data-exposure step you did not need.

How to actually create a PDF/A file

The pre-check surfaces issues; the fix happens upstream. Four reliable paths.

Microsoft Word. File → Save As → PDF → Options → check "ISO 19005-1 compliant (PDF/A)" in the Word for Windows export dialog. The output is PDF/A-1b. For Word on Mac, use File → Print → PDF dropdown → Save as Adobe PDF (Acrobat required) and pick the PDF/A-1b preset. This handles font embedding, color profile, transparency flattening, and metadata in one step.

LibreOffice. File → Export As → Export as PDF → in the dialog, check "Archive (PDF/A)" under the General tab. Pick PDF/A-1b in the version dropdown. The export embeds fonts and the sRGB ICC profile automatically. Output is veraPDF-clean on typical office documents.

Adobe Acrobat Pro. File → Save As Other → PDF/A → pick PDF/A-1b. Acrobat handles every requirement internally — font subsetting, ICC embedding, XMP, transparency flattening. Subscription is around USD 14.99 per month at the time of writing. For a one-off MCA or court filing this is sometimes cheaper than the cost of a missed deadline. For ongoing CS or CA workflow, Acrobat is the lowest-friction option.

Ghostscript (free). Command line: gs -dPDFA=1 -dPDFACompatibilityPolicy=1 -sColorConversionStrategy=RGB -sDEVICE=pdfwrite -o output.pdf input.pdf. The flag -dPDFACompatibilityPolicy=1 tells Ghostscript to flag and adjust non-PDF/A elements rather than failing outright. -sColorConversionStrategy=RGB converts device colors to RGB; Ghostscript embeds the sRGB profile automatically with PDF/A mode set. Install via brew install ghostscript on macOS, apt install ghostscript on Ubuntu, or download from ghostscript.com on Windows. Output is usually veraPDF-clean on text-based documents.

After the fix, re-run the pre-check. If all checks PASS, upload to the portal. If the portal still rejects, the final verdict is veraPDF — download the Greenfield release from verapdf.org/software (a Java archive, around 80 MB), run java -jar verapdf-greenfield-X.Y.Z.jar --format text yourfile.pdf, and check the failing clause. veraPDF is the canonical validator funded by the PDF Association; its verdict matches what most portal validators run server-side.

India-specific considerations

A few patterns recur on Indian regulator workflows. Bank statements arrive password-protected from SBI, HDFC, ICICI, Axis, and Kotak; the password format is usually a combination of PAN and date of birth. Unlock locally before pre-check. Aadhaar copies attached as KYC supporting documents have to be masked under UIDAI rules — first eight digits hidden. Use the Aadhaar masking tool before the PDF/A conversion. For Hindi-language Aadhaar removal walkthroughs, see Aadhaar PDF password kaise hatayen.

For Chartered Accountants and Company Secretaries filing on behalf of clients, the workflow loop tightens every Q1 and Q4 — audit season for AOC-4 in October, GSTR-9 in December, and DIR-3 KYC in September. Building the pre-check into the firm's pre-flight checklist before any MCA21 or GST upload removes the most common cause of last-day rejections. The pre-check runs in 5 to 15 seconds per file. On a batch of 40 attachments for a year-end filing, that is under 10 minutes of verification — cheaper than one re-submission cycle at midnight before a deadline.