Mauritius Country Tax procedure

Hi Friends,
I need to assign tax calculation procedure for a new company code I have created. I want to know the tax calculation procdure for Mauritius Country.
Please help .
Thanks,
Hani

You need to define Tax Procedure based on the applicable rates in SPRO and then got ot Transaction Code -OBBG - Assign Country to calculation procedure
Regards
Jaydip

Similar Messages

Relation between Tax procedure and Pricing procedure

Dear All,
I would like to get more clarity on Tax procedure, Pricing procedure.
a) Why do we have Tax procedure and assigned to Country?
b) If the tax procedure has been created and assigned to Country-IN (in FI module), then why do we need to create pricing procedure with same condition type for purchasing in MM module? We are even creating lot of pricing procedure for Sales in SD module.
Regards
Manivannan R

Hi
Tax
During SD document transactions, tax calculation procedure TAXUSX is only relevant to determine the tax liability accounts for output sales tax. Notice that in pricing procedure RVAXUS, the condition types XR1 - XR6 carry the tax rates and tax amounts - resulted from the external tax system calculation - which is posted to tax G/L accounts. However, the tax accounts are not specified in the pricing procedure but rather in the tax calculation procedure.
Tax codes are the link between pricing procedure and tax calculation procedure.
Pricing
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
Example
Example of a Pricing Procedure
If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
Pricing Procedures in the R/3 System
The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
Creating and Maintaining Pricing Procedures
You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
To reach the pricing procedure screen from SD Customizing:
1. Choose Basic Functions
2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

MM Pricing procedure VS Tax procedure

Hi Gurus,
I have checked many thread here , but still can not find the answer.
Tax calculation procedure basically calculate the tax amount based on condition recaord maintained
(dor tis corresponding Condition type).
But we also can maintain Condition record for the condition type NAVS (pricing procedure) that bring tax amout into the pricing procedure of PO).
My question is why do we have to maintain Tax procedure as well as pricing procedure (regarding tax of course ).
Cheers Guys
Julien

HI
Basically why we have taxing procedure is that its always country specific that means it can be any vendor selling any material but he has to follow some government regualations whcih is what will be given in the taxing procedure that sholuld be the same for all customers it will be different if the customer is foreign.
the pricing procedure is where we carry out pricing that is customer specific here we can have different prices for different customers depending on what he buys and ETC.
hope this clarifies .
Regards
Vignesh

Questions about CIN tax procedure choice and pricing schemas

Hi all,
I have to implement SAP on a Indian company and I'm verifying all particularity about this country (in particular tax procedures and the great number of differents tax conditions used).
I have two questions about tax procedures and pricing schemas. Every feedback about thse points will be appreciated.
a) To choose tax procedure TAXINN or TAXINJ which are the elements that I have to consider?
I have read lot of documentation about CIN implementation and Iu2019m oriented to choose TAXINN schema, but If possible I would to understand better which are on behalf of one choice or another.
b) To define pricing schemas for India, after check with local users and using examples of documents (in particular tax invoice) actually produced, I have understood that taxes have to be applied on amount defined starting from price list, minus discounts recognized to customer plus surcharges eventually to bill (packing, transport, etc.).
Itu2019s correct for any type of taxes that tax amount is calculated on u201Cnet valueu201D defined at item level or there are exceptions to this rule?
Thanks in advance
Gianpaolo

hi,
this is to inform you that,
a) About point 1 I know the difference between the 2 tax procedures (conditions or formulas). I also have read in others post in the FORUM that TAXINN is preferable. So I would to understand which are the advantages to choose instead TAXINJ. There are particular reasons or it'a only an alternative customizing setting?
a.a. for give for posting the link : plese give me the advantages of TAXINJ and TAXINN
CIN - TAXINN and TAXINJ
b) About point 2, to define which value has to be used as base amount to calculate taxes isn't a choice, but is defined depending by fiscal requirement of the country, in this case India fiscal requirement. I know that, as Lakshmipathi
write as answer on my question, exception could be, but it was important for me to understand if I have understood correctly the sequence of the pricing condition in the schema in "normal" situation.
b.b. you can create your own pricing procedure for this and go ahead.
hope this clears your issue.
balajia

Pricing Procedure vs Tax Procedure

