Examples of a TRM Sales Tax registration process

Hi.  I would be grateful for an example of a Sales Tax registration process using TRM.  I have looked at the Solution Map and the ES web service bundle material, but they have very little detail.   Other 'create business partner' documentation is too generic - i.e. individual, not organisation.   A typical example of a real business process scenario would be great.  Perhaps I'm looking in the wrong place?  Guidance welcome!
Regards,
Nick

Hi Nick,
you can process tax calculation in FI. See link :http://help.sap.com/erp2005_ehp_04/helpdata/EN/36/41913ab525fb23e10000000a114084/frameset.htm
BR, Tomislav

Similar Messages

  • Tax registration numbers

    hi experts
    can you tell me which table stores sales tax registration number and national tax registration number of application runnning company??
    regards
    anwer

    Hi,
    In 11i, it's defined in AR->Setup->System->System Options, folder Tax.
    Regards,
    Ketter Ohnes

  • Excise invoice and sale tax  applicable  in consignment process

    Hi,
    How excise invoice and sale tax  applicable  in consignment process in below stages--
    in consignment fill up,consignment issue,Return andpickup
    Regards
    Ishikesh

    Hi,
    You have to pass JV for 50 picked up items through J1IS. For this you have to create new subtransaction type type and accordingly maintain the G/L in the tax on goods movement settings for acoount determination node.
    Regards,
    Sagar Wairagade

  • Origin of sales tax ID number in billing documents

    Hello,
    The field "Origin of sales tax ID number" in billing documents determines from where the tax ID number is taken, for example:
       A - Ship-to party
       B - Payer
       C - Sold to Party
    When the partner functions of the customer are different, how can I decide whose tax ID number the billing document takes? I need to take the tax ID of the payer but it takes of the ship to party.
    Thanks in advance, best regards,
    Silvia

    hi,
    The path here is IMG, Sales and distribution, Basic functions, Taxes, Maintain sales
    tax—Identification number determination.
    Three available options can be assigned to each sales organization. It is recommended that in order to keep consistency throughout the system, use the same determining rules across all sales organizations.
    The first is determination rule A, which indicates that the tax number and tax indicator classification are generally taken from the sold-to party customer master record.
    Determination rule B indicates that the tax number and tax classification are generally taken from the customer master record of the payer.
    Finally, if the field is left blank, the system determines the tax number and the tax classification according to the following sequence:
    1.If the payer has a VAT registration number and is identical to the sold-to party, the tax number and tax classification are copied from the payer (in this case, the ship-to party is not relevant). The tax number is copied according to the country of destination relevant for taxes.
    2. If 1 does not apply, the ship-to party has a VAT registration number, and the sold-to party does not, the tax number and tax classification are copied from the ship-to party.
    3. If 2 does not apply, the tax number and tax classification are copied from the sold-to party.
    CHAN

  • Calculate sales tax based on all line items on the order

    My users have asked to determin tax on the sales order, based on all the line items on the order. For example, if all the items are for product only, or if all the line items are for labor only, or if there is a mix of product and labor,
    Order 1
    line 1 product flag as both for vertex
    line 2 labor flag as both for vertex
    Order 2
    line 1 product flag as product only
    line 2 product flag as product only
    Order 3
    line 1 labor flag as labor only
    line 2 labor flag as labor only
    I do not see away to do this while the order is being created. In the order 1 example above, line one is entered, priced, and taxed as product only (it is the only line on the order at that time and it is product only). Line two is entered, it is marked as both. But I cannot send line item one back through vertex marked as both. Vertex processing is already complete.
    I have looked at using both FYTX0001 and FYTX0002. With both of these exits I can only work with a single line item, i.e. once item one is processed it will not go through the exit when item two is added.
    Any assistance would be appreciated.
    Jay

    Hi WCG,
    Our business is located in California as well. California is a modified-origin state, where state, county, and city taxes are based on the origin of the sale, while district taxes are based on the destination of the sale. You only need to add Sales tax when your customer's billing address is in California. I do not believe that Catalyst currently supports district based sales tax. You could look into a third party solution like TaxJar and see if it could be integrated into Catalyst. We currently charge our California based customers exactly what we would charge them in our retail store.
    So you want to do something like this:
    -Ryan

  • Maintain Sales Tax Exemption Certificate info in Customer Master Record

    Hello people!
    I really need your help in this one: we are going to implement SAP in a company settled in Canada. The users requested us that it is highly important to maintain Tax exemption certificate for GST (GST is "Goods and sales tax" -- not withholding) in the customer master record.
    I couldn't find anything in SAP to store this info in the Customer Master Record... have you ever had this issue before? is there a workaround? We are not using any external tax system (for example: Vertex). Any information is useful. Thanks in advance. Maria.

    Hi Maria,
    I was going through how GST works and I think you can create Tax codes under withholding tax and use the same as withholding tax.
    As per my understanding of GST, all your process can be met...
    However, for reports because there is no standard avail, you would need to develop reports..
    Hope this helps..
    Cheers,
    Redoxcube

  • Authorization object for sales tax code (MWSKZ) in FB60

    HI, there is a FI tcode FB60 in FI module. The requirement is that user wants to restrict some users to enter only few sales tax codes from among the list. For example if there are 30 tax codes, then user should be authorised to enter only 5 tax codes from the list. In standard authorization, there doesn't exist an authorization object to restrict tax codes. Kindly tell me the process of making authorization object for this task.
    I have made one authorization object. I think i need to call this object somewhere in user exit of FB60. Is this the way of doing this?? Kindly if someone have done this, mention down the procedure of making authorization object and how to implement it. Thanks

    Hi,
    Instead of creating a authorization obejct and assigning it to the tax code, it will be easy to write the code in a user exit to check whether the tax code is applicable for the user. Suppose if the user enters a non-applicable tax code, you can throw an error.
    Do u want to restrict the number of entries in F4 help for tax code for a particular user?
    Cheers
    ~Niranjan

  • A/R Installment Payments with Sales Taxes and Freight in 1st payment

    Our sales dept. wants to offer our customers Installment Payment plans (6, 12, 24 mths) for product sales which is easy enough to set up using Payment Terms and the Installment Payment flag.
    But our Accounting Dept wants to collect the Sales Taxes and Freight "up front" in the first payment.
    We do not want to use Milestone billing since Accounting wants to recognize the revenue of the sale during the month of the sale ... so a single Invoice to the customer with the Payment Plan printed on the invoice is the option they want done.
    I have not been able to find any way to set up the Installment Plan configuration to do such a thing.  The Terms of Payment refer to the total Invoice amount.
    Has anyone here be able to accomplish such configuration (without doing custom coding in a User Exit)?
    Example:  $60,000 item, %5,000 tax, $100 frieght = $65,100 total invoice.  (6 month payment plan)
       Payment #1 = $15,100
       Payment #2 = $10,000
       Payment #3 = $10,000
       Payment #4 = $10,000
       Payment #5 = $10,000
       Payment #6 = $10,000

    I have already set up the installment plan in OBB9 with 6 entries (1 - 6) for my IP Payment Term of IPM1.  I have the percentages setup as 16.67 for each of the installments and the last set at 16.65 (equaling 100%).
    The problem with Sales Tax and Freight is that you can not simply assign an arbitrary percentage to the 1st installment (for example make the 1st installment 25% and break up the remaining 5 installments fromt he other 75%).
    We need to make sure that the first Installment from the customer is for the Sales Tax, the Freight, and exactly 1/6 of the material cost (if it is a 6 month payment plan).
    I have activated User Exit EXIT_SAPLV60B_007 to intercept table generation of the installment plan that is sent to Accounting to fix this problem.  Now the Accounting document connected with the customer invoice is correct.  My next step is to fix the SmartForm print of the Installment Plan on the customer's Invoice.

  • Sales tax Diferential adjustments in credit/debit memo instead of F-02

    Dear All
    While creating Sales order we have maintained sales tax percentage instead of 4% we haved maintained 12%. and delivery and billin also been done. after all FI posting to AR we came to know that we have maintained sales tax % wrongly, Now we need to
    rectify this sales tax enty only. Is it possible thoruh Creditt memo process and differential amount should be post to subsequest accounts automatically instead of adjusting though FI side manually.  Kindly suggest me how we can rectify through SD flow
    (both rectification entry for Sales tax and customer value adjustment)
    Kindly do the needfull

    Just for information, check following SAP Notes, these may assist you in understanding:
    - Note 542862 - FAQ: Country Version India (CIN) General MM queries
    - Note 952441 - CIN: General Clarifications for CIN - SD
    - Note 535616 - FAQ: Country Version India (CIN) General SD queries
    Also, refer following thread:
    - Credit Memo for Tax
    Thanks & Regards
    JP

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

  • Decimal conversion of Sales Tax in 'SPARE PARTS SALE INVOICE' ( smart form)

    Hello,
    I am displaying a the value of the Sales Taxc in 'SPARE PARTS SALE INVOICE'. (in Smart Form)
    The field(which holds the Sales Tax value is 'KWERT' -LBBIL_INVOICE-IT_KOND ), with datatype 'CURR', reference table 'KOMK' and reference field 'WAERK'.
    In my smart form,i have declared a variable 'SALES_VALUE' of datatype 'KWERT' and reference field 'IT_PRICE-WAERK' (LBBIL_INVOICE-IT_PRICE), where 'WAERK' is the SD document currency.
    Now when i display the field 'SALES_VALUE' i get 735.00 , whereas the original value in the field is 73.5
    how to correct this and where am i wrong ?
    Thankyou for yur time and really appreciate the help.
    Shehryar

    You are using currency fields that reference a currency code. Most currencies in SAP have two decimal places. Dividing by 100 will work in most cases. Ideally you should get the CURRDEC value in table TCURX for the currency you are working with... then divide by 10 that number of times.
    example-
    USD, 2 decimals, divide by 10 twice.
    There is a function module that will do this for you. Can't think of the name...???

  • Deduction of Sales Tax

    Dear All,
    We have new Tax policy according to which we have to deduct 16% sales tax for the vendors who are not registered with tax authorities. For example we procure services of $100 from an unregistered vendor then at the time of invoice we need to have follwing accounting entries:
                         Expense        Debit $100
                         Vendor                                 Credit $84
                         Tax Liability                          Credit $16  (16% of 100)
    Tax will be paid to the Government at the end of month.
    Kindly suggest how can i handle effeciently it in SAP. Should i need to create some special Sales tax code, with-holding tax or should i use some condition type in PO.
    Thanks,
    Shahzad Shakoor

    Thank you for your reply.
    In case we have with-holding tax of 16% then lets suppose we have a services of $100 then at the time of invoice well have following accounting entry:
               Expense           Debit $100
               Vendor                           Credit $100
    and at the time of payment with-holding tax will be deducted. This will record $100 in expense but our requirement is to debit $84 in expense and credit $16 in tax liability.
    Looking forward for solution.
    Regards,
    Shahzad Shakoor

  • Origin of Sales Tax ID Number in billing document

    Hi
    In the billing Header, Taxes, there is a field "Origin of Sales Tax ID Number". Can you pls. guide me what is the mean of this field and how the value for that particular field is detemined.
    with regards

    Hi Lin
    The field "Origin sls.tax no." actually indicates that from where the VAT registration no. in Billing Document is coming. If you check the F4 help of this field then you will find that there are different option like - from Ship to party, Payer or Sold to Party etc. The determination rule is maintained in customising at IMG> Sales and Distribution>Basic Functions -->Taxes -->Maintain Sales Tax Identification No. Determination.
    Hope this will clear your doubt.
    Regards
    Amitesh Anand

  • Customization for Origin of sales tax ID number

    hello,
    I am trying to understand how Tax is being determined according to the field "Origin of sales tax ID number" which get to the sales order and Billing document.
    I have a situation where the value of this field in the Billing doc is different then the Order and it is has different options. sometimes "sold-to" sometimes "ship-to".
    Which customization affect the value of this field in the Billing document?
    Regards,
    Tomer Zimmerman

    Hi Tommer,
      Check the path:  spro-sd-basic func---taxesmaintain sales tax ident  no.
      This field is used to control determination of the VAT registration number in the order and the billing document.
    It is linked to determination of the tax classification.
    If BLANK is set, then the standard prioirty ruls apply, as follows:
    1. If PY has a VAT ID no. and PY <> SP, then the tax number and tax classification are taken from PY (the SH is no longer relevant).
    The tax number is taken according to the 'tax country of destination'.
    2. If 1 does not apply:
    If SH has a VAT ID no. or SP has NO VAT ID no., then the tax number and the tax classification are taken from SH.
    3. If 2 does not apply:
    Tax number and tax classification are taken from the sold-to party.
    If 'A' is set, then the tax number and the tax classification are generally taken from the sold-to party.
    The tax number is taken according to the 'tax country of destination'.
    If 'B' is set, then the tax number and the tax classification are generally taken from the payer.
    The tax number is taken according to the 'tax country of destination'
    Reward points if it helps.
    Regards
    Karan

  • Sales Tax Calc (Line Item level calc versus header level calc)

    Hello,
    My company utilizes vertex to calculate sales and use tax in our sales orders that are created via resource related billing (DP96).
    We store tax code O1 using condition type UTXJ for each SD Contract.
    Condition types XR1 thru XR6 receive the sales tax calculations/amounts from vertex for EACH line in the billing request.
    See below example of calculated tax amount per line item
    Line1 of Bilreq:   NetVal  2.25     X tax rate for XR1 .05  = sales tax of 0.11  (rounded up to 2 decimal places)
    Line2 of Bilreq:   NetVal  2.25     X tax rate for XR1 .05  = sales tax of 0.11  (rounded up to 2 decimal places)
    Totals                             4.50                                                                  0.22
    When our invoice(billing document) is sent to our customer which shows just totals our customer sees:
    Net Amout:  4.50
    tax rate .05
    Sales Tax Amt:  0.22
    When our customer multiplies 4.50 by .05 they come up to 0.23
    So they are questioning why the calculation is incorrect and they want it to match to the penny.
    Anyone have any suggestions to solve this problem.
    Any help is greatly appreciated.
    Thanks,
    Ermanno Incollingo

    Hello Ermanno
    Does your pricing Procedure have condition type DIFF just after the tax conditions XR 1-6?  If not, please review standard pricing procedure RVAXUS ( Step 917).
    Also try to use condition types NETP and PNTP  as described in OSS note  80183 - Rounding.
    Hope this helps. Thanks.

Maybe you are looking for