The Service Bureau processes EDI data from one partner into a readable format for the destination partner and then sends it to the intended business partner.

Tag Archive for: Service Bureau


In today’s article, I will be addressing the best option to process EDI data, exchanged between business partners, by identifying the advantages and inconveniences of two methods; an EDI Service Bureau and a Translation/Integration solution.

It’s not a surprise to business people that exchanging business data using EDI protocols and formats has been around for a while and is clearly here to stay. If you’ve stumbled upon this EDI article, then you are perhaps either interested in enhancing your EDI capabilities or looking to implement EDI in your business environment. Either way, it is proof that EDI is still in demand in the business community.

As this is my first time addressing EDI through a Service Bureau in my blogs, I will clearly define and explain what a Service Bureau does and provide my opinion on the topic.

EDI Service Bureau

EDI Service Bureaus have been around for many years. They were created as a third party provider sitting between business partners. How it works is simple. The Service Bureau receives EDI data from one partner to process into a human readable format (on behalf of the destination partner) and then send out to that destined business partner.

How A Service Bureau Processes EDI Data

As mentioned above, upon receiving the EDI data from a VAN or directly from a business partner, a Service Bureau will take that data and process it to generate a format that is agreed upon by the destination partner. The most commonly used formats are:

  • Paper document
  • PDF document
  • Excel format or CSV (Comma Separated Values)
  • Web-based document

Once the EDI data received by the Service Bureau is translated to one of the above formats, the Service Bureau would then transmit the translated document to his client (final destination partner) using one of the following methods:

  • Fax
  • FTP or sFTP
  • E-mail

For outgoing EDI documents, the partner would return the information to the Service Bureau in the same formats as mentioned above (i.e. paper, PDF, Excel or CSV documents). Nowadays, some Service Bureaus provide web-based interfaces for their clients, to manually enter the data in order to generate outgoing EDI files to be sent to their partners.

EDI solution and ERP

How Businesses Process Data Received From Service Bureaus

Depending on which format the Service Bureau translates the EDI data into, the business partner would have to deal with it differently. Here are the possible scenarios for incoming EDI documents:

  • If the data is treated in a web-based format, the business would need to login to the Service Bureau web portal, retrieve the data (orders, invoices, etc.), print or export the document, and then either key it in manually into their own management system or import it from CSV, only if their internal system supports this kind of process.
  • When the EDI converted data is sent as a paper document or PDF (received by either fax or e-mail), the user will then have to key the information received in manually into their system, without question.
  • When the data is received in Excel or CSV format, the user can either key in the data manually or import it into his internal ERP system.

The same concept applies for outgoing EDI documents through Service Bureaus. In all cases, the business has to either key in data in Excel or manage it through a web-based interface provided by the Service Bureau.

Service Bureau Inconveniences

As you may have noticed by now, exchanging EDI via a Service Bureau is not the most efficient way of communicating with business partners (click to tweet). In fact, the likelihood of human errors and inefficiencies are very high. In this day and age, where there are constant improvements in technology, it is extremely inefficient for SMEs to be keying in orders received by EDI (through paper document or PDF) (click to tweet). Even with the web-based alternative that Service Bureaus offer, it is still unproductive to manage multiple systems rather than having one single platform with full EDI capability.

Read: Convert EDI to XML: the Winning SaaS Option

EDI Translation & Integration

Once businesses have switched from using a Service Bureau to implementing an EDI translation and integration solution, they have eliminated all kinds of inefficiencies and human errors and have become much more efficient. The way it works is by having a fully integrated business solution in place that has built-in capability to process incoming and outgoing EDI documents. Refer to my previous article entitled See What It Means To Be Fully Integrated with an Efficient Business Software Solution that expands more on integrated solutions.

However, it is very common for business owners to be hesitant to implement a fully integrated solution into their small business, as they believe all ERP systems are expensive. That is simply not the case anymore, as we are in 2014 and IT solutions have become very affordable. EDI2XML offers affordable EDI integration that fits into the budgets of small and medium sized businesses (click to tweet).

What Is The Best Option: EDI via a Service Bureau or a Translation & Integration method?

As a professional IT consultant and developer, I have helped many small and mid-sized businesses streamline their business processes for over 20 years. I truly believe a fully integrated process and solution would be the best option to go with. Not only is it more efficient for your company as a whole but is also affordable. I have already published my arguments in a previous article entitled EDI integration projects: Advantages and Benefits.

If you are interested to learn more about this topic or any other issue related to IT or EDI, please click on the image below and I will be more than happy to contact you for a FREE consultation.

2 copy

 

This post was updated to reflect current trends and information.


As soon as there is a requirement for EDI implementation and integration, company executives, along with their IT personnel, begin by determining how they will comply with their EDI business partner to exchange EDI documents. They will need to acquire EDI translation software, initiate testing, and so on. This however is a complex and lengthy process, which many executives do not look forward to. Difficult questions arise, such as, “Shall we outsource to an EDI service provider? Shall we do it ourselves “on-premises”? Shall we do the translation and conversion of EDI “as a service” using an outside provider?

Which of these options is the best and most affordable way to go?”

Why Do We Need To Translate EDI

