Customs Explorer
⌕

Customs Explorer

SAP customs integration

ENTERPRISE CUSTOMS INTEGRATION

SAP Customs Integration

Connect SAP enterprise processes with customs compliance, declaration preparation and international trade workflows.

Explore how SAP S/4HANA, SAP ERP and SAP Global Trade Services (SAP GTS) can support customs data management, trade compliance and integration with external customs systems across the European Union.

SAP S/4HANA & ERP
SAP Global Trade Services
EU Customs Framework
INTEGRATION MODEL SAP / CUSTOMS
ENTERPRISE SOURCE SYSTEM SAP S/4HANA / SAP ERP Sales · Purchasing · Logistics · Master Data
BUSINESS DATA EXCHANGE
TRADE COMPLIANCE LAYER SAP Global Trade Services Customs Processes · Compliance · Trade Data
SUPPORTED CUSTOMS INTERFACES
EXTERNAL CUSTOMS ENVIRONMENT EU / National Customs Systems Declarations · Responses · Status Events
01 ERP Integration Enterprise transaction data
02 Customs Compliance Classification, origin and procedures
03 Declaration Workflows Supported electronic interfaces
04 Operational Visibility References, decisions and status
02 / SYSTEM ARCHITECTURE

How SAP Systems Connect to Customs Operations.

SAP customs integration typically combines enterprise transaction data, trade compliance functions, integration services and external customs communication. The precise architecture depends on the SAP landscape, licensed functionality, country coverage and customs procedures involved.

REFERENCE ARCHITECTURE

Enterprise-to-Customs Integration

CONCEPTUAL MODEL
ENTERPRISE APPLICATIONS

SAP S/4HANA / SAP ERP

Sales, purchasing, materials, inventory, logistics, billing and business partner records.

01
DOCUMENTS · MASTER DATA · BUSINESS EVENTS
GLOBAL TRADE MANAGEMENT

SAP Global Trade Services (SAP GTS)

Configured trade compliance and customs management processes, including customs-relevant document processing and supported declaration scenarios.

02
CONFIGURED MESSAGE EXCHANGE
CONNECTIVITY & TRANSPORT

Integration Services / Customs Interfaces

SAP-supported interfaces, middleware or external connectivity services may transform, route, transmit and receive customs messages.

03
AUTHORIZED SYSTEM ACCESS · RESPONSES
EXTERNAL REGULATORY SYSTEMS

EU / National Customs Systems

Electronic customs declaration processing, official responses and procedure-specific status events where connectivity is available.

04
PLATFORM RESPONSIBILITIES

Four Layers. Different Responsibilities.

Understanding the role of each component prevents a common design error: assuming that commercial ERP data automatically constitutes a complete customs declaration.

01 / ERP

SAP S/4HANA & SAP ERP

Provide the underlying commercial and logistical information used to initiate customs-related processes.

  • Sales and purchasing documents
  • Materials and business partners
  • Invoices and delivery records
  • Inventory and shipment context
02 / TRADE

SAP Global Trade Services

Supports trade compliance and customs management capabilities according to the installed product, licensing and configuration.

  • Trade-relevant document processing
  • Customs-specific data management
  • Compliance-related controls
  • Supported customs procedures
03 / CONNECTIVITY

Integration & Messaging

Moves data between applications and manages the technical exchange required by the selected architecture.

  • Interface mapping and transformation
  • Message routing and monitoring
  • Technical error handling
  • Secure system connectivity
04 / CUSTOMS

Customs Authorities & Systems

Process declarations and issue the relevant official decisions and responses under the applicable customs procedure.

  • Declaration acceptance or rejection
  • Customs controls and interventions
  • Release decisions
  • Procedure-specific status messages
DESIGN CONSIDERATIONS

Architecture Decisions That Matter.

Not every SAP environment needs the same integration components. These choices should be established from verified technical and business requirements.

01

Which SAP products and versions are in scope?

Differentiate SAP S/4HANA Cloud, SAP S/4HANA on-premise, older SAP ERP environments and the relevant SAP GTS product or edition. Supported interfaces and extension options may differ.

