Skip to main content
Need help in this area? See Bill Pay FAQ.
Rules are the logic engine behind Bill Pay. Each rule defines conditions (when should this rule fire?) and actions (what should happen?). When a bill is evaluated, every active rule is checked in priority order — all matching rules fire, and their actions execute.

​
Rule types

Bill Pay has two types of rules, evaluated in sequence: GL coding rules are evaluated first, then routing rules. This means a bill can receive a GL code and be forwarded in the same evaluation pass.

​
Creating a rule

1

Choose a rule type

Go to Bill Pay > Rules and click New rule. Select either Add GL coding rule or Add routing rule.
2

Name your rule

Give the rule a descriptive name (e.g., “Northeast electricity to AP team”) and optionally add a description explaining its purpose.
3

Build conditions

Drag condition blocks from the palette onto the canvas. Each condition tests a specific field against a value — for example, “Commodity equals Electricity” or “Total charges is greater than 1000.”
4

Add logic groups

Combine conditions with AND (all must match), OR (any can match), or NOT (inverts a condition). Drag group blocks from the palette to create complex logic.
5

Configure actions

Drag action blocks onto the canvas. For routing rules, choose where the bill should go. For GL coding rules, specify the GL code to assign.
6

Preview and save

Use the dry-run preview to test your rule against recent bills before activating. When ready, click Save & enable to activate the rule immediately, or Save to keep it inactive.

​
Condition fields

You can build conditions using any of these bill, site, and account attributes:

​
Operators

Each condition uses an operator to compare the field against a value:

​
Action types

​
Routing rule actions

​
GL coding rule actions

​
Priority and evaluation order

Rules are evaluated in the order shown in the rules table. If multiple routing rules match the same bill, all matching actions fire — but delivery is deduplicated so each destination only receives the bill once. You can reorder rules by dragging them in the rules list.

​
Dry-run preview

Before activating a rule, click Preview to test it against your recent bills. The preview shows:
  • How many bills would have matched this rule
  • Which specific bills matched and which didn’t
  • What actions would have fired
This lets you verify your conditions are targeting the right bills without affecting live routing.

​
Version history

Every time you save changes to a rule, a new version is created. You can view the full edit history by clicking Edit history when viewing a rule. This audit trail shows who changed what and when, making it easy to understand why routing behavior changed.

​
Catch-all destination

If a bill doesn’t match any routing rule, it enters a Pending routing state and waits for manual assignment. To avoid this, you can designate a catch-all destination — a fallback that receives any unmatched bills. Set this from the rules page using the catch-all configuration option.