Site Tools

User Tools


Recommended Best Practices for Easy Reporting in GSTR Forms

  • Enable tax reporting date (VATDATE) and configure the same based on your needs so that it is updated for all documents with Goods and Service Tax (GST) lines. This would help determine the tax reporting period during GST reporting.
  • Use a two-character unique prefix per official document class to enable determination of number ranges to be filled in GSTR reports. The document class should be a representation of the ‘nature of document’ as defined in GSTR forms number range section.
  • Ensure that Invoice reference is filled for each credit/debit memo transactions (MM/SD/FI) as it is required for reporting in GSTR forms.
  • While with TAXINN, it is possible to do all transactions in MM and SD with very few tax codes, it is recommended that you use different tax codes to differentiate certain business scenarios that are required to be identified from GSTR reporting perspective. For example, Import of goods, import of services, Reverse charge scenarios, Nil rated, exempted and non-GST supplies. This will enable easy data preparation for reporting.
  • Ensure that the business place (BUPLA) is filled and unique in a document. For example, in MIRO/FB60/FB70 and similar transactions, if BUPLA is not filled at the header, the system determines BUPLA from the plant of last line item. This must be unique as the same is used to determine tax G/Ls (BUPLA-wise determination).
  • For advance payment postings (F-29, F-48) and similar other FI transactions, make sure to capture BUPLA at line items. The same from first line item is passed for tax G/L determination.
  • Ensure that an HSN/SAC code is maintained in master data and hence determined for each line item in invoice transactions. This is required for HSN-wise summary reporting in GSTR forms.
  • If you are using business place wise tax account determination, a dummy G/L account is still required to be maintained in OB40 for technical reasons.
  • Maintain all the Pricing Procedure GST Condition Types in the view J_1IEXCDEFN. This is mandatory to determine the output taxes.
  • Maintain and use the customer tax classifications as suggested by SAP master configuration note 2385575. This information is used to determine the GSTR invoice type classification Regular / SEZ / Deemed Export etc…
  • Maintain and use the material tax classifications as suggested by SAP master configuration note 2385575. This information is used to determine the GSTR Exempted / Nil / Non-GST Amounts…
  • Maintain separate Seq. No. for Tax Categories CGST, SGST, IGST and UGST condition types in OVK1.
  • Maintain the capital goods indicator as suggested by SAP in the SAP Note. This information is crucial while filing GSTR2.
  • Make sure that you are capturing the Shipping Port, Shipping Bill & Date details for all the exports.
  • Make sure that you are capturing the information on whether the SEZ exports are with pay or without pay for all the SEZ supplies.
  • Make sure that you capture the eCommerce marketplace TIN number for all the sales through eCom Marketplaces like Flipkart / Amazon etc…
Last modified: 2018/05/05 01:59 (external edit)