02

Is SAP GTS part of the intended architecture?

SAP GTS may provide customs management capabilities, but its presence, edition, licensing, supported country functions and configuration must be confirmed. It should not be assumed to be available in every SAP ERP deployment.

03

How will the external customs connection work?

Identify the specific national customs system, supported interface, message format, authentication requirements and any necessary provider or certification arrangements before selecting the technical route.

04

Which system owns customs-relevant information?

Define authoritative sources for commodity classification, origin, valuation, partner identifiers, procedure information and customs responses. Ownership and synchronisation rules are essential for reliable processing.

DATA EXCHANGE MODEL

Information Must Flow in Both Directions.

Outbound business data and inbound customs responses serve different purposes. A complete design must account for both, while preserving transaction identity and the meaning of each official event.

Enterprise → Customs

Commercial documents, parties, goods, quantities, values and customs-specific attributes are prepared for the applicable customs workflow.

DATA PREPARATION & SUBMISSION SUPPORT

Customs → Enterprise

Supported references, acceptance messages, rejections, release decisions and other procedure-specific events are associated with the relevant business records.

STATUS SYNCHRONISATION & AUDIT
03 / CUSTOMS DATA INTELLIGENCE

SAP Customs Data Mapping & Validation.

Reliable customs integration depends on more than transferring fields between systems. SAP business data must be interpreted, enriched and validated against the requirements of the applicable customs procedure before it can support a declaration.

DATA TRANSFORMATION MODEL

From SAP Transactions to Customs-Ready Information

CONTROLLED DATA FLOW
01

SAP Source Data

Material master, partners, orders, deliveries, invoices and logistics records.

BUSINESS CONTEXT
02

Mapping & Enrichment

Translate source information and add customs-specific attributes where required.

DATA TRANSFORMATION
03

Customs Validation

Check completeness, consistency, business rules and procedure-specific requirements.

QUALITY CONTROLS
04

Declaration Preparation

Provide validated information to the configured customs processing workflow.

CONTROLLED HANDOFF

This is a conceptual data-processing sequence. It does not imply that SAP automatically determines legal classification, preferential origin or customs value.

FIELD-LEVEL MAPPING

What SAP Data Can Contribute to Customs Processing.

Source fields are starting points, not automatic substitutes for legally required customs determinations. The mapping must reflect the declaration type, jurisdiction and applicable data requirements.

Customs data area Potential SAP source Required mapping or validation Principal risk
01 Commodity classification Material master and maintained classification records Verify the relevant CN/TARIC classification, validity date and applicable measures. Legal determination
02 Country of origin Material, procurement and supplier information Distinguish non-preferential origin from preferential origin and verify supporting evidence. Evidence required
03 Customs value Invoices, pricing conditions and purchasing records Assess valuation method and relevant additions, exclusions and adjustments. Valuation rules
04 Parties and identifiers Business partner master and company records Validate EORI and other identifiers, party roles and declarant or representative information. Identity consistency
05 Goods and quantities Delivery, material and logistics documents Map goods descriptions, net mass, supplementary units and package details where applicable. Unit conversion
06 Customs procedure Business process context and configured trade records Determine procedure codes, additional procedure codes and authorisation references as applicable. Procedure eligibility
07 Transport information Shipment and transportation records Check transport modes, locations, references and relevant document identifiers. Missing shipment data
08 Supporting documents Document references and connected document systems Validate required certificates, licences, authorisations and document codes. Regulatory requirements

Illustrative mapping categories. Actual data elements and code lists must be checked against the relevant EU customs data requirements and national system specifications.

VALIDATION FRAMEWORK

Four Levels of Customs Data Quality.

A robust integration should detect problems before submission and distinguish technical errors from customs compliance issues requiring expert review.

LEVEL 01

Structural Validation

Verify that mandatory fields are populated and that the information conforms to the required data types, formats and message structures.

SCHEMA · FORMAT · COMPLETENESS
LEVEL 02

Reference Validation

