{"id":25,"date":"2026-09-11T11:05:55","date_gmt":"2026-09-11T11:05:55","guid":{"rendered":"https:\/\/wealth4india.com\/insights\/?p=25"},"modified":"2026-09-11T13:39:17","modified_gmt":"2026-09-11T13:39:17","slug":"dgft-certificate-of-origin-api-2026","status":"publish","type":"post","link":"https:\/\/wealth4india.com\/insights\/dgft-certificate-of-origin-api-2026\/","title":{"rendered":"DGFT Certificate of Origin API 2026 : Exporters Can Now File CoO Directly Through ERP"},"content":{"rendered":"\n

DGFT Certificate of Origin API 2026: ERP Filing Guide<\/strong><\/h2>\n\n\n\n

The DGFT Certificate of Origin<\/strong> process has entered an important new phase of digital integration. The Directorate General of Foreign Trade (DGFT), Ministry of Commerce & Industry, has introduced an Open API facility for Certificates of Origin (CoO)<\/strong> on the Trade Connect e-Platform, allowing eligible exporters to connect their ERP, accounting or other business software directly with the government\u2019s Certificate of Origin system.<\/p>\n\n\n\n

The facility was announced on 7 September 2026<\/strong> and covers both Preferential and Non-Preferential Certificates of Origin<\/strong>. In practical terms, exporters who presently enter the same invoice, product, buyer and shipment information in their accounting system and again on the CoO portal may now be able to transfer that information electronically through API integration. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

For Indian exporters, this is not merely another portal update. It is part of a broader movement towards system-to-system compliance<\/strong>, where accounting records, GST data, customs documentation and export documentation increasingly originate from the same underlying digital records.<\/p>\n\n\n\n

What has DGFT changed?<\/h2>\n\n\n\n

Until now, an exporter might prepare an export invoice in an ERP or accounting system and then separately enter many of the same details while applying for the Certificate of Origin.<\/p>\n\n\n\n

The new API facility enables eligible systems to exchange application data directly with DGFT.<\/p>\n\n\n\n

In simple terms, the workflow can move from:<\/p>\n\n\n\n

ERP \/ Accounting Software \u2192 Manual CoO Portal Entry \u2192 Certificate<\/strong><\/p>\n\n\n\n

to:<\/p>\n\n\n\n

ERP \/ Accounting Software \u2192 DGFT API \u2192 CoO Processing \u2192 Certificate<\/strong><\/p>\n\n\n\n

DGFT states that the objective is to reduce repetitive data entry, minimise errors and expedite the application process. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

Exporters considering such integration should first ensure that the underlying accounting and ERP data is reliable. Businesses that need help organising books, MIS, accounting systems and internal financial processes may refer to our Accounting & Virtual CFO Services<\/a>.<\/p>\n\n\n\n

What is a Certificate of Origin?<\/h2>\n\n\n\n

A Certificate of Origin<\/strong> is an important international trade document certifying the origin of exported goods.<\/p>\n\n\n\n

Depending upon the transaction and importing country, it may be required for customs clearance, contractual compliance, trade-remedy requirements or entitlement to preferential customs duties.<\/p>\n\n\n\n

There are broadly two categories relevant to the new DGFT facility.<\/p>\n\n\n\n

Preferential Certificate of Origin<\/h3>\n\n\n\n

A Preferential Certificate of Origin is issued under an applicable Free Trade Agreement, Regional Trade Agreement, CEPA, CECA, PTA or similar arrangement.<\/p>\n\n\n\n

Where the prescribed Rules of Origin are satisfied, the overseas importer may be entitled to claim a concessional tariff or other preferential treatment.<\/p>\n\n\n\n

Non-Preferential Certificate of Origin<\/h3>\n\n\n\n

A Non-Preferential Certificate of Origin establishes the country of origin of the goods but does not itself provide an FTA-related customs-duty concession.<\/p>\n\n\n\n

It may nevertheless be necessary for customs clearance, banking, buyer documentation, tenders, trade remedies or other commercial purposes.<\/p>\n\n\n\n

DGFT has specifically confirmed that the Open API facility supports both categories<\/strong>. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

How does the DGFT Certificate of Origin API work?<\/h2>\n\n\n\n

An API\u2014Application Programming Interface\u2014allows two software systems to communicate and exchange structured information without requiring users to repeatedly type the same data.<\/p>\n\n\n\n

For an exporter, information such as exporter details, buyer particulars, invoice numbers, product descriptions, quantities and other relevant application data may already be available in the ERP.<\/p>\n\n\n\n

The new integration framework allows such data to be transmitted to DGFT\u2019s CoO platform, subject to registration, authentication and the prescribed technical requirements.<\/p>\n\n\n\n

The official registration and technical integration process is available through the Trade Connect Certificate of Origin portal<\/a>.<\/p>\n\n\n\n

Three APIs are available<\/h2>\n\n\n\n

DGFT has introduced three separate APIs within the framework.<\/p>\n\n\n\n

API<\/th>Main Function<\/th><\/tr><\/thead>
Authentication Token API<\/td>Secure authentication and generation of access credentials<\/td><\/tr>
CoO File API<\/td>Submission of Certificate of Origin applications and receipt of certificates<\/td><\/tr>
Certificate Verification API<\/td>Verification of Certificates of Origin already issued<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Exporters are required to obtain API credentials and register the IP addresses from which their systems will connect. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

This structure is particularly useful for larger exporters, manufacturers and organisations handling high volumes of CoO applications.<\/p>\n\n\n\n

Electronic tracking of Certificate of Origin applications<\/h2>\n\n\n\n

Another useful feature is the transaction ledger maintained for each application.<\/p>\n\n\n\n

DGFT states that the ledger records application status such as Draft, In Process, Approved, Certificate Issued and Rejected<\/strong>, together with information including acknowledgement ID, file number, file date and certificate number. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

From a finance and compliance perspective, this can create a stronger audit trail.<\/p>\n\n\n\n

Businesses should consider reconciling their CoO records with export invoices, shipping documents, accounting entries and GST records rather than treating Certificate of Origin applications as a separate administrative process.<\/p>\n\n\n\n

Security framework for DGFT Open API<\/h2>\n\n\n\n

The API framework also incorporates multiple information-security safeguards.<\/p>\n\n\n\n

According to the Ministry of Commerce & Industry, requests and responses are digitally signed using SHA-256 RSA digital signatures with 2048-bit X.509 certificates<\/strong>. Passwords are protected using PBKDF2 hashing with a dynamic salt, connections are restricted to IP addresses whitelisted by the exporter, and each access token remains valid for 60 minutes. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

Businesses implementing ERP-to-DGFT integration should therefore involve both their finance\/compliance team and their IT or ERP provider.<\/p>\n\n\n\n

Where businesses separately require Digital Signature Certificates for their corporate and regulatory compliance requirements, they may also review Digital Signature Certificate Services \u2013 Wealth4India<\/a>. The Wealth4India page inventory confirms this service page is part of the live business-setup section.<\/p>\n\n\n\n

Which FTAs and trade arrangements are covered?<\/h2>\n\n\n\n

The DGFT framework covers a substantial range of preferential trade arrangements and certification schemes.<\/p>\n\n\n\n

These include India\u2013Japan CEPA, India\u2013Korea CEPA, SAFTA, SAPTA, ASEAN\u2013India FTA, India\u2013Singapore CECA, India\u2013Malaysia CECA, India\u2013Chile PTA, India\u2013Mercosur PTA, India\u2013UAE CEPA, India\u2013Australia ECTA, India\u2013Oman CEPA, India\u2013EFTA TEPA and India\u2013UK CETA, besides the Generalized System of Preferences and the Non-Preferential CoO Scheme. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

The system automatically applies the relevant fields, origin criteria and validation requirements according to the selected agreement or certification scheme.<\/p>\n\n\n\n

That automation is useful\u2014but exporters should not interpret it as a substitute for analysing the underlying Rules of Origin<\/strong>.<\/p>\n\n\n\n

A Certificate of Origin does not automatically create FTA eligibility<\/h2>\n\n\n\n

This point deserves particular attention.<\/p>\n\n\n\n

An exporter cannot obtain tariff benefits merely because a Certificate of Origin can be generated electronically.<\/p>\n\n\n\n

The exported goods must independently satisfy the Rules of Origin under the relevant trade agreement.<\/p>\n\n\n\n

Depending upon the agreement, this may involve issues such as tariff classification, change in tariff heading, regional value-content requirements, manufacturing criteria, sourcing of inputs and other product-specific rules.<\/p>\n\n\n\n

Accordingly, exporters should maintain supporting documentation capable of demonstrating how the origin criterion has been satisfied.<\/p>\n\n\n\n

Automation should make the process faster\u2014it should not automate an unsupported origin declaration.<\/p>\n\n\n\n

Why this matters for accounting and ERP systems<\/h2>\n\n\n\n

The most important long-term implication of the DGFT Certificate of Origin API may actually lie outside the CoO portal.<\/p>\n\n\n\n

The same business data may increasingly feed several compliance systems.<\/p>\n\n\n\n

An export transaction can potentially touch:<\/p>\n\n\n\n

Accounting records \u2192 GST \u2192 e-Invoice \u2192 Shipping Bill \u2192 Customs \u2192 Certificate of Origin \u2192 Banking \u2192 Foreign-exchange realisation<\/strong><\/p>\n\n\n\n

If the product description in the ERP differs from the export invoice, the HS classification differs from GST\/customs records, or customer and shipment information is inconsistent across systems, automation can reproduce those inconsistencies very quickly.<\/p>\n\n\n\n

This makes ERP master-data governance<\/strong> increasingly important.<\/p>\n\n\n\n

For exporters using Tally, Zoho Books, QuickBooks or integrated ERP systems, periodic reconciliation of financial and statutory data should become part of the compliance framework. Our Virtual CFO and Accounting Outsourcing practice<\/a>covers accounting-system setup, MIS and internal-control processes relevant to such businesses.<\/p>\n\n\n\n

GST compliance should also be aligned with export documentation<\/h2>\n\n\n\n

The Certificate of Origin system and GST system serve different statutory purposes, but exporters frequently use the same underlying invoice and transaction data for both.<\/p>\n\n\n\n

A well-controlled export compliance system should therefore compare export turnover and supporting documentation across books of account, GST returns, invoices and export records.<\/p>\n\n\n\n

Exporters should particularly examine whether invoice numbers, dates, taxable values, product descriptions and other transaction particulars reconcile across systems.<\/p>\n\n\n\n

Businesses requiring assistance with return filing, reconciliation and indirect-tax compliance may review GST Services \u2013 Wealth4India<\/a>. The attached Wealth4India inventory confirms the GST service page as an active tax-and-compliance page.<\/p>\n\n\n\n

Who is likely to benefit most?<\/h2>\n\n\n\n

The new facility is likely to create the greatest operational benefit for exporters processing a significant volume of Certificate of Origin applications.<\/p>\n\n\n\n

For example, consider a manufacturer generating hundreds of export invoices each month. Its ERP may already contain the buyer name, invoice details, product master, HS code, quantity, value and destination country.<\/p>\n\n\n\n

Re-entering this information separately for every CoO application consumes time and also creates a risk of typing errors.<\/p>\n\n\n\n

With appropriate API integration, much of this information can potentially flow directly from the business system into the DGFT Certificate of Origin process.<\/p>\n\n\n\n

For smaller exporters filing only occasional CoO applications, however, a full API integration project may not immediately be commercially justified.<\/p>\n\n\n\n

The PIB announcement describes the API as a facility available to eligible exporters; it does not state that every exporter must compulsorily migrate to API-based filing. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

What exporters should check before implementing the API<\/h2>\n\n\n\n

Before beginning technical integration, management should first review the compliance architecture.<\/p>\n\n\n\n

    \n
  1. Verify exporter master data.<\/strong> IEC, legal name, registered details and other master information should be current and consistent.<\/li>\n\n\n\n
  2. Review the product master.<\/strong> Product description, HS classification, unit of measurement and other relevant data should be standardised.<\/li>\n\n\n\n
  3. Review Rules of Origin.<\/strong> Preferential treatment should be claimed only where the applicable agreement and origin criteria are actually satisfied.<\/li>\n\n\n\n
  4. Map ERP fields with DGFT fields.<\/strong> The implementation team should identify exactly which ERP information will feed each CoO application field.<\/li>\n\n\n\n
  5. Clean customer and country data.<\/strong> Incorrect destination-country or buyer details can create avoidable rejection or reconciliation issues.<\/li>\n\n\n\n
  6. Establish maker-checker controls.<\/strong> API-based filing should still require an appropriate review and approval mechanism.<\/li>\n\n\n\n
  7. Maintain supporting documents.<\/strong> Automation of filing does not eliminate the need to maintain evidence supporting the declared origin.<\/li>\n\n\n\n
  8. Test before full deployment.<\/strong> A limited number of transactions should be tested before applying the integration to the entire export workflow.<\/li>\n\n\n\n
  9. Reconcile issued certificates.<\/strong> Certificates issued should periodically be matched with export invoices and underlying commercial records.<\/li>\n\n\n\n
  10. Review exception cases.<\/strong> Rejected or manually modified applications may indicate data-quality or process issues requiring correction.<\/li>\n<\/ol>\n\n\n\n

    New exporters should build compliance correctly from the beginning<\/h2>\n\n\n\n

    Businesses planning to enter export markets should preferably establish their entity, accounting, GST and compliance systems before volumes increase.<\/p>\n\n\n\n

    A properly structured company or LLP, organised books of account, GST registration where applicable and a suitable ERP or accounting system can significantly improve the ability to manage export documentation later.<\/p>\n\n\n\n

    Entrepreneurs still formalising their business may review our Company & LLP Registration Services<\/a> and, where eligible, Startup India Registration and DPIIT Recognition<\/a>.<\/p>\n\n\n\n

    This is also preferable from an SEO and user-experience perspective: a reader looking at DGFT compliance is linked only to genuinely related business-compliance services rather than unrelated tax pages.<\/p>\n\n\n\n

    DGFT API and internal controls: a management perspective<\/h2>\n\n\n\n

    For management, the right question is not simply:<\/p>\n\n\n\n

    \u201cCan our software connect with DGFT?\u201d<\/strong><\/p>\n\n\n\n

    The more important question is:<\/p>\n\n\n\n

    \u201cAre the records being transmitted by our software complete, accurate and consistently classified?\u201d<\/strong><\/p>\n\n\n\n

    When filing is manual, an experienced employee may sometimes notice an unusual description or incorrect field before submission.<\/p>\n\n\n\n

    With API automation, incorrect master data may move through the system far more efficiently.<\/p>\n\n\n\n

    The stronger approach is therefore:<\/p>\n\n\n\n

    automation + validated master data + approval controls + periodic reconciliation.<\/strong><\/p>\n\n\n\n

    This is particularly relevant for manufacturing companies, export houses, merchant exporters and businesses operating across multiple product lines or FTAs.<\/p>\n\n\n\n

    Will the DGFT API reduce compliance cost?<\/h2>\n\n\n\n

    Potentially, yes\u2014particularly for businesses handling a significant number of CoO applications.<\/p>\n\n\n\n

    Possible efficiencies include reduced duplicate entry, fewer manual transcription errors, faster preparation, easier application tracking and better integration with existing ERP workflows.<\/p>\n\n\n\n

    However, the initial integration itself may require technical development, testing, mapping and control design.<\/p>\n\n\n\n

    Businesses should therefore evaluate the expected number of CoO applications against the implementation and maintenance cost.<\/p>\n\n\n\n

    The business case is likely to be much stronger for high-volume exporters than for occasional exporters.<\/p>\n\n\n\n

    Frequently Asked Questions<\/h2>\n\n\n\n

    What is the DGFT Certificate of Origin API?<\/h3>\n\n\n\n

    The DGFT Certificate of Origin API is an Open API facility introduced through the Trade Connect e-Platform that enables eligible exporters to integrate ERP, accounting or other business software with DGFT’s Certificate of Origin system. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

    Can an exporter apply for Certificate of Origin directly from ERP software?<\/h3>\n\n\n\n

    Yes. Subject to API registration, authentication and the prescribed technical requirements, the facility enables electronic transfer of CoO application data from the exporter’s system to DGFT.<\/p>\n\n\n\n

    Does the API cover Preferential Certificate of Origin?<\/h3>\n\n\n\n

    Yes. It covers Preferential Certificates of Origin under supported FTAs and other trade arrangements.<\/p>\n\n\n\n

    Does it also cover Non-Preferential Certificate of Origin?<\/h3>\n\n\n\n

    Yes. DGFT has specifically stated that the facility covers Non-Preferential Certificates of Origin as well. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

    Is DGFT API integration compulsory?<\/h3>\n\n\n\n

    The Government announcement describes it as an available facility for eligible exporters. It does not state that every exporter is required to implement API integration.<\/p>\n\n\n\n

    Where can exporters register for the API?<\/h3>\n\n\n\n

    Registration, authentication and technical integration information is available on the official Trade Connect Certificate of Origin section<\/a>.<\/p>\n\n\n\n

    Does API filing guarantee preferential customs duty?<\/h3>\n\n\n\n

    No. Preferential treatment depends upon compliance with the applicable trade agreement and its Rules of Origin. The API automates processing; it does not independently establish that the goods qualify for preferential origin.<\/p>\n\n\n\n

    Professional perspective<\/h2>\n\n\n\n

    The DGFT Certificate of Origin Open API<\/strong> is a significant development in India’s export-compliance digitisation.<\/p>\n\n\n\n

    Its immediate benefit is obvious: exporters may reduce repetitive entry of information already available in their ERP or accounting system.<\/p>\n\n\n\n

    Its more important long-term implication, however, is that regulatory compliance is becoming increasingly dependent on the quality of the underlying business data.<\/p>\n\n\n\n

    Exporters should therefore use this development as an opportunity to review not only their Certificate of Origin filing process, but also ERP masters, HS classifications, accounting records, GST reconciliation, export documentation and internal approvals.<\/p>\n\n\n\n

    The businesses that will benefit most from automation are those whose underlying records are already disciplined.<\/p>\n\n\n\n

    Need assistance with accounting, GST or export-related business compliance?<\/h2>\n\n\n\n

    Our team assists businesses with accounting-system setup, GST compliance, financial controls, business structuring, MIS, taxation and Virtual CFO support.<\/p>\n\n\n\n

    For accounting and finance-process assistance, see Accounting & Virtual CFO Services \u2013 CA Alok Kumar<\/a>.<\/p>\n\n\n\n

    For GST and related business compliance, see GST Services \u2013 Wealth4India<\/a>.<\/p>\n\n\n\n

    For entrepreneurs setting up or restructuring an exporting entity, see Company & LLP Registration<\/a>.<\/p>\n\n\n\n

    You may also Book an Appointment through Wealth4India<\/a> for a professional review of the business and compliance requirements. The attached inventory confirms Wealth4India’s appointment page and its current WordPress Insights section.<\/p>\n\n\n\n

    Official reference<\/h2>\n\n\n\n

    The update is based primarily on the Press Information Bureau release dated 7 September 2026<\/strong> <\/a>titled \u201cDGFT Introduces Open API Facility for Certificate of Origin on the Trade Connect e-Platform\u201d<\/em>. It refers further to DGFT Trade Notice No. 25\/2026-27 dated 7 September 2026<\/strong> and the step-by-step manual annexed to that Trade Notice. (Press Information Bureau<\/a>)<\/p>\n\n\n\n

    \n\n\n\n

    DGFT Certificate of Origin API 2026 Trade Connect ERP filing<\/a><\/code><\/h3>\n\n\n
    \n
    \"\"<\/a>
    DGFT Certificate of Origin API 2026<\/figcaption><\/figure>\n<\/div>\n\n\n

    <\/p>\n","protected":false},"excerpt":{"rendered":"

    DGFT Certificate of Origin<\/p>\n","protected":false},"author":1,"featured_media":26,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[30,31],"tags":[22,29,24,26,20,27,28,23,21,25],"class_list":["post-25","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dgft-certificate-of-origin","category-dgft-certificate","tag-certificate-of-origin-india","tag-certificate-of-origin-online","tag-certificate-of-origin-through-erp","tag-coo-api-integration","tag-dgft-certificate-of-origin-api","tag-dgft-open-api","tag-ecoo-dgft","tag-non-preferential-certificate-of-origin","tag-preferential-certificate-of-origin","tag-trade-connect-certificate-of-origin"],"_links":{"self":[{"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/posts\/25","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/comments?post=25"}],"version-history":[{"count":2,"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/posts\/25\/revisions"}],"predecessor-version":[{"id":40,"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/posts\/25\/revisions\/40"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/media\/26"}],"wp:attachment":[{"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/media?parent=25"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/categories?post=25"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wealth4india.com\/insights\/wp-json\/wp\/v2\/tags?post=25"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}