How receiving feedback works
When sending invoices through InExchange several validation steps are passed which touch on both the document and its content as well as the path its trying to take to the document recipient. This is an asynchronous process which might fail at any given step. These failures most often are relevant for the sender parties and can be necessary in order to know how to correct and resend documents.
InExchange can provide this feedback in several ways with the possibility for customizations in delivery intervals, delivery methods as well as failure type categories.
Feedback recipients
Feedback can be setup to be sent to different parties in the document transaction and is pre-agreed on and entirely up to the integrator.
Document issuer
This is the party that is the issuer of the document.
Data sender
Usually the data sender represents a party (Such as a ERP system provider) that acts on behalf of a document issuer to send the document to InExchange. If the integrator is of such that they act on their own behalf with the API then they are the data sender.
Feedback delivery method
Feedback can be setup to be obtained/available in different ways and is pre-agreed on and entirely up to the integrator.
API
By default issues are obtained/available in the API in the form of document status Stopped. As this can be customized there is an option to opt-out of this setting which means that document statuses wont be updated in the API to Stopped when issues occur.
File
Its also possible to get feedback actively pushed via different means of transport such as FTP and HTTP. This is done by serializing the feedback in either a file format that is provided by InExchange or in a custom file format.
The most common and generic way of receiving feedback is by email. This method allows for additional settings such as time based digets or number of emails to digest. This means you can receive feedback in batches instead of one by one for each feedback.
Feedback categories
There are several categories of feedback that describe different types of events and enable a more granular handling of feedback.
AcceptedDocument
Feedback of this type is an acknowledgement that the document has been recived and processed successfully.
DuplicateIncomingData
Feedback of this type indicate that the document is a duplicate and that the same document already has been processed.
DeliveredDocument
Feedback of this type indicate that the document successfully has been delivered to the recipient.
DocumentBatchTechnicalError
Feedback of this type indicate that the document contains technical errors which is doesnt make it possible to convert successfully.
StoppedDocument
Feedback of this type indicate that the document has failed validations. This may be caused by invalid/incorrect business data provided in the document or in rare cases by manual intervention from InExchange Support staff.