Check relevant codes, identifiers, reference datasets, effective dates and consistency between connected records.

CODES · IDENTIFIERS · VALIDITY
LEVEL 03

Business Rule Validation

Test relationships between goods, parties, procedures, values, transport information and supporting documents.

CONSISTENCY · DEPENDENCIES
LEVEL 04

Compliance Review

Route classifications, origin claims, valuation questions or authorisation conditions requiring legal or specialist assessment to an accountable reviewer.

LEGAL REVIEW · APPROVAL
DATA GOVERNANCE

Who Owns the Customs Data?

Customs integration becomes unreliable when ERP, trade compliance and external service providers maintain conflicting versions of the same information.

Define the authoritative system for each data category, the person responsible for approval, the conditions for updates and the records retained as evidence.

Source of truth Approval responsibility Change history Audit evidence
EXAMPLE RESPONSIBILITY MODEL
Commercial dataInvoices, purchasing and sales records
ERP OWNER
Customs determinationsClassification, origin and valuation decisions
TRADE / CUSTOMS
Technical interfacesMappings, monitoring and transport
IT / INTEGRATION
Official responsesCustoms decisions and system messages
AUTHORITY SOURCE

Illustrative allocation of responsibility. Actual ownership depends on organisational roles and the applicable legal obligations.

EXCEPTION HANDLING

What Happens When Data Fails Validation?

01

Identify the Issue

Record the affected field, document, validation rule and relevant transaction reference.

02

Assign Responsibility

Direct the issue to the responsible ERP, logistics, customs or integration team.

03

Correct and Revalidate

Apply authorised corrections and repeat the necessary validation checks.

04

Preserve the Audit Trail

Retain the relevant changes, approvals and processing outcomes for traceability.

04 / OPERATIONAL WORKFLOWS

SAP Import, Export & Automated Customs Workflows.

SAP customs integration can connect enterprise transactions with customs declaration processes, electronic message exchanges and operational status updates. Automation depends on the SAP GTS functionality deployed, the configured interfaces and the requirements of the relevant customs authority.

WORKFLOW 01 / INBOUND

Import Customs Workflow

From incoming goods and purchasing data to import declaration processing and release.

  1. 01

    Import Transaction Identified

    SAP purchasing, inbound delivery and logistics records provide the initial business context for the customs process.

  2. 02

    Customs Information Prepared

    Relevant goods, parties, values, origin, classification and procedure information are assembled and checked.

  3. 03

    Declaration Processing Initiated

    The configured customs solution prepares and, where supported and authorised, transmits the required declaration message.

  4. 04

    Customs Responses Received

    Acceptance, rejection, control instructions and other applicable messages are processed through the supported interface.

  5. 05

    Release & Record Synchronisation

    Official release information and relevant references are associated with the customs transaction and connected business records.

WORKFLOW 02 / OUTBOUND

Export Customs Workflow

From sales and outbound logistics to export declaration and exit confirmation.

  1. 01

    Export Transaction Identified

    Sales orders, outbound deliveries and shipment information provide the basis for export-related processing.

  2. 02

    Trade & Customs Checks

    Relevant compliance controls and customs data validation are performed according to the configured solution.

  3. 03

    Export Declaration Prepared

    Required declaration data is prepared and submitted through the supported customs communication channel.

  4. 04

    Release for Export

    Customs acceptance, controls and release decisions are handled according to the applicable export procedure.

  5. 05

    Exit Results & Follow-Up

    Where available, official exit-related messages are reconciled with the export transaction and retained for follow-up.

ELECTRONIC CUSTOMS COMMUNICATION

How Customs Messages Move Through the Integration.

Electronic customs processing is a two-way exchange. Sending a declaration is only one stage: the system must also handle official responses, errors, controls and procedure-specific events.

ILLUSTRATIVE MESSAGE LIFECYCLE

Declaration & Response Exchange

