Qualitative Response (Notification)

Key benefits for you

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.

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.

Note: All requests provided by you receive a response via this notification. It must be either a confirmation or an error. In any case, a response can be expected. If you do not receive a response, please reach out, so that we can investigate.

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

Trigger Events:

The notification can be triggered by any of the following:

• Invalid Data: sending create order, create invoice, add goodwill, or return order with incomplete or invalid data.
• Wrong order of requests: Submitting an action (e.g., invoice) in the wrong order (before the necessary preceding steps (e.g., order creation) have been confirmed.)
• Success: Submission was successfully processed by Riverty

Example for an error:

{
  "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"
}

Example for a confirmation:

{
  "parameters": {
    "requestType": "GET_BOOKING_CONFIRMATION",
    "transactionId": "5b4b345257893a0f8d78367269017aef0",
    "details": {
      "orderNo": "ORDNL0023996833",
      "result": "OK",
      "errorDetails": [
        {
          "ErrorDescription": "The request was successfully validated."
        }
      ]
    }
  },
  "type": "accounting/EDIErrorSent"
}

Field description

Please look here for the details of the Qualitative Response Notification.

• transactionId: This is the transaction ID you used when sending in the request. The transaction ID must be stored in your system as Accounting as a Service will reference to this ID
• requestType: This defines the request type you have sent in:
  • GET_ORDER: Create order request
  • GET_GOODWILL: Add goodwill request
  • GET_BOOKING_CONFIRMATION: Create invoice request
  • GET_RETURN: Return order request
  • GET_INVOICE_UPDATE: Update invoice request
  • GET_CANCELLATION: Cancel order request