Onboard every customer and vendor with confidence
Customers and vendors are validated and approved before anyone transacts with them. GSTIN, PAN and CIN are checked, verification is recorded, duplicates are caught, and changes to bank details and other sensitive fields need approval — working with SAP Business One’s own Business Partner Master Data.
Capabilities
Identifier checks at entry
GSTIN, PAN and CIN / LLPIN formats and the GSTIN check character are validated; the PAN inside the GSTIN and the GSTIN state code are compared with the request.
Recorded verification
A verifier records the result from the official portal with evidence and a validity period (GST 30, MCA 90, PAN 180 days). The verifier cannot be the requester.
Duplicate control
One active BP per GSTIN per role is a hard block; similar names, the same PAN and open requests are flagged as possible duplicates for the approver.
Approval matrix
Requests route through the BP Approval Matrix; self-approval stays off unless the settings allow it.
Governed changes
Only one open change request per BP; bank, tax and credit changes need approval, and discrepancies are shown to the approver.
SAP’s own save rules first
At Submit, SAP’s trial save checks the business partner, so SAP’s own refusals appear before the approvers spend time on it.
Correct, Retry or Cancel
A request SAP refused after approval can be corrected, retried or cancelled, and its GSTIN, PAN and code claims are released when cancelled.
How PartnerGuard works
- RequestA new business partner or a change is requested with identifiers first.
- VerifyIdentifiers are checked and verification is recorded with evidence.
- ApproveThe approval matrix routes the request; discrepancies are accepted or rejected.
- CreateThe approved business partner is created or updated in SAP.
See it with your own data
A live demo in your SAP Business One version, with your item groups, business partners and batches.