Summary

Learn how to create and configure a decision tree in Check & Decide to automate credit, risk, and compliance decisions based on your organization's policies. This article walks you through the key configuration steps and considerations before publishing a decision workflow.


Prerequisites

Before configuring a decision tree, ensure that:

  • You have access to Check & Decide.
  • You have the appropriate permissions to create or edit templates.
  • Your organization's decision criteria and approval requirements have been defined.
  • You understand which Creditsafe data points will be used in your decision process.
  • Any required compliance, risk, or onboarding policies have been reviewed internally.

Note: Decision trees can be updated and refined over time as your business requirements evolve.


What is a Decision Tree?

A decision tree is a configurable workflow that automatically evaluates information against predefined business rules and returns a decision outcome.

Common outcomes include:

  • Approve
  • Refer for Review
  • Reject

Decision trees help ensure decisions are applied consistently and reduce manual review time.


Step 1: Create a New Decision Tree

  1. Sign in to Check & Decide.
  2. Navigate to the Templates or Decision Trees area.
  3. Select Create New Template.
  4. Enter a name and description for your decision tree.
  5. Save the template.


Best Practice: Use a clear naming convention that identifies the purpose of the workflow, such as:

  • Customer Credit Approval
  • Supplier Risk Assessment
  • New Account Compliance Review

Step 2: Define Your Decision Criteria

After creating the template, determine the criteria that will drive automated decisions.

Examples may include:

  • Credit score thresholds
  • Company status
  • Payment performance indicators
  • Financial information
  • Associated businesses
  • Sanctions or compliance screening results
  • Bank verification results
  • Custom business requirements

Select the criteria that align with your organization's risk tolerance and approval policies.


Step 3: Build Decision Rules

Create rules that evaluate each selected data point.

Examples:

Rule Example 1

If:

  • Credit score is greater than your approved minimum threshold

Then:

  • Continue to the next check

Rule Example 2

If:

  • A sanctions match is found

Then:

  • Refer for review or reject

Rule Example 3

If:

  • Required information is unavailable

Then:

  • Refer for manual review

Tip: Consider how the workflow should respond when data is unavailable in certain countries or jurisdictions.


Step 4: Define Decision Outcomes

Configure the actions that occur when rules are met.

Typical outcomes include:

Approve

The application or onboarding request satisfies all requirements and can proceed automatically.

Refer

Additional review is required before a final decision can be made.

Reject

The request does not meet the organization's defined criteria.

Clearly documenting the purpose of each outcome helps users understand how decisions are being applied.


Step 5: Configure Manual Review Paths

Not every decision can be fully automated.

For cases requiring additional review:

  1. Define referral conditions.
  2. Identify who should review referred decisions.
  3. Configure notifications, if available.
  4. Determine how reviewers will record final decisions.

Organizations commonly use referrals for:

  • High-value accounts
  • Borderline credit decisions
  • Compliance exceptions
  • Missing information

Step 6: Test Your Decision Tree

Before making the decision tree available to users:

  1. Run test scenarios using sample companies.
  2. Verify that each rule behaves as expected.
  3. Confirm that approval, referral, and rejection outcomes trigger correctly.
  4. Review the results with stakeholders.

Testing helps identify gaps or unintended outcomes before the workflow is used in production.


Step 7: Publish the Decision Tree

After testing:

  1. Save the final version of the template.
  2. Publish the decision tree.
  3. Communicate availability to users.
  4. Monitor initial usage and results.

Published templates can be reviewed and updated when business requirements change.


Reviewing Decision History

Check & Decide maintains a decision audit trail that allows authorized users to:

  • View historical decisions
  • Review decision outcomes
  • See when decisions were made
  • Identify who completed a review or approval

Regularly reviewing decision history can help validate policy effectiveness and identify opportunities for improvement.


Common Setup Questions

 

  • Does the number of daily checks impact setup time?

No. The effort required to configure a decision tree is generally based on the complexity of the decision criteria and workflow, not the volume of decisions processed.

  • Can decision rules be modified later?

Yes. Decision trees can be updated as your organization's policies, risk appetite, or operational requirements change.

  • Can compliance checks be included?

Yes. Compliance screening can be incorporated into decision workflows alongside credit and risk criteria.

  • Can I see historical decisions?

Yes. Authorized users can access decision history and audit information within Check & Decide.


Setup Notes and Best Practices

  • Start with a simple workflow and expand over time.
  • Keep approval rules aligned with documented company policies.
  • Use referral outcomes when additional human review may be required.
  • Test decision trees thoroughly before publishing.
  • Review workflows periodically to ensure they remain aligned with business objectives.
  • Document any significant configuration changes for future reference.

Need Help?

If you experience issues configuring a decision tree or need assistance designing a workflow:

Including screenshots and examples of the expected outcome can help expedite troubleshooting.