SAP GTS content providers: sources, uploads and update cadence

SAP GTS does not ship with the regulatory content it checks against. It provides the structures and upload apps, while the content itself (tariff numbers, commodity codes, duty rates, control classes such as ECCNs, sanctioned party lists and preference rules) is loaded as XML files from a data provider or maintained by hand. Keeping it current means matching each data domain to the update rhythm of its official source: EU TARIC changes daily, the Combined Nomenclature once a year, sanctions lists whenever an authority acts. Every update should then go through a validated, logged path into a QA client before it reaches production.

What master data does SAP GTS need to work?

SAP GTS organizes regulatory content around legal regulations and numbering schemes. A numbering scheme represents a nomenclature (the EU Combined Nomenclature, the US Commerce Control List and so on), and a numbering scheme content defines where its codes come from: a data provider or manual maintenance. SAP’s own training material notes that the delivered numbering scheme EUSTA represents the CN, and that any numbering scheme in active use must be assigned to at least one legal regulation.

The content domains you will need, depending on which GTS areas you run:

• Commodity codes. Used for export declarations and foreign trade statistics, for example the CN for EU exports and Intrastat.
• Customs tariff numbers. The national import tariff of the importing country, such as the TARIC-level codes for EU imports.
• Customs duty rates and measures. Third-country duties, preferential rates and the EU and national measures (tariff and non-tariff) attached to tariff numbers, plus footnotes and texts.
• Control classes. Export control classification numbers such as US ECCNs and the EU dual-use list, used in Legal Control, together with license relevance codes, country/region groups and determination strategies.
• Sanctioned party lists (SPL). Names and addresses of designated persons and entities for screening business partners and documents.
• Preference rules. Rules of origin per trade agreement, used in Preference Management to calculate preferential eligibility and issue long-term supplier’s declarations.
• Customs code lists. Codes for documents, certificates and measures used in customs declarations. SAP’s training points out that authorities modify these codes frequently and that the list must be updated regularly.

Each of these has its own upload app in GTS, its own source and its own change rhythm. Treating them as one “content” problem is how teams end up with a current tariff and a screening list that is a month old.

SAP GTS 11.0 or SAP GTS, edition for SAP HANA: does it matter for content?

The upload model is the same in both releases: XML files, a data provider defined as a business partner, upload logs per domain. The support position is what differs.

SAP GTS 11.0 left mainstream maintenance on 31 December 2025. According to SAP’s own explanation, SAP offers no extended maintenance for GTS 11.0, so the release moved to customer-specific maintenance on 1 January 2026. That phase brings no delivery of legal changes and no new support packages. You can keep loading fresh tariff and SPL files, but the application logic that consumes them no longer follows new regulations.

The successor is SAP Global Trade Services, edition for SAP HANA. At the time of writing, the current documentation covers version 2025 FPS02, based on SAP S/4HANA Foundation 2025. Maintenance dates for each edition release are in SAP’s Product Availability Matrix, and you should check them there before you plan a conversion.

For content planning, a conversion is a good moment to re-baseline. Load a clean initial version of every numbering scheme content into the new system rather than carrying years of manual fixes across, then compare classification results on a sample of products.

How is content loaded into SAP GTS?

The Data Upload chapter of the GTS edition for SAP HANA administration guide lists a separate XML upload app for each domain: Upload Commodity Codes, Upload Tariff Numbers, Upload Customs Duty Rates, Upload European and National Measures for Tariff Numbers, Upload Control Classes, Upload License Relevance Codes, Upload SPL Master Data, Upload Country/Region Groups and Upload Determination Strategies (Legal Control), and Upload Preference Rules. Each has a matching upload log.

The details that matter in operations:

