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

Similar Messages

  • Can real estate post without a tax code?

    Hi there
    My client has a number of G/L accounts which have the flag/indicator "Posting without tax allowed".
    How can I configure the SAP REFX tax codes to post using no tax indicator.
    If you leave the tax code blank in the config, it reports that the sales tax is "inconsistent".
    Regards
    Joe

    Hi Joe,
    For Real Estate you can configure tax code  in the following customization path as given:
    Go to the t-code RECACUST:
    Accounting> FI Documents related to RE> Taxes> Assign Tax Codes.
    Here, you can maintain the combination of Country+ Tax Type + Tax Group + Valid From.
    So, you can maintain valid tax code with 0 VAT.
    The same can now be selected in the RE contract in the posting parameters tab.
    Thanks & Regards
    Shantanu

  • Gl Account master data - Posting without Tax allowed field

    Hi,
    I am looking to find out in which table the "Posting without Tax allowed" field's (GLACCOUNT_SCREEN_CCODE-XMWNO) flags are stored for the GL accounts. Would appreciate your help on this.
    Thanks,
    Ram

    You can go to the table SKB1. It is stored at gl account and company code combination level. Look at the field XMWNO.
    Assign points if helfpul

  • 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.

  • VAT/Excise calculation - map pricing & tax procedures

    Dear,
    Pls tell me how to map my blw senerio;
    In pricing procedure, i have
    A- Gross price
    B- Handlying charges
    C- Excise on A+B,
    here i need to calculate my exise on A+B values and it flows (C) frm tax procedure (taxinn). until here i'm ok.
    D - A BC
    E - Insurance (defined in pricing proce) on D value,
    here i'm unbale to map my price, since the sytem taking A+ B price only, its not taking my D values... I need to map pricing & tax procedures, since Gross price, Han. charges and insurance flows frm pricing proce and Excise frm tax procedure.
    Anyone has right solution, pls guide me...

    Hello sapjj
    Here in your issue, u have to maintain a dummy condition type for excise calculation in your pricing procedure. The excise on A+B will be calculated in pricing procedure itself and not it flows from tax procedure.You have to make a condition type in pricing procedure and mark it as statistical in the procedure so that it doesn't get added to material value.
    you are ok till gross price and handling charges, right?
    Then you include your dummy condition type for excise amount calculation.Then in the next step calculate a subtotal without giving any condition type and maintaining 'S' in the subtotal field in the pricing procedure.
    In the next step include the insurance condition type and calculate it on the subtotal.
    This will help
    Regards
    Gregory Mathews

  • 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 server’s 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 XR1–XR6 are maintained with a 100% rate.      A
    (Output tax)     2     
    O1     A/R Sales Tax     Condition types XR1–XR6 are maintained with a 100% rate.     A
    (Output tax)     0     
    I0     A/P Tax Exempt     Condition types XP1I–XP6I are maintained with a 100% rate.      V
    (Input tax)     2     
    I1     A/P Sales Tax     Condition types XP1I–XP6I are maintained with a 100% rate.     V
    (Input tax)     0     
    U1     A/P Self Assessment Use Tax     Condition types XP1I–XP6I are maintained with a 100% rate. Negative 100% is entered for condition types XP1U–ZP6U 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

  • Configuration of Deffered Tax Procedure, please help?

    Hi Experts,
    I am working on a project.
    please help me to configure Deffered Tax procedure.
    So far I have configured regular Tax codes & replica of the same as target tax code.
    Please advice how to :
    1. what special should i mention to in target tax code to declare it as a target tax code?
    2. how do i link Normal & target tax code
    3. which all sessions to run in SAP, so that a particular Tax is posted upon full / partial / downpayment payment.
    looking forward to hear from you all, soonest.
    Thank you all.

    Hi
    You have to make the following settings:
    Process
    ·     A deferred tax code has to be created for the calculation and the posting of the service tax to the intermediate account.
    ·     Input tax or Output tax type has to be mentioned in the tax code
    ·     The target tax code (actual tax code for the availment of the service tax) has to be entered (FTXP)
    ·     The different rates have to be maintained under the respective tax types
    ·     For the account keys, the GL accounts have to be mentioned in the OB40 settings. In this case the same account has assigned for all the three account keys.
    ·     The GL account (40140) has to be open item managed and the tax category has to be in line with the tax type mentioned in the Tax code.

  • Configure Deffered Tax procedure, please help?

    Hi Experts,
    I am working on a project.
    please help me to configure Deffered Tax procedure.
    So far I have configured regular Tax codes & replica of the same as target tax code.
    Please advice how to :
    1. what special should i mention to in target tax code to declare it as a target tax code?
    2. how do i link Normal & target tax code
    3. which all sessions to run in SAP, so that a particular Tax is posted upon full / partial / downpayment payment.
    looking forward to hear from you all, soonest.
    Thank you all.

    Hi
    You have to make the following settings:
    Process
    ·     A deferred tax code has to be created for the calculation and the posting of the service tax to the intermediate account.
    ·     Input tax or Output tax type has to be mentioned in the tax code
    ·     The target tax code (actual tax code for the availment of the service tax) has to be entered (FTXP)
    ·     The different rates have to be maintained under the respective tax types
    ·     For the account keys, the GL accounts have to be mentioned in the OB40 settings. In this case the same account has assigned for all the three account keys.
    ·     The GL account (40140) has to be open item managed and the tax category has to be in line with the tax type mentioned in the Tax code.

  • 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

  • Define tax procedure issue

    Dear SAP Gurus.,
                           When we define tax procedure TAXINN in t.code OBQ3 three option is there ,manual, required, statistical these are three check box option is there, when i was tick the check box of statistical indicator after i was going to post a invoice document with tax code A0 in t,code F-22 but system has not accepted to post invoice document,the system showing error message like tax code A0 not defined in the procedure of country IN in procedure of TAXINN,but i have done configuration everything fine.but when i was untick the check box of statistical indicator then i was going to post a invoice document with tax code A0 in t.code f-22 the system accepted to post a invoice document with tax code A0. i have done this in development server, i am facing that same problem also in production server,so now my question is before going to touch with production server i need some clarification,why should tick check box of statistical indicator or why should not tick check box of statistical indicator in t,code OBQ3,if i will tick check box of statistical indicator in t.code OBQ3 what problem i need to face, if i will not tick check box of statistical indicator in t.code OBQ3 what problem i need to face, finally my question is it should be tick or it should not be tick in statistical indicator box in .code OBQ3.please any one help me because i am facing this problem in production server, so before going to touch with production server what  i to do

    when i was maintaining statistical indicator field  in t.code OBQ3 whilst i was trying to post a invoice with tax code A0 in t.code F-22 The system has  not accepted post a document,when i was not maintaining statistical indicator field in t.code OBQ3 the system has accepted to post a document with tax code A0.i have done this in development server, i am facing this problem also in production server ,so in production server there is also statistical indicator field are maintained , so before going to touch with in production server we should maintain or we should not maintain statistical indicator field in t.code OBQ3, my senior consultant asked me this questions what i tell him   

  • ACCOUNT KEY IN TAX PROCEDURE

    Hi
    This is a tax related problem. I am implementing FICO in a US Based company.I am using TAXUSJ as the tax procedure.
    In US the tax is split in to the State, county and City. We have seperate tax rates for each of these items on the basis of the tax jurisdicition code.
    Now the problem is that when I am creating the tax codes with reference to tax jurisdiction for Country key "US", the inputable field is coming only for account key-NVV, VS1,MW1. The rest of the account keys are greyed out.Now if I want to maintain seperate tax rates for each of the account key so that I can post the amount related to state, county and city tax in seperate GL accounts, the system is not allowing to edit the field in front of the other account keys.
    How can this be done? Can any one give some help on the same.
    Regards
    Rakesh

    Closed

  • Suppress standard Tax procedure for tax returned from external tax server

    Hi All,
    We are facing an issue after implementing the external tax engine called CTE.
    In some scenarios, when CTE is returning reverse charge lines, we are passing the same lines into the BAPI for posting.
    Ex: We can clearly see that two reverse charge lines (input and output taxes) being returned by CTE.
    Now, we pass the tax lines into the BAPI for posting. We get the following:
    We can clearly see that apart from the tax lines which have been sent by CTE, we also get two additional lines having +-1000 as amount.
    Now, we tried to post the document without passing the tax lines into BAPI and we get,
    The additional lines are still there. Thus, I came to the conclusion that these tax lines are being added by SAP standard tax procedure as tax calculation.
    Now, since we have already calculated tax using CTE (for some cases specially reverse charge scenario), we do not need SAP standard tax procedure to calculate tax again and add new tax lines to the posted document.
    Thus, our main objective is to suppress the standard tax procedure ( like TAXAT, TAXGB, etc) or few of the cases.
    We tried to analyze from our end but still could not reach a solution for the same.
    Is there any way or any indicator which you can use to suppress the standard tax procedure in case we are using CTE to calculate tax?
    Please help.
    Regards,
    Saurabh.

    Hi
    You can create and use a new tax code which is applicable only for Delivery charge cases.
    Use a new pricing condition type for this Tax .and condition records with access sequence and tax code can be amintianed only for this condition type.
    You will have to modify pricing procedure for the same.
    Depending on condition records and document inputs the tax values for delivery will get triggered.
    You can also put an order reason in Accounting determination access sequence through which on This special sales ,
    account determiantion can be changed.
    hope this helps
    Regards
    Mandar

  • Pricing procedure and Tax Procedure.

    Hi,
    Can any body suggest, how to bring tax values in Condition, in Pricing procedure of MM. Now  as per my settings Tax is coming under tax head and MM pricing prodcedure is coming separately, I need ,
    Thanks & Regards
    Sudhansu

    Hi,
    Did all you taxes in tax procedure in %!
    No access sequence required for your requirement. Create a condition type as ZTFT & maintain
    Cond. Class: D
    Calculat.type: B
    Cond.category: N
    Keep BLANK access sequence filed & make it as item condition and then add this condition type in pricing procedure with logic just before calculation of TOTAL price.
    Now do create PO with all taxes  and now you can see all tax amounts in condition type  ZTFT in PO Condition TAB( which flow from  tax procedure to MM pricing procedure with a condition type ZTFT)
    Regards,
    Biju K

  • 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

Maybe you are looking for