Who this is for. SuperAdmins, and anyone asking why an invoice arrived without an owner. Access. Requires the
TEAM_MANAGEMENTpermission and the feature enabled for the tenant. See the Roles and Access Reference.
A rule that looks right but assigns nothing has a short list of usual causes. Work down this article in order. The first few checks account for most cases.
Check the rule before anything else
Is it a document rule? On an agent that also runs AP Helpdesk, a task rule never assigns a document however well its conditions match. Check the tab the rule sits under.
Is the policy active, and where does the rule sit in the order? An earlier, broader rule may be winning. Check every rule above it.
Was the vendor identified? Document distribution runs once the vendor is resolved. Where the vendor could not be identified, the document is created without an assignee whatever the rules say.
Does the document hold a value in that field? A condition matches only when there is something to compare. The usual blanks are no entity resolved, no address on the document, and an unmatched vendor leaving the supplier fields empty.
Is it a vendor record attribute on an unmatched vendor? Supplier Group, Supplier Default Payment Method and Supplier Category all need a matched vendor record.
Does a range rule still have both halves? Both the range starts with and range ends with rows need to be present.
Did you mean contains rather than in? The in operator is an exact match.
For a sender rule, is the value the sending address or domain rather than the vendor address printed on the invoice?
Is the chosen person still eligible? Where their role has changed, the match is discarded and the document is created without an assignee.
Was the document reprocessed? The assignee stays as it was, because document distribution does not run a second time.
Was the document added by hand? Then it belongs to whoever created it, and sender rules cannot apply to it at all.
Questions that come up often
Table 1. Common questions
What you see |
What it means |
|---|---|
The rule is not routing what I expected |
On an agent running both products, check the Document and Task selector on the rule. A rule created under the wrong kind is scoped to the wrong work. The two kinds also offer different condition attributes. |
I want to stop one rule for a while |
Individual rules cannot be switched off. They can be created, deleted and reordered. To stop a policy assigning, disable the policy from the distribution policies list. |
I cannot deactivate a team |
The team is the target of an assignment rule. Repoint or remove the rule, then deactivate the team. |
I cannot see a document a colleague mentioned |
Each tab opens filtered to your own work. Clear the filter to see everything. |
The buttons on a document are unavailable |
Either the document has no assignee, or it belongs to someone else. The reason shown on the control says which. |
A document shows AI Agent |
The agent processed and wrote it on its own. Where the write did not succeed, the document is released unassigned for a person to pick up. |
Worked examples
Each row is one rule unless the description says otherwise. Order them from the most specific at the top to the broadest at the bottom, because the first matching rule wins.
Table 2. Routing recipes
What you want |
How to set it up |
|---|---|
Everything from one company goes to the person who owns that relationship |
Email From Domain contains the company domain, assign to that person. |
One billing contact goes to a specialist |
Email From in that single address, assign to the specialist. |
Split the vendor list alphabetically across two people |
Two rules. Vendor Name range a to m to the first person, n to z to the second. |
A subsidiary goes to its local AP person |
Entity is that entity, assign to the local person. |
All invoices for one site go to the regional team |
Address contains the city and state, assign to the team. |
Utilities invoices go to one team |
Supplier Category is your utilities category, assign to the team. |
Everything else spreads across the AP team |
A final rule with no conditions, assigned to your AP team. |
On an agent that also runs AP Helpdesk, add the matching task rules alongside these, including a second rule with no conditions at the end of the task rules.
Related information
For the rules themselves, see Build Assignment Rules.
For the policy list and its counts, see Distribution Policy List.
For working with an assigned document, see Working with Assigned Documents.