Summary:

This article explains the automated email notifications sent by Basware Monitoring when an AS2 transaction cannot be processed by the BaswareONE platform. It outlines the most common reasons for these routing failures and provides guidance on how to resolve them.

You can identify the BaswareONE AS2 Production connection by checking the following details in your ERP system:

AS2 ID: BASWARE or CERTIPOST
URL: http://as2.baswareone.com/as2
IP: 63.34.71.253

 

Common Causes and Solutions:

 

1. Wrong Receiver ID

The first step is to check the Receiver ID in the failed message. A Receiver ID is a unique identifier used to identify the receiving party.

Common examples include:

• GLN (Global Location Number) issued by GS1: http://gepir.gs1.org/v32/xx/default.aspx?Lang=en-US/
• VAT numbers
• Other unique business identifiers

Why this happens:
The Receiver ID may not exist in the BaswareONE routing configuration, preventing the message from being delivered.

 

What to do:
Confirm that the Receiver ID is correct and configured in the BaswareONE network: If messages have been successfully sent to this Receiver ID in the past, verify whether the current message is of the same message type. Even if one message type is already configured, a new message type (for example, EINVOI, DESADV, ORDER, or another transaction type) may require additional setup adjustments.

If this is a new message type, refer to sections 2 or 3 of this article.

 

2. Check Routing Configuration

BaswareONE can operate as a point-to-point network.

Important:

Even if a receiver is connected to BaswareONE, they are not automatically connected to every sender and for every message type.

 

What to do:

Check if you previously sent this message type and/or to this receiver. If no connection is configured or it's the first time you're sending this message type, a billable Change Request may be required to establish the routing.

 

3. Confirm the Status of Any Ongoing Implementation Project

If an implementation project related to these messages is currently in progress:

• If the Solution Consultant has confirmed that the setup is deployed in Production, contact the Basware Support Team for further investigation.
• If the setup has not yet been deployed to Production, continue working with your Solution Consultant through the existing Service Request.

 

 

4. New Setup required

If the required routing or configuration has not been set up and there is no existing contractual agreement in place:

 

What to do:
Submit a billable Change Request to request the setup.

For instructions, see:
How to Raise a Change Request

 

 

5. Existing setup that is not working:

In case this you're encountering errors on an otherwise working connection, please contact Basware Support Team and raise a case for investigation.

 

If you have completed the checks outlined above and require further assistance, please contact our Basware Support Team  and provide the email received from our Monitoring team. 

We will be happy to assist you!