sap tax indicator for account assignment

How to configure SAP S4 HANA MM Tax in 7 Easy Steps

In this post we will configure SAP S4 HANA MM Tax in 7 Easy Steps

In this step we will see the difference between two types of SAP S4 HANA MM input tax -Jurisdiction Tax (Used in USA) & VAT (Used in EU)

In this step we will configure Tax Jurisdictions, FI Tax calculation Procedure, Tax code configuration & condition records creation

In this step we will configure all necessary parameters for automatic Tax code determination in PO and to bring the Tax amount from FI Tax calculation procedure to PO Price determination.

In this step we will look into the master data requirement

In this step we will test Automatic Tax ode determination, Tax amount calculation & flow of tax amount from Tax calculation procedure to PO Price determination.

In this step we will check accounting entries related to mm input tax at the time of Goods Receipt as well as at the time of invoice receipt.

In this step, various FAQs related to MM input tax are answered.

Input tax (Purchase Tax) is levied on all types of purchases and output tax (Sales Tax) is levied on all types of sales. Every country follow its own sales tax, purchase tax procedure.

Table of Contents

1. introduction to SAP MM Input Tax

At a broad level, there are two types of input tax

• Jurisdiction Tax (Used in US/Canada)
• Non- jurisdiction Tax (VAT in EU)

The choice of methods is a parameter in configuring the country’s global settings

To check the detail difference between Jurisdiction Tax (Used in USA) & VAT (Used in EU), Please check FAQ section at the end of the post. In this post we will look in detail into Jurisdiction Tax (Used in US/Canada) , which is more complex to configure compare to VAT configuration.

1.1. Jurisdiction Tax (Sales & Use Tax in USA)

With this method, you manually define the jurisdiction for every region in which you do business.

US follow Jurisdiction tax where tax authority is different for each area and tax authority decides tax percentage in that area.

There are three type of taxes in US

• A/P Sales Tax (MM input Tax)
• Self -Assessment Tax

Out of these three taxes US sales tax is MM input tax (Since we are purchaser, then our vendors collect and remit the collected tax to tax authorities) Hence it is classified as A/P MM input tax

Let,s configure & test A/P Sales Tax (MM input Tax) in the post.

1.1.1 A/P Sales Tax (MM input Tax) in SAP S4 HANA

If a transaction is happening within a state, then Sales tax is levied on the sale of taxable goods and is imposed by the tax authorities. If we are purchaser, then our vendor should collect and remit the collected tax to tax authorities.

As vendor is responsible to collect the A/P sales tax , so at the time of incoming invoice posting in Sap S4 HANA MM module , Vendor Account will be debited cost of material + Applicable A/P Sales tax (MM input Tax)

Credit side is handled two ways in SAP S4 HANA

1.1.1.1. Non-deductible A/P Sales tax (MM input Tax)

Non-deductible tax is not refunded or offsetting against liabilities by tax authorities , so this tax is treated as extra cost . Therefore, the non-deductible part of the tax is added to the stock value during the inventory posting.

1.1.1.2 Deductible A/P Sales tax (MM input Tax)

The deductible tax amount is not to be considered as a cost item of the procurement. This tax is levied within the state

In this post we will configure & test Non-deductible A/P Sales tax (MM input Tax) (1.1.1.1. in the above two)

Let,s start with FI related configuration first.

2. FI related Configuration of SAP S4 HANA MM Input Tax

Let,s first do FI related configuration for the MM input tax

2.1 Assign Tax Jurisdictions to Regions

First of all We need to assign our plant regions to the tax Jurisdictions. We have three plants for our car business. The three plants have the below regions

So we will assign the Jurisdictions to these regions

SPRO -> Cross-Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Tax Jurisdictions -> Using SAP Software -> Assign Tax Jurisdictions to Regions and Postal Codes -> Assign Tax Jurisdictions to Regions

2.2 Check Calculation Procedure

We have to first select a Tax schema to calculate the taxes. We will use SAP standard Tax schema w. Jurisdictions given by SAP

