Thai Customs 2026: What's changing for air import declarations

Thailand's Customs Department has been steadily modernizing its electronic filing systems since the National Single Window (NSW) initiative launched. In January 2026, the Department published Customs Notification No. 12/2569 (B.E.), which introduces the most significant changes to air cargo import declarations since the e-Customs XML schema migration of 2022. These changes take effect on July 1, 2026, and every customs broker and freight forwarder handling air imports into Thailand needs to understand them.

This article summarizes what is changing, how it affects AWB data extraction workflows, and what KabyTech is doing to help its customers stay compliant.

The three major changes

1. Mandatory pre-arrival AWB data submission

Starting July 1, customs brokers must submit structured AWB data to the e-Customs system at least 4 hours before aircraft arrival for long-haul flights (origins outside ASEAN) and 2 hours before arrival for ASEAN-origin flights. Previously, AWB data was submitted as part of the import declaration, which could be filed up to 30 days after arrival. The new rule means brokers need electronic AWB data much earlier in the process.

For forwarders who still rely on manual data entry from PDF or paper AWBs, this timeline compression is serious. If a flight from Frankfurt lands at Suvarnabhumi at 06:00 and you receive the house AWB documents at 22:00 the night before, your team has just 2 hours to process and submit all AWB data. For consolidated shipments with 30-50 HAWBs, manual processing is simply not viable under the new timeline.

2. Expanded data fields for air import entries

The notification adds 14 new data fields to the air import declaration schema. The most impactful additions include:

• Full OCI regulatory data — All OCI lines from the FWB must now be transmitted, not just the security screening status. This includes customs broker identifiers, known consignor codes, and any country-specific regulatory references.
• SPH code validation — Special handling codes must match against a Thai Customs-maintained reference list. Codes not on the list will trigger a filing rejection.
• Piece-level weight declaration — For shipments with multiple rate description lines, the gross weight per RTD line must be declared separately, not just the total.
• HS code pre-classification reference — If the shipment carries goods that were pre-classified under the BOI (Board of Investment) or FTZ (Free Trade Zone) schemes, the reference number must appear in the declaration and match the FWB's HTS section.
• Agent IATA code cross-reference — The issuing agent's IATA code from the AGT section must be validated against the Customs-registered forwarder database.

3. Real-time validation with rejection codes

The e-Customs system will begin real-time validation of submitted AWB data against airline manifest data (received via the Advance Cargo Information system). Mismatches in key fields — AWB number, pieces, gross weight, origin, and destination — will generate immediate rejection codes rather than being flagged for post-clearance audit.

This means data accuracy is no longer just an efficiency issue; it directly determines whether your declaration is accepted. A typo in the gross weight field that previously might have been caught during a random audit will now cause an immediate rejection, delaying clearance and potentially incurring storage charges.

How these changes affect FWB data extraction

For teams that already use automated AWB parsing, the impact is manageable but requires attention in three areas:

More sections needed, not fewer

The expanded field requirements mean your parser must extract data from sections that many systems previously ignored. OCI, HTS, SPH, and AGT are no longer optional — they are required fields in the new declaration schema. If your current solution only parses 15-18 sections, you will have data gaps that require manual intervention.

Higher accuracy thresholds

Real-time validation against airline manifest data means your extracted values must exactly match the carrier's records. A weight of "380.5 KGS" parsed as "380.5" is fine, but parsed as "3805" will trigger rejection. Similarly, IATA airport codes must be exactly three characters — "BKK" not "BKK " with a trailing space. Parser accuracy that was "good enough" before may not pass the stricter validation.

Faster turnaround required

The pre-arrival submission requirement compresses the available processing window. Automated parsing becomes not just a convenience but a necessity for meeting the 2-4 hour deadline, especially for consolidated shipments with multiple house AWBs.

What KabyTech is doing

We have been working closely with the Thai Customs Department's IT division since the draft notification was circulated in October 2025. Here is what we have built and what is coming:

Already available

• Full 29-section parsing — All the newly required fields (OCI, HTS, SPH, AGT) are already extracted by our API. No upgrade needed.
• Cross-validation engine — Our API already validates extracted data against IATA reference tables (airport codes, airline prefixes, SPH codes). This catches the kinds of errors that will trigger the new real-time rejections.
• Piece-level RTD extraction — We have always parsed RTD at the line-item level, including per-line piece counts and weights. The new piece-level weight requirement is already covered.

Coming in Q2 2026

• e-Customs XML export — Direct export of parsed AWB data into the new e-Customs XML schema, eliminating the need for manual mapping between KabyTech's JSON output and the customs filing format.
• Pre-arrival submission workflow — A new Operations Portal feature that tracks inbound flight schedules and alerts your team when AWB data needs to be submitted, based on the 2-hour or 4-hour deadline.
• SPH code validation against the Thai Customs reference list — Automatic flagging of SPH codes that are valid under IATA standards but not recognized by the Thai Customs system.

What you should do now

July 1 is less than four months away. Here is a practical checklist for customs brokers and freight forwarders:

1. Audit your current AWB data extraction. Identify which of the 14 new fields you can already capture automatically and which require manual entry. Focus on OCI, HTS, and piece-level RTD data.
2. Test your e-Customs filing against the new schema. The Thai Customs Department has published a sandbox environment for testing the new XML schema. File test declarations now to identify data gaps before the deadline.
3. Evaluate your processing timeline. Simulate the pre-arrival submission window using your current workflow. If you cannot process a consolidated shipment of 30 HAWBs within 2 hours using your current tools, you need automation.
4. Talk to us. KabyTech offers a free compliance assessment for Thai freight forwarders preparing for the July changes. We will review your current workflow and identify exactly where automation can close the gaps.

Related Articles