Egisedge GSTR Solution: GSTR-2B Reconciliation Demo

GSTR-2B is the monthly statement of input tax credit available to a business, based on what its suppliers have filed. Matching it against your purchase register is slow and error-prone when done in spreadsheets.

In this demo we show the Egisedge GSTR Solution reconciling GSTR-2B data with purchase invoices from the ERP. We walk through importing data, automatic matching, reviewing mismatches by reason, following up with suppliers, and producing a clean position before you claim credit. The same solution also covers GSTR-2A and GSTR-3B.

At Policybazaar, Egisedge built a GSTR 2A/2B/3B solution covering 2A reconciliation, 2B matching and 3B preparation. Egisedge also built a vendor portal with KYC and GSTR-2B checks there.

This demo uses sample data only. Always confirm tax positions with your tax adviser.
Learn more: https://egisedge.com

#GST #GSTR2B #OracleERP

Transcript

[Scene: Presenter on camera. On-screen title: "GSTR-2B reconciliation demo".]

PRESENTER: Every month, finance teams in India face the same task. You download GSTR-2B from the GST portal. You compare it with your purchase register. You find what matches, what is missing and what is wrong. Then you decide how much input tax credit to claim. In spreadsheets, that takes days. In this demo, we show how the Egisedge GSTR Solution handles it.

[Scene: Split screen. Left: a long spreadsheet with highlighted rows. Right: the GSTR Solution dashboard, clean. Label: "Sample data".]

PRESENTER: A quick reminder. GSTR-2B is a statement of input tax credit available to you, based on the returns your suppliers file. It is generated for each return period. Your purchase register comes from your ERP. The two will rarely match line for line.

[Scene: Chapter card, "Import 2B and purchase data".]

PRESENTER: Step one. Bring the data in. We load the GSTR-2B file for the period, and we pull purchase invoices from the ERP. In this demo, the ERP is Oracle Fusion, and the invoices come from Payables.

[Scene: Screen recording. Upload screen for the 2B file. Then a data pull screen showing invoice count, period and GSTIN. Blur any real GSTINs; use sample numbers.]

PRESENTER: The solution checks the files as they load. Wrong period, wrong GSTIN, or missing fields are flagged before matching starts.

[Scene: Chapter card, "Automatic matching".]

PRESENTER: Step two. Run the match. The solution compares supplier GSTIN, invoice number, invoice date, taxable value and tax amounts. It also handles common differences, such as invoice numbers written with extra characters or leading zeros.

[Scene: Matching summary screen. Tiles: Matched, Partially matched, In 2B only, In books only.]

PRESENTER: Here is the summary. Most invoices match. The rest fall into three groups. Partially matched, where values differ. In 2B only, where the supplier reported an invoice you have not booked. And in books only, where you booked an invoice the supplier has not reported.

[Scene: Chapter card, "Review mismatches by reason".]

PRESENTER: Step three. Review the exceptions. Each mismatch has a reason, so your team can work through them by type instead of line by line.

[Scene: Exceptions list grouped by reason: "Tax amount difference", "Date difference", "Invoice not in books", "Invoice not in 2B". Click into one.]

PRESENTER: Take this one. The taxable value matches but the tax amount is different. The detail view shows both records side by side. The user can accept the difference, correct the booking in the ERP, or mark it for supplier follow-up. Every action is recorded with the user's name and time.

[Scene: Detail view with the action buttons. Click "Supplier follow-up".]

[Scene: Chapter card, "Supplier follow-up".]

PRESENTER: Step four. Follow up. Invoices in books but not in 2B usually mean the supplier has not filed, or filed with an error. The solution groups these by supplier, so you send one message per supplier with the full list, instead of many separate emails.

[Scene: Supplier follow-up screen. One supplier selected, list of five sample invoices, a draft email preview.]

PRESENTER: When the supplier files, the next 2B cycle picks it up and the item moves to matched.

[Scene: Final position screen showing eligible credit, credit on hold, and items pending.]

PRESENTER: The result is a clear position for the period. What you can claim now, what is on hold, and why. That feeds your GSTR-3B preparation. The same solution also reconciles GSTR-2A.

[Scene: Chapter card, "Results at Policy Bazaar". Simple text slide, no logos other than as published on egisedge.com.]

PRESENTER: At Policy Bazaar, Egisedge delivered a GSTR 2A, 2B and 3B solution. It reduced filing time by 95 percent and achieved 98 percent calculation accuracy. We also built a KYC and GSTR-2B vendor onboarding solution there, which made vendor onboarding 70 percent faster.

[Scene: Presenter on camera.]

PRESENTER: Those are one client's results. Your results depend on your data quality and volumes. And please confirm tax decisions with your tax adviser. The solution supports the work; it does not replace professional judgement.

[Scene: Chapter card, "Recap".]

PRESENTER: To recap. Import 2B and purchase data. Run the automatic match. Review mismatches by reason. Follow up with suppliers in one go. Then claim credit on a clear position. To see the GSTR Solution with your own sample data, visit egisedge dot com or write to info at egisedge dot com.

[Scene: End card with egisedge.com.]