The reason for the following idea is to request support to solve the error in the XML of the stamp of the payment complement, field equivalenciaDR.
Based on the investigation, the issue appears to be directly related to the field being pre-configured in the code to display only 6 decimal places. However, for compliance with SAT requirements, it is necessary to display 10 decimal places.
10 decimals for EquivalenciaDR attributeAccording to what was stipulated by the SAT on January 7, 2023 regarding the Payment Receipt Complement 2.0, the EquivalenceDR attribute will have 10 decimals, as long as the payment currency is different from the currency of the invoice documents (Income) associated to it.
En las validaciones del atributo Monto:
When the currency registered in the Related Document is the same as that of the Payment, the sum of the values registered in the node RelatedDocument, attribute ImpPaid, must be less than or equal to the value of the attribute Amount. Since they are the same currencies, the variation margins (lower and upper limits) are not calculated due to rounding.
When the currency registered in the Related Document is different from that of the Payment, first calculate the variation margin, that is, calculate the lower and upper limits of each amount paid and then convert the amounts paid (dividing ImpPaid/EquivalenceDR) of each Related Document to the currency of payment, followed by validating that the sum of the values registered in the node RelatedDocument, attribute ImpPaid, must be less than or equal to the value of the attribute Amount.
Comments
Bug 565342
Category: Financial Management
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team