Skip to main content

Classified and Unclassified Reason Codes

Learn how classified and unclassified reason codes differ and how classification affects workflow decisioning and evaluation outcomes.

Reason codes provide additional context about signals returned by a data provider during an evaluation. In Alloy, returned reason codes are shown as either classified or unclassified based on whether they belong to a reason code group.

Classified reason codes

A classified reason code is included in at least one reason code group under Settings > Reason Codes. Reason Code Groups let you organize provider codes into meaningful categories, such as identity warnings, address risks, or sanctions matches.

Reason Code Groups codes can be used in workflow decisioning. When a returned reason code matches a group that is connected to workflow logic, Alloy can set a corresponding tag and use that tag in the outcome logic.

Classifying a reason code does not automatically change an evaluation outcome. The reason code’s group must also be referenced by the applicable workflow logic.

Unclassified reason codes

An unclassified reason code is a reason code returned by a data provider that is not included in any reason code groups configured in your organization’s Alloy account.

Unclassified reason codes are displayed for informational purposes and do not contribute to the evaluation outcome or trigger workflow actions.

Unclassified reason codes may still include a description on the evaluation summary page. The data provider determines the meaning of the code; Alloy displays the available description.

How classification affects outcomes

The outcome impact follows this sequence:

  1. A data provider returns one or more reason codes.

  2. Alloy checks whether each code belongs to a configured reason code group.

  3. If a code is unclassified, it is displayed but does not affect workflow logic.

  4. If a code is classified, it can contribute to workflow logic when its group is connected to a tag or outcome logic.

  5. The workflow evaluates the configured rules and applies the resulting outcome, such as Approve, Deny, or Manual Review.

A classified reason code is therefore eligible to influence decisioning, while an unclassified reason code is not. Your organization determines which reason codes should carry decisioning weight and which workflows should use them.

Review and classify reason codes

To review the available codes and add one to a group:

  1. Go to Settings > Reason Codes.

  2. Open the relevant Reason Code Group.

  3. Review the available reason codes and their descriptions.

  4. Select the code or codes you want to include in a reason code group.

  5. Add them to an existing group or create a new group.

  6. Review the applicable workflow to confirm that the group is connected to the intended tag or outcome logic.

Recommended review process

Periodically review returned unclassified reason codes, especially when they appear repeatedly on approved applications. If a code represents a signal your organization wants to consider, add it to an appropriate group and update the relevant workflow logic. Before making a production change, confirm the intended treatment with your organization’s risk, compliance, or change-management team.

Frequently asked questions

Does adding a reason code to a group automatically cause an application to be decisioned to deny or manual review?

No. Classification makes the code available to workflow logic. The reason code group must be connected to the relevant workflow rule, tag, or threshold before it can affect an outcome.

Why did an evaluation show a concerning code but still get approved?

The code may have been unclassified, meaning it was displayed but not configured for decisioning. It may also have been classified but not connected to a rule that changes the workflow outcome.

Can one reason code belong to more than one group?

Yes. A reason code can be included in multiple groups when your organization needs to use the same provider signal in different decisioning categories.

Did this answer your question?