Sovos Wiki
-
GST Compliance Solution
-
- GSTR 9 Structural and Business Rules
- ITC 04 Structural and Business Rules
- GSTR 8 Structural and Business Rules
- GSTR 7 Structural and Business Rules
- GSTR 6 Structural and Business Rules
- GSTR 3B Structural and Business Rules
- GSTR 2 Structural and Business Rules
- GSTR 1 Structural and Business Rules
- Validation Rules of Sovos GST Compliance Solution
-
- Group Level Reports
- PAN level report for 2A (B2BA and CDNA)
- (Group Level) List of common invoices in Supplier Only and Purchaser Only across the group, includes across taxpayer GSTIN, across financial year and across regular and amendment section
- List of Invoices in Supplier Only and Purchaser Only across the group
-
- GSTIN Level Reports
- List of invoices which have been uploaded by taxpayer in the filing period which is earlier than supplier filing period
- (GSTIN Level ) List of common invoices in Supplier Only and Purchaser Only across the group, includes across taxpayer GSTIN, across financial year and across regular and amendment section
- GSTIN Level List of invoices present in one financial year which belong to previous financial year as per invoice date
-
- Value added Facility – Filter Facility
- Value added Facility – Send single and bulk Mail to Vendors
- Net Vendor Summary
- Post Action Summary
- Original Supplier Only Amended
- Manual PO SO Movement
- Purchaser Only
- Supplier Only
- Invoice Reconciliation Results
- Reconciliation Summary and Category wise Vendor Summary
- Snapshot of Recon Results
- Probable invoice number match concept
- Introduction to Recon Results
- 2P Summary
- Deemed Match
- Mismatched Invoices
- Matched invoices
- Show Remaining Articles (2) Collapse Articles
-
E-invoicing Solution
-
E-way Bill Solution
-
Taxpayer APIs
-
Garnet
Probable invoice number match concept
Probable invoice number match concept
In smart reconciliation, one more important scenario related probable matches based on invoice numbers get covered. So here in probable matches we will derive the invoice number after removing “prefix to invoice number as 0”, special characters like “ / ” and “ – “ in invoice numbers.
So the mismatches which come due to “special characters like / or – and 0 prefix to invoice number” will get minimise and got categories as probable matches. Based on this derived invoice number your invoices further get reconciled as Match/Value mismatch/invoice mismatch categories.
The invoices lying in Supplier only or Purchaser only categories, you will get the probable invoice no. matches for that particular counter-party. If there are more than one probable matches then you need to select one with which is you want to do reconciliation. Based on this selection your invoice will get categories further as Match / value mismatch / invoice mismatch. Also the one that you have not selected will get categorised as supplier only or purchaser only.
Now this concept of probable invoice number match is extended in Advance reconciliation to cover maximum scenarios of invoice no. mismatches. To know in details see Fuzzy invoice no. logic of Advance reconciliation.
As you know in Sovos GST Compliance solution, reconciliation is auto-triggered. Thus whenever GSTR 2A is downloaded from GST system or GSTR 2 data is uploaded in Sovos GST Compliance solution, the invoices are compared and the results of comparison are displayed.