Home / Service
Service
From the first file to round-the-clock operations
We take care of the whole journey of data between you and your partners.
Receiving, checking, translating, delivering and monitoring.
How it works
Three steps for every message
One message type from a partner is one flow.
Orders, invoices and dispatch advices each have their own settings.
-
01
Receiving
The partner sends the file the way they are used to.
To their own folder on our SFTP, via AS2, to an API or by e-mail.If the partner cannot do that, we regularly pick the files up from their server.
received 16:40:08 -
02
Checking and translation
We check the file against its schema.
Then we convert it into the format you need.We rename fields, recalculate totals and add codes from your lookup tables.
A separate file can be created for every line item.EDIFACT → CSV + JSON -
03
Delivery
The result goes where you expect it.
Into your system, by e-mail to accounting or back to the partner via AS2.If the destination is not responding, delivery is retried.
delivered to 2 destinations
Live
The message flow in one diagram
Regular messages, a file per line item, a blocked message with an alert and a delivery retry.
Switch the API between synchronous and asynchronous mode.
Try simulating destination maintenance too.
Swipe the diagram sideways.
Formats and connections
We adapt to your partner, not the other way round
Any combination of input and output works.
EDIFACT can become XML and CSV at the same time.
Transfer methods input and output
- Our SFTP
- The partner has their own locked folder.
Sign-in with a password or an SSH key. - The partner's SFTP
- We pick files up from their server or deliver them there.
- AS2
- Signing, encryption and MDN receipts.
We prepare the certificates. - HTTP API
- Receiving and sending over REST.
You choose the mode for each flow.
A synchronous call gets the result right in the response.
An asynchronous one is accepted into the queue and the receipt comes immediately. - Attachments received from a mailbox.
Outputs sent as an attachment or a ZIP, with the subject and text you want.
Formats any combination
- EDIFACT
- ORDERS, DESADV, INVOIC, APERAK and other messages.
- XML
- Your own and standard schemas.
Validation against XSD. - JSON
- For modern systems and APIs.
- CSV and TXT
- With or without a header, any separator, or fixed-width records.
- Excel
- xlsx and xls on input and output.
- Other files
- PDFs, images and other attachments are passed on unchanged.
Need something else?
Another format, a special connection or a custom extension can be added as needed and agreed.
Checks and rules
Nothing that does not fit reaches your system
We set the rules to your requirements.
An invalid message is blocked before it can do any harm.
Input check
We validate the partner's file against its schema.
We also check required values, such as the document number or the buyer.
Output check
The result of the translation must also match your system's schema.
If it does not, it is not sent.
Blocking and alerts
A faulty message is stopped.
An e-mail alert goes out and the portal shows exactly what is wrong.
Lookup tables and calculations
Unit and partner codes, recalculated totals, date formats.
The rules live in lookup tables and can be changed quickly.
Document numbering
Your own number sequences with a yearly or monthly reset.
The same number in the content and in the file name.
Operations and support
Stable operations, even during outages
The service runs around the clock.
We made sure a message is never lost and never overtakes another.
The order is kept
Every message type has its own queue and is processed in order of arrival.
On an error the queue can stop so the order does not break.
Synchronous or asynchronous
With a synchronous call the sender waits for the result and gets it in the response.
With an asynchronous one the message is accepted into the queue at once and processed in order.
Pausing input and output
Planning downtime for your ERP?
We pause delivery.
Messages keep arriving in the meantime and go out in order when it ends.
Retries when a destination is down
When your system does not respond, delivery is retried.
If even that does not help, you get an alert.
Nothing gets lost
A received file is stored before processing.
Unfinished messages are completed even after a server restart.
Test and production
Separate environments with their own accounts and addresses.
We verify a change on test data and only then switch it on.
24/7 monitoring and support
We watch operations all the time.
When there is a problem, we act and you get a message about what is going on.
Access and roles
Everyone sees and does only what they should
We set up access for each partner separately.
The number of users and their rights follow our agreement.
Roles in the portal
- Read.
Overview, list of transfers, detail and file downloads. - Upload.
The user can send a file directly from the portal. - Reprocess.
Run processing or delivery again after a fix. - Partner admin.
Extended rights for your key people.
Security
- Separated data.
A partner sees only their own transfers. - Locked folders.
No SFTP access outside the partner's own folder. - Encryption.
Transfers over SFTP, AS2 and HTTPS.
Passwords to external systems are encrypted in the database. - Change history.
Who changed what and when.
Let's walk through your case
Tell us who you exchange data with.
We will suggest a solution and estimate the time to go live.