As you already know, EDI (Electronic Data Interchange) is the standard to exchange business data between business partners in a very proprietary EDI format. Your business partner would send data such as a P/O (EDI 850), an Inventory Inquiry/Advice (EDI 846), or any other EDI transaction, based on his own terminology of business parameters. It is then up to the “receiving party” to take the sender’s EDI data and information, translate it into a well-understood format, which the receiver’s system will be able to use and process. With EDI2XML, we translate the EDI format of incoming documents to a much simpler, more structured XML format so humans, namely the IT developers, and systems can easily work with.

Translate EDI “On-premises”

Normally, translating incoming EDI documentson-premises” requires a lot of parameters before launching such a project. As a starting point, a good level of expertise in EDI, EDI communication, and systems integration is required. Integrators should also have a fairly advanced knowledge and expertise in how the company’s software system (ERP, CRM, etc.) works and how to integrate and push data into that system.

While the ability to integrate with the most commonly used ERP and CRM systems does not create any major challenge for experienced IT developers, the main problem is having a high level of proficiency in EDI implementation.

Another major task for the “on-premisestranslation is, in most cases, the need for the company to invest on hardware, software licenses, and services (internet, dedicated IP, VAN) to be able to exchange EDI documents with their business partner.


Useful Reading: What are the advantages of using EDI2XML?


Translate EDI “As a Service”

With the emergence of cloud-based IT services and the affordable plans offered by service providers, the ability to translate EDI “as a service” in the “cloud” and deliver the end result to the ultimate destination, has become a more productive approach.

Typically, an EDI service provider offering EDI translation “as a service” will:

– Act as an intermediary layer between the EDI sender and EDI receiver

– Receives the EDI incoming document (i.e. 850, 860, 864,…) on behalf of the “ultimate receiver”

– Extract the data received in EDI format and translate it into a standard format (i.e. XML)

– Transmit the XML data to its ultimate destination for Integration OR integrate directly into the software system of the ultimate receiver.

To send EDI documents out, the EDI service provider will be acting also as an intermediary hub between business partners and do the following:

– Receive data in XML format to be sent to the business partner from the sender through FTP or sFTP

– Translate data received and convert from XML to EDI format

– Transmit that EDI data to the destination

Dive into the world of EDI (Electronic Data Interchange) with our insightful video explanation. Explore the video

Advantages of EDI Translation “As a Service”

With the EDI translation in the cloud offered as a service, companies have a lot of great advantages:

– Quick implementation cycle

– Secured and proven platform to exchange EDI with partners

– No initial investment on hardware or software licenses

– Get up-and-running quickly: your projects are on-time and on-budget

– Use the wealth of expertise your EDI service provider has in EDI

– Let your team of IT professionals focus on integrating XML files into your system rather than learning EDI

– Predictable and static recurring monthly fee for the service

– Possibility to move to “on premises” mode any time

– Ability to integrate to your system directly without your internal IT resources

Discover how you can streamline and simplify your EDI projects with EDI2XML Fully Managed Services

The Best EDI Solution

Most companies usually lean towards the “on-premises” option when they have “internal policies” and security measures in place or are a large enterprise with their own team of IT experts.

The “as a service” option is much more advantageous for small to mid-sized enterprises, where they may have a lower number of exchanged EDI transactions.

As the “as a service” option’s low initial investment and quick deployment are attractive features, every situation is different and should be dealt with on a case-by-case basis with one of our EDI experts prior to making a final decision.

Why use an EDI integration project?

In today’s business world, lots of decision makers are still wondering whether to plunge into EDI integration projects or to hire a couple of new employees to manually enter data received and processed by a third party EDI service bureau.

Which option is much more beneficial for their company and returns the most on their investment?

At a quick glance, hiring data entry clerks might seem appealing for the following reasons:
1) The EDI understanding is still a complex topic to understand by non-technical people;
2) The considerable initial capital investment on integration projects: professional services, EDI consultants, professional services…
3) The ongoing EDI service bureau transactional fees, connectivity fees..
4) The time and effort needed to integrate EDI with their ERP, or Business management software solution, that will be billed by IT consultants, EDI specialists and consultants.

While the above reasons are completely valid, companies stop short from researching about the evolution of the EDI world.

With EDI2XML and its “Software as a Service” model, companies are able to cut over 75% of their EDI integration projects costs and gain efficiency and accuracy within a short amount of time. Just by implementing and using EDI2XML translators, the IT consultant of an SMB, will be able to focus on building the integration between XML data files and the business management software solution in place, since XML is widely used and understood nowadays. EDI2XML is able to generate a readable XML of the EDI file, easily understood by humans and systems. As long as the IT consultant has access to the ERP database structure, he will be able to read the EDI formatted file in XML, and push to the tables, after applying all kinds of business validation. The same applies for outgoing EDI documents. As long as the IT consultant is able to generate an output XML file based on a pre-defined schema, XML2EDI engine will process that file and convert into an EDI file format.

EDI communication protocols are becoming very straightforward today; less complexity and more security. Major retailers and corporations are using AS2 or FTPs secured in order to communicate EDI documents back and forth between business partners. Even better, if a company is not able to handle EDI projects due to lack of budget or expertise, EDI2XML technology is used and empowering erpwizard which is a fully integrated business management software solution offered “as a service” (SAAS) either “on customer premises” or in “the cloud“. Not only is it a fully integrated ERP software solution, but it offers a complete EDI solution.

We have over 15 years in EDI integration in the retail, manufacturing, distribution and healthcare industries. We’ve been very active in Montreal, Canada, where our EDI consultants are experienced at the business level just as much as they are at the technical level.

Read: Free EDI to XML converter: What’s the catch?


Free EDI Demo