Dear all,
The scenario is as follows
My company purchase material from a trading company which imports the materials from other countries.
In PO we have maintained import pricing procedure so that we can take the duties paid by trading company during import.
We pay duties to the trading company.
Taxes are also involved in this.
I have created a pricing procedure for this seperate where there is a line with 'condition value' = total of
[ Net price of materialCustoms dutyCVD+ECS on CVD + SEC ECS on CVD + AED]
Now we all know tax should be calculated on this total amount.
In normal case the Net price will come as the base price for tax calculation which is here wrong.
I want this total amount to be the base amount for tax calculation in tax procedure.
What i need to assign in the pricing procedure against this 'total' so that it is taken as base amount for tax calculation
How to do this?
sapmmlearner

Hello,
As per your said scenario:
My company purchase material from a trading company which imports the materials from other countries.
In PO we have maintained import pricing procedure so that we can take the duties paid by trading company during import.
We pay duties to the trading company.
Taxes are also involved in this.
I have created a pricing procedure for this seperate where there is a line with 'condition value' = total of
Net price of materialCustoms dutyCVD+ECS on CVD + SEC ECS on CVD + AED
Now we all know tax should be calculated on this total amount.
In normal case the Net price will come as the base price for tax calculation which is here wrong.
I want this total amount to be the base amount for tax calculation in tax procedure.
What i need to assign in the pricing procedure against this 'total' so that it is taken as base amount for tax calculation
My question is if your company and your vendor /supplier (Is a trading company from where you are procuring the materials) are geographically located at the same place (such is within country in same place or within country at different places, etc)
means, then you should not worry about the Import duty. Because for you, when you procure the goods it should be treated as Inland/Domestic procurement (by the by your vendor, who is trading company procures materials from Abroad, that is his risk or his duty to pay the Customs duty or Importation clearing charges, etc since he is procuring from outside the country through Import procurement process, so don't worry for that).
Hence when you order the material through standard PO to your vendor (that is trading company), then Logically it must be Domestic pricing procedure (there is no involvement of import duties, importation, etc), that means system will pickup the Pricing procedure - Domestic - which consists of Gross price, and all other suitable pricing elements which are in currently used in your company (for the vendor) and part from the tax condition elements such as Basic excise duty (BED), SED, AED, Cess, etc... these are not part of the Pricing proceudre, but relevent to the Tax procedure. So which can be arranged in a sequential order for the Tax procedure - TAXINN - which is currently in use from any industry - for calculating the tax amount for the item that you procure from the supplier or vendor. And thats how you (your company) will pay the Duty or tax amount agains the goods that are procured from external source.
Please note: the tax caluclation is always based on the Base amount, not on anything else, that is based on the total ordered amount through the PO. And the tax amount is always interm calculated by adopting the suitable tax code in the PO (in item details), provided you have to maintain all these tax condition elements in a Condition records through FV11 t.code. then once the tax code (i.e., Input tax - which is tax on purchases) is adopted for the PO, system will pick all the valid condition records and sum the total tax amount in the PO.
Maintainaing of condition records is required, because the tax procedure which is a Condition based tax calculation procedure. hence you have to maintian the condition records as you said. Then it will calculate correctly.
Hope it clarifies,
Regards,
Sapsrin

Error in F-44 tax procedure taxinn tax cd V1 change/ deleted incorrectly

While clearing vendor in F-44
in Tax procedure taxinn taxcode v1 changed incorrectly or deleted error is occuring. paymnet of bill is from one company code and invoices are in different co code.
Please help

Hi,
Check whether the taxcode V1 exists in country IN in FTXP.
Regards
A

Can SAP tax procedure be set up for both internal and external ?

Hi all,
Hoping to get some help from you here.
Our current SAP system is set up with internal tax procedure, and we are planning to use Vertex as the external tax system. However, due to phase approach, we are planning to launch Vertex for part of the company codes and the rest of the company codes will stay with internal tax procedure. Is this possible?
Thanks in advance for all your help!
Best,
Cyanna

Hi,
The tax procedure ia activated at country level. So this can cont be setup company code wise.
Regards,
SDNer

EFFECT OF TAX PROCEDURE

HI
First we configured CIN settings (TAXINN procedure) in our 650 client (DEV clinet) later we changed to TAXINJ in DEV itself and again we changed to TAXINN only. Now the tax codes are not working while doing the MM transaction is coming stating that Tax code is not assigned to TAXINN procedure. Now i want to know is there any effect by chaning the tax procedure like this manner will effect the tax codes or not? Please help me in solving this issue.

hi sravani,
the following are the SAP Tax Procedures to configure
OBBG - Assign Country to calculation procedure.
OBCO - Specify structure for Tax Jurisdiction code. For country like U.S.A.
LG -> character length of first level of hierarchy within your tax jurisdiction code structure.
LG -> Second level of hierarchy as above.
LG -> Third level of hierarchy as above.
LG -> Fourth level of hierarchy as above.
TX -> Tick if you want the system to determine taxes on a line by line basis instead of determining them on a cumulative basis
           per tax jurisdiction code.
OBCP - Define Tax Jurisdiction code
Dil -> Tick if you do not want tax amounts included in the based amount used for calculating cash discounts.
Txl -> Tick if you want the cash discount amount deducted from the base amount that is used to calculate taxes.
FTXP - Define Taxes on Sales/Purchases Code.
OBCL - Allow Tax codes for non-taxable transactions.
     External Tax Determination U.S.
SAP AG
Neurottstr. 16
69190 Walldorf
Germany     Configuration Guide
Copyright
© Copyright 2006 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Icons
Icon     Meaning
     Caution
     Example
     Note
     Recommendation
     Syntax
Typographic Conventions
Type Style     Description
Example text     Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example text     Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT     Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text     Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT     Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example text     Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
     Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
External Tax Determination
1.1     Prerequisites
Before using this configuration guide, you need to install the following building blocks in the order shown:
Building Block     Description
B32     Best Practices R/3 Installation
V32     Best Practices Technical Objects (Manual DDIC, Tables, User Exit, Routine) + Install Transport
J02     Organizational Structures
V03     Financial Accounting
V08     Basic Controlling
V05     Delta Materials Management
J04     Sales and Distribution
V04     Delta Sales and Distribution
1.2     Configuration
1.2.1     Defining Physical Destination
Use
This activity defines an RFC destination.
Procedure
1.     Run the following activity:
SAP R/3 Menu     Logistics  Central Functions  Supply Chain Planning Interface  Core Interface Advanced Planner  Settings  RFC Destination for Application
Transaction Code     SM59
2.     On the Display and Maintain RFC destinations screen, click TCP/IP connections.
3.     Choose the Create button.
4.     In the RFC Destination screen, enter the following:
RFC destination     VERTEX_MAXTAX
Connection type     T
Description 1     Connection to Vertex
5.     On the Technical settings tab, enter the following:
Gateway host     Vertex servers name
Gateway service     Your gateway service for Vertex server
6.     Choose the Save button.
1.2.2     Define Logical System
Use
This activity defines the logical destination for external tax determination.
Procedure
1.     Start the following activity:
IMG Menu     Financial Accounting (New)  Financial Accounting Global Settings  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Define Logical Destination
Transaction Code     SPRO
2.     Enter the following values:
N     Ex     Event for ext. taxation proc.     Function Module     RFC Destination
1     V     JUR     RFC_DETERMINE_JURISDICTION     VERTEX_MAXTAX
2     V     TAX     RFC_CALCULATE_TAXES1     VERTEX_MAXTAX
3     V     UPD     RFC_CALCULATE_TAXES1     VERTEX_MAXTAX
3.     Choose Save.
1.2.3     Maintain Pricing Procedures
Use
This activity maintains pricing procedures.
Procedure
1.     Start the following activity:
IMG Menu     Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define and Assign Pricing Procedures
Transaction Code     SPRO
2.     Enter the following values:
Table VV_T683_VA
N     Cl     U     App     Proc     LA     Destination     TSPP     PrTy
1     030     A     V     ZVAXUD     EN     BU SMB with ext. Jurisd.NEW
2     030     A     V     ZCAX01     EN     Intercompany Billing US Ext.     X
3     030     A     V     ZDPJXD     EN     myPCC US DownPaym/Tax per doc.
4     030     A     V     ZSER02     EN     Service BP Exp Settlement Ext.
5     030     A     V     ZSPUS1     EN     SP:Resource Related Bill Ext.
6     030     A     V     ZSPUS2     EN     SP: Res Rel Bill Down Pay Ext.
7     030     A     V     ZSPUS3     EN     SP: Res Rel Bill CrossComp Ext
8     030     A     V     ZU0030     EN     Credit memo (US) Ext.
3.     Choose Save.
1.2.4     Define Pricing Procedure Determination
Use
This activity defines pricing procedures.
Procedure
1.     Start the following activity:
IMG Menu     Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define and Assign Pricing Procedures
Transaction Code     OVKK
2.     Enter the following values:
Table V_T683V
N     SOrg     DChl     Dv     DoPr     Cupp     PriPr     CTyp
1     BP01     01     01     A     1     ZVAXUD     PR00
2     BP01     02     01     A     1     ZVAXUD     PR00
3     BP01     01     01     I     1     ZCAX01
4     BP01     01     01     V     1     ZSPUS1     RB00
5     BP01     01     01     W     1     ZSER02
6     BP01     01     01     W     2     ZSER02
7     BP01     01     01     Z     1     ZU0030
8     BP01     02     01     Z     1     ZU0030
9     BP01     03     01     I     1     ZCAX01
10     BP01     03     01     I     1     ZCAX01
3.     Choose Save.
1.2.5     Activate External Tax Interface
Use
This activity activates external tax interface.
Procedure
1.     Start the following activity:
IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Activate External Tax Calculation
Transaction Code     SPRO
2.     Enter the following values:
Table V_TXD_E
N     Reference     Ex     version of the tax interface     TC     RFC Destination
1     TAXUSX     V     TAXDOC00          VERTEX_MAXTAX
3.     Choose Save.
1.2.6     Assign Country to Tax Calculation Procedure
Use
This activity assigns a country to tax calculation procedure.
Procedure
1.     Start the following activity:
IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  Assign Country to Calculation Procedure
Transaction Code     SPRO
2.     Enter the following values:
Table V_005_E
N     Cty     Proc     Name
1     US     TAXUSX
4.     Choose Save.
1.2.7     Allocate Company Code to Non-Taxable Transactions
Use
This activity allocates company code to non-taxable transactions.
Procedure
1.     Start the following activity:
IMG Menu     Financial Accounting (New)  Asset Accounting  Asset Accounting(Lean Implementation)  Organizational Structures  Assign Input Tax Indicator for Non-Taxable Acquisitions
Transaction Code     OBCL
2.     Enter the following values:
Table V_001_J
N     CoCd     Company Name     City     Input tax code     Output tax code     Jurisdict. code
1     BP01     SAP Best Practices     Palo Alto     I0     O0     XX00000000
3.     Choose Save.
1.2.8     Create Number Range for External Tax Document
Use
This activity creates a number range for the external tax document.
Procedure
1.     Start the following activity:
IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Define Number Ranges for External Tax Returns
Transaction Code     OBETX
2.     Enter the following values:
Table NRIV
N     Object Name     Subobject value     Number range number     To year     From number     To number     Curr. Number     External
1     ETXDC_NR          01     0000     000000000001     999999999999
3.     Choose Save.
1.2.9     Activate External Updating
Use
This activity activates external updating.
Procedure
1.     Start the following activity:
IMG Menu     Financial Accounting (New)  Financial Accounting Basic Settings (New)  Tax on Sales/Purchases  Basic Settings  External Tax Calculation  Activate External Updating
Transaction Code     SPRO
2.     Enter the following values:
Table V_TRWCA
N     Comp     To year     Activ
1     EXTX     2999     X
3.     Choose Save.
1.2.10     Creating Tax Codes for External Tax Calculation
Use
This activity creates tax codes for external tax calculation.
Procedure
1.     Start the following activity:
Transaction Code     FTXP
2.     The following five tax codes were created for the tax procedure TAXUSX and country US.
Tax Code     Description     Condition types      Tax Type     Relevant to Tax     Tax Category
O0     A/R Sales Tax Exempt     Condition types XR1XR6 are maintained with a 100% rate.      A
(Output tax)     2
O1     A/R Sales Tax     Condition types XR1XR6 are maintained with a 100% rate.     A
(Output tax)     0
I0     A/P Tax Exempt     Condition types XP1IXP6I are maintained with a 100% rate.      V
(Input tax)     2
I1     A/P Sales Tax     Condition types XP1IXP6I are maintained with a 100% rate.     V
(Input tax)     0
U1     A/P Self Assessment Use Tax     Condition types XP1IXP6I are maintained with a 100% rate. Negative 100% is entered for condition types XP1UZP6U to force the credit entry to the tax liability accounts.     V
(Input tax)     0     1 (Consumer Use Tax)
The values in the Relevant to Tax column can be interpreted as follows:
     Setting the Relevant to tax indicator to 2 will bypass the call to the external tax system, which saves processing time. If handling exemptions within Vertex or Taxware, then this indicator must be set to 0 or space, because the call must be made to Vertex or Taxware to access their exemption handling.
     Leaving the Relevant to tax indicator blank means that the tax code is relevant to tax and a call will be made to Vertex or Taxware to decide the tax rate.
You can verify the settings using transaction FTXP.
1.2.11     Change Jurisdiction Codes for SAP Best Practices Cost Centers
This activity removes the standard jurisdiction codes from cost centers in order for Vertex to determine a valid jurisdiction code. The jurisdiction code found by Vertex is based on our default Palo Alto address.
If you want to create different addresses for each cost center, choose Accounting  Controlling  Cost Centers  Master Data  Cost Center  Individual or Collective Processing.
1.2.12     Change Jurisdiction Codes for SAP Best Practices Company Code and Plants
This activity goes through the organizational elements of the SAP Best Practices company code BP01 and plants BP01 and BP02 and remove the standard-delivered jurisdiction code from the related addresses in order for Vertex to determine a valid jurisdiction code. The jurisdiction code found by Vertex is based on our default Palo Alto address.
If you want to create a different address for each of the organizational elements, use transaction OBY6 to change the company code address, and transaction OX10 to change the plant addresses.
dont forget to reward me points if it helps you
regards
karthik

Tax procedure

Dear all,
What exactly the difference between Taxinj (condition based and formula based tax procedure), Taxinn (conditionbased taxprocedure)?I want to know the advantages & disadvantages of both.
Thanks.
Regards,
Aditya.

Taxinj :
1. This we call as formulae pricing procedure.
2. condition record is calculated based on the tax code.
Taxinn:
1. This we call as condition based pricing procedure.
2. The condition record is determined based on the tax code as well as condition record.
Mainly if we have big project it is not sufficient to get the condition record for tax conditions through tax code, so it is necessary to maintain the condition record.
Ex: Tax code is a two letter alpha numeric naming convention we use. ex if it country USA , U1 - - - - U9 .or ua - - - uz.
If we want to maintain more then this it is very difficult , so this is an disadvantage for the formulae pricing procedure.
Thanks
Gopalkrishna

Tax Procedures are empty

Dear Experts
We have to implement SAP ECC 6.0 for a German client.
I've run the Country installation program to start with organisational set up but when I check the tax procedures including TAXD for Germany they dont have any default tax conditions updated under it. Transaction OBQ3
Also no default tax codes have been delivered in the client.
I read the SAP library on Country installation and it says that the basic tax procedure and some default tax codes are delievered which has not happened in our case.
Pls suggest.
Regards
Kapil

Hi Vivek
Its TAXD but the tax procedure has no values delivered by SAP. And no delivered tax codes
Regards
Kapil

Comparing the Tax procedures of Europe and Asia

Hi
There is a requirement for me to compare and produce an analysis report on the Tax procedures followed by Europe and Asian Countries.
As i have not worked much in this area,i have no clues as of where to start from. Out of my own study i have gathered the following info :-
a) A tax procedure would be defined for every country :- But here we have so many condition types ( more than 20 for each country) and moreover they differ from each other.
In the above case how should we begin the analysis. Should we have to compare condition type by condition type ?
If so then it would consume a lot of time. Please advise.
b) I feel that once this procedure is defined, almost three-fourths of the job is done.
The rest remains to assign a country and define the GL accounts for thr relevant ActKeys mentioned in the respective procedures.
But i wish to know the analysis part of the Tax procedure. Also how can i know that a particular country is following a specific Tax procedure. Is there any place where i can check this out ?
Thanks in advance

