How to Process Rejections and Errors

The Tax Authority rejects a transaction when the record doesn’t exist in the authority database.

Follow these steps:

1. Investigate and resolve the issue on the transaction if this is possible.

   For example, the third party Taxpayer ID may be invalid or null.

   Note: (*) If the Taxpayer ID doesn’t exist in the Tax Agency portal, then resend in 24 hours and if rejected again then assign ID Type 07 to the third party. This action enforces non-validation of the taxpayer ID by the Tax Agency.
2. Confirmation process sets the transaction status as ‘R’ (Ready) for this transaction so that it is ready for resubmission. Depending on the error, correction may be necessary on the invoice itself or setup, such as incomplete third-party information. After the corrections are done, you can resubmit the transaction in the Addition mode. If the confirmation status is ‘AE’ (Accepted with errors), the confirmation process updates transaction status as ‘M’ (Modified), making this transaction eligible for selection by a Modification run. These features help you to manage changes, for example a high level setup update is needed when a high volume of transactions were rejected due to a common problem.
   Note: Correct the reason for not accepting then the invoice is picked up in the next submission unless you manually changes the Transaction Status to, for example, ‘O’ (On Hold).
3. If the issue can't be corrected, take action based on each individual case.

   For example, if an AR transaction is rejected and the rejection code is indicating that the record already exists then you have unintentionally changed the submission status from ‘S’ (Submitted) to ‘R’ (Ready). The duplication of the record occurred and no further reporting is required.