Cross-border process automation
Customs and Cross-Border Process Automation
Cross-border shipments depend on commercial invoices, packing lists and transport documents reaching your broker complete and consistent, and on status coming back in time. ECOM prepares, validates and transmits that data over X12 and EDIFACT, exchanges status with brokers, and has capabilities to support ACE and ISF workflows. ECOM is not ACE- or ISF-certified; filing responsibility stays with the customer, broker, carrier or authorized filer.
Overview
What is cross-border process automation?
Cross-border process automation is the integration and automation of the data and documents that move between a business, its customs broker, freight forwarders and carriers around an international shipment. It covers collecting and preparing commercial and transportation data, validating that it is complete, sending it to the party that prepares the filing, and receiving status back. Filing with a government agency remains the responsibility of the customer, broker, carrier or other authorized filer; ECOM integrates and automates the data exchange around it.
Overview
For the teams that supply and chase cross-border data
Different roles feel the problem at different points in the process.
Importers and exporters
You provide invoices, packing lists and product data to a broker and wait for status, often through e-mail and spreadsheets.
Freight forwarders and NVOCCs
You collect documents from many shippers and pass data to carriers and brokers, in each party’s own format.
Customs brokers’ clients and trade compliance teams
You need data to reach the broker complete and consistent, and to see what the broker needs from you.
Carriers and logistics providers
You exchange transport documents and release information with brokers and customers across modes.
How ECOM helps
How ECOM supports the cross-border workflow
ECOM’s role is the integration and automation around the filing, not the filing itself.
Less re-keying of shipment data
Invoice, packing and transport data is passed from your systems to your broker and forwarders instead of retyped.
Gaps found before they cause delays
Validation checks that the data a broker needs is present and consistent, so questions come back earlier, not after the cargo has moved.
Clearer status
Status from the broker is exchanged with your systems, so teams are not chasing updates by e-mail.
Exceptions with a trail
Missing data, mismatches and holds can be raised, assigned and tracked with the documents that explain them.
How ECOM delivers it
Document and data exchange
The ECOM Systems Integrator connects ERP, TMS, forwarding and WMS platforms with the broker and forwarder systems that need the data, where those partners accept it.
Validation workflows
Required data can be checked for completeness and consistency before it is sent, against rules agreed with you and your broker.
Status exchange
Clearance status that your broker sends back is received and passed to your systems and teams, where the broker supports it.
Exception handling
The Exception Management Center helps automate exception handling and manage internal and customer-facing SLAs.
Document retention with the shipment
The Transaction Life Cycle Manager holds shipment paperwork and supporting evidence with the shipment record.
Carrier and broker onboarding
Freight Onboarding and the self-service Trading Partner Onboarding portal set up and test carriers, brokers and forwarders.
ECOM offerings for this workflow
Systems Integrator
Connects the ERP, TMS, forwarding and WMS platforms that hold commercial and transport data with the partners that need it.
Exception Management Center
Helps automate exception handling and manage internal and customer-facing SLAs, for example when your broker reports missing data or a hold.
Transaction Life Cycle Manager
Holds shipment paperwork and supporting evidence, including proof of delivery, signatures, damage reports and shortage reports, with the shipment.
Freight Onboarding
Brings carriers and other freight partners live.
Trading Partner Onboarding
A self-service portal that supports almost all verticals, with customer click-through onboarding, protocol-specific setup and automated transaction testing.
Reconcile360 (invoice-to-cash)
Invoice-to-cash automation across all verticals, including air and ocean partners, so freight billing connects to cash.
Filing responsibility stays with the customer, broker, carrier or authorized filer. ECOM has capabilities to support ACE and ISF workflows and is not ACE- or ISF-certified. Which offerings apply, and the partners, protocols and systems in scope, are agreed with you during scoping.
Workflow
From commercial data to clearance status
The stages below show a typical cross-border process and where responsibility sits. Requirements vary by country, mode, product and program, so confirm with your broker.
- 01
Collect commercial data
Orders, commercial invoices, packing lists and product data are gathered from ERP, WMS and suppliers.
Typical messages: Commercial invoice, packing list; X12 810 and 856 where exchanged
- 02
Validate and prepare
The data is mapped and checked for completeness and consistency against rules agreed with your broker. ECOM supports this stage.
Typical messages: Validation results and queries
- 03
Send to the broker or forwarder
Documents and data go to the party that will prepare the filing, in the format and channel it accepts. ECOM supports this stage.
Typical messages: Partner-specific formats and APIs
- 04
Broker prepares and files
The licensed broker or another authorized filer prepares and files with the agency. ECOM carries the data in and the status back.
Typical messages: Filing by the broker; agency responses
- 05
Clearance status returns
Status from the broker, such as accepted, rejected or held, is exchanged with your systems and teams.
Typical messages: Status messages; CUSRES or X12 350 and 355 in some workflows
- 06
Cargo moves or is held
Carriers and terminals move, hold or release the cargo according to the status.
Typical messages: Transport events; 214, 315, XFSU, per mode
- 07
Resolve exceptions
Missing data, mismatches and holds are assigned and resolved with the documents that explain them.
Typical messages: Exception queue and SLA tracking
- 08
Keep the documents
Documents and evidence stay linked to the shipment record.
Typical messages: Document set per shipment
Who exchanges what in a cross-border shipment
The importer or shipper supplies commercial data, the carrier supplies transport documents, and the broker works with both and files with the agency.
Illustrative example: data to a broker and status back
An illustrative import shipment, followed step by step. Partners define their own messages and sequence.
| Step | Document or message | From → to | What the integration checks |
|---|---|---|---|
| Prepare | Commercial invoice and packing list data | ERP and WMS → ECOM | Required fields are present and the invoice and packing list agree. |
| Send | Shipment data | ECOM → broker | The broker receives the data in the format it accepts. |
| Query | Data question | Broker → ECOM → ERP team | The query reaches the person who owns the source data. |
| Status | Clearance status | Broker → ECOM → TMS | The status is attached to the shipment. |
| Exception | Hold notice | Broker → ECOM | The hold is raised and assigned, with the documents attached. |
Messages
Transactions and messages
Typical requirements—confirm with your trading partner.
Commercial and transportation documents in the workflow
These documents feed the broker’s preparation. They are described as business documents; how they are exchanged electronically depends on each partner.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| Commercial invoice Commercial invoice Business document (X12 810 where exchanged) | Describes the goods, parties, values and terms of sale. | Seller or exporter to Buyer, broker, forwarder | The goods are shipped | Parties, descriptions, quantities, values, terms | ERP | Value and product data reach the broker from the source system |
| Packing list Packing list Business document (X12 856 carries similar detail) | Lists what is in each package, container or pallet. | Shipper or exporter to Broker, forwarder, carrier | The shipment is packed | Package, quantity, weights, marks | WMS, shipping system | Packing data matches the invoice and the cargo |
| Transport document Bill of lading, waybill or equivalent Transport document (X12 304, 211, 404 and others by mode) | Records the contract of carriage and links the cargo to a carrier movement. | Carrier or forwarder to Shipper, broker, consignee | The cargo is accepted for carriage | Parties, cargo description, references | TMS, forwarding system | Transport references link the commercial data to the move |
Customs-related message standards you may meet
These standards exist for customs data. ECOM supports transmission of all EDI X12 and EDIFACT transaction types, including these, and exchanges status with brokers. Not every transaction is required for every partner; which ones apply depends on the partner and the workflow.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| 309 Customs Manifest ANSI X12 | Gives customs manifest data for cargo on a vessel, train or other conveyance. | Carrier, terminal operator or port authority to Customs authority | Cargo arrives or departs | Conveyance, bills of lading, cargo | Carrier systems | Describes who files: carriers and terminals, not shippers |
| 350 Customs Status Information ANSI X12 | Gives cargo release and hold information to carriers, terminals and service providers. | Customs authority to Carrier, terminal operator or service provider | A release or hold decision | Bill of lading, release or hold status | Carrier and terminal systems | Release status reaches those who move the cargo |
| 355 Customs Acceptance/Rejection ANSI X12 | Reports errors and discrepancies in customs transaction sets submitted. | Customs authority to Ocean carrier, terminal operator, port authority or service center | A submission is checked | Error and discrepancy detail | Carrier and terminal systems | Rejections are seen and corrected |
| CUSDEC Customs declaration UN/EDIFACT | Submits customs declarations for import, export or transit to a customs administration. | Declarant to Customs administration | A declaration is made | Goods, parties, values, procedure | Broker or declarant systems | A common declaration format in many countries |
| CUSRES Customs response UN/EDIFACT | Acknowledges declarations and reports, reports errors and communicates decisions. | Customs administration to Declarant or carrier | A declaration or report is processed | Acceptance, errors, decisions | Broker or declarant systems | Responses return in a structured form |
Systems
Where ECOM sits in the exchange
The diagram separates ECOM’s data exchange and process automation from the preparation and filing done by the customer, broker, carrier or authorized filer. ECOM moves, maps, validates and tracks the data your business exchanges with its broker, forwarder and carriers.
Systems a cross-border integration connects
Data starts in business systems and ends with your broker and carriers. Scope usually covers these.
| System | What flows | What to plan for |
|---|---|---|
| ERP | Orders, commercial invoice data, product and party data. | Product classification and valuation data live in different places in different companies; confirmed during scoping. |
| TMS or forwarding system | Bookings, transport documents, milestones. | Transport references link the commercial data to the movement. |
| WMS | Packing and shipping detail. | Packing list data often originates in the warehouse. |
| Broker and forwarder systems | Data for entry preparation and status back. | Each broker accepts data in its own formats and channels. |
Problems and exceptions
Problems cross-border teams recognize
These are the points where manual work enters the process.
| Problem | Why it hurts | How ECOM addresses it |
|---|---|---|
| Data re-keyed to the broker | Invoice and packing data is retyped or pasted into e-mail, introducing errors and delay. | Data is exchanged from your systems to the broker through integration, where the broker accepts it. |
| Missing or inconsistent data found late | The broker asks for corrections close to the movement date. | Validation checks the data against agreed rules before it is sent. |
| Status chased by e-mail | Operations and customer service do not know if a shipment is accepted, held or released. | Status from the broker is exchanged with your systems, where the broker supports it. |
| Documents spread across systems | The invoice, packing list and transport document live in separate places. | The Transaction Life Cycle Manager keeps shipment paperwork with the shipment. |
| Holds nobody owns | A hold is noticed late and no one is responsible for resolving it. | The Exception Management Center supports assigning exceptions and tracking SLAs. |
Common cross-border exceptions and what is needed to resolve them
Your broker decides what the agency requires. ECOM helps get the right information to the right person quickly.
| Exception | Typical cause | How it is handled |
|---|---|---|
| Transport reference mismatch | Booking, bill of lading or container number differs between documents. | Needs the transport document and the commercial data side by side. |
| Rejected submission reported by the broker | The agency or broker system found an error. | Needs the broker’s message and the original data; the broker corrects and resubmits. |
Get started
How a cross-border engagement starts
Start with how data reaches your broker today.
- 01
Describe the current process
Tell us who your broker and forwarders are and how documents and data reach them.
- 02
Review the data and formats
We look at what the broker needs, in what format, and where the data lives.
- 03
Agree scope and responsibilities
Which data flows ECOM automates, and which parts remain with the broker, are agreed in writing.
- 04
Connect and test
Partners are set up and transactions tested, using the self-service onboarding portal where it fits.
- 05
Go live and support
Go-live is arranged with you and your partners, with 24×7 support defined in your service agreement.
Helpful to share, never required
- Your customs broker or forwarder, and the systems you exchange data with
- Your ERP, TMS or forwarding system, and WMS
- The documents involved (commercial invoice, packing list, transportation documents)
- Where preparation, rework or status chasing is manual
- The trade lanes and modes involved
- Your target timeline
Have a carrier specification? Send it for review Call Sales: 972-836-7750
Sources
Sources and related pages
Standards and partner requirements are revised over time, and each trading partner publishes its own. Confirm current versions with the partner before you build.
Standards and public sources
- CBP: ACE, the import and export processing systemCBP describes ACE as the centralized system for import and export processing, reached through a web portal or an EDI channel.
- CBP: Importer Security Filing (10+2)Applies to cargo arriving by vessel; the importer or its agent, such as a broker, files.
- ASC X12 transaction setsNames of the 309, 350 and 355 sets; matched to ECOM’s transaction guides.
Related pages
- Carriers and Freight Transportation hubAll six modes and processes.
- Ocean freightBooking, container events and customs workflows.
- Air cargoAir waybills and handling events.
- EDI 309 Customs ManifestThe manifest message in detail.
- CUSDEC Customs declarationThe EDIFACT declaration message in detail.
- EDIFACT messagesEvery EDIFACT message type.
- Rail Freight EDI and API IntegrationRail EDI and API integration for shipment instructions, waybills, interchange, equipment visibility and freight invoices.
- Logistics AutomationAutomate tenders, status updates, freight invoices and warehouse orders with logistics partners.
- EDI and B2B StandardsIndustry EDI, XML and payment standards handled by one B2B gateway, so each partner uses the standard it requires.
FAQs
Frequently asked questions
What does ECOM do in a cross-border shipment?
ECOM prepares, validates and transmits the data exchanged around a cross-border shipment over X12 and EDIFACT, exchanges status with brokers and connects your systems to your partners. Customs brokerage, and the filing itself, remain with your licensed broker or another authorized filer.
Does ECOM support ACE and ISF workflows?
ECOM has capabilities to support ACE and ISF workflows and is not ACE- or ISF-certified. CBP describes ACE as the system through which import and export data is processed. Filing responsibility stays with the customer, broker, carrier or authorized filer, and the data flows involved are defined in scoping.
Which documents are involved?
Commonly the commercial invoice, packing list and transportation documents such as a bill of lading or air waybill. Which documents and data a broker needs depends on the shipment and the regulation, so confirm with your broker.
Who is responsible for clearance and compliance?
Clearance decisions belong to the government agency, and compliance responsibilities stay with the importer, exporter and broker. ECOM makes the data exchange around them more reliable and visible.
How do exceptions work?
The Exception Management Center helps customers automate exception handling and manage internal and customer-facing SLAs. Which exceptions are raised, such as missing data or a hold reported by your broker, is agreed during implementation.
Where are the documents kept?
The Transaction Life Cycle Manager holds shipment paperwork and supporting evidence with the shipment record. Retention requirements are your own obligation; confirm them with your advisers.
Discuss your cross-border data exchange
Tell us how invoices, packing lists and transport documents reach your broker today, and where preparation, rework or status chasing is manual. An ECOM specialist will review the data exchange and options.