SPRO–> Financial Accounting –> Financial Accounting Global Settings –> Tax on Sales/Purchases –> Basic Settings –> Check Calculation Procedure

Note : The above given tax procedure is SAP standard. Mostly this serves the purpose. Generally 3 Tax condition types (S.No. 210, 220 & 230 in the above) are used to configure US input tax with Jurisdictions. See the details below

• A/P Sales Tax 1 Inv. with 6% for state (JP1I).
• A/P Sales Tax 2 Inv. with 1% for county (JP2I).
• A/P Sales Tax 3 Inv. with 1% for city Taxes (JP3I).

2.3 Assign Country/Region to Calculation Procedure

We need to assign our county “US” to the calculation procedure.

We will select the standard Tax scheme given in system for US and make the necessary changes for automatic determination of Tax code in the purchase orders & subsequently automatic tax calculation.

SPRO–> Financial Accounting –> Financial Accounting Global Settings –> Tax on Sales/Purchases –> Basic Settings –> Assign Country/Region to Calculation Procedure

2.4 Check and Change Settings for Tax Processing

Here we make the necessary specifications for posting taxes.

We have used NVV key for all our three tax level i.e. County level, City level, state level

2.5 Define Tax Codes for Sales and Purchases

We will configure below two input tax codes

• I0 – A/P Sales Tax, exempt
• I1 – A/P Sales Tax,taxable, distributed to line items

First Created I0 tax code for Massachusetts Tax Jurisdiction.

Press Enter and you will be presented below screen

Note : In the above screen do not fill any value (for both I0 & I1). just save it . This will get value automatically once we will maintain FV11 for our Condition Types given in Tax procedure. We will see this soon.

Complete the above for the below Combination

2.6 Condition Record Creation (FV11)

We need to create condition records for all the three Condition Types of Tax schema

Below Condition records will be created

• A/P Sales Tax 1 Inv. with 6% for state (JP1I) for all our 3 Tax Jurisdictions.
• A/P Sales Tax 2 Inv. with 1% for county (JP2I) for all our 3 Tax Jurisdictions.
• A/P Sales Tax 3 Inv. with 1% for city Taxes (JP3I) for all our 3 Tax Jurisdictions.

Once you maintained the above check the FTXP. It is maintained automatically

FI configuration related to S4 HANA MM Input tax is completed now.

Let,s check the MM configuration

3. MM Related Config. of SAP S4 HANA MM Input Tax

We need to do the below configuration in order to be able for the system to calculate the input tax automatically in the Purchase Oder

3.1 Condition Types Related to MM input Tax

3.1.1 condition type to bring tax amount in purchase order.

Tax amount is calculated in Tax schema. The system only calculates the non-deductible part of the tax. This amount should be regarded as an additional cost item of the procurement because the tax authorities do not refund this amount unlike the deductible part of the tax. Therefore, the non-deductible part of the tax is added to the stock value during the inventory posting. In the purchase order item, the non-deductible tax amount is saved in field EKPO-NAVNW

NAVS is the condition type which brings the value of the calculated tax to the PO field EKPO-NAVNW , if configured as per below configuration.

Note : Please ignore NAVM as we want to calculate and flow the tax to PO automatically. NAVM is the manual Condition type

3.1.2 Condition Type for Automatic Determination of Tax Code in PO

We will do configuration to determine the tax code automatically in the PO item. Please note that the tax code can be defaulted from the purchasing info record also in the purchase order item. We will create condition records through MEK1 to determine Tax code automatically in the PO.

During the determination via the condition technique an access sequence is assigned in the standard system of condition. Assign access sequence 0003 to our condition type MWVZ

Insert this condition type in our pricing procedure

Note : Please click HERE to check the configuration of price determination procedure.

3.1.3 Supporting Configuration for Automatic Tax Determination in PO

Below configuration is required for automatic tax code determination in PO in S4 HANA MM

3.1.3.1 Setting Tax Indicator for Material

Here we maintain the tax indicators for corresponding materials, specific to each destination country

We have created below three Tax indicator for our companies

3.1.3.2 Setting Tax Indicator for Plant

