Resources · ECOM B2B Gateway
What the B2B Gateway covers
One gateway for the data formats, EDI and industry standards, and communication protocols your partners require. This page lists each, with the qualification that applies, so you can see quickly whether a partner's requirement is covered.
Each colored card is one part of the coverage: the formats the gateway reads, the standards it translates, the VDA messages supplied, the wider catalog, the protocols it connects with, and the few formats that are scoped separately.
The communication protocols cover the first step. Formats and standards cover reading and translating. Validation uses the partner's rules, and the last step delivers to your ERP or other systems.
General data formats
General data formats
The file and data layouts the gateway reads and writes, alongside the EDI standards.
| Format | Support details |
|---|---|
| Fixed-width / fixed-length files | Positional records and fields |
| Variable-length delimited files | Configurable delimiters |
| CSV | Supported through delimited-file mapping |
| Other delimited text | Custom record and field layouts |
| XML | XML mapping with schemas and namespaces |
| SQL / relational database structures | Relational database structures |
| Custom application files | User-defined positional, delimited, XML, JSON or EDI layouts |
EDI and industry standards
Standards and families
The EDI, payment and industry standards the gateway handles. Where support depends on the standards database installed for you, a licence or a bank's current requirements, ECOM confirms it during scoping.
| Standard or family | Qualification |
|---|---|
| ANSI ASC X12 | Transaction sets and versions follow the standards database installed for your gateway |
| UN/EDIFACT | Messages and directory releases follow the standards database installed for your gateway |
| TRADACOMS | Supported EDI syntax and message definitions |
| CII (Center for Informatization of Industry) | Japanese EDI syntax; industry message definitions are loaded from the published standards |
| VDA | Supplied through specific record layouts and system maps; see the VDA messages below |
| ODETTE | EDIFACT-based automotive messages and OFTP2 transfer |
| RosettaNet | Partner Interface Processes and RNIF packaging |
| cXML | Commerce XML documents for procurement networks |
| HL7 v2 and FHIR | HL7 2.9 schema validation, HL7 v2 transformation, HL7 v2 to FHIR conversion, FHIR validation and prior authorization, MLLP over TCP/IP |
| NACHA / ACH | Dedicated mapping support; licensing terms may apply to processing |
| SWIFT MT / ISO 15022 | Optional SWIFT dictionary; syntax and semantic validation |
| Fedwire | Dedicated mapping layouts; message generation and the bank's current requirements are confirmed during scoping |
| CHIPS | Dedicated mapping layouts; the supported release is confirmed during scoping |
| ATA SPEC2000 | Online messages, batch layouts and XML; Chapter 9 Automated Identification and Data Capture preloads are excluded |
Message-by-message reference for VDA, TRADACOMS, ODETTE, RosettaNet, CII, SPEC2000 and cXML
VDA messages
VDA flat-file messages supplied
The VDA flat-file messages supplied with the gateway, with the editions available. Every VDA recommendation, including the EDIFACT-based ones, is listed on the VDA page.
| VDA message | Supplied editions |
|---|---|
| 4905 Delivery call-offs | Edition 3 (October 1988); Edition 4 (April 1996) |
| 4906 Invoice data | Edition 2 (May 1993) |
| 4907 Payment advices | Edition 2 (August 1993) |
| 4908 Credit advices | Edition 3 (May 1996) |
| 4913 Delivery notes and transport data | Edition 1 (October 1994) |
| 4915 Detailed call-offs | Edition 1 (November 1989) |
| 4927 Container account statements and movements | Edition 1 (February 1993) |
The wider catalog
Implementation subsets, regional, healthcare, payment and XML catalogs
Subsets, variants and industry definitions available beyond the core standards.
| Category | Catalog entries |
|---|---|
| X12 implementation subsets | AIAG, Chrysler, Ford, GM, RAIL, RAIL FORUM, UCS, VICS |
| EDIFACT subsets and related messages | AIAG, EANCOM, EDIFICE, AUTACK |
| Regional EDI | RND (Rede Nacional de Dados) |
| Healthcare | X12 HIPAA validation |
| ACH variants | CCD, CCD+, CTX |
| Other payment formats | BECS, SAP payment formats |
| Financial XML | ISO 20022, FIXML, FpML, IFX, OFX, TARGET2 |
| Supply-chain XML | OAGIS, GUSI, TWIST |
| Industry XML | CIDX, PIDX, RosettaNet |
| ERP and application definitions | SAP IDoc, COBOL copybook import |
| SWIFT market practices | Germany MT515; US MT536 |
| SWIFT MX business areas | Alternative Funds, Bulk Payments, Cash Management, Cash Reporting, eMandate, Exceptions & Investigations, FpML, Funds, Funds Processing Passport, Proxy Voting, SCORE, Trade Services Utility, Transaction Reporting |
Communications
Communication protocols
How the gateway connects to partners. Available in both the B2B Gateway and managed file transfer. Protocol versions and configuration are confirmed during scoping.
| Protocol or standard | Support details |
|---|---|
| AS1 | EDIINT messaging |
| AS2 | EDIINT messaging |
| AS3 | Applicability Statement over file transfer |
| AS4 | Through the AS4 microservice and integration components |
| HTTP / HTTPS | Communication services and adapters |
| FTP / FTPS | File-transfer capabilities; adapter configuration applies |
| SFTP / SSH | Secure file transfer |
| SMTP / email | Email transport |
| SOAP / web services | Service-based exchange |
| REST APIs | REST API client service; payload handling depends on the service and release |
| WebDAV | Document exchange over HTTP or HTTPS |
| OFTP / OFTP2 | Dedicated adapter support; protocol version and configuration are confirmed during scoping |
| RosettaNet RNIF | Internet B2B exchange framework |
| ebXML | Internet B2B packaging and exchange |
| Zengin TCP/IP | Communication option for Zengin partners |
Documents and other formats
Documents and formats that are handled separately
Business documents are converted by PRISM-SmartConvert. A few formats need a conversation first, because carrying a file is not the same as parsing it or checking its meaning.
| Format or family | What to expect |
|---|---|
| Emails, PDF, Word, Excel and scanned images | Converted into structured data by PRISM-SmartConvert, then carried by the gateway |
| Advanced HIPAA compliance validation | Confirmed during scoping; X12 HIPAA validation is covered in the catalog above |
| NCPDP | Confirmed during scoping |
| Any proprietary binary file | Carrying the file does not establish parsing or semantic validation |
Frequently asked questions
Which EDI standards does the ECOM B2B Gateway support?
ANSI X12, UN/EDIFACT, TRADACOMS, CII, VDA, ODETTE, RosettaNet, cXML, ATA SPEC2000 and the payment standards NACHA, SWIFT, Fedwire and CHIPS, plus subsets such as EANCOM and the AIAG, Ford and GM implementation guides. The page lists the qualification for each.
Which communication protocols are available?
AS1, AS2, AS3, AS4, HTTP and HTTPS, FTP, FTPS, SFTP, SMTP, SOAP, REST, WebDAV, OFTP and OFTP2, RosettaNet RNIF, ebXML and Zengin TCP/IP. They are available in both the B2B Gateway and managed file transfer.
Can the gateway read files that are not EDI?
Yes. It reads fixed-width and delimited files, CSV, XML, relational database structures and custom application files with user-defined layouts, and maps them to and from EDI.
What about emails, PDFs, Word and Excel files?
PRISM-SmartConvert takes care of them. It converts emails, PDFs, Word and Excel files into structured data, which the gateway then validates, maps and delivers.
Does the gateway handle HL7 and HIPAA?
Yes. It covers HL7 2.9 schema validation, HL7 v2 transformation and conversion to FHIR, FHIR validation and prior authorization, MLLP over TCP/IP, and X12 HIPAA validation. The HIPAA and HL7 page has the detail.
What does "confirmed during scoping" mean?
Some capabilities depend on the standards database installed for you, a licence, a bank's current requirements or a protocol version. ECOM checks the exact versions with you and your partner before building a map, and tells you if anything falls outside the coverage.
Check a partner's requirement
Tell us the format, standard or protocol your partner asked for. An ECOM specialist confirms whether it is covered and how we would connect it.