Hi llona,
we are having the same situation that our Company Code is having its offices in almost all the countries. So we have created Tax Codes with reporting countries in the same way you told that first character for type of tax and second character for reporting country. Deductible/non-deductible is maintained in the description itself. As per my knowledge it is the better way.
bye
Mallik

Tax Procedure for Non Leading Ledger

Hi
Can we assign two different tax procedure to Leading and non leading ledgers, If so how can we do that.
i have created a non leading ledgers based on geographical locations, i.e my Leading ledger is assigned to UK based company code so the tax GB is now tax procedure assigned at country level and to record the transactions of France and other Europian countries, we have created a Non leading ledgers at each country level,
i could able to assign different curriences and Fisacal years to these non leading ledgers but i could not able to assign different tax procedures to non leading ledgers.
The main requrement of creating non leading ledgers to report the business transactions and tax on them to local authorities.
Please let us know if non leading ledgers can have different tax procedure to that of leading ledger.
Regards,
karunakar.

Hi Karunakar,
I think you can do that. Please follow SAP note
Note 873125 - DART: Ledger can be selected if NewGl is active
Thanks
Aravind

Tax Posting without maintaining Tax Procedure

Hi Gurus -
Currently we get invoice information from thrid party software to post into SAP through interface. The Tax Code and Tax Amount are passed to SAP as a line item and the Taxes are already calculated in the thrird party and we only need to post that tax amount with Tax Code in SAP. Could anyone explain me what are the different config settings need to be done to accomodate this? I don't want SAP to calculate the Tax because the invoice file that comes from thrid party software already brings in the calculated Tax values.
Pls suggest how to handle this in SAP.
Thanks
Jay

