Belgian VAT

Hi everyone,
  I am looking into configuring Belgian VAT. There are some standard tax codes in ftxp for BE but our requirement is to have a few more different tax codes with same tax rates but different VAT declaration.
Has anyone worked on Belgian VAT before and could shed some light on this "VAT Declaration" thing? and how does it work?
I checked the building block document for Belgium VAT but couldn't find anything.

Hi ,
   Please tell me ur senario regarding.I had done recently immplimentation in phillipines.So please specify ur requirement clearly.So that i may give you help full answer.
     For Ex: Tax codes can create for the diffrent percentages.That is the fundamental.You can assign the same tax account to diffferent tax codes or each percentage wise u can maitain vat gl accounts.which ever is convinient according to ur business requirement u can adopt. Please specify your doubt clearly.Hope this might help full to you.Please assign points.Thanks for the consideration.
Regards,
Suma.

Similar Messages

  • Question on Belgian VAT Purchase Journal

    HI,
    Can some one help me with Belgian VAT Reports.
    There is a report called Belgian VAT purchase journal, which is Oracle Standrad. We found that the report displays incorrect calculations for certain AP transactions.
    For some of the transactions (with offset tax) on this report , Invoice amount with VAT is always less than Invoice Amount with out VAT, where as we expect Invoice Amount with VAT to be more than Invoice Amount with out VAt.
    Can you please let us know if you are aware of any similar issues with Belgian VAT Purchase Journal and also suggest your views on how to resolve the issue.
    Many Thanks
    Kotesh

    HI,
    Can some one help me with Belgian VAT Reports.
    There is a report called Belgian VAT purchase journal, which is Oracle Standrad. We found that the report displays incorrect calculations for certain AP transactions.
    For some of the transactions (with offset tax) on this report , Invoice amount with VAT is always less than Invoice Amount with out VAT, where as we expect Invoice Amount with VAT to be more than Invoice Amount with out VAt.
    Can you please let us know if you are aware of any similar issues with Belgian VAT Purchase Journal and also suggest your views on how to resolve the issue.
    Many Thanks
    Kotesh

  • Electronic Belgian VAT declaration

    Hello,
    In Belgium, while using electronic VAT declaration (S_ALR_87012357 or RFUMSV00), how is it possible to re-run or to generate more than one declaration.
    It's possible while using the "paper" declaration but I don't know with the electronic .
    Thanks in advance
    Georges HUYNEN

    Hello,
    You can run many declaration you want with these transaction.
    Thanks

  • Belgian VAT reporting via internet

    Dear Support,
    In Belgium you may send your VAT returns (INTERVAT) electronically via the website of the Finance Department using the FREE Isabel OfficeSign 5.0 component.
    In february 2007 companies ( depending on their turnover ) will be obliged to use INTERVAT.
    Which tools will be provided by SAP in release 4.6C to create this electronical declaration ?
    When they will be available ?
    Best regards,
    Anne De Maesschalck

    Dear Anne,
    As software developer in Knokke-Heist (B) we are also looking for a general solution for the Intervat issues.  The creation of the VAT declaration XML is not so difficult, but I haven't found a way yet to make it in SAP B1.
    If any progress on this topic, I will reply on your original message.
    Regards,
    Marc Stepman

  • Problem with Intrastat handling (MEIS)

    Dear SCN Members,
    we have a problem with Intrastat handling:
    Our company is in Great Britain (example VAT-No. GB123456789)
    We have a vendor in Switzerland (no EU VAT-No.), who has a fiscal representative in Belgium (example VAT-No. BE1234567890).
    Both have a separate vendor number (swiss vendor: 23176, belgian vendor: 33179).
    We created a partner "WL" (Goods Supplier) in the vendor master data of the swiss vendor and assigend the belgian vendor number. The swiss vendor master data has nothing filled in the "VAT Reg. No." field (LFA1-STCEG) of the vendor master data. The belgian vendor number has the belgian VAT-No. filled in the "VAT Reg. No." field (LFA1-STCEG) of the vendor master data.
    The partner "WL" is automatically taken into the purchase order header partners and is also taken into account for the goods receipt posting.
    After I have posted the vendor invoice, the line is shown in transaction MEIS, but the incompletion log is always showing message no. EIP029:
    The system did not find the VAT registration number of vendor 23176.
    In my opinion, the VAT no. of the fiscal representative (BE1234567890) should be taken into account for the Intrastat reporting, as the swiss vendor has no VAT number. We have not yet managed to get the belgian VAT into the Intrastat report.
    Could you please clarify. Thanks in advance for your help!

    Hi,
       Please refer the KBA: 1988909 - MEIS: Error EIP 029 "The system did not find the VAT registration number of vendor The reason and the solution is well explained in the KBA. You may change the configuration as explained in the KBA and test again.
    Regards,
    AKPT

  • Creating Tax Codes FTXP

    Transaction:  FTXP
    This area gives you a step by step explanation on u201Chow to create a tax code in SAPu201D. Later on these tax codes must be used in the creation of condition tables such as for MWST.
    Go to transaction code FTXP and select the country for which you need to create a tax code.  This country is automatically linked to the Tax Procedure which has been set up in the menu path [IMG - Financial accounting - Financial accounting global settings - tax on sales/purchases - basic settings - Assign country to calculation procedure].
    Enter in the field tax code. This must be a 2-digit alphanumeric code i.e. A5, 55, BB, etc..  Before SAP 4.5 (I believe) you could use other special characters such as @, ? etcu2026 But this is no longer applicable. See OSS note 212806.SAP will ask you to complete other additional fields such as:
    description of the tax code: please give a clear description
    define the tax type: define whether the tax code is relevant for input or output tax
    Indicator which determines that an error message should be issued if the tax amount is not correct. It it recommended to flag this.
    Eu code: One of the most forgotten parameter. If you do not set this parameter at u201C1u2033 then all transactions with this code will be not picked up in the ESL listing of that specific country. This code u201C1u2033 represents all the Sales from one EU country to another EU country.
    The target tax code fields are used in case of deferred taxes. This is applicable for example in France. The VAT needs to be paid for example not when the invoice is issued but when the customer pays the VAT. There are here again special programs available in SAP for deferred taxes.
    Reporting country: this field needs to be completed when you are using the plants abroad functionality. This means that when you as a German company have a Belgian VAT number and you have sales in Belgium (+ you need to submit a VAT return in Belgium) , then of course these invoices need to be booked in SAP with a Belgian tax code.
    Further in the menu you can also allocate the amount where this specific tax code is used to a certain tax account. The tax type fields such as Base Amount, Input tax, Output Tax u2026 can be determined via the calculation procedures.  Calculation procedures are defined in the IMG at [Financial accounting - Financial accounting global settings - tax on sales/purchases - basic settings - Assign country to calculation procedure].  Here you will need to define also the calculation levels. For example the Output tax is level 125 and the output tax will be calculated on the basis of the base amount. Therefore you put for the output tax in the field u201Cfrom levelu201D 100. The level of Base amount is 100. You do the same for the others.
    Account Keys.
    NVV: The non deductible VAT is automatically added to the expenses account
    NAV: Indicate for this key a separate account for the non deductible VAT
    ESA: Output tax in case of Acquisition of EU goods
    ESE: Input tax in case Acquisition of EU goodsLast but not least you also need to complete the tax rate field.
    Tax Percentage & GL Account assignment
    Tax percentage can be maintained in two ways & that depends upon the Tax procedure that has been followed i.e. if tax procedure is formula based then percentage can be maintained in FTXP only, where as if the procedure is condition based then percentage has to be maintained under the identified condition type.
    Once done GL accounts has to be assigned under OB40 for automatic posting of tax amounts.

    Hi Manoj,
    What do you mean by advisable solution? Do you know where in SAP documentation (SAP help or elswhere) it is mentioned that a new tax code should be created in that case?
    That's why I opened this question. If there is no harm then it is easier to change the gl accounts (client requested to change the gl accounts for 127 tax codes). However if there might be a negative effect and it is mentioned somewhere by SAP or anyone of you had a bad experience then of course I would prefer creating the new tax codes.
    Your answers are welcomed!
    Regards,
    Vlad

  • Tax code - Info record

    1. how or where to enter the Tax code in info record ...
    2 in MIRO , we have to enter Tax code ,, but  in the Tax code - tab is blank ... no possible entry there ....( i have not mainted Tax code anywhere ..but when doing MIRO with out tax code it is not saving .... pls help
    alifff

    As you might be aware of Tax code is specified to:
    -     Check the associated transaction is related input or output tax.
    -     Check if a tax account with tax type (input or output tax) can be posted to
    -     Check the tax on procurement amount in the document
    -     Calculate the amount of tax on sales automatically on request
    -     Determine the tax account
    Use TCode FTXP for creating TAX Code.
    Select the country for which you need to create a tax code. 
    This country is automatically linked to the Tax Procedure
    Enter in the field tax code. This must be a 2-digit alphanumeric code i.e. A5, 55, BB, etc.
        description of the tax code: please give a clear description
        define the tax type: define whether the tax code is relevant for input or output tax
        Indicator which determines that an error message should be issued if the tax amount is not correct. It it recommended to flag this.
        Eu code: One of the most forgotten parameter. If you do not set this parameter at u201C1u2033 then all transactions with this code will be not picked up in the ESL listing of that specific country. This code u201C1u2033 represents all the Sales from one EU country to another EU country.
        The target tax code fields are used in case of deferred taxes. This is applicable for example in France. The VAT needs to be paid for example not when the invoice is issued but when the customer pays the VAT. There are here again special programs available in SAP for deferred taxes.
        Reporting country: this field needs to be completed when you are using the plants abroad functionality. This means that when you as a German company have a Belgian VAT number and you have sales in Belgium (+ you need to submit a VAT return in Belgium) , then of course these invoices need to be booked in SAP with a Belgian tax code.
    Thanks & Regards
    JP

  • Create Tax code - non deductable

    Dear all ,
    Pl guide step by step : how to create new tax code (non deductable )
    As well pl also guide for the steps need  to carry out before the tax creation .
    Regards

    Hi Venky,
    Go To Transaction:  FTXP
    This area gives you a step by step explanation on u201Chow to create a tax code in SAPu201D. Later on these tax codes must be used in the creation of condition tables such as for MWST.
    Go to transaction code FTXP and select the country for which you need to create a tax code.  This country is automatically linked to the Tax Procedure which has been set up in the menu path [IMG - Financial accounting - Financial accounting global settings - tax on sales/purchases - basic settings - Assign country to calculation procedure].
    Enter in the field tax code. This must be a 2-digit alphanumeric code i.e. A5, 55, BB, etc..  Before SAP 4.5 (I believe) you could use other special characters such as @, ? etcu2026 But this is no longer applicable. See OSS note 212806.SAP will ask you to complete other additional fields such as:
              o description of the tax code: please give a clear description
              o define the tax type: define whether the tax code is relevant for input or output tax
              o Indicator which determines that an error message should be issued if the tax amount is not correct. It it recommended to flag this.
              o Eu code: One of the most forgotten parameter. If you do not set this parameter at u201C1u2033 then all transactions with this code will be not picked up in the ESL listing of that specific country. This code u201C1u2033 represents all the Sales from one EU country to another EU country.
              o The target tax code fields are used in case of deferred taxes. This is applicable for example in France. The VAT needs to be paid for example not when the invoice is issued but when the customer pays the VAT. There are here again special programs available in SAP for deferred taxes.
              o Reporting country: this field needs to be completed when you are using the plants abroad functionality. This means that when you as a German company have a Belgian VAT number and you have sales in Belgium (+ you need to submit a VAT return in Belgium) , then of course these invoices need to be booked in SAP with a Belgian tax code.
    Further in the menu you can also allocate the amount where this specific tax code is used to a certain tax account. The tax type fields such as Base Amount, Input tax, Output Tax u2026 can be determined via the calculation procedures.  Calculation procedures are defined in the IMG at [Financial accounting - Financial accounting global settings - tax on sales/purchases - basic settings - Assign country to calculation procedure].  Here you will need to define also the calculation levels. For example the Output tax is level 125 and the output tax will be calculated on the basis of the base amount. Therefore you put for the output tax in the field u201Cfrom levelu201D 100. The level of Base amount is 100. You do the same for the others.
    Account Keys.
              o NVV: The non deductible VAT is automatically added to the expenses account
              o NAV: Indicate for this key a separate account for the non deductible VAT
              o ESA: Output tax in case of Acquisition of EU goods
              o ESE: Input tax in case Acquisition of EU goodsLast but not least you also need to complete the tax rate field.
    Tax Percentage & GL Account assignment
    Tax percentage can be maintained in two ways & that depends upon the Tax procedure that has been followed i.e. if tax procedure is formula based then percentage can be maintained in FTXP only, where as if the procedure is condition based then percentage has to be maintained under the identified condition type.
    Once done GL accounts has to be assigned under OB40 for automatic posting of tax amounts.
    Also Check : http://www.sap-exp.com/creating-tax-codes-in-sap.html

  • Tax code creatinon..?

    Hi all
    Can nybody explain me , how to create new tax code and what are things i have do in configuration part
    FOR eb, Z1 is tax code
    Z1- ECess 14%Secess2%Hsecess1% + vat4%
    For tax code how we have to configure and create in SAP
    Please explain me in Both tax procedures (TAXINN & TAXINJ)
    Thanks
    sap-mm

    hi
    u can create the tax code in FTXP
    for taxinj process u have maintain the values in tax code only but for taxinn process u have to maintain condition records
    Go to transaction code FTXP and select the country for which you need to create a tax code.  This country is automatically linked to the Tax Procedure which has been set up in the menu path [IMG - Financial accounting - Financial accounting global settings - tax on sales/purchases - basic settings - Assign country to calculation procedure. 
    Enter in the field tax code. This must be a 2-digit alphanumeric code i.e. A5, 55, BB, etc..  Before SAP 4.5 (I believe) you could use other special characters such as @, ? etc... But this is no longer applicable. See OSS note 212806.SAP will ask you to complete other additional fields such as:
    description of the tax code: please give a clear description
    define the tax type: define whether the tax code is relevant for input or output tax
    Indicator which determines that an error message should be issued if the tax amount is not correct. It it recommended to flag this.
    Eu code: One of the most forgotten parameter. If you do not set this parameter at "1" then all transactions with this code will be not picked up in the ESL listing of that specific country. This code "1" represents all the Sales from one EU country to another EU country.
    The target tax code fields are used in case of deferred taxes. This is applicable for example in France. The VAT needs to be paid for example not when the invoice is issued but when the customer pays the VAT. There are here again special programs available in SAP for deferred taxes.
    Reporting country: this field needs to be completed when you are using the plants abroad functionality. This means that when you as a German company have a Belgian VAT number and you have sales in Belgium (+ you need to submit a VAT return in Belgium) , then of course these invoices need to be booked in SAP with a Belgian tax code.
    Further in the menu you can also allocate the amount where this specific tax code is used to a certain tax account. The tax type fields such as Base Amount, Input tax, Output Tax ... can be determined via the calculation procedures.  Calculation procedures are defined in the IMG at [Financial accounting - Financial accounting global settings - tax on sales/purchases - basic settings - Assign country to calculation procedure].  Here you will need to define also the calculation levels. For example the Output tax is level 125 and the output tax will be calculated on the basis of the base amount. Therefore you put for the output tax in the field "from level" 100. The level of Base amount is 100. You do the same for the others.
    Account Keys.  
    NVV: The non deductible VAT is automatically added to the expenses account
    NAV: Indicate for this key a separate account for the non deductible VAT
    ESA: Output tax in case of Acquisition of EU goods
    ESE: Input tax in case Acquisition of EU goodsLast but not least you also need to complete the tax rate field.
    Tax Percentage & GL Account assignment
           Tax percentage can be maintained in two ways & that depends upon the Tax procedure that has been followed i.e. if tax procedure is formula based then percentage can be maintained in FTXP only, where as if the procedure is condition based then percentage has to be maintained under the identified condition type.
    Once done GL accounts has to be assigned under OB40 for automatic posting of tax amounts.        
    http://www.4shared.com/file/30654921/44e1737/00017-FI-GL-Define_Tax_Codes_for_Sales_and_Purchases-SAP_FICO_Configuration.html
    hope it clears
    regards
    kunal

  • Foreign Tax Reporting and Plant Abroad

    Hi,
      While looking into Plant Abroad documentation, I found that it mostly speak about European Union nations.
      Does this work for a US Company having a warehouse in Brazil (one of the places with most complex taxes)?
      (I think Plant Abroad is a misnomer, ideally it should have been something like Foreign location tax set up!)
    Regards
    BBC

    Hello Thierry,
    I have a related problem but different than yours. I have 8 European company codes in scope and we are struggling to choose separate tax procedure for each country versus TAXEUR for all countries (Belgium, UK, Germany, France, the Netherlands, Spain, Italy and Luxembourg).
    If we have the following tax codes:
    G1 - UK VAT
    G2 - UK VAT 0%
    B1 - Belgian VAT
    B2 - Belgian VAT
    We want to maintain VK11 condition and FTXP settings for G1 and G2 in UK only and not in Belgium.
    Similarly, we want to maintain B1 and B2 in BE only and not in UK using TAXEUR.
    If we use separate tax procedures TAXB for Belgium and TAXGB for UK. Using TAXEUR we hope that the tax codes maintenance should be simplified. There is a "reporting country" field inside FTXP tax code properties and this should be used to identify the tax code to a particular country.
    Unfortunately using the TAXEUR and with the above mentioned settings, the invoice is not getting release to accounting until we extend the tax codes to both the countries.
    How was your experience and do you have a solution?
    Thanks a lot
    Sharabh

  • Process step by step for creating Tax Code ?

    Dear All ,
                            Kindly provide me step by step manner to create  tax code in FTXP , I need each & every single step which is to be used to create a tax code , pl it is urgent , for ex. i need to know that what is filled in target tax code , EU Code , check id ( why it is checked ) etc .
    sap11

    Hi,
    Transaction:  FTXP
    This area gives you a step by step explanation on "how to create a tax code in SAP". Later on these tax codes must be used in the creation of condition tables such as for MWST.
    Go to transaction code FTXP and select the country for which you need to create a tax code.  This country is automatically linked to the Tax Procedure which has been set up in the menu path [IMG - Financial accounting - Financial accounting global settings - tax on sales/purchases - basic settings - Assign country to calculation procedure]. Enter in the field tax code. This must be a 2-digit alphanumeric code i.e. A5, 55, BB, etc..  Before SAP 4.5 (I believe) you could use other special characters such as @, ? etc... But this is no longer applicable. See OSS note 212806.SAP will ask you to complete other additional fields such as:
    description of the tax code: please give a clear description
    define the tax type: define whether the tax code is relevant for input or output tax
    Indicator which determines that an error message should be issued if the tax amount is not correct. It it recommended to flag this.
    Eu code: One of the most forgotten parameter. If you do not set this parameter at "1" then all transactions with this code will be not picked up in the ESL listing of that specific country. This code "1" represents all the Sales from one EU country to another EU country.
    The target tax code fields are used in case of deferred taxes. This is applicable for example in France. The VAT needs to be paid for example not when the invoice is issued but when the customer pays the VAT. There are here again special programs available in SAP for deferred taxes.
    Reporting country: this field needs to be completed when you are using the plants abroad functionality. This means that when you as a German company have a Belgian VAT number and you have sales in Belgium (+ you need to submit a VAT return in Belgium) , then of course these invoices need to be booked in SAP with a Belgian tax code.
    Further in the menu you can also allocate the amount where this specific tax code is used to a certain tax account. The tax type fields such as Base Amount, Input tax, Output Tax ... can be determined via the calculation procedures.  Calculation procedures are defined in the IMG at [Financial accounting - Financial accounting global settings - tax on sales/purchases - basic settings - Assign country to calculation procedure].  Here you will need to define also the calculation levels. For example the Output tax is level 125 and the output tax will be calculated on the basis of the base amount. Therefore you put for the output tax in the field "from level" 100. The level of Base amount is 100. You do the same for the others.
    Account Keys.  
    NVV: The non deductible VAT is automatically added to the expenses account
    NAV: Indicate for this key a separate account for the non deductible VAT
    ESA: Output tax in case of Acquisition of EU goods
    ESE: Input tax in case Acquisition of EU goodsLast but not least you also need to complete the tax rate field.
    Tax Percentage & GL Account assignment
           Tax percentage can be maintained in two ways & that depends upon the Tax procedure that has been followed i.e. if tax procedure is formula based then percentage can be maintained in FTXP only, where as if the procedure is condition based then percentage has to be maintained under the identified condition type.
    Once done GL accounts has to be assigned under OB40 for automatic posting of tax amounts.        
    Reward points if helpful,
    Regards,
    Archit

  • BELGIAN DOWN PAYMENT REQUEST --Need a feedback experience URGENT

    Hi all,
    The case concerns the down payment request in a belgian company code:
    1/ The process begins with the posting of a FAZ document type from SD module (through transaction VF01) => Therefore a down payment request is posted in FI with special G/L account "F". This document is a statistical document.
    2/ But in the belgian legislation this statistical document should be in program RFUMSV00 and therefore the VAT must be declared.
    I found a program(RFUMSANF that SAP developped to create another document in reference of the down payment request document issued from SD but with a different numbering. The fiscalist told me that he can't accept because the belgian legislation said that it's the down payment request number that must appear in the declaration and in the solution provided by SAP we're obliged to create a new document number => Therefore there is a gap in the sequential numbering generated from SD.
    If you have already faced this problem, thanks for telling me what were your answers and what kind of solutions have you implemented to solve this problems.
    I take any help.
    Thanks a lot for your help.

    Hi,
    The concept of Downpayment is to have the advance payment received booked in the system by creating a downpayment request/invoice.
    In your case the Downpayment Request is 100%, so it becomes difficult to apply the same to the Invoice in the Payment window.
    Through Internal Reconciliation window, the same cannot be reconciled. Check Note no. : 1340606 regarding the system behavior.
    The following options can be checked in the COPY of the database :
    1) Option of applying the Downpayment Request and the Invoice and making a payment of 0.01 cent and then transfering the same to the Rounding account.
    2) Checking the option of AR Reserve invoice in case there is 100% Downpayment.
    Please check and consult the account of the company.
    Kind Regards,
    Jitin
    SAP Business One Forum Team

  • BELGIAN DOWN PAYMENT REQUEST --Need a feedback experience

    Hi all,
    The case concerns the down payment request in a belgian company code:
    1/ The process begins with the posting of a FAZ document type from SD module (through transaction VF01) => Therefore a down payment request is posted in FI with special G/L account "F". This document is a statistical document.
    2/ But in the belgian legislation this statistical document should be in program RFUMSV00 and therefore the VAT must be declared.
    I found a program(RFUMSANF that SAP developped to create another document in reference of the down payment request document issued from SD but with a different numbering. The fiscalist told me that he can't accept because the belgian legislation said that it's the down payment request number that must appear in the declaration and in the solution provided by SAP we're obliged to create a new document number => Therefore there is a gap in the sequential numbering generated from SD.
    If you have already faced this problem, thanks for telling me what were your answers and what kind of solutions have you implemented to solve this problems.
    I take any help.
    Thanks a lot for your help.

    Hi,
    The concept of Downpayment is to have the advance payment received booked in the system by creating a downpayment request/invoice.
    In your case the Downpayment Request is 100%, so it becomes difficult to apply the same to the Invoice in the Payment window.
    Through Internal Reconciliation window, the same cannot be reconciled. Check Note no. : 1340606 regarding the system behavior.
    The following options can be checked in the COPY of the database :
    1) Option of applying the Downpayment Request and the Invoice and making a payment of 0.01 cent and then transfering the same to the Rounding account.
    2) Checking the option of AR Reserve invoice in case there is 100% Downpayment.
    Please check and consult the account of the company.
    Kind Regards,
    Jitin
    SAP Business One Forum Team

  • VAT allocation rules for pricing

    Hi,
    We have following scenario applicable to allocate VAT on a trade invoice :
    1. VAT to be applied for a product on a trade invoice is depending of the combination of the country of the selling organization & the country of the customer ship-to location.
    In Project 'ABC', it is found that this is currently implemented in SAP as
    "the VAT to be applied for a product on a trade invoice is depending of the combination of the country of the plant code from which the product is shipped and the country of the customer ship-to location".  
    For example :
    1. In case a French,Client Organization invoices a French customer for product shipped from a DC in
        Germany, the VAT rules are to de defined via a country France / France combination setting (while in
        Project 'ABC',this is done by Germany / France combination).
    2. In case a Netherlands Client Organization invoices a Germany customer for product shipped from a
        DC in Belgium, the VAT rules are to de defined via a country Netherlands / Germany combination
        setting (while in project 'ABC' this is done by Belgium / Germany combination).
    The way, project 'ABC'' rules are implemented in SAP, represents two issues :
    3. Unnecessary, fault sensitive VAT data maintenance : in case a product is shipped from a DC in
        another country (e.g. in case of availability issues), then VAT rules are to be defined in Project 'ABC' 
        settings for the new DC country / customer country combination.
         If not, no VAT will be allocated (without users being aware)
    4. In case a Belgian Client organization ship product from a French to a customer in Belgium  :
        Belgium only VAT rules should apply.  
        In case a Netherlands P&G organization ship product from a French to a customer in Belgium  :  
        combination Netherlands / Belgium VAT rules should apply.    
        But, in Project 'ABC' Prof VAT is determined through the France / Belgium combination in both
        scenarios.
    Please advise how VAT solution can work from pricing perspective.
    Any pointers on this will be highly apperciated.
    Regards
    Tushar

    Hi,
    Any pointers on this please.
    Regards
    Tushar

  • How to resolve VAT triangulation determination in CRM 70

    Please adjust SAP CRM so that it supports external tax software packages like Vertex.  There are at least two scenarios to be considered for VAT. 
    The first is a direct sale from seller to customer where there are no triangulation issues:
    Bentley Systems  sells software licenses (perpetual licenses) and software maintenance contracts.  All of these products and services are electronically delivered out of our European location to our EU customers on one to one basis using SAP CRM as our billing engine.  Because these intangible goods are sold directly from the Bentley entity to the end user, there are no scenarios where EU triangulation comes into play.  No inventory is shipped from the Bentley.  You just need to pass the BP information for the sold to BP.
    The second scenario for Bentley is the delivery of services by employees or third party contractors where there may be cross border issues and would need to support triangulation:
    Bentley Systems  sells customer training and consulting services.  These may be delivered either electronically or on-site at a physical location.  It is possible that a consultant from our Bentley Finland entity would deliver training to the Belgian office of a French customer.  This means that the SAP CRM billing engine needs to be able pass sufficient BP information to the external tax engine like Vertex so that the VAT triangulation tax rules can be properly calculated.
    Since billing out of SAP CRM is an SAP standard supported methodology, it should be updated to support external tax software providers such as Vertex, Taxware, and Sabrix.

    Yes it is well possible to resolve the collisions in MAS. that's what called as Concurrent Development. Two users modify the same object,Collsion will result. In such cases, you need to choose which version to be released.
    Instead of writing everything here, I will provide one quick link which explains about how to resolve collisions.
    http://help.sap.com/saphelp_crm50/helpdata/en/25/96033cc68e3f05e10000000a114084/content.htm
    In your case, If you require the changes done by both the suersm then you need to go for Merge option. Please check the above link for more info.
    Best Regards
    Shankar

Maybe you are looking for