Provide own tax amount?

[mhupf]

Is it possible to set the tax amounts yourself instead of relying that the automatic calculation fits all your purposes?

<ram:ApplicableSupplyChainTradeSettlement> <ram:ApplicableTradeTax> <ram:CalculatedAmount currencyID="EUR">31.35</ram:CalculatedAmount>

[jstaerk]

Currently only by specifying the complete xml (https://mustangproject.org/use/#custom), why do you need it?

[mhupf]

Thanks for the quick response. I would like to avoid my own XML creation but let's see.

Reasons for giving my own values:

1. In Germany there are two ways to calculate the VAT (Called horizontal and vertical. Don't know if there are international phrases for them). Currently Mustang seems to go the vertical way, but I need the horizontal one (+Maybe the vertical one in the future, too).
2. I would like to avoid calculating and rounding these values on multiple instances to minimal the risk of anomalies.

[mhupf]

Sorry for pushing this issue. Is there any opinion on this topic and is it likely to be implemented in future versions?

[jstaerk]

I think you may refer to the german "Bruttorechnung": In that case my question would be if it is covered by EN16931-1 at all and where.

Note for myself: "Impossible amounts" are 20,20 and 7,99 with 19% VAT.

[mhupf]

That's another interesting case, but not what I meant initially. Here's an example:

Horizontal:

Posten  Einzelpreis    MwSt (19%)    Gesamt 
  #1           0.99          0.19      1.18 
  #2           0.99        + 0.19      1.18 
  #3           0.99        + 0.19      1.18 
=========================================== 
               2.97        = 0.57      3.54

Vertical:

Posten  Einzelpreis    MwSt (19%)    Gesamt 
  #1           0.99                    1.18 
  #2           0.99                    1.18 
  #3           0.99                    1.18 
=========================================== 
               2.97 * 0.19 = 0.56      3.53

I still think the Zugferd XML Creator is not the right place to calculate and round tax related numbers. Atleast an override should be possible in my opinion.

[jstaerk]

So far I was of the impression that only vertical is correct? In the end you anyway have to specify the net amount by tax rate and the calculated amount and 0,57 would look strange, wouldn't it? Does it validate?

[BoHamburg]

Fehlermeldung (Rechenfehler) bei Nutzung Rounding amount (BT-114) #239

I tested it again, only Mustang has problems with the calculation (probably due to rounding * 100 and / 100 as indicated in the error message) and issues an error message!

If Mustang would calculate exactly as in the documentation (Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) -Paid amount (BT-113) + Rounding amount (BT-114)) - it should do not give an error message!

Other online auditors do this correct, including the testing software for XRechnung.

[hkucharek-pgt]

I ran into the same problem of differences between tax amounts we compute for our invoices and amounts we get from mustang when we just give prices and tax rate. Looking at the code, it seems one possibility would be "dumb" calculators which just take amounts given and do no own calculations (except summing up line amounts). Are there any plans to do such things?

[jstaerk]

Please note that I do not know of any case where my calculation is wrong (please open a ticket if it is) and there should be no reason why anyone would like to provide his/her own calculation, as it is described very clearly in EN16931-1 (available for free at your local CEN provider, in german e.g. at https://www.beuth.de/en/standard/din-en-16931-1/314992770) how the calculations work. Sorry but this is a wontfix.

I would also like to point out that certain requirements (Bruttorechnung/gross invoice) may not be covered at all in the e-invoicing context, I guess that's just the borderline where one would talk about e-receipts instead of e-invoices.

[pgtaboada]

This makes it impossible for us to use Mustang.
We are obliged to ensure XML and PDF have the same data.

How are you folks dealing with this situation?

[jstaerk]

please also note that you can supply your own XML although I would strongly advise against supplying invalid XML