FAQs

Integration Debug Guide

Data Mismatch (Purchase Register)

👉 Check SAP PR Extraction with Base Data .

👉 SAP PR Extraction Program vs Data Overview- ingestion error or multiple voucher or Invoice having the same details . After the above also check for document type b2bur which gets ingested and has tax values but doesn't become part of reconciliation. 👉 Documents ingested and were ITC actioned after running reconciliation, user then deleted the same from the data overview .

Data Mismatch (2b)

👉 Amendment data and original both appearing in 2B download but in reconciliation we only store original values. 👉 If supplier amends MY GSTIN we store both amendment and original docs on Reconciliation. 👉 API quota exhausted and user pulling 2b data ,data pulled partially. 👉 ISD data is part of 2B govt data, but we don’t store same in reconciliation.

Reconciliation Failure

👉 OTP is inactive and user triggers reconciliation, since OTP is inactive and data cannot be pulled and reconciliation cannot be triggered Message for same should appear on Ui “ OTP is inactive please activate OTP"

👉 “400 internal Server error” SAP connectivity issue

👉 Reconciliation triggered from long(Time out issue), then try retrigger( on SAP it should fail with time and option to retrigger for same should appear)

👉 Multiple reconciliation triggered at same time from ERP

Payment blocking FAQs

👉 Invoice and Hold JV is posted, but invoice is supposed to be released 👉 Multiple Hold JVs got created for the same invoice/voucher - why this can happen

👉 Payment hold JV was not created in SAP even though invoice is missing/not compliant

-> Check recon has been triggered from SAP or not

-> Check invoice status in recon table in SAP

-> Check invoice status in the payment block table in SAP. If there are any config errors while posting JV, the message column will have the error message