Supplier due diligence
Japanese Customer and Counterparty Screening
Counterparty screening is not only for suppliers. Customers, borrowers, investment targets, and business partners may also require public-source review.
Key takeaways
- Customer screening should still begin with entity identity.
- Public enforcement records may affect credit, legal, or reputational review.
- Use the relationship type to decide which records matter.
- RegBase does not replace KYC, AML, sanctions, or credit processes.
Practical workflow
- 1Collect customer legal name, Japanese name, Corporate Number, address, and website.
- 2Search company identity and public records in RegBase.
- 3Review enforcement and public-risk records by relationship relevance.
- 4Preserve source URLs and reviewer notes.
- 5Escalate to credit, legal, financial crime, or sales leadership when policy requires.
Why customers can require public-record checks
Customers can create payment risk, regulatory exposure, reputational risk, or downstream compliance concerns. For high-value or high-risk relationships, public-source screening helps teams understand whether disclosed records should affect approval terms.
The screening question is different from supplier review: you are usually asking whether the relationship creates credit, legal, financial-crime, reputational, or operational exposure.
How to interpret customer records
A customer with a public enforcement record is not automatically unacceptable. Review recency, severity, business relevance, transaction size, and whether additional contract controls or approvals are needed.
Important limitation
RegBase supports public-source screening and evidence collection. It is not a credit report, sanctions result, legal opinion, or final due-diligence conclusion.