BIDIRECTIONAL
ENTERPRISE ENVIRONMENT SAP ERP / SAP GTS Business data & customs processing
DECLARATION / REQUEST
RESPONSE / STATUS
REGULATORY ENVIRONMENT Customs Authority Applicable national / EU customs system
Possible processing events
Submission Acceptance / Rejection Control Release Exit-related Result

Message types, sequences and availability differ between customs procedures, national systems and implemented interface specifications.

REFERENCES & TRACEABILITY

MRN Tracking & Customs Status Synchronisation.

A Movement Reference Number (MRN), when assigned by the relevant customs system, provides an important reference for identifying and following the corresponding customs movement or declaration.

Integration can associate the MRN and supported official status events with the corresponding SAP business documents, helping teams reconcile customs processing with operational activities.

Link official references to relevant transactions.

Distinguish technical delivery from customs acceptance.

Retain the history of official messages and decisions.

Monitor unresolved or inconsistent customs statuses.

CUSTOMS PROCESS MONITOR
OFFICIAL REFERENCE MRN — WHEN ASSIGNED Associated with the customs transaction
Declaration prepared Internal processing
Message submitted Technical exchange
Customs response Official event
Procedure outcome Release, exit or other result
Conceptual monitoring view — not a live SAP interface.
CONTROLLED AUTOMATION

What Can Be Automated — and What Still Requires Review?

Automation can reduce repetitive processing, but legal customs determinations and exceptional transactions still require appropriate controls.

CONFIGURABLE AUTOMATION

Repeatable System Tasks

  • Transfer business document data.
  • Apply predefined field mappings.
  • Perform technical and reference checks.
  • Route supported customs messages.
  • Capture official references and status events.
  • Generate processing alerts and exception queues.
CONTROLLED HUMAN OVERSIGHT

Compliance Decisions & Exceptions

  • Resolve uncertain tariff classifications.
  • Review preferential origin eligibility and evidence.
  • Assess complex customs valuation cases.
  • Verify special procedure authorisations.
  • Investigate rejected or inconsistent declarations.
  • Approve changes affecting legal declarations.
EXCEPTION MANAGEMENT

Build Workflows for Failure, Not Only for Success.

A dependable SAP customs integration must identify failures, assign ownership and prevent uncontrolled retries or inconsistent records.

01 / TECHNICAL

Transmission Failure

Detect failed deliveries, timeouts and connection errors. Confirm message status before any retry.

02 / VALIDATION

Rejected Declaration

Capture the authority’s response, identify the cause and route corrections through an approved process.

03 / OPERATIONAL

Missing Customs Status

Investigate absent or delayed responses without treating silence as official acceptance or release.

04 / CONTROL

Duplicate or Conflicting Events

Reconcile references, message identifiers and transaction history to avoid duplicate processing.

Important: A successful technical transmission does not establish that customs has accepted a declaration or authorised the release of goods. Only the relevant official customs response can establish that status.

05 / IMPLEMENTATION & GOVERNANCE

SAP Customs Integration: Implementation, Security & Costs.

Implementing SAP customs integration requires more than configuring an interface. Organisations must verify SAP product capabilities, licensing, customs system connectivity, regulatory obligations and operational responsibilities before committing to development.

PRE-IMPLEMENTATION READINESS

Five Questions to Resolve Before Development

FEASIBILITY FIRST
01

Which SAP landscape?

Confirm the ERP product, deployment model, release, SAP GTS edition and relevant support arrangements.

PRODUCT & VERSION
02

Which customs processes?

Define the countries, declaration types, customs procedures and operational volumes in scope.

BUSINESS SCOPE
03

Which interfaces exist?

Verify supported national customs connections, message specifications and available integration services.

TECHNICAL ACCESS
04

Which authorisations?

Identify EORI, declarant or representative arrangements, procedure authorisations and access credentials where required.

REGULATORY ACCESS
05

Who owns the process?

Assign responsibilities for customs decisions, data quality, system operations and exception handling.

ACCOUNTABILITY

Critical dependency: Confirm external customs connectivity, contractual requirements and any applicable onboarding or certification conditions before building the integration. A technically complete SAP solution may still be unusable if the required external access is unavailable.

