What the Automation of Anti-Social Force Screening Asks: The True Nature of “Business Partner Risk” for SMEs

WACTO announces an anti-social force screening tool, and ELEVAN introduces a supplier management platform. News like this indicates the accelerating “toolization” and “automation” of business partner risk management. Many SME owners may feel, “Perhaps it’s time for us to introduce something too.” However, we urge you to pause and think here. Is tool adoption the true goal? Or is it merely one “implementation device” for solving a larger design challenge?

The “Design” Questions to Ask Before Tool Adoption

The background to the focus on tools for anti-social force screening and supplier compliance management lies in the trends of regulatory tightening and digitalization. However, before considering tools, we need to re-examine our fundamental design philosophy regarding our company’s “business partner risk.” This is because it falls into the realm of management judgment—not merely management “to avoid violations,” but “what risks to tolerate, to what level, while growing the business.”

In many companies, business partner risk tends to be discussed as a binary opposition of “zero or one hundred.” The principle that “transactions with anti-social forces are absolutely unacceptable” is a given. However, when implementing that principle in practice, keeping all business partners perfectly “clean” incurs virtually infinite costs in reality. The key is to perceive risk not as 0 or 100, but as a continuous quantity from 1 to 99, and to design an acceptable level. Tools are merely “devices” for efficiently executing that design.

Shifting Perspective from “Management” to “Design”: 3 Practical Steps

So, how can we change business partner risk from a “subject of management” to a “subject of design”? Let’s consider the following 3 steps.

Step 1: Define Your Company’s “Risk Tolerance Zone”

First, verbalize what kind of business partner risks your company can tolerate, and to what extent. This varies greatly by industry, business scale, and stakeholders (financial institutions, major clients, etc.).

• Risks to absolutely avoid (Risk Tolerance 0): Direct or indirect involvement with anti-social forces, companies that repeatedly commit serious legal violations, etc. This is a common line for many companies.
• Risks that can be tolerated while managing them (Risk Tolerance 1–50): Unstable financial condition, lack of internal controls, past history of minor compliance violations, etc. These risks can potentially be covered by transaction terms (e.g., strict prepayment, strengthened contract clauses, setting audit rights).
• Risks that can be actively taken (Risk Tolerance 51–99): Promising startups in emerging markets, ventures with technology but immature management systems, etc. This is a judgment to bear a certain level of operational risk in exchange for high growth potential.

The first step is for management to agree on and document this “tolerance zone.” Introducing a tool without this foundation will leave you reacting to every single “risk” the tool detects.

Step 2: Design a “Transaction Architecture” According to Risk

Based on the risk tolerance defined in Step 1, design the very structure of the transaction. This is a collaborative effort between legal and business departments.

• High-risk tolerance partners: Stricter contract clauses, change payment terms from prepayment to post-payment/success-based fees, incorporate regular audit rights. Set a cap on transaction amount.
• Medium-risk tolerance partners: Use standard contracts, mandate quarterly or semi-annual performance reports. Require key person guarantees.
• Low-risk tolerance partners: Conduct transactions with simple contracts or purchase orders, perform credit management as usual.

The key is the idea of not deciding “to transact or not” based on risk level, but changing “how to transact” according to the risk level. This is “design” thinking.

Step 3: Position the Tool as an “Execution Device”

Only after reaching this point does considering tools like those in the opening news become meaningful. The role of a tool is to execute the designed risk management process efficiently, reducing human error.

• Tools like AntiSocial Checker: Automate the limited but crucial role of screening for “absolute avoidance risks” when starting new transactions. Attempting to use them for continuous monitoring of all partners can worsen cost-effectiveness.
• Supplier management platforms like ReposiTrak: Streamline the collection and update management of compliance documents (insurance certificates, certifications, etc.) for numerous suppliers, especially in manufacturing or retail. This allows human resources to be allocated to higher-level risk analysis or transaction term negotiations.

The criterion for tool selection is, “To what extent can it support the risk tolerance zone and transaction architecture our company has designed?” The key is not the number of features, but whether it aligns with our company’s design philosophy.

Common Failure Patterns: 3 Traps to Fall Into with Tool Adoption

Tool adoption lacking design thinking leads to failures like the following.

1. Decision Paralysis from a Flood of “Detected Risks”: When a tool detects many “yellow flags” or “minor risks,” treating them all as equally serious problems leads to a series of decisions to halt transactions. As a result, business opportunities are lost, and conflict deepens between procurement and legal departments.
2. Decline in “Thinking Ability” Due to Tool Dependence: Blindly trusting the tool’s judgment results leads to losing the habit of considering the essence of the underlying risk (why did that risk arise, what is the real impact?). It can even have the counterproductive effect of dulling risk sensitivity.
3. Cost Bloat and Loss of Flexibility: After introducing a high-functionality tool, high license costs disproportionate to the company’s transaction scale or risk profile accumulate. Also, the company’s operations become constrained by the tool’s workflow, losing the ability for agile transactions.

The State of the Manager After Reading (After)

Having finished this article, when you see news about anti-social force screening or supplier management, you should be able to think in the following ways, rather than simply wondering “Should we adopt it?”

• “First, let’s define our risk tolerance zone in light of our company’s transaction strategy.”
• “To realize that design, which part should the tool handle? Where should human judgment remain?”
• “Is this tool a device for stopping transactions, or a device for safely expanding transactions?”

Governance is not a brake to stop the business, but the chassis design to run faster and farther. Business partner risk management is part of that. Tool adoption is merely a milestone in materializing that design philosophy. Designing your company’s “way of running” and choosing the optimal device to help realize it. That very perspective is the core governance capability for SMEs to maintain competitiveness and grow.