• For SPL uploads you must enter the legal regulation, list type and data provider, and the provider has to exist as a business partner in GTS.
• Tariff files arrive as versions split into packages. The Upload Tariff Numbers app runs a package check, and SAP warns that loading a version before the previous one is complete can leave the content inconsistent, to the point where no further versions can be loaded. Treat turning off the package check as an exception you agree with the provider first.
• The tariff upload can run in simulation mode first, so you can preview a file’s contents before anything is written.
• GTS runs a plausibility check on SPL records on upload and only accepts consistent data. SAP recommends updating the list first and then rebuilding the comparison index, because screening runs against that index.
• When codes expire, the numbering scheme content is updated first (validity periods adjusted, new codes added). Then a reclassification file moves products to the new codes through the Reclassify Products - XML-based app.

The upload apps read files from a local front end or from the application server. Manual uploads from a laptop do not scale past a handful of jurisdictions, so in our delivery approach we automate the path end to end:

official sources          provider / feed          landing zone          SAP GTS
(TARIC, CN, HTS,   --->   normalize, version, --->  object store /  --->  QA client: simulate,
 SPL, CCL ...)            render XML               app server dir        upload, regression
                                                         |                     |
                                                         |               PRD client: upload,
                                                         +-- change log  reclassify, monitor

Because tariff and SPL content is master data rather than Customizing, plan for it to be uploaded in each client instead of moving with transports. The QA-first sequence has to be built into the schedule on purpose; it will not happen as a side effect of your transport process.

Where does customs and trade compliance data come from?

The original sources are public. For the EU:

• The Harmonized System is maintained by the WCO. HS 2028, the eighth edition, enters into force on 1 January 2028.
• The Combined Nomenclature is updated annually by Commission Implementing Regulation. The 2027 version was published on 30 October 2026 and applies from 1 January 2027.
• TARIC integrates tariff, trade defense and agricultural measures, and the Commission transmits TARIC data daily to national administrations. It does not contain national VAT or excise rates.
• The EU dual-use list in Annex I of Regulation (EU) 2021/821 is updated by an annual delegated regulation. The 2026 update was adopted on 14 September 2026.
• The EU consolidated financial sanctions list is managed by DG FISMA, which updates it whenever necessary.

Outside the EU, each jurisdiction publishes on its own terms. The US tariff schedule changes several times a year; USITC published 2026 HTS Revision 22 on 30 October 2026. US ECCNs live in the Commerce Control List. The UK Sanctions List has been the only source for UK designations since the OFSI Consolidated List closed on 28 January 2026, which is exactly the kind of source change that breaks a home-grown SPL feed. The US Consolidated Screening List is refreshed automatically every day at 5:00 AM Eastern.

None of these sources publish in the XML layouts GTS uploads. That gap is why the content-provider market exists. Some providers sell broad bundles. Descartes CustomsInfo, for example, markets content for SAP GTS covering tariff codes, ECCN and dual-use codes, rules of origin and denied party lists. Thomson Reuters ONESOURCE Global Trade Content covers a similar range of domains. Other providers focus on a single domain, such as tariff data only or screening lists only. When you evaluate any of them, ask for sample files for your release and your jurisdictions, and check how they handle versioning and expired codes.

How often does each content domain change?

Data domain	Primary source	Update cadence	GTS area / upload
HS nomenclature (6-digit)	WCO	New edition every five years; HS 2028 from 1 Jan 2028	Underlies all numbering schemes
EU Combined Nomenclature	European Commission (Implementing Regulation)	Annual; 2027 version published 30 Oct 2026	Commodity codes (export, statistics)
EU TARIC codes, duties, measures	European Commission (DG TAXUD)	Daily	Tariff numbers, customs duty rates, measures
US HTS	USITC	Multiple revisions per year	Tariff numbers, customs duty rates
Other national tariffs	National customs authorities	Varies by jurisdiction	Tariff numbers, customs duty rates
EU dual-use list (Annex I)	European Commission (delegated regulation)	Annual update	Control classes (Legal Control)
US ECCNs (CCL)	BIS, EAR Part 774	Varies; changes by published rule	Control classes (Legal Control)
EU financial sanctions list	DG FISMA	Whenever necessary	SPL master data
UK Sanctions List	UK government	Whenever designations change	SPL master data
US Consolidated Screening List	ITA (from source agencies)	Refreshed daily	SPL master data
Rules of origin	Trade agreement texts	Varies by agreement	Preference rules (Preference Management)
Customs code lists	EU and national authorities	Varies by jurisdiction	Customs code lists (Customs Management)