DELIVERY METHODOLOGY

A Practical Implementation Roadmap.

Use a staged approach with explicit acceptance criteria. Each phase should reduce uncertainty before additional development expenditure is committed.

PHASE 01DISCOVER

Requirements & Feasibility

Document procedures, legal responsibilities, existing SAP capabilities and customs system prerequisites.

Exit criterionValidated scope and external dependencies
PHASE 02DESIGN

Architecture & Data Mapping

Define source systems, data ownership, message flows, interface contracts and exception handling.

Exit criterionApproved solution and data specifications
PHASE 03BUILD

Configuration & Integration

Configure supported SAP functionality, mappings, connectivity, monitoring and security controls.

Exit criterionDemonstrated technical processing
PHASE 04VALIDATE

Testing & Acceptance

Test normal transactions, rejections, duplicate prevention, customs responses and recovery scenarios.

Exit criterionApproved end-to-end test evidence
PHASE 05OPERATE

Go-Live & Monitoring

Establish support ownership, controlled deployment, operational dashboards and change management.

Exit criterionDocumented production controls
PROJECT ECONOMICS

What Determines the Cost of SAP Customs Integration?

There is no reliable universal implementation price. Costs depend on the existing SAP environment, licensing, geographic scope, supported interfaces, external providers and the complexity of the customs processes.

Cost category Typical cost drivers What to verify
SAP products & licensing SAP GTS entitlement, applicable editions, deployment and support agreements. Actual contractual rights, required components and ongoing fees.
Implementation services Solution design, configuration, customs expertise and project management. Scope, deliverables, responsibilities and change-request terms.
Middleware & connectivity Integration services, adapters, transport mechanisms and monitoring. Existing infrastructure, subscription terms and message volumes.
Customs system access Country-specific interfaces, provider services, onboarding and testing. Access conditions, service charges and any mandatory technical approval.
Data remediation Classification records, origin evidence, partner data and mapping corrections. Quality of existing master data and manual review effort.
Testing & compliance Integration tests, customs scenarios, user acceptance and documentation. Required test environments, participants and acceptance criteria.
Ongoing operations Support, system updates, regulatory changes, monitoring and training. Recurring costs, support coverage and maintenance obligations.

Budgeting principle: Obtain separate estimates for one-time implementation, recurring software and service charges, country-specific connectivity and ongoing compliance maintenance. Avoid treating an initial integration quotation as the total cost of ownership.

SECURITY & AUDITABILITY

Secure the Entire Customs Data Lifecycle.

Customs integrations exchange commercially sensitive information and may support legally significant declarations. Security controls must cover both the SAP environment and every connected system or service provider.

Access restrictions, message integrity, change traceability and operational monitoring should be designed into the architecture rather than added after deployment.

Least-privilege access Encrypted transport Audit logging Controlled changes
SECURITY CONTROL MODEL

Identity & Access

Role-based permissions, technical accounts and controlled authorisation of customs actions.

Secure Communications

Appropriate authentication, protected transport and management of keys or certificates where applicable.

Processing Integrity

Message correlation, duplicate prevention, retry controls and validation of received responses.

Evidence & Retention

Traceable decisions, relevant supporting records and retention aligned with applicable obligations.

Controls must reflect the actual deployment model, contracts, risk assessment and applicable requirements.
LIMITATIONS & DEPENDENCIES

What SAP Integration Does Not Automatically Solve.

Enterprise software can support customs processes, but it does not remove legal obligations or guarantee compatibility with every customs authority.

01 / COVERAGE

Not Every Country or Procedure Is Supported

Verify the specific SAP GTS country functionality, declaration scenarios and external interfaces for the intended deployment.

02 / LEGAL

Automation Does Not Replace Customs Responsibility

Declarants and other responsible parties remain subject to the applicable customs obligations, irrespective of the software used.

03 / DATA

ERP Records Are Not Always Customs-Ready

Classification, origin, valuation, authorisation and supporting-document information may require enrichment and specialist review.

04 / EXTERNAL SYSTEMS

