Issue with foreign currencies

XML and business rules
1

Since a few hours, all invoices containing a foreign currency have been returning this warning :

WARNING: [BR-53] [BR-53]-If the VAT accounting currency code (BT-6) is present, then the Invoice total VAT amount in accounting currency (BT-111) shall be provided

All of the invoices contain two repetitions of BT-111 TaxAmount in both currencies. The SDK validates the document correctly but not the API.

Is there a new way to report this tax segment ?

2

XML is missing Invoice Total VAT Amount in SAR (BT-111). Please add it in XML and warning will not appear. Look at sample XMLs in SDK for invoices in foreign currency .

3

The vat amount in SAR is already reported, this is the XML snippet :

<cac:TaxTotal>
        <cbc:TaxAmount currencyID="USD">174.99</cbc:TaxAmount>
        <cac:TaxSubtotal>
            <cbc:TaxableAmount currencyID="USD">1166.61</cbc:TaxableAmount>
            <cbc:TaxAmount currencyID="USD">174.99</cbc:TaxAmount>
            <cac:TaxCategory>
                <cbc:ID>S</cbc:ID>
                <cbc:Percent>15</cbc:Percent>
                <cac:TaxScheme>
                    <cbc:ID>VAT</cbc:ID>
                </cac:TaxScheme>
            </cac:TaxCategory>
        </cac:TaxSubtotal>
    </cac:TaxTotal>
    <cac:TaxTotal>
        <cbc:TaxAmount currencyID="SAR">656.21</cbc:TaxAmount>
    </cac:TaxTotal>
4

Try to shift positioning of the UBL tag for Tax Total in SAR. Bring it before the Tax Total tags in USD. Sometimes it could be due to positioning in XML. Check the positioning of tags in sample XML in SDK. If you still get warning for BR-53, please share XML through support emails sp_support@zatca.gov.sa and E-invoicing@zatca.gov.sa

5

Thank you for your response.
This comes as a surprise as the reason why we we had the USD first is because the SDK set it up that way(not sure if it had changed with new versions).

I assume there will be a lot of affected taxpayers, shoudnt this validation be handled from Zatca to allow both approaches ?

1 Like
6

@ohari yes team is working on this issue. Were you able to fix the warning by repositioning UBL tag? Or are you still getting warning?

7

Hi,
We have tried the following but the same warning persists :
<cac:TaxTotal> <cbc:TaxAmount currencyID="SAR">112625.55</cbc:TaxAmount> </cac:TaxTotal> <cac:TaxTotal> <cbc:TaxAmount currencyID="USD">30033.48</cbc:TaxAmount> <cac:TaxSubtotal> <cbc:TaxableAmount currencyID="USD">200223.2</cbc:TaxableAmount> <cbc:TaxAmount currencyID="USD">30033.48</cbc:TaxAmount> <cac:TaxCategory> <cbc:ID>S</cbc:ID> <cbc:Percent>15</cbc:Percent> <cac:TaxScheme> <cbc:ID>VAT</cbc:ID> </cac:TaxScheme> </cac:TaxCategory> </cac:TaxSubtotal> </cac:TaxTotal>

8

We are facing the same problem if you reach a solution please share it with us

9

I’m also facing the same problem should we continue with warning or wait till this warning resolved I also tried to shift the tag

10

@Jibran please continue. You can ignore the warning safely as it is a bug from ZATCA’s side. This will be fixed in coming release of bug fixes.

3 Likes
11

hello,
we are facing the exact issue.
tried shifting the position of the tax total but the same issue persists.

12

We also have the same issue,
below is the xml which we are sending, This warning didn’t used to be there before.

<cac:TaxTotal>
    <cbc:TaxAmount currencyID="SAR">3926.25</cbc:TaxAmount>
</cac:TaxTotal>
<cac:TaxTotal>
    <cbc:TaxAmount currencyID="USD">1047.00</cbc:TaxAmount>
    <cac:TaxSubtotal>
        <cbc:TaxableAmount currencyID="USD">6980.00</cbc:TaxableAmount>
        <cbc:TaxAmount currencyID="USD">1047.00</cbc:TaxAmount>
        <cac:TaxCategory>
            <cbc:ID>S</cbc:ID>
            <cbc:Percent>15.00</cbc:Percent>
            <cac:TaxScheme>
                <cbc:ID schemeID="">VAT</cbc:ID>
            </cac:TaxScheme>
        </cac:TaxCategory>
    </cac:TaxSubtotal>
</cac:TaxTotal>
13

Hi Team,
Is it mandatory to change the tag position?
Thanks

14

We are facing same issue. we checked the XML all tags populated as per SDK.
Can you safely ignore this issue @Ankit_Tiwari
Appreciate your response Sir