OptiGST

We can fetch data from SAP to OptiGST solution using a process called batch update, this can be scheduled on a weekly, daily or monthly basis.

/n/obiz/zgst

The following are the various registers available:

1. Sales Register
2. FI Register
3. Purchase Register
4. Stock Transfer Register
   

• Check whether the document is a backdated entry, if yes re-run the Batch update process
• Confirm whether the document type and transactional code is already configured, if no, then it is required to configure the Tcode and Document type
• To also check the Tax code & Condition type or G/L code is configured in OptiGST
• To also check the Tax entry of the document posted in SAP
• To also check whether the Business Place is maintained for the document in SAP

Yes, data from the GST portal is fetched and compared with the OptiGST data. This will help to reconcile the records before Saving to GST portal.

• If Yes- documents from GSTR1 return will reconcile with GSTR1 fetch data (portal data with E-invoice reference)
• If No- Data will be confirmed without reconciliation

• S - Data will not push to the portal (Complete match)
• T - Data will not push to the portal (Amount Tolerance applied)
• I - Data will be pushed to the portal (Document available in GSTR1 not available/auto-update fail in E-invoice)
• D - Data will be pushed to the portal (Document available in E-invoice and not available in GTSR1. Document will be deleted from the portal)
• M - Mismatch (Data is not matched with E-invoice data - require analysis)

These three types of status will be returned as responses in common.

P – Process successfully (All documents send to portal successfully)

PE – Processed with Errors (Few documents rejected by the portal, the same can be viewed from Error log report)

E - Error (No document processed to portal/Error in JSON file)

• If the HSN summary quantity is zero and any of the UQC is not matched with GST portal UQC, then HSN will not be updated in the portal.
• If the quantity is negative, also then the HSN will not be updated to the GST portal

Document can be parked for GSTR1 filing with parking feature provided in Sales register all sales register and FI register.

The parked document can be un parked using Unpark sales documents report. The un parked documents will be fetched to GSTR1 return.

These are 3 different scenarios, which can occur while GSTIN filing

1. Missing GSTIN No.- If the GSTIN no. is missing, OptiGST find it out in the Validation stage itself. Then you can correct the Masters and file GST returns
2. Wrong GSTIN No.- This error can be found out only, once the document is filed to the GST portal and returns an error. For this issue, the customer can get the correct GSTIN no. from the Customer and the correct the Master and file the returns
3. Inactive GSTIN no.- This error can be found out only, once the document is filed to the GST portal and returns an error. For this issue, we have to inform the customer to file his returns. It is a business call, how to handle this scenario

Please check your Customer Tax classification in SAP. If the logic is based on the GSTIN no., please check if the GSTIN no. is maintained for the Customer.

To check the Customer Tax classification in SAP or If the logic is based on the GSTIN no., please check if the GSTIN no. is maintained for the Customer.

Check your Material Tax classification in SAP. If the Material is not classified as GST relevant it will not be displayed in Tab -4.

• Check the Batch Update Date in OptiGST – To check whether the Batch Update scheduled has been updated till that date. If no, run the Batch Update Manually.
• Check the Document Date in SAP- If the Document Date is of the previous period.
• Check the Customer Tax classification in SAP- Check if the Customer is classified as registered.
• Check the Material Tax classification in SAP- Check if the Material is classified as GST relevant.

Yes, it is required to manually Authenticate with OptiGST to integrate with the GST portal. Since there is a relevance of OTP- One-time Password enabled by the GST system. This cannot be bypassed.

The various Tabs of OptiGST GSTR-1 returns are:

Tab 4 – B2B Invoices

Tab 5 – B2CL

Tab 6 – Exports, Deemed exports, and SEZ

Tab 7 – B2CS

Tab 8 – NIL, GSTE, NGST

Tab 9 – CDNR, CDNUR

Tab 10- Amendment of Tab 7

Tab 12 – HSN summary

Tab 13- Doc issued

1. B2B Credit note should be cancelled by Seller and removed from auto-populated data, and a fresh B2C Credit Note be issued and reported under CDNUR section of GSTR1?
   (OR)
2. Seller should file a B2B Amendment with reduced taxable value and reduced tax with the date when Customer was Active.

Yes, OptiGST does a reconciliation with the GSTR-1 fetch data and OptiGST data and those documents which are missing in SAP, will be marked for deletion from GSTR-1 returns.

Steps to do Vendor Reconciliation

Step 1: GSTR-2A fetch

Step 2: Set /Check the Rules for Reconciliation

Step 3: Update Process

Step 4: Verify Vendor Reconciliation Report

1. A- Accepted (Both the GSTR-2A data and SAP data is Matching)
2. I- Insert (Document is not there in GSTR-2A)
3. M- Modified (Both the GSTR-2A data and SAP data is Matching with some Modification)
4. P- Pending (Document is not there in SAP)

1. Steps to fetch auto-populated GSTR 1 data.
   Step 1: Authenticate with GSP and GST Portal
   

Step 2: Select GSTR-1 Fetch

Provide required data ((B2B, CDNR etc)

• To check the Customer Tax Classification in SAP
  (OR)
• If the identification of Exports is based on the Tax code in OptiGST, check whether the correct Tax code is used for the Export scenario.