Here we maintain the tax indicators to assign to plants. This is done for each country of destination

For our three plants we have maintained below two tax indicators

3.1.3.3 Assigning Tax Indicators for Plant

Here we assign tax indicator to each of our three plants

To promote clean fuel, our Electric car plant is tax free

Maintain Tax indicator for plants as below

Out both IC Car plants are taxable

Configure Electric car plant as Tax exempt

3.1.3.4 Condition Record to determine Tax code automatically in PO

4. Master Data Requirements

In the material master purchasing view maintain the “Tax ind. f. mater” field

• Plant Tax indicator is coming from configuration as explained in the post.
• Import indicator logic is hard coded in SAP system.

5. Testing of MM Input Tax

Create a Purchase order for material “66” and vendor “PA01VEN03”

5.1 Automatic Tax Code Determination

System has correctly determined tax code as “I1” automatically as per the condition type values explained HERE.

To check how system has considered condition type & record to determine tax code automatically go to “Conditions” tab and click on “Analysis”

5.2 Tax Calculation Check

Click on Taxes on Invoice Tab

System has successfully calculated all the three taxes as required and total.

5.3 Flow of Tax amount from Tax Procedure to Pricing Procedure

Te amount of tax calculated shown in the previous step should flow to the PO Pricing procedure (under NAVS condition Type).

To check this click on conditions

6. Accounting Entries

Post The Goods Receipt. System will create the material document & corresponding FI Document. Similarly when the enter raise invoice so at the time of entering invoice , system will post the documents.

First we need to create a Purchase order to check the good receipt & invoice entry accounting entries.

Please note that this PO is different from the previous PO created at the Point 5.

We have created PO in the post Ultimate guide to configure S4 HANA MM-FI Integration . You can check the details of the PO price and it’s components HERE

In the PO created in the above link , Tax code is determined automatically as “I1”.

Tax calculations in PO (shown below)

This calculation of tax of USD 1.53 is brought into PO MM price determination procedure (Picture Below) from the FI Tax determination procedure (Picture Above) through condition NAVS to calculate the total value of material. This is fully explained in the post above

Below is the summary of full PO Price components. We will refer this to check the GR accounting entries as well as invoicing accounting entries

Tax Postings at Goods Receipt (GR)

Below is the FI document generated after posting the Goods Receipt (MIGO)

As expected & explained in the post, system has added the tax value to the material value and debited the cost to the inventory

Credit to the GR IR/IR account , which will be cleared at the time of invoicing.

Tax Postings at Invoice Receipt (IR)

Below is the FI document generated after posting the Invoice (MIRO)

Tax amount (including material value) is credited to vendor , as expected because vendor is responsible to collect A/P input tax.

7. FAQ on Input Tax

We get the offset of deductible tax amount so system does not include this in material landing price calculation. Example – PO pricing: Basic     –  USD 100                       Input Tax (16%)     –  USD 16   (Deductible) Since input tax is deductible, NAVS condition value in PO pricing will be 0.00. Goods Receipt:            Credit GR/IR Account    – USD 100              Debit Inventory Account   –  USD 100                 (Input tax is not loaded on Inventory due to deductible tax)   Invoice Receipt: Credit Vendor                    –  USD 116                      Debit GR/IR Account           –  USD 100                      Debit VAT Credit Pool Account   – USD 16

System calculate non-deductible tax and inserted the amount under non-deductible tax amount in PO. So Non-Deductible tax is included in landing price calculation and loaded on inventory i.e. included in material valuation as shown through FI document posting in the post.

* Sales tax is state level, plus thousands of local jurisdictions; VAT is only levied at the country level. * Sales tax is set by the US states – 45 of the 50 US states, plus DC, have a sales tax. However, and this is where sales tax gets very cluttered. Counties, cities and a number of other special jurisdictions (in excess of 12,000) have the right to set and charge tax on the transaction on top of the state sales tax. This makes the determination of the right sales tax rate a huge challenge as the business must determine exactly which jurisdictions’ taxes apply, and how to combine them. VAT is controlled and levied at the federal government only. * Huge diversity of sales tax rates, with frequent changes. While only three or fewer VAT rates and changes are rare. * Sales tax only on final consumer; VAT is collected on all transactions. This is where sales tax is ‘simple’. It is only charged on the final consumer (at the till or online checkout).

