EDI Error Sent - Notification

The EDI-Error Sent notification informs you about the success or failure of a request made to Accounting as a Service. It is primarily used to notify clients whether an action (such as creating an order, invoice, or return) was successfully processed or if errors occurred during validation. These notifications ensure that you are immediately aware of any issues, allowing you to address them before the request is finalized.

Key benefits for you

This notification helps you:

• Monitor the processing status of key transactions (e.g., orders, invoices, returns).
• Detect issues early, allowing for swift resolution and reprocessing.
• Ensure accurate data flow and prevent delays in financial operations.

Setting up the notification

To register to this notification, please look in the general notifications-page using accounting/EDIErrorSent

You need to have a system in place to monitor these notifications. When an error is detected:

• Inform the responsible team to correct the data in your system.
• Ensure the data is resubmitted with the same transaction ID.
• If no response is received within the expected timeframe (up to 24 hours), reach out to the Accounting as a Service Team to investigate further.

Technical Details

Purpose:

The EDI-Error Sent notification is triggered when a request (e.g., create order, create invoice) fails validation or cannot be processed by Accounting as a Service. It provides detailed information about the error, allowing you to identify and correct issues quickly.

Trigger Events:

The notification can be triggered by any of the following:

• Submitting an order, invoice, goodwill, or return with incomplete or invalid data.
• Submitting an action (e.g., invoice) before the necessary preceding steps (e.g., order creation) have been confirmed.

Example:

The notification provides details about the error in a structured JSON format. Below is a typical payload:

{
  "parameters": {
    "requestType": "GET_ORDER",
    "transactionId": "0a6b660174a3306898a924639688dffb",
    "details": {
      "orderNo": "ORDPL8100235158",
      "result": "ERROR_IN_FILE",
      "errorDetails": [
        {
          "fieldName": "LINEITEMSTATUS",
          "ErrorDescription": "Field LINEITEMSTATUS must not be empty."
        },
        {
          "fieldName": "BILLTOLANGUAGECODE",
          "providedValue": "PL",
          "ErrorDescription": "The content of field BILLTOLANGUAGECODE may only consist of lower case letters."
        }
      ]
    }
  },
  "type": "accounting/EDIErrorSent"
}

Field Descriptions

Please look here for the details of the EDI-Error Sent Notification.

Response Handling

• Steps for Technical Users:

  • Review the error details provided in the notification payload.
  • Correct the data in the relevant request (e.g., order, invoice).
  • Resend the corrected data using the same transaction ID to avoid duplicate entries.
  • If multiple errors are detected, ensure all issues are resolved before resubmitting.

• Retry Logic:

  • Requests should be retried until a positive confirmation is received. If no response is received within 24 hours, reach out to the Accounting as a Service Team to investigate.
  • Ensure your system handles retries appropriately to avoid overwhelming the API with duplicate requests.

Troubleshooting Tips

• Ensure all required fields are filled in according to the API documentation.
• Verify that data types and formats match the expected values.
• Follow the correct sequence of actions (e.g., create order first, then create invoice).