Tradeshift Implementation Guide - Engv2
Tradeshift Implementation Guide - Engv2
Tradeshift Implementation Guide - Engv2
Implementation-Guide
For suppliers of
Eberspächer Climate Control Systems GmbH & Co. KG
Eberspächer Exhaust Technology GmbH & Co. KG
Inhalt
1. Introduction .................................................................................................................................... 3
1.1. About this document .............................................................................................................. 3
1.2. Intended audience .................................................................................................................. 3
2. Tradeshift Introduction ................................................................................................................... 3
3. Eberspächer’s use of Tradeshift ...................................................................................................... 4
3.1. Eberspächer’s current set-up on Tradeshift ........................................................................... 4
3.2. Eberspächer’s scope of use ..................................................................................................... 4
3.2.1. Outbound Purchase orders (PO) ......................................................................................... 4
3.3. Eberspächer validation rules on Tradeshift ............................................................................ 4
4. Getting started on Tradehshift ....................................................................................................... 5
4.1. The basics of Tradeshift .......................................................................................................... 5
4.2. Creating your account in Tradeshift for existing Eberspächer suppliers ................................ 5
4.3. Creating and managing connections....................................................................................... 6
4.4. Navigating through the Tradeshift platform ........................................................................... 6
4.5. Sending your first invoice........................................................................................................ 8
5. Options for automated invoice sending ......................................................................................... 9
5.1. Web Interface ......................................................................................................................... 9
5.2. Cloudscan (PDF) ...................................................................................................................... 9
5.3. Integration options for automated invoice sending ............................................................... 9
5.4. Interoperability ..................................................................................................................... 10
6. Annexes ......................................................................................................................................... 10
6.1. FAQ........................................................................................................................................ 10
6.2. Eberspächer Legal Entities on Tradeshift .............................................................................. 13
6.3. Further information on integration options ......................................................................... 13
Seite 2
eInvoicing Implementierungs-Leitfaden
1. Introduction
1.1. About this document
This implementation guide for electronic invoices was prepared by all introducing Business Units from
Eberspächer (in the following referred to Eberspächer) to provide all necessary information to the Eberspächer
suppliers they require in order to be able to send electronic invoices to Eberspächer via the Tradeshift
platform.
If you, at any time, require assistance, please do not hesitate to contact Tradeshift’s Support Team on the
following email address:
If you are reading this document, you will be required to use Tradeshift in order to send e-invoices to
Eberspächer in the future.
Larger suppliers to Eberspächer will probably need to develop a fully automated integration with Tradeshift,
while for smaller suppliers using Tradeshift’s cloud-based web portal might suffice. Regardless of your needs,
this document contains all the information that you require in order to support the necessary changes to your
existing business processes in relation to working with Eberspächer.
2. Tradeshift Introduction
Founded in 2009 in Denmark, Tradeshift is today the world’s fastest growing business-to-business network,
which supports the exchange of business data in the form of documents such as (but not limited to): quotes,
purchase orders, invoices and credit notes, and the softer communicative processes that typically accompany
the exchange of such documents such as document status.
Tradeshift differs from other EDI based networks on a number of key points:
Finally, Tradeshift has all the necessary security and compliance certifications, which are required in order to
run a platform on this scale. For more information regarding security or compliance, please do not hesitate to
contact Tradeshift support.
Seite 3
eInvoicing Implementierungs-Leitfaden
Please remember that in order to send electronic invoices to any member of the Tradeshift network, the
parties must have a mutually accepted connection, see section 4.3. “Creating and managing connections”.
Once installed, the primary contact and any added members will receive email notifications on any POs
received via the app. One additional advantage is that POs can easily be flipped in an invoice.
• Eberspächer PO Number: All invoices sent via Tradeshift must contain an Eberspächer PO Number.
This number should be issues to you by your Eberspächer representative at the time of order
placement. These numbers can be provided once at the invoice header level, or, on all lines of the
invoice.
• Person Reference: In some specific cases, a Person Reference might be required instead of a
Eberspächer PO Number. The format of the field is specific, and must be in following format:
“[email protected]”
• Eberspächer material number: All invoices sent via Tradeshift must contain an Eberspächer material
number, which will be indicated on our orders. If the Eberspächer material number is not available,
the supplier-material number is to be used instead. These numbers can be provided on all invoice
lines.
Further to this, it is important to note that there are some standard fields on typical invoices that Eberspächer
does not wish to receive from the Tradeshift platform (not visible in the web interface, and simply ignored in
the case of EDI files). They are:
• Invoice due date: invoices will always be paid based on the previously agreed terms and conditions, as
stipulated in your supplier agreement, and therefore are not necessary within the individual invoice.
The due date will be calculated by using the transmission date to Tradeshift.
Seite 4
eInvoicing Implementierungs-Leitfaden
• Payment details: invoices will always be paid, based on the payment details that your customer has
registered within its financial system. If you need these changed, then you should contact your
customer directly.
Once the account has been created, and the connections have been established, it is up to each user to decide
how they would like to use Tradeshift. In order to get you started, the following section will cover account
creation, managing connections and sending your first invoice.
Furthermore, the connection that is established between your organization and Eberspächer also contains
“connection properties”. Connection Properties are internal information about the customer or supplier with
which you have a connection, and as such are only visible to the part that creates them. Eberspächer has
stored connection properties on the connection with your organization. These “connection properties” are
internal Eberspächer information and although they are not visible to you they are important to Eberspächer
in order to facilitate faster invoice processing (information includes your Vendor ID number at Eberspächer).
Once created, the account is yours to manage as you please. It is always best to start by editing your company
details, including your company name, address, logo, tax and legal identifiers etc. The tax identifier has to be
completed. The national Tax ID has to be inserted in the field “Steuernr.” and the VAT ID in the field „MwSt-
Nr.“.
One important point to consider is the “Notifications” options, under the “Edit your settings” menu. The
Notifications option allows you to configure what notifications you would like to, and not like to, receive from
the Tradeshift platform.
Seite 5
eInvoicing Implementierungs-Leitfaden
As Eberspächer will be using the Tradeshift platform to receive invoices on behalf of many legal entities across
the EU, it is vitally important to consider who from within your organization will receive these notifications
when a new Eberspächer entity wants to connect with you on Tradeshift. Furthermore, as more and more of
your suppliers and customers join Tradeshift, it is important that you manage all “connection requests” that
you might receive. Remember that this account is the face of your company on the Tradeshift network, and
many more of your customers and suppliers will need to find you here in the future.
Regardless of whether your other customers or suppliers are a part of the Tradeshift network or not, you can
use Tradeshift to send documents to these additional customers or suppliers completely free of charge. If your
customers / suppliers are already on the Tradeshift network, you can simply search for them on search bar
under the “’Connections” tab and send a connection request. As soon as the other party has accepted the
connection request, they will become part of your private network and you can start sending invoices to them
immediately.
If your customers / suppliers are not a part of the Tradeshift network, you can simply add them as a “manual
contact”. Any documents sent to your manual contacts will simply be sent as PDF attachments emailed to the
email address that you provide under the manual contact, or in the EDI file you dispatch (in the case of fully
electronic senders).
Regardless of how many invoices your organization sends per year, and regardless of how you are planning to
use Tradeshift (web portal or a fully automated integration) you will need to start the process by having a good
understanding of the Tradeshift web interface, as it is within this interface that you create and manage your
account, connection and any integration efforts.
Seite 6
eInvoicing Implementierungs-Leitfaden
Simple navigation
After logging onto the Tradeshift Platform, you will notice the menu on the left of the screen. This
menu is made up of four main sections:
Tasks
This is s new Feed showing what is happening in your network with regards to documents, statuses and
connections.
Profile
The “Profile” sub-section is your profile on Tradeshift and contains all the information about your company’s
presence on Tradeshift that is visible to the entire network.
Network
Shows an overview of your existing network on Tradeshift, including manual and Tradeshift connections, and it
is from here that you can add new receivers and accept connection requests
Documents
This section contains an overview of all your business documents on Tradeshift. Within this section, you can
create and manage all your document types including Purchase Orders, Invoices and Credit Notes.
Support
This section contains a link to Tradeshift’s support site
Settings
In this section you can change your personal settings, company data and notifications.
Seite 7
eInvoicing Implementierungs-Leitfaden
Select the receiver and add the invoice details as per the template. Bank account details, Attachments and
notes can be added to the invoice by clicking the buttons at the bottom of the template. When you are
satisfied with the invoice you can see a preview by selecting “Preview” at the top of the page, otherwise, select
“Send” when you are ready to send the invoice.
If there are any errors with the invoice, you will receive an instant error message on the screen, and you will be
given a chance to rectify the problem. Once successfully dispatched, you can see the document by clicking on
the “Sales” item from the menu on the left. Within this view, you can see the following information about the
document:
• All your documents on Tradeshift, including the invoice number and due date (can be sorted)
• The status bar shows the time left before payment of the invoice is due. Once the payment date is
reached, the status bar will turn red, and the status will become overdue.
• The status of each document is visible when rolling your mouse over the specific document.
• You can click on the documents to see them in detail.
• You can search for specific details about invoices by using the search bar at the top of the screen
Please note that you are able to add base quantity pricing (price per 100/1.000) should there be a need for
that. You can do this when creating invoices in the web UI by choosing the line item Unit and then choosing
"Add Base Quantity" in the same drop down list. This will allow you to define a price such as "5 EUR per 1000
things".
This feature is also available for suppliers sending via an automated solution.
Seite 8
eInvoicing Implementierungs-Leitfaden
This option will be usually chosen with an annual invoice volume up to 10 invoices.
This option will be usually chosen with an annual invoice volume up to 50 invoices.
• „Document-Uploader“ App
• Forwarding via Email
The corresponding email address can be found in the menu under
„network“ -> Eberspächer-entity -> „View company details“
All the information required in order to make these decisions is contained in the following section.
Tradeshift offers a number of free integration options so you can automatically transfer documents.
These options are:
• SFTP (http://tradeshift.com/integrate/sftp/)
• FTPS (http://tradeshift.com/integrate/ftps/)
• Interface / API (http://developer.tradeshift.com/rest-api/)
More information regarding the integration options can be found in Annex 6.3
Once you have decided which transfer mechanism suits your requirements, the next thing is to look at
which formats your accounting system can export.
Tradeshift support a wide range of formats. This basically means that if your system exports invoices
in any of the Tradeshift formats, you can upload them to Tradeshift for free and without having to
make changes to the original format.
Most used formats are cXML, BASDA, CSV, EDIFACT and OIOXML. You can find detailed information on
these and the rest of the supported formats here:
http://tradeshift.com/integrate/.
Seite 9
eInvoicing Implementierungs-Leitfaden
Within the different formats on http://tradeshift.com/integrate/, there is a zip file. The zip file
package includes further information.
Before you move forward with the integration, we strongly suggest you to look at the zip package for
your file format.
5.4. Interoperability
Tradeshift promotes the use of multilateral interoperability models like PEPPOL (EU), EasyTrade (DK), ELMA
(NO). This ensures full scalability at the lowest costs for customers and their suppliers. Requests to interface
directly with other service providers are also supported as long as the service provider uses Tradeshift API and
send in supported formats. Tradeshift provides all support and traffic free of charge for the service provider in
both of the above cases.
If you know that your buyer is registered on PEPPOL and therefore able to receive via that channel, you
can simply reach out to them, ask for their PEPPOL ID, and use that when dispatching your documents to
them.
You can also reach out to Tradeshift’s support team for any questions around PEPPOL or interoperability in
general.
6. Annexes
6.1. FAQ
Seite 10
eInvoicing Implementierungs-Leitfaden
Once you have created your test account, you are welcome to find and connect with the Eberspächer test
accounts on Tradeshift. Simply search for them in the network and send a connection request. Your request is
automatically approved.
What are validation rules, and why are they put in place?
Validation rules ensure that the sender of a document provides the information necessary to process the
invoice. Eberspächer requires some specific fields in your invoice in order to process them efficiently.
Ultimately they are put in place to make sure that the invoice can be handled without any further contact, and
that the supplier gets paid on time. Validation rules are a way of enforcing business rules.
• Eberspächer PO Number: All invoices sent via Tradeshift must contain a Eberspächer PO Number.
This number should be issues to you by your Eberspächer representative at the time of order
placement. These numbers can be provided once at the invoice header level, or, on all lines of the
invoice.
• Person Reference: In some specific cases, a Person Reference might be required instead of a
Eberspächer PO Number. The format of the field is specific, and must be in following format:
“[email protected]”
• Eberspächer material number: All invoices sent via Tradeshift must contain an Eberspächer material
number, which will be indicated on our orders. If the Eberspächer material number is not available,
the supplier-material number is to be used instead. These numbers can be provided on all invoice
lines.
Seite 11
eInvoicing Implementierungs-Leitfaden
Further to this, it is important to note that there are some standard fields on typical invoices that Eberspächer
does not wish to receive from the Tradeshift platform (not visible in the web interface, and simply ignored in
the case of EDI files). They are:
• Invoice due date: invoices will always be paid based on the previously agreed terms and conditions, as
stipulated in your supplier agreement, and therefore are not necessary within the individual invoice.
The due date will be calculated by using the transmission date to Tradeshift.
• Payment details: invoices will always be paid, based on the payment details that your customer has
registered within its financial system. If you need these changed, then you should contact your
customer directly.
On top of these validation rules, please note that if you plan to send invoices and credit notes automatically
from your ERP system, there is a range of mandatory fields you would need to adhere to. For mandatory fields,
please go to http://integrate.tradeshift.com/, and download the specific zip file for the format you wish to use.
Seite 12
eInvoicing Implementierungs-Leitfaden
Tradeshift offers a number of free integration options so you can automatically transfer documents.
• SFTP (http://tradeshift.com/integrate/sftp/)
• FTPS (http://tradeshift.com/integrate/ftps/)
• API (http://developer.tradeshift.com/rest-api/)
Advantages of FTP/SFTP/FTPS:
• Well-known, standard and widely used transfer protocols
• Most likely already used in some of your enterprises in one shape or form
• The integration will - in many cases - need little extra development work.
Disadvantages:
• Basic functionality available only
• Uploading documents have to be finished with files with the so-called semaphore mechanism
• No interaction with documents and companies on Tradeshift
• After uploading and dispatching documents, monitoring the documents on the server is required.
Advantages of API:
• Real time interaction, such as search functionality and immediate response on the status of your
uploaded documents.
• Offers the whole range of functionality from the Tradeshift public API.
Disadvantages:
• Might be a new way of transferring documents for some enterprises and thus more time consuming
in the beginning.
In the following, each integration option is described in more detail. You can also find a lot of useful
information using the links above.
SFTP stands for ‘SSH File Transfer Protocol’. It is not related to FTP except that it also transfers files
and has a similar command set for users. If you are not familiar with SFTP it is recommended to find
out more about it before continuing reading this page. There is plenty of information about SFTP
available on the web.
In order to use this integration method you have to have an accounting or ERP software which is able
to send documents over SFTP or an SFTP client (there are plenty of free SFTP clients available). You
have also to activate the ‘SFTP Uploader‘ app from the Tradeshift apps.
Seite 13
eInvoicing Implementierungs-Leitfaden
To integrate your ERP, accounting system or SFTP client with Tradeshift, please follow these steps:
For more detailed information, please refer to http://tradeshift.com/integrate/sftp/ and this article
on the Tradeshift support forum: https://support.tradeshift.com/entries/22975226-SFTP-Uploader.
FTPS stands for ‘File Transfer Protocol Secure’. It is a standard network protocol used to transfer files
from one host to another over a TCP-based network, such as the Internet. If you are not familiar with
FTPS it is recommended to find out more about it before continuing reading this page. There is plenty
of information about FTPS available on the web.
In order to use this integration method you have to have an accounting or ERP software which is able
to send documents over FTPS or an FTPS client (there are plenty of free FTPS clients available). You
have also to activate the ‘FTPS Uploader‘ app from the Tradeshift apps.
To integrate your ERP, accounting system or FTPS client with Tradeshift, please follow these steps:
NOTE: FTPS servers data transfer is enabled in the PASSIVE mode only. FTPS server is using IMPLICIT
data transfer mode.
For more detailed information, please refer to http://tradeshift.com/integrate/ftps/ and this article
on the Tradeshift support forum: https://support.tradeshift.com/entries/22975236-FTPS-Uploader
Seite 14
eInvoicing Implementierungs-Leitfaden
generate a daily report about the contents of these folders, please also see section “Integration
Monitoring”.
The API is HTTPS+REST based and talks JSON or XML. Documents, dispatches and everything else is
considered 'resources', which you can use HTTP PUT/POST/GET/DELETE to manage. The Tradeshift
Web portal itself uses the API. Security is 3-legged OAuth-based.
All functionality of Tradeshift is exposed through a REST API, but only a subset of this API is exposed
publicly. The public API gives control over the following resources:
• Content – for handling raw documents (invoices, attachments, any kind of business documents).
• DocumentMetadata– holds document metadata.
• DocumentList – lists of document references, based on filter- and search criteria.
• DispatchRequest – sends documents to other Tradeshift companies, or to external networks.
• TagList - gets a list of tags put on a specific document.
The ‘Connection’ resource is used to manage the business network of your company, and for
referencing senders and receivers of business documents.
Users and tenants (companies in Tradeshift terms) are handled with the "Tenant" and "User"
resources. Tenants and users are referenced in the API through their Tradeshift-internal IDs.
Client considerations
• Always send a User-Agent header in all requests. The header should identify your client and
version. Use something like BananaCorpClient/3.4.
• Always send an Accept header indicating either application/json or text/xml
• All requests can fail in a number of ways. For application errors, we always return the same error
structure, so be prepared to handle that always. The structure is described on the REST API page.
Documents considerations
• One often seen use of the API is to synchronize documents to another system. This is possible by
polling the external/documents resource for changes. There are two strategies for this: either poll
for changes since last poll, or poll for unknown documents. When polling for changes since last
poll, simply do a poll, save the timestamp, and include it in the "since" query parameter in the
next poll. When polling for unknown documents, do a poll, loop through all received documents,
use the external/documents/{documentId}/tags/{tag} resource to PUT a custom tag to the
document, such as "POLLED_BY_BANANACORP". All requests to external/documents should then
Seite 15
eInvoicing Implementierungs-Leitfaden
6.3.7. Connectors
http://tradeshift.com/blog/tradeshift-apps-where-do-i-start/
Apart from the FTP/SFTP/FTPS and API integration options, Tradeshift also offered off-the shelf
connectors. Some of these are:
Advantages:
• Someone else has done the work
• Needs little effort
• Easy to activate (install) and use
• Integrates Tradeshift with your accounting or ERP system.
Disadvantages:
• Inflexible – you get what’s in the connector
• In some instances the connector is not free
• Usually dependent on a third party provider.
QuickBooks
The QuickBooks Online App is currently UK only. You can export Tradeshift invoices to QuickBooks.
You can also import QuickBooks customers into Tradeshift. The App is free.
KashFlow
The KashFlow connector allows you to manage your sales and purchase invoices in KashFlow, and
send and receive them via the Tradeshift network. The connector is free.
Seite 16