Hi,
Even though you do not want the system to calculate the taxes, still, if you want the tax codes to be appearing in the transaction, you have to customize / use the standard tax procedure that is provided.
Now once you have assigned the tax procedure to the country, you can create the tax codes and at the time of creation of the tax codes make sure that all the tax codes have only the descriptions, but the rates to be maintained as 0. this will ensure that SAP does not calculate tax again.
So for example if you have two different tax combinations like:
ED + 4% VAT
ED + 12.5% VAT,
you can create them as two tax codes say, V1 and V2, but inside both these tax codes, the % has to be maintained as 0.
The above example is on the assumption that you will be using TAXINJ as the tax procedure.
If you are using TAXINN, then the condition types are to be maintained with 0%.
Again assuming that you are implementing in India. The same logic can also be applied for other countries.
Regards
Venkatesh

Tax procedure compatability in different countries

Hi All,
Can we have two companies (Company codes) operating in differeng countries under same client?
We are operating in India, can we have another subsidiary say in Spain within same Client?
And is the Tax Procedure Company Code specific or Client?
We are currently using TAX INJ condition, will it be compatable to the Tax procedure of Spain or we have to migrate to TAX INN condition to incorporate TAX procedure of Spain.
Regds,
Ritesh

Hi Ritesh,
Yes. you can have two company codes operating under same client. You can have a company code for India and another for Spain But keeping under same client. This allows you to share the settings like master data, config settings, and also it enables intercompany transactions between India and Spain .
Tax Procedure is country specific actually. Hence you will be assigning your tax calculation procedure for a specific country i.e in this case India and spain respectively. Transaction code is OBBG. And the procedures will be different.
Hope it helps!
Thanks & Regards,
Preethi

Link between OB40 and tax procedure.

Hi Experts,
In OB40 GL code is maintained for different transaction like NAV,MWS etc.Could not get how it is link with OBCN & tax procedure.In tax procedure we maintain different condition type.For example in tax procedure for condition type MWZI account key is NVV but in OB40 could not see this transaction key NVV.
Thanks & Regards
Atharva G.

Hi,
   The tax account keys are maintained in OBCN transaction.
    In OBCN, NVV account key is maintained with posting indicator as 3 (Distribute to relevant expense/revenue items) which doesnt require any GL account maintenance. Because of this reason, the account key is not displayed in OB40.
    If you maintain the posting indicator as 2 (Separate line item), then it requires GL and then the account key will be visible in OB40. You may check the case.
    The tax procedure is linked to country in OBBG.
    Hope you understood the logic. Revert back if you need further clarification.
Regards,
AKPT

Mauritius Country Tax procedure

Similar Messages

Maybe you are looking for