201: Created
status code. In this case, the document Status field should be set to TRANSMITTED
.
202: Accepted
status code. In this case, the document Status field should be set to NO_ACTION
. Possible reason for Procuros not to forward documents:
422: Validation Error
or a 400: Bad Request
status code.
In this case, the document Status field should NOT be set to make sure the document will be retried the next time you are processing outgoing transactions. The response from Procuros will contain a link to view the error on the Procuros Portal. You can optionally add this link to a “Error URL” field attached to the document you were trying to send, giving users easy access to view and resolve errors.
TRANSMITTED
or NO_ACTION
.
You should instead retry the document until it is able to be handled by Procuros. This should occur by the ERP administrators making changes to the document to resolve why it was not valid.
This is why you must report any errors documents have via the API, in order for Procuros to notify the customer.