Your supplier ESG declaration was not built for CBAM, either.

Two weeks ago we wrote about how bills of lading don’t carry the data CBAM needs. The follow-up question almost every reader sent back was the same: “But I have my suppliers’ ESG declarations on file. Those should be enough, right?”

They’re not. And the gap between what your supplier already gave you and what a CBAM submission actually requires is wider than most APAC exporters realise.

What you actually have today

If you ask one of your suppliers in Vietnam, Malaysia, or Indonesia for their ESG data, you’ll usually get one of three things back:

• An annual sustainability report in PDF form, sometimes 60 pages long, modelled on the SGX or HKEX sustainability reporting template. Scope 1 and Scope 2 emissions are listed as annual totals, sometimes broken down by facility, almost never by product.
• A GHG inventory spreadsheet covering one full calendar year, scoped to the supplier’s operations as a whole, with a single column per emission source.
• A third-party verifier letter, sometimes from a Big Four auditor, sometimes from a local energy consultancy, attesting to the totals at company level.

All three are useful documents in their own right. None of them are formatted to answer the question CBAM is actually asking.

What CBAM actually demands

The quarterly CBAM submission template wants something different in shape and granularity:

• Per-product embedded emissions in kgCO2 per tonne of output, for each CN8 commodity code you import.
• Per-shipment attribution that links each tonne shipped to the specific production facility and production run that produced it.
• Scope 1 and Scope 2 reported separately, with the Scope 2 figure derived from the grid emissions factor of the country, and ideally the subnational region, where the supplier facility actually operates.
• Third-party verified actuals, not industry default values. The EU allows defaults only for the first quarter of any new exporter relationship; after that, defaults trigger a heavy penalty multiplier.
• Methodology documentation explaining how emissions were calculated, which factors were used, what was excluded, and why.

The shape mismatch is structural. Your supplier’s ESG declaration was written for annual investor reporting. CBAM wants per-shipment operational data, on a quarterly cycle, attributable to specific facilities and production runs.

Where the gap actually lives

Six places, in our experience, where APAC compliance managers find themselves stuck when they sit down to fill in a CBAM submission with the supplier data they already have:

• Granularity gap. You have an annual Scope 1+2 total. CBAM wants per-product, per-shipment intensity expressed as kgCO2 per tonne of output.
• Attribution gap. You have company-level emissions. CBAM wants facility-level emissions for the exact production facility that produced this specific shipment, and the EU will check shipment-to-facility traceability.
• Cycle gap. Your supplier reports annually, aligned to their financial year. CBAM reports quarterly, aligned to EU submission windows.
• Verification gap. You have a self-attested statement or an audit letter. CBAM requires verification by an EU-recognised body using EU-approved methodology, and the list of qualifying APAC verifiers is currently short.
• Format gap. You have a free-text PDF. CBAM accepts structured XML matching the EU CBAM template. Even a perfect dataset on the wrong template will be rejected.
• Factor gap. Your supplier’s Scope 2 calculation uses the national grid average. CBAM allows that as a fallback but rewards subnational or facility-specific factors with materially lower implied embedded emissions, which translate directly into lower certificate purchases for your EU buyer.

For most APAC exporters we have spoken to, none of the six rows match what is currently in the file. That is the work between now and your next CBAM submission.

What “CBAM-ready” supplier data looks like

If you’re starting from a typical supplier ESG declaration today, the realistic path to CBAM-ready data has four moving parts:

1. A supplier conversation to extract per-product intensities and the production facilities behind them. Most suppliers will not have these on hand on day one; expect a 4 to 8 week engagement, longer if the supplier has not been audited recently.
2. A verification body engagement to certify the supplier’s emissions calculations to EU CBAM standards. EU-recognised verifiers operating in APAC are still scarce; book early and budget for queueing.
3. A methodology document explaining how each emissions figure was derived, what factors were used, and what was excluded. This is the artefact most APAC exporters skip, and it is exactly what the EU asks for in a CBAM audit.
4. A structured submission pipeline that turns the verified supplier data plus your trade documents into the EU template XML. This is the integration step where everything either fits together or falls apart.

What Vialode does (and what it doesn’t, yet)

Vialode’s first module is Document Intelligence. We extract clean structured data from bills of lading, commercial invoices, packing lists, and certificates of origin: the trade-document side of a CBAM submission. That is the upstream input to step 4. When you sit down to assemble a CBAM submission, the shipment IDs, ports, weights, HS codes, supplier names, and product descriptions arrive ready-structured.

The supplier ESG side, steps 1 through 3 above, is not yet a Vialode module. Our dedicated CBAM and ESG product is planned for early 2028. Until then, we are not pretending to replace your verification body or your CBAM consultant. We make the trade-document side a non-issue, so your compliance team can spend their hours on the part that is actually hard: the supplier conversation, the verification chain, the methodology write-up.

If you are filing CBAM in 2026 and the supplier ESG data side is currently the thing keeping your compliance manager awake at night, that is a problem worth solving with a partner who has been through it. But solve the document-data side too. Because even with perfect supplier data, a manual document workflow does not get to a quarterly EU submission window on time.

Join the waitlist. We are onboarding design partners with CBAM exposure now, with a focus on operations teams who need the trade-document layer to be already-solved before the harder CBAM work even begins.