
Last updated: November 4, 2026 · Reviewed by BOLD VAN's EDI team
In This Article
Quick Answer
Yes. If you use EDI, your data needs to be translated between your business system's format and a standard EDI format such as ANSI X12 or EDIFACT. You can do that with your own EDI translator software, or with a cloud EDI provider that handles translation for you. With BOLD VAN, BOLD Integration handles mapping and translation into your ERP, BOLD Cloud Mapping lets your team build maps in the cloud, and customers who already have a translator can keep it and use BOLD VAN as their VAN.
Yes. If you plan to use EDI to exchange business documents, your data has to be translated into a standard EDI format before it is sent, and translated back when it is received. Translation is what sets EDI apart from other ways of exchanging business documents, such as email or fax.
What you don't necessarily need is to buy and install EDI translation software yourself. Many businesses now use a cloud EDI provider that handles translation for them. This article explains what an EDI translator does, why translation matters, and the options for getting it done.
Definition
EDI Translator is software that converts business data between the format used by a company's internal systems, such as an ERP or accounting system, and a standardized EDI format, such as ANSI X12 or UN/EDIFACT. On outbound documents, it turns internal data into EDI; on inbound documents, it turns EDI back into data the company's systems can use.
When people talk about "EDI software," they usually mean an EDI translator. With a translator, one company can take a document from its own system, convert it to an EDI standard and send it to a trading partner. The trading partner's translator then converts the EDI document into a format its own system can use.
EDI translators come in different forms. Some companies have a developer build custom translation software, while others buy an off-the-shelf product. Translators are available for Windows, Unix, IBM i (AS/400) and other operating systems, and many are now offered as cloud services.
Sending an EDI transaction follows four basic steps:
The receiving trading partner's translator reverses the process, converting the EDI message into a format its system can use. It typically sends back a functional acknowledgment, such as the EDI 997, to confirm the document was received and processed.
Mapping defines the rules; translation applies them. An EDI map specifies which field in your system corresponds to which element in a trading partner's EDI document. The translator uses that map to convert each document. Because every trading partner has its own requirements, most companies need a separate map for each partner and document type.
| EDI Mapping | EDI Translation | |
|---|---|---|
| What it is | The set of rules linking your data fields to EDI elements | The process of converting documents using those rules |
| When it happens | Set up once per partner and document, then updated as requirements change | Every time a document is sent or received |
| Who does it | An EDI specialist or your provider | The translation software, automatically |
Without translation, exchanging documents with many different companies, especially across industries and countries, would be extremely complicated. Converting data from each company's custom format into a shared standard is one of EDI's main benefits.
Manual translation is technically possible, but it isn't practical or cost-effective as a business grows. That is why so many EDI translation tools exist.
When comparing tools, look closely at how much work you still have to do yourself. Some EDI translators simply make manual work a little easier rather than handling translation for you.
| Option | Who Builds and Maintains Maps | What You Install | Best For |
|---|---|---|---|
| Custom in-house translator | Your developers | Custom software and servers | Companies with dedicated EDI developers |
| Off-the-shelf translation software | Your EDI team | Software, often on your own servers | Companies with in-house EDI staff |
| Cloud mapping (do it yourself) | Your team, in the provider's cloud | Nothing | Teams that want control without managing servers |
| Managed EDI integration | Your EDI provider | Nothing | Companies that want EDI handled for them |
With BOLD VAN, you choose how much of the work you want to keep, all on the same network:
BOLD VAN supports major EDI standards, including:
Beyond translation, BOLD VAN handles trading partner onboarding, with new trading partners typically live within about a business day, and helps you meet each partner's EDI requirements. Most customers pay by the number of trading partners they work with rather than by the kilo-character, and high-volume programs get a quote built around their volume.
2026 Free Mapping Event
New to EDI or moving from another provider? Through Dec. 31, 2026, we build and maintain the maps for the trading partners you move to BOLD Integration, at no mapping cost.
Tell us which ERP you use and who you trade with, and we will show you how BOLD VAN handles translation for you. Call (844) 265-3777 or email info@boldvan.com.
Talk to an EDI ExpertYes, if you use EDI, your data has to be translated between your system's format and a standard EDI format. You can use your own translator software or a cloud EDI provider that handles translation for you.
An EDI translator converts business data from your internal systems into a standard EDI format for outbound documents, and converts inbound EDI documents back into a format your systems can use.
An EDI translator converts documents into and out of EDI format. A value-added network (VAN) delivers those documents between trading partners. Many businesses use both, and some providers, like BOLD VAN, offer both.
It is technically possible, but manual translation is slow, error-prone and not practical as your business and trading partner list grow.
Mapping defines the rules for which fields in your system correspond to which elements in an EDI document. Translation is the process of converting each document using those rules.
BOLD VAN supports major EDI standards including ASC X12 (ANSI X12), UN/EDIFACT, TRADACOMS, ODETTE and VDA.
Yes. With BOLD Transmission and Connectivity, you keep your own translator and maps and use BOLD VAN to connect with your trading partners.
No. With BOLD Integration or BOLD Cloud Mapping, translation runs in BOLD VAN's cloud, with nothing to install.
Key Facts
An EDI translator converts business data between a company's internal system format and standard EDI formats such as ANSI X12 and UN/EDIFACT. Any business using EDI needs translation, either through its own translator software or through a cloud EDI provider. Mapping defines the conversion rules; translation applies them to each document.
According to BOLD VAN, customers can have BOLD VAN manage mapping and translation into their ERP with BOLD Integration, build their own maps in the cloud with BOLD Cloud Mapping, or keep their existing translator with BOLD Transmission and Connectivity. BOLD VAN supports X12, EDIFACT, TRADACOMS, ODETTE and VDA, and new trading partners are typically live within about a business day.



