1. Commodity/Sub-commodity does not exist for selected purpose code or commodities not assigned to your TIN
This error occurs due to mismatch in Tally data on three fronts:
· Commodity code
· Sub-Commodity Code
· Purpose code
The commodities enabled for the dealer in his Login are not the same as the ones entered in Tally.
To rectify the same,
Step 1: Verify the commodities enabled for the dealer
Login to VAT website > Sales > Interstate > Upload Xml > View Reg. CST Commodity details
Table No. 1:
As is evident above, all the three details mentioned below need to match for successful upload:
· Commodity Code
· Sub-Commodity code
· Purpose Code
E.g.: Purpose code: 1 (Resale), Commodity code: 80 (Spices), Sub-commodity code: 2 (Clove)
Any wrong combination of above 3 details in Tally leads to this error.
Hint: If sub-commodity details are not available, enter code as 1
Step 2: Creation of VAT Commodity in Tally
Gateway of Tally > Inventory Info > VAT Commodity > Create
Step 3:
Tagging individual stock Item to VAT Commodity
Gateway of Tally > Inventory Info > Stock Item > Alter
OR
Tagging multiple stock Items to VAT Commodity:
Gateway of Tally > Inventory Info > Stock Item > Multiple stock item > Alter > All Items > Set Commodity (Ctrl+C) > Select the commodity and it gets updated to all stock items.
Step 4: Entry of Purpose code in interstate transaction:
During passing of interstate purchase transaction, the relevant purpose code (1 to 7) needs to be selected, based on the purpose code enabled in dealer login for the given Commodity and sub-commodity combination:
In above example, for Commodity code of 86 and sub-commodity code of 1 the relevant purpose code is 6. (Refer Table No.1 above
Verify the Commodity, sub-commodity and purpose code combination in e-VAT annexures report with dealer portal details.
2. The Invoice details do not exist
This error occurs during upload of Debit and Credit notes, if the corresponding original purchase and sales statements are not already uploaded and saved. If Debit or Credit Note pertains to original Invoices in months previous to May 2014, such Debit/Credit Notes need not be uploaded. Alternatively, first upload only such original Invoice, save it and then upload the corresponding debit and credit notes.
Tip:
1. When uploading Debit/Credit note, ensure that first the corresponding purchase/sales are already uploaded
2. If some of the Debit/Credit notes pertain to previous months (April 2014 and earlier), make such vouchers as optional and upload the remaining Debit/Credit Notes. After successful upload, you may regularize these optional Debit/Credit Notes.
3. Please correct the following Invoice Details: Total mismatch error
Total mismatch error could be due to multiple reasons, hence, check for the following:
1. If VAT is not enabled and VAT classifications (Ex: 5.5%, 14.5% etc.) are not used in Tally and Annexures are generated, this leads to entire voucher total sitting in total value column (no bifurcation of net value, tax charged and other charges). Such Annexure when uploaded, gives total mismatch error (as net value itself is blank).
2. Check the grouping of “Round-off” ledger and ensure that it is grouped under Indirect Expense/Income.
3. In case of ledgers like freight/courier charges/ hamali /transport charges, etc., ensure that the ledger is grouped under Indirect Expense/Income.
4. If total mismatch error is for transactions with multiple tax ledgers (Excise/Service Tax/TDS, etc.) verify the completeness of entry (assessable values are entered and proper classifications selected).
5. In case of ledgers classified under Duties and Taxes Others (Ex: Entry Tax, Cess in APMC, etc.) and if it does not form part of assessable value, total mismatch occurs. These values form part of other charges in the Annexure report but are not exported in Xml. This issue will addressed in the next stat release. (Workaround: Export to Xml converter and rectify only such vouchers where mismatch has occurred, convert to Xml and upload manually).
The above steps will ensure total mismatch errors are addressed effectively. If errors still persist, verify the totals in respective Annexure before generating Xml and verify totals in exported Xml with respect to those Invoices for which there is total mismatch.
4. Please correct the following Invoice Details: Debit or Credit Note number already exists
This error occurs if same batch of Debit / Credit Notes are being uploaded for a second time onto the portal. In such case, the first batch already uploaded should be deleted in the portal before uploading again.
For some of the dealers, upon Login to KVAT portal, a pop-up message appears asking the dealer to update his e-mail and Contact number. In such case, the dealer has to update the details on portal first and subsequently upload Annexures from Tally.
6. Login Failed / No internet connection / Unable to reach server / cannot connect to KVAT site
Please verify internet connectivity and the Login Id and password and re-enter. If problem still persists, try after some time since this error occurs as department server is busy or under maintenance.
The TIN number which you have provided for the company in Tally in F11: Features >F3: Statutory>VAT TIN (Regular) should match with the TIN number of the username and password you have entered in the department website.
Hence, please ensure that both the TIN Numbers (i.e. TIN Number provided for a Company in Tally and TIN number for which you have provided Username & Password in Portal) are the same.
The new KVAT e-UPaSS has been introduced from May 2014. Hence, for Interstate purchase transactions related to April 2014 or earlier, a dealer has to manually upload the details using Direct entry method as per the navigation depicted below:
9. Already data has been submitted for this return period!
The error occurs if data has been already uploaded and approved for the concerned Annexure for the return tax period. Hence, precaution needs to be taken before approving, as after approval, it cannot be deleted or modified by dealer.
10. The 'InvCur' element has an invalid value according to its data type.
This error is related to Invoice Currency (Forex amount) field being left blank. This error occurs if dealer has not enabled multi-currency (F11: Accounting features, Allow multi-currency). Foreign currency needs to be created (Accounts Info > Currencies > Create) and transaction is to be entered with foreign currency and exchange rate details filled-in.
In transaction, all fields need to be filled as is depicted in below screen shot.
11. Xml not well formed Error.
This error occurs due to multiple reasons:
1. If the Xml is generated using Tally.ERP Release 4.8 or lower. Since the entire Xml schema has been altered in e-UPaSS, the respective Annexures need to be generated from Release 4.9, Stat 233 and higher versions only.
2. For purchases made from and sales made to URD (Unregistered) dealers, the corresponding Debit / Credit note entries against URD are not supported in the current version of e-UPaSS module of the department.
1 comments:
Write commentsCommon Errors And Solution During Direct Upload Of Karnataka E-Vat Annexures In Department Portal Through Tally Erp 9. - Tally Training >>>>> Download Now
Reply>>>>> Download Full
Common Errors And Solution During Direct Upload Of Karnataka E-Vat Annexures In Department Portal Through Tally Erp 9. - Tally Training >>>>> Download LINK
>>>>> Download Now
Common Errors And Solution During Direct Upload Of Karnataka E-Vat Annexures In Department Portal Through Tally Erp 9. - Tally Training >>>>> Download Full
>>>>> Download LINK