Connectivity Is a Separate Dependency

Official access, supported message formats, authentication and external service arrangements must be confirmed independently.

05 / CHANGE

Regulatory and Technical Requirements Evolve

Changes to customs data requirements, national interfaces or SAP products can create ongoing maintenance obligations.

06 / OPERATIONS

Human Intervention Remains Necessary

Rejections, inspections, exceptional procedures and uncertain compliance determinations may require manual decisions.

IMPLEMENTATION DECISION

Establish a Go / No-Go Gate Before Full Development.

A sound feasibility assessment should confirm the essential dependencies before the project enters its most expensive phase.

Proceed When

Supported functionality, legal prerequisites, technical access, data ownership, budget and acceptance criteria have been validated.

Pause When

Critical interfaces, licences, authority access, country coverage or legal responsibilities remain unresolved.

06 / KNOWLEDGE & RESOURCES

SAP Customs Integration: Frequently Asked Questions.

Practical answers to common questions about SAP Global Trade Services, customs declarations, EU customs integration, technical requirements and implementation.

01 What is SAP customs integration?

SAP customs integration connects business information managed in SAP systems with customs-related processes, compliance controls and external customs communication. Depending on the architecture, SAP ERP or SAP S/4HANA can provide transaction data to SAP Global Trade Services or another configured customs solution. The supported functions depend on the software, licensing, configuration and customs jurisdiction.

02 What is SAP Global Trade Services (SAP GTS)?

SAP Global Trade Services is an SAP solution for managing international trade compliance and customs-related business processes. Depending on the product edition and configuration, its capabilities can include customs management, trade compliance controls and integration with supported customs communication systems. SAP GTS is not automatically included in every SAP ERP or SAP S/4HANA installation.

03 Can SAP GTS submit customs declarations electronically?

SAP GTS supports customs management scenarios that may include electronic declaration processing. Actual submission capabilities depend on the supported country functionality, the customs procedure, the configured interface and any required external connectivity or service provider. The availability of a particular national customs interface must be verified before implementation.

04 Can SAP integrate with EU customs systems?

SAP-based customs solutions can be integrated with supported electronic customs systems, but the European Union does not operate a single interchangeable interface for every customs procedure. The relevant EU and national systems, access arrangements, message specifications and technical requirements must be identified for each implementation.

05 Does SAP automatically determine customs classification and origin?

SAP can store, exchange and process customs-relevant classification and origin information according to the configured functionality. However, the legal correctness of a commodity classification or origin determination cannot be assumed simply because a value exists in the system. Applicable rules, supporting evidence, validity periods and responsible review procedures remain essential.

06 Can SAP track MRNs and customs declaration statuses?

Where the customs interface and configured solution support it, official references such as Movement Reference Numbers (MRNs) and customs status messages can be associated with SAP-related transactions. The available events vary by procedure and customs system. A successful technical message transmission must not be confused with official customs acceptance or release.

07 How much does SAP customs integration cost?

Costs depend on the existing SAP environment, SAP GTS licensing, integration architecture, number of countries and procedures, external connectivity, data quality, testing and ongoing support. There is no universal implementation price. Organisations should separately assess initial project expenditure, recurring software and service fees, and long-term maintenance obligations.

08 What should be checked before starting a SAP customs integration project?

Before development, verify the SAP products and versions in scope, the required customs procedures, available country functionality, supported interfaces, licensing, access credentials, authorisations, data ownership and operational responsibilities. External dependencies should be confirmed early to avoid building an integration that cannot be connected or operated as intended.

CUSTOMS EXPLORER / DIGITAL CUSTOMS

Build Customs Integration on Verified Requirements.

Effective SAP customs integration begins with accurate data, supported technology and a clear understanding of regulatory responsibilities. Validate the architecture, country coverage and external dependencies before automating critical customs processes.

Back to the beginning

This guide provides general technical and regulatory information. SAP functionality, licensing and customs interfaces must be checked against the applicable product documentation and national customs requirements. It does not constitute legal advice or confirmation of a particular integration capability.