Openbravo Issue Tracking System - Localization Pack: Spain
View Issue Details
0025828Localization Pack: SpainAEAT 347public2014-02-25 13:012014-02-26 16:16
maite 
jonalegriaesarte 
urgentmajoralways
newopen 
5
 
 
0025828: Wrong amount in 347 when working with tax defined as "alternate tax base amount"
Wrong amount in 347 when working with tax defined as "alternate tax base amount"
0. Access Tax Rate window and define tax "Adquisiciones IVA 21%" as Base Amount="Alternate Tax Base Amount"
1. Register Purchase Invoice for any BP, add line with qty=1 and unit price= 6781.22 and tax= "Adquisiciones IVA 21%"
2. Edit "Alternate Taxable Amount" field to set 6781.21
3. Process invoice and realize that total is calculated to 8205.27
4. Post invoice
5. Run 347 report and realize that amount set for that BP is 8205.26 (instead of 8205.27)
No tags attached.
Issue History
2014-02-25 13:01maiteNew Issue
2014-02-25 13:01maiteAssigned To => jonalegriaesarte
2014-02-25 13:01maiteIssue Monitored: networkb
2014-02-25 13:14PracticsIssue Monitored: Practics
2014-02-25 14:27vmromanosNote Added: 0064567
2014-02-26 16:16vmromanosNote Added: 0064623
2014-02-26 16:16vmromanosTypedefect => design defect

Notes
(0064567)
vmromanos   
2014-02-25 14:27   
I'm not sure whether this is a bug or not:

1. The tax rate configuration provided by OB has been manually changed by the user. The fiscal reports provided by OB must always work with the provided configuration and source code. Any modification must be done under the client's responsibility and may not be supported by OB. This is clearly the case, so we should reject this issue.

2. The reports take amounts related to tax rates: tax parameters linked to report parameters.
Inside the C_InvoiceTax (Invoice | Tax) we have the list of tax rates with the tax amount and taxable amount introduced by the user as the alternative taxable amount. This value is OK, and it's properly taken by the 347 report.

3. The invoice's grand total amount doesn't correspond to the sum of tax amount + alternative taxable amount, but remember that the 347 takes into account the tax amounts and not the invoice's grand total amount. For example, what should happen in case an invoice has two different tax rates: one of them with an alternative taxable amount (exactly the same scenario reported), and another tax rate that shouldn't be declared into the 347? That's why we can't trust into the invoice's grand total amount.

4. Probably the best way to work with this scenario is to manually add a "compensation" line with the rounding difference. Alternatively, the pricelist including taxes functionality may also work.
(0064623)
vmromanos   
2014-02-26 16:16   
Changed to design defect.

Initially we don't consider this is as a bug, we will take this scenario into account for a further 347 report refactor.