Errors
      Back to home
      1. Knowledgebase
      2. Troubleshooting
      3. Errors

      Warning: "The Invoice Amount Tolerance is Too High in Dooap and D365"

      If the invoice has this warning entry when transferring the invoice from Dooap, how to proceed?

       

      This warning is related to PO invoice discrepancies.

      tolerance too high

       

      When transferring invoice data from Dooap to D365/AX2012, Dooap performs a reconciliation to ensure the invoice is transferred correctly.

      Warning message "The invoice amount tolerance is too high in Dooap and D365" in Dooap indicates that some information did not transfer correctly between Dooap and D365/AX2012.

      In such cases, Dooap prevents the invoice from being posted and places it in the pending invoices table for manual review and correction.

      Cause


      The specific cause can vary, but it is often related to outdated purchase order (PO) data or unsupported combinations of matching criteria, such as tax codes and certain miscellaneous charges.

       

      Resolving the Issue

       

      When encountering this situation, it is crucial not to post the invoice from the pending invoices table without first verifying that the data has transferred correctly.

      If discrepancies are found, there are two options for resolving the issue:

      1. Correct the issue in Dooap using updated PO data:

        • Delete the pending invoice in D365/AX2012.
        • Return the invoice in Dooap to the Approved status from the transfer batch.
        • Refresh the PO information by clicking "Fetch Lines" on the invoice.
        • Match the invoice with the updated data and re-transfer it.

      2. Manual correction in D365/AX2012:

        • If the issue persists, the invoice can be manually corrected in the pending invoices table in D365/AX2012 before posting.
        • Please also send the invoice details to support@dooap.com for further investigation into the root cause.

       

      For more detailed instructions, please refer to the articles: