Formulas - AR

Purpose

The purpose of this page is to clarify the customizing of Pricing Procedures Formulas 333 and 334 in Localization Argentina.

Overview

The following section will explain the step-by-step of Formulas in Argentina, which is the first part of the process of configuration, that is preceded by Basic Customizing of Pricing Procedure - ARand Different Taxes - AR. Use transaction VOFM for the customizing.

Formula 333

Before calling Formula 333, the customer is checked for the tax categories that are maintained for him along with the exemption rate and its validity. These details are stored in table KNAT. If a tax category has some exemptions, then the condition type for it will consider these details in this formula. Firstly, table T007C is checked to get the details of grouped tax codes. Go to SPRO > Financial Accounting (New) > Financial Accounting Basic Settings (New) > Tax On Sales / Purchases > Basic Settings > Argentina > Tax Categories > Maintain Tax Categories.

Account type considered is always 'D' (customer). Example of tax category is IVA which has condition types J1AU and the reference condition type is J1AX. This is a VAT condition and so the flag 'is VAT like' is set.

 

Secondly, read the entries in table J_1ATXMIN for minimum amount maintained for Argentina accounting key.

Details of table J_1ATXMIN:

In this table, you maintain the minimum amount for a particular account key. If the minimum amount threshold is not reached, then that amount is not posted to G/L. Customization for this is in SPRO > Financial Accounting > Financial Accounting Basic Settings > Tax On Sales / Purchases > Basic Settings > Argentina > Maintain Minimum Amounts Per Processing Key.

Example: J1F account has a minimum amount set to ARS 21,30. In the pricing procedure, we have the condition types and from there we pick the account key. If that account key is J1F, then if the calculated amount is less than ARS 22,30, then it is not posted to G/L. They are converted to ARS 0,00.

- Read the internal table with pricing procedure detail for the reference conditions found in T007C.

- Pass all the condition base values to another in ternal table.

- Modify limit for for credit memos: If in th e preceding document (i.e., billing document) condition with same posting key has a non-zero value, set the lower limit to zero. Again, if preceding document exists and taxes are not explicitly to be redetermined, take over value from preceding document.

- Table T007C is read to get the reference condition and tax group, so read the customer (KNAT) to get the rates for exemptions maintained. Then check the exemption period.

- Apply exemption to reference condition of entire document and compare to limit.

- Fetching all the distinct tax rates in order to find the rounding differences.

- Loop for each tax rate. Loop on all reference conditions of same document to determine sum. Sum up base value of the reference condition and get the tax rate considering exemption rate. Calculate taxes for each item and sum up the calculated tax amount .

- Take over base value from reference condition and calculate actual.

- Rounding difference has to be added after considering all items.

- Rounding works when the rate is same for same tax type. Difference in amount is adjusted with highest tax amount.

- Field “Reason for Zero VAT” available at item level in sales and billing documents.

- Pricing has to be set up in a way that a non-initial value of this field would bring the VAT amount down to zero.

Finally, consider the functions and details shown below:

- Rounding: This is considered on the header level, once all the condition rates of all items are summed and if there is any adjustments to be done, and then it is done on the reference condition. Rounding works when rate and tax type are same. Difference is adjusted with the highest tax amount (considering all items).

- Exemptions: These are considered from the customer master as we know the exemption rates applicable for a particular customer. Accordingly the taxes are calculated.

- Minimum amount: It is again maintained in table against accounting key. If suppose for VAT, the minimum amount maintained is ARS 21,30. Then if after calculation in document, VAT is less than this particular minimum amount, the value is set to ARS 0,00. Thus for any condition, if the final amount is less than the minimum amount, the value is set to zero.

- In case of VAT Perception (J1AQ): Full VAT perception is calculated in condition J1AP, which is the previous condition. This formula applies partial exemptions if present the customer is ‘subjected to’ via the tax category associated with condition J1AP. It is checked whether the document total value after application of the exemption exceeds the lower limit defined by the field 'low er_limit'.

- In case of Gross income perception (J1X1, J1X2, and J1X3): The full gross income perceptions are calculated in conditions J1A1, J1A2 and J1A3. This formula applies partial exemptions if present the customer is subjected to via the tax category associated with conditions J1A1, J1A2, J1A3.

- In case of partial VAT exemption (J1AX): This case is very seldom. The full VAT is calculated in condition J1AX. This formula applies if the VAT condition J1AU applies.

Formula 334:

The Formula 334 is used for calculating GI perception in SD. The SAP Note 1342470 contains the details of the customizing.

Considerations on Argentina's Pricing Procedures:

Formulas 333 and 331 validate that the perceptions (VAT perception / IG perceptions) is calculated at header level, is equal or bigger than ARS 21,30. Then it should be charged and also if the customer has exemptions. Routines 81 and 82, assures that the date to be consider to calculate taxes is the billing date for all documents and for referenced Credit or Debit Memos, it should be the date of the original document.

Related Content

Related Documents

Related Notes/KBA

Fonte: https://wiki.scn.sap.com/wiki/display/LOCLA/Formulas+-+AR