Trade Portal Document Upload Errors: Causes & Fixes
TL;DR - Summary
- What are trade portal document upload errors? - These are failures when attaching, validating or submitting documents on services such as DGFT, ICEGATE and the GST portal. A successful file transfer does not always mean the application has been submitted.
- What causes trade portals to reject uploaded documents? - Common causes include the wrong file type or size, incomplete or mismatched details, signing problems and browser or session issues. Portal outages and incomplete submission steps can also cause failures.
- How do you fix the most common trade portal document upload errors? - Save the exact error, check the requirements for that upload field, then fix the file, data or signing issue. Check the saved application before retrying so you do not create a duplicate filing.
- What should you check before uploading a document to a trade portal? - Check the field’s file type and size limit, document readability, current application details and supported browser. If signing is required, check the portal’s signing utility and certificate too.
What Are the Common Trade Portal Document Upload Errors?
Trade portal document upload errors can occur while attaching a file, validating its details or submitting an application. Common causes fit into four useful troubleshooting groups: file format, file size, signing or browser issues, and missing or mismatched data. These are a starting point, not an exhaustive list: service outages, access permissions and incomplete submission steps can also block a filing.
Indian exporters and compliance filers encounter these problems when applying for an IEC, uploading customs supporting documents, registering bank details or filing GST applications. A failed submission can delay the related registration, clearance or claim. AD Code registration is handled through ICEGATE; it is not a separate government ‘AD Code portal’.
⚠️ COMMON MISCONCEPTION
A document that opens fine on your computer is not automatically accepted by the portal. Format, size, and security settings all matter independently.
Why Do Trade Portals Reject Uploaded Documents?
Start with four checks: does the field accept this file type, is the file within its size limit, are the signing tools and browser working, and are the required details complete and correct? If those checks pass, look for a portal notice, permission issue or an unfinished submission step.
Requirements vary by service and upload field, not just by portal. The table gives workflow-specific examples and distinguishes the Indian Trade Portal information service from statutory filing portals. Follow the instructions on your current upload screen.
| Portal | Accepted File Formats | Size Limit | Recommended Browser |
|---|---|---|---|
| DGFT (IEC application) | Maximum 5 MB for scanned supporting documents | Updated Chrome; follow DGFT’s current signing-utility instructions | |
| ICEGATE (e-SANCHIT) | PDF; preparation guidance specifies PDF/A (ISO 19005-2) | FAQ: 1–20 MB, depending on document type; check the selected field | Common Signer guidance lists Chrome, Edge and Firefox; check the required setup |
| GST Portal (normal-taxpayer registration) | PDF or JPEG in the cited registration fields | Photos: 100 KB; signatory appointment and premises proof: 1 MB; E-KYC documents: 2 MB. Check each field. | Desktop Edge, Chrome or Firefox; DSC signing is not supported on mobile |
| Indian Trade Portal | Trade-information service, not the statutory filing service described here | Statutory document filing takes place on the relevant filing portal | Follow the destination filing portal’s browser guidance |
- PDF security and format: Use the PDF variant required by the workflow. ICEGATE’s e-SANCHIT preparation guidance specifies PDF/A (ISO 19005-2). Check encryption and signing requirements separately; a PDF that opens on your computer may still need changes to meet those rules.
- Image files: JPG or JPEG may be accepted in some fields and rejected in others. Check the exact document category; a photograph field can have different rules from a bank-proof or invoice field.
⚠️ COMMON MISCONCEPTION
A file under the size limit is not automatically accepted. Format and security settings are checked independently of file size.
How to Fix Trade Portal Document Upload Errors
Read the exact message before changing the document. Use the four groups below to narrow down the issue, but also check whether the application is saved, awaiting a signature or affected by a service outage.
- Format errors: Export the original document to the type accepted by that field. Changing a filename from .jpg to .pdf does not convert it. Keep the original and avoid converting or compressing a digitally signed file, which can invalidate its signature.
- Size errors: Compress the file or adjust the scan settings to meet the field’s limit. Reopen the result and check every page, stamp and signature before uploading. Use a trusted local tool for confidential business documents.
- DSC or browser errors: If the workflow requires a Digital Signature Certificate (DSC), check the portal’s signing utility, token driver and certificate validity. Confirm that the correct certificate is registered or selected, then retry in a supported browser.
- Data mismatch errors: Compare the specific field named in the error with the application, supporting document and current portal record. Correct the wrong record or document rather than changing a valid document to match outdated data.
Refreshing a page is not the same as submitting an application. It may lose unsaved work. Check the saved application and any acknowledgement before reattaching a file or starting another submission.
✅ PRO TIP
Save the exact error message, time, application reference and a screenshot before troubleshooting. Change one thing at a time so you can tell which fix worked.
How to Resolve File Format, Size and Naming Errors
Match the requirements shown for the specific upload field. Use an accepted file type, keep within its size limit and follow any filename rules. A file that works in one application may not work in another, even on the same portal.
- Format: Use the file type the field accepts and check that it opens without an error. For e-SANCHIT, follow its PDF/A preparation guidance and DSC submission steps. For other services, follow the field’s own rules rather than assuming every portal accepts the same PDF settings.
- Size: Compress a file or adjust scan settings only while keeping every page clear and meeting the workflow’s requirements. e-SANCHIT preparation guidance calls for at least 200 DPI in black and white. Recheck small print, stamps and signatures after compression.
- Naming: Follow any filename restrictions on the upload screen. A short name such as ‘shippingbill001.pdf’ can help avoid problems with special characters or long paths, but it does not fix an incorrect file type.
- Image files: Upload JPG, JPEG or PNG only where that field accepts them. If PDF is required, convert the image properly and check the result rather than simply changing the extension.
💡 QUICK INSIGHT
Compression can reduce file size, but the result depends on the document. Check the final size and readability instead of relying on a promised percentage reduction.
How to Fix Errors Caused by Incorrect or Missing Document Details
A mismatch error can relate to the application fields, linked master data or supporting evidence. Read the field or error code first, then compare the records. An upload failure alone does not prove the portal has read and checked every detail inside the document.
Depending on the application, relevant details can include legal name, PAN, IEC, GSTIN, bank account and address. Some forms also use email and mobile details for verification. Check the fields required for your filing rather than assuming every portal checks the same set.
- Shipping bill filings on ICEGATE: Reconcile exporter identifiers, invoice references, HS codes, quantities and values with the commercial invoice and packing list. Check port, bank and transport details against the relevant records. Supporting-document uploads through e-SANCHIT are a separate step from filing the shipping bill.
- AD Code registration on ICEGATE: Check the AD Code and associated bank account in Bank Account Management. Registration is required at one Customs port; after approval it is available system-wide. Amendments go through the port where the code was registered, not a fresh registration at every shipment location.
- DGFT portal uploads: Check the application’s IEC, PAN and other required details against current records. If a recent amendment is not reflected, check its status and the portal’s update instructions before changing a correct document or submitting again.
Keep current, readable evidence for each field and explain legitimate differences, such as a separate registered and business address or a freight adjustment. Do not force unrelated fields to match just because they appear on different documents.
What to Do When a Trade Portal Shows an Error Despite a Successful Upload
A successful upload message may confirm only that the file was attached. The application may still need validation, a signature, payment or final submission. For e-SANCHIT, select the document type and submit with a valid registered DSC to obtain IRN/DRN references, then link the IRN to the relevant customs declaration.
A missing document can reflect an unfinished step, processing delay, display issue or a validation error. Use the actual status or error code to decide what to do next; do not assume the portal rejected the document’s contents.
- Check the workflow’s stated processing time and actual acknowledgement. e-SANCHIT’s FAQ says a confirmation email is triggered within five minutes after submission. That is not a processing promise for other portals or a substitute for checking the IRN/DRN.
- If the display appears stale, save your work and sign out, then log in again and reopen the application. Clear site-specific cache or cookies if the portal’s troubleshooting instructions recommend it; doing so can end your session.
- If the status remains unclear, raise a ticket through the official helpdesk. Include the service, error code, time, application or document reference and a screenshot. A transaction reference helps trace the attempt; only the relevant acknowledgement or final status confirms completion.
⚠️ COMMON MISCONCEPTION
Check existing references before retrying. e-SANCHIT requires unique document names, and a document submitted with an IRN/DRN cannot be deleted. Uploading another supporting document is not the same as filing a second shipping bill.
How to Resolve Login, Session and Technical Errors During Upload
For login, session or signing errors, check the portal’s system requirements and service notices first. Save your work before restarting a session. Use the browser and signing utility supported for that particular service rather than applying one setup to every portal.
- Session timeouts: Save each stage where possible, prepare files before signing in and avoid leaving the form idle. If you are logged out, reopen the saved application in a fresh session. Reduce file size only if it exceeds the field’s limit or makes the upload impractically slow.
- DSC errors: Where DSC signing is required, check that the USB token is recognized, the portal’s utility and token driver are running, and the certificate is valid. Also check the selected certificate and authorized signatory details. Follow the portal’s error-specific instructions.
- Browser compatibility: Use a supported, up-to-date browser. GST lists desktop Edge, Chrome and Firefox, while DGFT’s IEC FAQ also lists Firefox and Safari. Check the signing utility’s separate requirements; GST does not support DSC signing on mobile devices or mobile browsers.
- Extensions: Temporarily disable an extension if it appears to block the upload or signing window. A private window can help isolate a session issue, but it may also disable a required extension or block cookies. Use it only if the portal’s setup supports it.
- Pop-up blockers: Allow pop-ups for the official portal if its instructions or a blocked-window alert show they are needed. Keep protections enabled for other websites; not every upload or signature uses a pop-up.
- Cache and cookies: Try a fresh login first. Clear site-specific browser data only when troubleshooting a persistent display or session problem, after saving your work. GST requires cookies and JavaScript to be enabled, so do not disable them as an upload fix.
Pre-Upload Checklist
- File type matches the instructions for this upload field
- File size is within the portal's stated limit
- Scanned pages, stamps and signatures are clear at the permitted settings
- DSC token is recognized, if this filing requires it
- Required signing utility and drivers are installed; certificate is valid
- Browser and signing setup meet this service’s current requirements
- Required pop-ups are allowed only for the official portal
- No extension or browser setting is blocking the required upload or signing tools
- Session is fresh: log in just before uploading, and don't leave the tab idle
Portal filing and payment collection are separate tasks; customers may pay before or after shipment under your agreed terms. With Skydo, Indian exporters can receive international business payments and download a free, automatically generated Foreign Inward Remittance Advice (FIRA) for each payment. Check our current pricing for the applicable transaction fee.
⚠️ WATCH OUT
Uploading, signing and final submission can be separate steps. Before closing the session, check for the acknowledgement or completion status required by that workflow.
What to Do If Your Documents Keep Getting Rejected
Repeated rejection is a reason to stop guessing, not proof of a system-wide fault. Review the error history, the exact upload field and the saved application. Check the document and account records together, then ask the official helpdesk for help if the cause remains unclear.
For a goods-export filing, keep the relevant documents below ready. An IEC or GST registration application will have a different checklist, so follow that service’s requirements rather than uploading every item here:
- Commercial invoice and packing list
- IEC, GST and exporter details
- AD Code approval and associated bank information in ICEGATE
- Product description with HS code, quantity and value
- Transport, port and shipment details
- Export scheme or incentive details, where applicable
- Consistency: Check the same identifiers wherever they are required, and explain legitimate differences between documents. A name variation may need correction or supporting evidence, but not every spelling or formatting difference automatically causes rejection.
- Current, readable records: Replace missing pages, unreadable scans or outdated evidence. Reopen the final uploaded version to check that compression has not made it unusable.
- Portal profile: Compare current master data with the application. If an address, bank account or other detail has changed, follow the portal’s amendment process and check the update status before refiling.
- Helpdesk: Use the official DGFT, ICEGATE or GST helpdesk for the service involved. Include the error message, screenshot, attempt time and reference if available. Never share passwords, OTPs or a DSC token PIN. Keep the ticket number and check the submission status before retrying.
Why does my upload show "success" but the document is not reflected in the portal?
Upload success can mean only that the file was attached. Check whether validation, signing, payment or final submission is still pending. Use the saved application and relevant acknowledgement to confirm completion, and follow that workflow’s stated processing time.
Why is my DSC signature failing after I upload the document?
Why are my image files being rejected even though they are under the size limit?
How long does portal processing take after a successful document upload?
Can I upload documents on any browser, or does it matter which one I use?
What should I do if the portal keeps logging me out during the upload?
Does uploading the same document multiple times cause any problems?
Is a PDF/A file the same as a standard PDF for portal uploads?