I n the Previous post, we have completed Business Partner & CVI related configuration. Please click on the above button to see the details

In the next post we will configure S4 HANA MM Pricing procedure .

Image Courtesy : Business vector created by macrovector – www.freepik.com

Join the discussion Cancel reply

Further reading.

All About Purchase Orders in SAP MM

How to Configure Logistics Invoice Verification in SAP S4 HANA

Ultimate guide to SAP S4 HANA MM Pricing Procedure

2 Minutes Guide to Create your First Material in S4 HANA

Ultimate guide to configure S4 HANA MM-FI Integration

How to activate Material Ledger in S4HANA in 5 Easy Steps

• SAP Tutorial

T163KS SAP table for – Assignment of Tax Indicator to Account Assignment Category

Table of Contents

Here we would like to draw your attention to T163KS table in SAP . As we know it is being mainly used with the SAP MM-PUR (Purchasing in MM) component which is coming under MM module (Material Management) . T163KS is a SAP standard transparent table used for storing Assignment of Tax Indicator to Account Assignment Category related data in SAP. It comes under the package ME.

Table T163KS technical data

SAP T163KS Table Fields

Here is the details of each fields in this table.You can find the discription, data type and assigned lenth of each of the fields in T163KS table.

• KNTTP : Account assignment category Its a key field. Its data type is C (Character String) with field length 1
• LAND1 : Country Key Its a key field. Its data type is C (Character String) with field length 3

T163KS related tables

• T161B : Default Business Transaction Type for Import
• EINE : Purchasing Info Record: Purchasing Organization Data
• T163X : “Zombie” T163X
• EKKO : Purchasing Document Header
• TMKG : Group of Conditions Table
• TMKW1T : Taxes: Plant (Purchasing)
• EKRS : ERS Procedure: Goods (Merchandise) Movements to be Invoiced
• EKBE_SC : Component Consumption History for Subcontracting
• TEBOT : Volume Rebate Groups (Purchasing): Texts
• T163E : Confirmation Categories
• EKBE_MA : History of Purchasing Document at Account Assignment Level
• TBSGT : Purchasing Documents: Reasons for Ordering: Texts
• T161E : Release Codes
• EKBE_SRV_SUM : Totals History for SRV Documents
• T161PH : Activate Park and hold in Purchasing documents
• T024W : Valid Purchasing Organizations for Plant
• TMKM1 : Taxes: Materials (Purchasing)
• EKCPH : Purchasing Contract Commitment Plan Header Information
• TMSRM_EHTYP : SRM Hierarchy Types
• EKAB : Release Documentation

T163KS related t.ransaction codes under SAP package ME

• ME5R : Archived Purchase Requisitions
• OMJP : Batch Input: Consignment Info Recs.
• MN25 : Change Message: Shipping Notif.
• MN10 : Create Message: Schd. Agmt. Schedule
• ME35L : Release Scheduling Agreement
• MKVZ : List of Vendors: Purchasing
• ME3L : Outline Agreements per Vendor
• ME31K : Create Contract
• ME80A : Purchasing Reporting: RFQs
• MEKX : Transport Condition Types Purchasing
• ME4L : RFQs by Vendor
• ME08 : Send Source List
• ME38 : Maintain Sched. Agreement Schedule
• MN12 : Displ. Message: Schd. Agmt. Schedule
• MEK3 : Display Conditions (Purchasing)
• ME33K : Display Contract
• ME33 : Display Outline Agreement
• ME23N : Display Purchase Order
• M_LA : Purchasing: Condition List
• ME3N : Outline Agreements by Agreement No.

Related References

• SAP Purchasing in MM transaction codes Full List
• SAP Purchasing in MM (MM-PUR) module tables list
• SAP Purchasing in MM Component Tutorial
• SAP MM Module tutorial & PDF training materials

