Skip to content

Error Handling

Three categories of errors can occur when using the eXite® Web Service API.

1. SOAP Faults

Returned when the SOAP envelope is malformed, required elements are missing, or credentials are invalid. The entire request is rejected — no invoices are processed.

Common causes:

  • Wrong SOAP version (must be SOAP 1.2)
  • Missing or malformed sessionRequest header
  • Invalid user ID or password
  • Missing required elements according to the WSDL schema
<soapenv:Fault>
  <soapenv:Code>
    <soapenv:Value>soapenv:Sender</soapenv:Value>
  </soapenv:Code>
  <soapenv:Reason>
    <soapenv:Text xml:lang="en">
      Invalid credentials or missing required header element.
    </soapenv:Text>
  </soapenv:Reason>
</soapenv:Fault>

2. Content Errors

Returned inside a successful SOAP response when a specific invoice could not be processed (e.g. recipient address not found). Other invoices in the same batch may still be accepted.

Rejected invoices are indicated by a processingError element inside their interchangeResponse, and are also counted in totals[@type="REJECTED"] in the response header.

<eXite:processingError>
  <eXite:errorSeverity>70</eXite:errorSeverity>
  <eXite:errorCode>RTG0004</eXite:errorCode>
  <eXite:errorDescription>Recipient address '9009999999999' not found.</eXite:errorDescription>
</eXite:processingError>
Field Description
errorSeverity Numeric severity level of the error
errorCode Machine-readable code (e.g. RTG0004)
errorDescription Human-readable message (language based on user's eXite® configuration)

3. Session Processing Codes

Returned in the sessionProcessing element of the response header. These indicate warnings about session state — they do not necessarily mean the request failed.

Code Applies to Description
UTIDREUSED send, receive The uniqueTransmissionID was already successfully processed. The response mirrors the original result — nothing is re-processed.
UTIDPROCESSING send, receive A previous request with the same ID is still in progress. Wait and retry with the same ID.
REFETCH receive, status More documents match the criteria than were returned due to session limits. Send another request to collect the remainder.
EXTENDLIMITS receive, status Session limits are too low to return even one document. Increase maxInterchangeReceive and/or maxSizeReceive. 
<eXite:sessionProcessing>
  <eXite:sessionProcessingInformation
    eXite:sessionProcessingInformationCode="REFETCH">
    Found too many matching interchanges. Please fetch again.
  </eXite:sessionProcessingInformation>
</eXite:sessionProcessing>