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 minimize 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 categorized 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 IRIS Sapphire, reconciliation is auto-triggered. Thus whenever GSTR 2A is downloaded from GST system or GSTR 2 data is uploaded in IRIS Sapphire, the invoices are compared and the results of comparison are displayed.