Related Tutorials

T163A table in SAP MM (Purchasing in MM) module. This tables is used for storing data of Check Item Category/Account...

T163RCT table in SAP MM (Purchasing in MM) module. This tables is used for storing data of Description of Reason...

T163RC table in SAP MM (Purchasing in MM) module. This tables is used for storing data of Reason for Final...

EKBEH_MA table in SAP MM (Purchasing in MM) module. This tables is used for storing data of Removed PO History...

T163I table in SAP MM (Purchasing in MM) module. This tables is used for storing data of Texts for Account...

T162K table in SAP MM (Purchasing in MM) module. This tables is used for storing data of Field Selection, Account...

EKCPA table in SAP MM (Purchasing in MM) module. This tables is used for storing data of Purchasing Contract Commitment...

What is ERP? What is SAP? ERP vs CRM vs SAP SAP Certification Help & Details SAP R3 Architecture SAP Functional Modules (Solutions) Overview List of SAP solutions & software products SAP software capabilities and benefits

Most Popular

SAP SD tcodes SAP HR Tables & Infotypes SAP SRM Tutorial SAP Workflow Tutorial SAP Business One SAP EWM What is SAP transaction code ? What is Tables in SAP?

SAP Analytics & Administration

SAP Basis Administration SAP HANA SAP Crystal Reports SAP Lumira SAP Predictive Analysis SAP Enterprise Performance Management SAP Fiori SAP BW

Useful References

SAP Interview Questions SAP Articles & References Transaction Codes Tables

TAXIK1 Field in SAP | Tax Indicator: Account Assignment (Purchasing) Data Element using tables

TAXIK1 is a data element in SAP used for storing Tax Indicator: Account Assignment (Purchasing) data in table fields. Here is it basic details and list of tables using this TAXIK1 field in SAP .

• Data Element : TAXIK1
• Description : Tax Indicator: Account Assignment (Purchasing)
• Data Type :CHAR

Here is some free PDF files that you can download free for your reference. Download Now

Definitions

SAP is the short form of Systems, Applications & Products in Data Processing. It is one of the largest business process related software. This software focused on business processes on ERP & CRM.

Like most other software, SAP also using database tables to store the data. In SAP thousands of tables are there to store different data. A table contains several fields and some of the fields will be key fields.

List of Tables using TAXIK1 Field

Latest Table Searches

Popular table searches.

TAXIK is a standard field within SAP Table A087 that stores Tax Indicator: Account Assignment (Purchasing) information. Below is the list of attribute values for the TAXIK field including its length, data type, description text, associated data element, search help etc... You could also view this information on your SAP system if you enter the table name A087 or data type TAXIK into the relevant SAP transactions such as SE11 or SE80 etc. Also check out the Contributions section below to add and view useful hints, tips and screen shots specific to this SAP table field.

Key data for field A087-TAXIK

Below is everything you need to know about the SAP taxik field in table A087, Including example ABAP code to show you how to select data, attributes/info such as that it is a Key Field of table A087 and that it stores Tax Indicator: Account Assignment (Purchasing)

Attributes of TAXIK field in SAP Table A087

Below is the field in the previous position and the next position of table A087

Comments on this SAP object

2784104 - Error message FF856 is issued when you post a document

When you post a document with tax codes, the following error message is issued. --------------------------------------------------------- Message ID: FF856 Tax indicator not assigned to account and country ---------------------------------------------------------

Environment

• Financial Accounting (FI)
• SAP enhancement package for SAP ERP
• SAP enhancement package for SAP ERP, version for SAP HANA
• SAP S/4HANA Finance
• SAP S/4HANA

FF856; Tax indicator not assigned to account and country; Tax code; Assign Country and Tax Code to G/L Accounts; VC_T007_GL_ACC; 2362557; 2445072; Country. , KBA , FI-GL-GL-F , Value Added Tax (VAT) , How To

About this page

Search for additional results.

Visit SAP Support Portal's SAP Notes and KBA Search .

Privacy | Terms of use | Legal Disclosure | Copyright | Trademark