Two calendar effects stand out. The turn of the year concentrates change, because the CN and many national tariffs switch on 1 January. And 2028 is an HS year, so expect a much larger set of expired codes and reclassification files than usual.

What goes wrong when SAP GTS content is stale?

Typical failure modes:

• A product still classified under a code that expired on 1 January produces declarations that customs rejects or that need correcting, until someone reclassifies it.
• A missed TARIC change (a new anti-dumping duty, an expired suspension) means duty calculations in GTS no longer match what customs will charge.
• If a control class changes and the new list is not loaded, Legal Control can let through an export that now needs an authorization.
• A party designated yesterday is not in a list loaded last week. With sanctions, the gap between publication and your next load is the exposure window.
• A partial or truncated source file, loaded as a full replacement, can end-date thousands of valid codes. GTS’s package check helps for tariffs, but only if you leave it on.
• Origin calculations based on superseded rules can produce supplier’s declarations or origin statements that do not hold up.

How should you govern SAP GTS content updates?

Most of these risks are process gaps, and the operating model we recommend closes them in four parts.

1. One owner per domain. Trade compliance owns the meaning of each domain (tariff per jurisdiction, control classes, SPL, preference rules). The GTS application team owns the upload path and the jobs. The provider owns file correctness. Write down who approves a production load for each domain and who is on call when an upload fails.

2. Validation before upload. Check every file before GTS sees it:

• schema validity and expected encoding
• completeness against the provider’s manifest (all packages of a version present)
• delta sanity: an unusual share of deletions or end-dated codes should stop the pipeline and page a person
• version continuity: the new version follows the last one loaded

3. QA client first, then production. Run the upload in simulation mode, load into QA and run a small regression pack: classification of a fixed product sample, duty determination on a few reference documents, SPL screening against known test names that must hit and must not hit, and a Legal Control check on a controlled product. Only then load production. For daily TARIC and SPL changes, automate the pack so it finishes in minutes. Keep the manual review for the annual and HS cut-overs.

4. A change log you can show an auditor. For every load, record the source publication date, provider version, file checksum, target client, who released it, the GTS upload log reference and any reclassification run. When customs asks why a declaration used a given rate on a given day, this log answers it.

A short pre-production checklist for year-end:

• provider’s year-end delivery schedule confirmed in writing
• reclassification files received and test-loaded in QA
• products under expiring codes listed and assigned to classifiers
• upload jobs rescheduled around the 1 January switch
• rollback plan agreed (which version to reload, and who decides)

Where Duces fits

Duces offers SAP GTS Trade Data as a managed subscription. It covers SAP GTS-ready commodity codes, duty rates and footnotes, delivered as NOM, TXT and DTR files in the LLNS provider layout that GTS ingests, with the full nomenclature tree. We collect the data from official customs authorities and tariff publications. Sixteen jurisdictions are live today, and others are available on request. You get one Initial baseline, then an Update whenever the source changes. EU TARIC daily changes flow through the same day, and history is kept bitemporally so obsolete codes are end-dated rather than silently deleted. Every file is validated before it ships. Files are pushed to your object storage or handed off for GTS upload, with an optional SAP BTP Integration Suite flow that routes them into GTS and triggers the upload. The feed covers tariff content; sanctioned party lists, control classes and preference rules come from their own sources, as described above.

For the system itself, our Enterprise Apps & Platforms practice implements, integrates and runs packaged enterprise software, including SAP, with testing and application management services.

If you want a sample feed for your jurisdictions or a second opinion on your upload path, talk to the people who build it.