Tax Error while posting Customer Invoice

Hello Everyone,
When I try to post a customer invoice using one of the default tax code (eg. 1O - output tax 10%), during simulation the system gives following error message with the item list as below: "Error message still exist - see error log". The error log shows following description -  Msg Type E : Item 003 must be corrected. 
Itm PK Account    Account short text            Assignment         Tx           Amount
  1 01 100253     DDS SERVICES                                              1O          8.000,00
  2 50 800000     Sales revenues - dom                                    1O         7.272,73-
  3 50 175000     Output tax                                                      1O          727,27-
Can anyone plz help me out as to why am I getting this error and what is the solution to it?
Thanks,
AMD

Dear AMD008
were you maintain properly in OB40 MWS (out put tax) relevant GL Account
Note: are you using NEW GL please conform me
Regards
shankar

Similar Messages

  • Clear Withholding tax data while posting customer invoice

    Gurus,
    I am trying to post Customer invoice document using FB01 transaction.
    If the customer has with holding tax information available in Customer Master the corresponding information is getting posted into invoice document.
    Is there any user exit, enhancement or substitution available to clear this with holding tax data.
    Please do share if any code examples on this issue.
    Appreciate your quick response.
    Thanks,
    Suneel

    Dear AMD008
    were you maintain properly in OB40 MWS (out put tax) relevant GL Account
    Note: are you using NEW GL please conform me
    Regards
    shankar

  • Tax error while posting an invoice in SRM

    We are using SRM 5.5 SP4, ECS and ECC 6.0. We are using vertex for tax caluculation and we configured the tax calculation to always occur in ECC.
    One more important point is, client has decided to use invoicing in SRM. Now the problem is we ran in to so many tax related issues and we opened OSS messages for this but SAP did not help. Let me explain the problem in detail.
    1) We used to get "Tax jurisdiction code could not be determined" error while creating shopping cart, but we implemented note 436760 and hardcoded a value and got rid of that error.
    2) When we create a SC, the copy of PO is created in ECC and vertex is called for tax calculation and tax is calculated properly based on the tax hierarchy except when you use the Shipping Address (external), so when I used the delivery address other than plant, it should calculate based on that address but it was not doing that, its calculating based on the cost object's jurisdiction code. For this problem, we have implemented ME_ADDRESS BADI in ECC, but with this BADI, it is always taking delivery address's jurisdiction code, which is also wrong.
    The tax jurisdiction determination should be from 1) Delivery address if its different from plant, else it should look in to the cost object, else storage location then plant.
    So we implemented the above logic in that BADI and there is no problem with PO taxes.
    3) When we create an invoice with reference to PO, the invoice verification program is always determining the tax jurisdiction code from plant even though the taxes on PO are calculated based on cost object, hence the IDOC is erroring out by saying there is a difference in tax.
    So we implemented the user exit and used the same logic of tax determination and its fixed now.
    4) Finally, we are trying to create invoices without PO's in SRM, here no tax calculation is happending in SRM, but when we try to post the invoice in to ECC, we are getting the following error
    "SAX processing failed on input stream#SAX processing failed when attempting to add child element to parent.  (parent element=com.vertexinc.tps.common.domain.LineItem, child element=com.vertexinc.tps.x.."
    So I am not sure how to fix this, we are at the dead end now out of ideas, so trying to get some help from experts like you about looking at this problem in a different angle. Now there are a couple of questions I can ask you
    1) Did we do something wrong by selecting R/3 as the tax calculation system, if not is it difficult to fix this error and move forward?
    2) What if we need to change the design and start calculating the taxes in SRM by connecting SRM to Vertex, will there be any new challenges? and do you have any config doc for this? Also we are implementing this rollout for US, Canada and Mexico companies.
    I would really appreciate if you can reply me with your valuable input. You can also email me if @ [email protected]
    Thanks a lot,
    Sreedhar

    Hi
    <b>It's recommended to have the same Tax related configuration data replicated in SRM system from R/3 as well.
    I don't recommeded you to go with Hard-coding of tax codes.
    We have faced similar issues with Delivery address and we have to solve it using our custom logic inside the BBP_DOC_CHANGE_BADI  and BBP_CREATE_PO_BACK BADIs.</b>
    Anyways, send the detailed business requirements to my mail which are already having with you.        )
    I will definitely help you out.
    <u>Please refer to following threads as well.</u>
    <b>sales tax gurus
    How to display country related tax codes in SRM
    e-Invoice tax calculation.
    Tax code T1 does not exist for jurisdiction code error in shopping basket
    Drill down facility not working for Tax codes ....Urgent!!!!!
    Tax Issue
    Tax Calculation
    Tax setting in Extended Classic Scenario
    Withholding Tax in SRM5.0
    IDOCS for Tax Information
    Taxes in Bid Invitation
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul

  • Error while posting vendor invoice in F-43

    Hi experts,
    while posting vendor invoice with Tax code , i am getting the following error:
    Posting is only possible with a zero balance; correct document
    Message no. F5060
    Here tax line item is not yet all displaying in simulation.
    If I posted with tax code with ZERO percentage it is posting correctly.
    where as same transaction I am able to post through transaction code FB60.
    What could be the reason?
    regs,
    ramesh b

    Hi
    Please check and correct the respective line items , because your selecting incorrect GL account with respective posting keys
    Example : You have exp gl a/c at first line items against vendor invoice posting's, normaly this vendor will post in first line item with posting key is 31 with vendor a/c and second line item 40 with exp GL a/c and same you will check any required inputs have missed out from this transactions.
    Regards
    CHOWDARY

  • Error while posting Excise Invoice

    Hi Experts,
    I have captured incoming excise invoice for an Import PO of Asset material.
    GR has been made.
    Also partial payment to vendor has been done through MIRO.
    During check it do not show any ERROR message
    While posting Excise invoice , error message is displayed "ACCOUNTING DOCUMENTS NOT GENERATED"
    and immediately current session is closed
    How to solve the problem?
    Regards
    Jai

    Hi,
    Import cycle :-
    1. MIRO-Bill of Entry
    2. Excise Invoice capture
    3. Goods Receipt
    4. Excise Invoice posting
    5. MIRO -Vendor settelement
    Tcode you used for capturing excise invoice  -   j1iex
                                  posting the excise invoice.  j1iex
    Thanks
    jai

  • J1IEX, error while posting Excise Invoice

    Dera Gurus,
    While posting the excise invoice for the invoice which has already been captured at the time of MIGO, I am getting the error message " All Part I entries have been canceled for excise invoice 5810 2009"
    I have checked the PO history and found that the GR has also not been canceled and moreover the entries are being posted in RG23A Part 1 table. The movemet type 101 has also been maintained for the updation of RG23A part 1
    The only thing that I have found  suspicious is while displaying the Excise invoice is that Quantity available for CENVAT credit is Zero. I think this field needs to populated. How does this this field gets populated.
    Regards
    Prabhjot Singh
    Edited by: Prabhjot Singh Nayyar on Jun 15, 2009 10:11 AM

    Dear All,
    I have already checked the table for the Part 1 entry, the Part 1 register is getting updated but it is now allowing me to post the Excise Invoice. As soon as I try to post the Excise Invoice, it gives me the error message " All Part I entries have been canceled for excise invoice 5810 2008 "
    Regards
    Prabhjot Singh

  • Tax error when posting vendor invoice

    Dear Friends ,
    I am posting this 3rd time, I am geting this error when poatin vendor invoice , I am geting this error in production system before GOLIVE ,when we are doing live data entry test . All the seting related to taxes has been testing more than 10times , But we are unable to find the problem . We had checked with all past messages and best possible solution in SDN ......but problem is not solved . Said error is as follows ....
    Tax code V0 country IN does not exist in procedure TAXINN
    Message no. FF713
    Diagnosis
    You entered a tax code which is not defined for the country of the company code to be posted to in the tax calculation procedure.
    System Response
    Procedure
    Check and, if necessary, correct the entry.
    Procedure for System Administration
    If it is not an input error, check and possibly change the system settings.
    To do this, choose Maintain entries (F5).
    Check whether the company code is assigned to the correct country and whether the correct tax calculation procedure has been entered for the company code country.
    Create a new tax code if necessary.
    Caution:
    Since it is possible that the tables in question are being updated at a different time on another computer, it can take a certain amount of time for the tax code to be on all local machines in client server architectures after saving the new code.
    Raghu

    hi
    go to ftxp choose tax code v0
    here in first input field give 00
    then select that field and click on gl acct tab
    here mention a gl or go to ob40 and mention gl for the acct key of that field
    try finding
    Tax code country IN does not exist in procedure TAXINN
    on SDN u will get many threads
    Tax code XX country IN does not exist in procedure TAXINN (MIRO Error)
    conclusion is u must get acct for at least one condition in the tax code
    regrads
    kunal
    award if helpful

  • Lockbox error while posting customer payments

    Hello,
    I am testing the lockbox file upload and the system was able to locate the Customer number but while clearing customer, I am getting an error saying
    No payment advices were found
    Message no. F5664
    I am trying to edit payment advice and I am getting the error as below
    Payment advice 01 10000000 does not exist for account 110006 C850
    Message no. FA006
    Please let me know why this error is coming.
    Thank You.
    Edited by: Raghavaa on Dec 26, 2011 8:17 PM

    I have found the cause and solution to this problem.
    This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
    This was resolved by splitting the IDOC into 2.
    The solution is to First post only the KNA1 segment and create the customer.
    In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”:  you would have got the KUNNR after the first step.
    Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC. 
    I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
    Cheers
    Venkat

  • Error while posting Customer with Multiple sales areas using DEBMAS05.

    Dear experts,
    We are generating IDOCS vis SAP DS for posting Customer master. The message type used is DEBMAS and basic type is DEBMAS05.  we have a requirement to create 1 customer with multiple sales areas. However, we are ending up with a strange error:  "Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1". Despite the IDOC going into status 51, the customer gets created and the 1st sales area too. the 2nd sales area however is not created!  The IDOC data definitely contains Name1, otherwise the customer would not have been created in the first place.
    As the error message is related to the Address data, I also explored upon exploring this erorr further on the lines of Central Address management where in the ADRMAS and DEBMAS have to be passed together(IDOC Serialiization).  OSS Note (384462)  provides further details about this. One Important point from the note is: 
    "As you have to specify the logical name of the sending system among other things, SAP is not able to make any default settings in the standard systems. When you use the serialization groups delivered as a standard by SAP, the address objects are imported before the master objects.Thus the sequence address data before master objects must only be adhered to if one of the following points applies to your application:
    Such fields are set as required entry fields that are only provided by the BAS in the Customizing of the customer or vendor master.
    For your customers, contact persons exist to which a private address or a different business address is assigned.".
    This is not the case in our situation, as we do not have required entry fields in customizing that are only provided by the BAS, so the error is all the more confusing and I am not too sure what the cause is.
    If someone have experienced the same issue before and have found a solution to it, kindly help out.

    I have found the cause and solution to this problem.
    This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
    This was resolved by splitting the IDOC into 2.
    The solution is to First post only the KNA1 segment and create the customer.
    In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”:  you would have got the KUNNR after the first step.
    Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC. 
    I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
    Cheers
    Venkat

  • Getting error while creating Customer Invoice Request via Web Service

    Hello,
    I am trying to create customer invoice request via web service.
    But I am getting the error message "No scheme configuration found for scheme '&CIRHP&' " continuously.
    It is working fine in reference tenant. But using the same payload its giving error in another tenant.
    Can you please tell me what is the root cause for this error?
    I have included the payload used in the prototype tenant(Payload.txt) and screen shot of the error.
    Thanks and Regards,
    Sriram

    Hi,
    Check the WSDL file is wellformed or not..You can test it using tools like XML Spy.
    Might be the attribute tag is missing something..If WSDL file is correct then, create proxy by selecting the WSDL file from local machine..
    Regards,
    Sunitha

  • Tax error while posting MIRO

    Hi All,
    Im currently facing following prob "While in MIRO posting, error coming as tax procedure V1 not maintained in TAXEXL" .
    Pls let me know how to go ab taxation prob ??

    Please check procedures maintained in the tax type mentioned. If V1 is given. If not please assign input tax.
    Hope this will help.

  • Error while posting MM invoice.

    We are trying to post and Rack purchase Invoice using "BAPI_INCOMINGINVOICE_CREATE" but the BAPI fails and the error message that we are getting is "Field Material is a required field for G/L account 3862 21201000". We checked the GLACCOUNT data that is getting passed into the BAPI but there is no material field available in the structure. Even posting online using MIRO returns the same error.
    Just to give you a quick background on the issue with MATNR. The automatic posting is generating an entry to account 21201000, which is set to require MATNR on the GLACCOUNT posting details. Online in core MIRO the MATNR field does not show up, but you can set the screen variant to allow it to show and therefore enter a value, however, even if you do this if you attempt to cancel the invoice with standard TCode MR8M it again fails because the MATNR is not carried through to posting. There are a couple of OSS notes that relate to this issue, but we are not sure if it will solve our problem. We need to be able to pass a value in MATNR for GLACCOUNTDATA (not MATERIALDATA) so the posting can be effected.
    Please let me know if anybody has come across this issue and a way to resolve. Any kind of help will be appreciated.

    Please look at the field status of the GL Account. I am guessing in the field status group for that GL Account, it might have material as a required field.
    Every company code must be assigned to a field status variant which can be checked at
    Financial Accounting --> Fin accounting global settings --> document --> line item --> controls -->assign company code to field status variants.
    Get that variant and go to
    Financial Accounting --> Fin accounting global settings --> document --> line item --> controls --> maintain field status variants.
    Here look for the field status group that you have assigned to the GL Account number (FS00) and see if the material is required entry or not.
    Shail

  • Error while posting USD Invoice

    Dear Experts
    Error Message is displayed and the details are as under
    *Price too low (below tolerance limit of 0.23 USD)*Message no. M8084
    Diagnosis
    The invoice price (value invoiced divided by the quantity invoiced) varies too greatly from the net order price.
    Note:
    The category of this message can be changed in Customizing for Invoice Verification. This means that you can receive a message as an error message even though it is defined as a warning message in the standard system.
    The following documentation deals with the case applicable to the standard system only.
    System Response
    The system has established that the value invoiced falls short of the expected value (quantity invoiced * net order price) by more than the tolerance for price variance (0.23 USD) set in the Customizing system.
    Procedure
    Check what you have entered and make any necessary corrections.
    Hence where shall the same can be rectified .Pls Guide
    Regards
    Veena

    Hi,
    Tolerence limits are defined at "SAP IMG > Materials Management > Logistics Invoice Verification > Invoice Block > Set Tolerance Limits", you can change the limit.
    Or you can control the Tolernace check using user-exit.
    EXIT_SAPLMRMC_001 - Customer Exit: Change Tolerance Check - Logistics Invoice Verification

  • Getting error while posting the invoice "Different Local currency "

    Hello All,
    User created Non MRP PO with CNY currency for China and cost center entered which belongs to US country.
    User posted invoice for this PO and then he understood that cost center which has been entered in the PO was wrong.
    and he tried to cancel the invoice with Tcode MR8M and with MIRO credit Memo as well.
    But getting error "Different Local currency from CNY to USD"
    How this can be solved,pls suggest.
    Thanks...
    Trupti

    hi
    please check that you might have changed the currency of PO
    please reset it and then reverse the MIRO
    Note 592312 - MIRO: Termination M8396 'Different local currency'
    Edited by: Kunal Ingale on Nov 12, 2010 8:15 AM

  • Witholding error while posting vendor invoice (f-43)

    hi friends
    Could not determine the year for TDS certificate number range
    Massage no.81017
    Diagnosis
    The excise year could not be determined for generating the numbers for TDS Certificates. The number range is linked to the excise year and not on the financial year directly
    Procedure
    Check the customizing done for the company code in the India version IMG: maintain the start month for the excise year correctly

    Hello,
    I believe the error is 8I017.
    Please check the following:
    1. Goto transaction SM30, view J_1IINDCUS -> Maintain
    IMG -> Logistics - General -> Tax on Goods Movements -> India ->
    Basic Settings -> Maintain Company Code Settings               
    2. Create an entry here for your company code.                    
    Test the same scenario for which you got the mentioned error.
    I hope this helps.
    Lucas Michel

Maybe you are looking for