Most AP systems route approvals one way: by amount. An invoice under $5,000 goes to one tier, over $25,000 to another, and so on up an authority hierarchy. It's a sensible default — but on its own, it's incomplete.
The reason is simple. Who should approve an invoice frequently depends on the supplier, not the number on it. The contractor doing roof work on a specific property should be approved by the manager responsible for that property. The IT vendor should go to whoever owns the IT relationship. A $2,000 invoice and a $40,000 invoice from the same supplier may both belong to the same person — because what matters is the relationship, not the threshold the amount happens to cross.
When the only routing lever is dollar amount, AP ends up doing the supplier-to-approver mapping in their heads, manually reassigning invoices every day. That's slow, it's inconsistent, and it's institutional knowledge that walks out the door when an AP clerk leaves.
Two routing models, working together
The fix isn't to replace amount-based hierarchy — it's to add a second, complementary model and let them coexist.
1. Manual approver assignment. From the data-entry screen, an AP user should be able to assign a specific approver to an invoice directly. That approver is then notified by email, and the invoice drops into a clearly labeled tab in their queue — something like Invoices Pending My Approval. No hunting through a shared pile; the right person sees exactly what's waiting on them.
2. Automatic assignment by supplier name. This is the real time-saver. You define, once, which approver owns which supplier. Then, as soon as an invoice's required metadata fields are complete, the system assigns the correct approver automatically — no manual step, no daily reassignment. The supplier-to-approver knowledge moves out of someone's head and into a rule the system enforces every time.
The two models don't conflict. Supplier-based assignment handles the predictable majority automatically; manual assignment covers the exceptions.
The override matters more than it looks
A rigid auto-router that only assigns by rule creates its own friction — the moment reality doesn't match the rule, AP is stuck. So the design has to include a clean escape hatch: the user can override the automatic assignment and route the invoice to any other user in the organization.
That override is what makes auto-assignment safe to trust. When a regular approver is on leave, when an unusual invoice needs a different reviewer, or when the supplier rule simply doesn't fit a particular case, AP isn't fighting the system — they reassign in one action and move on. Automation handles the 90% that's routine; the override handles the 10% that isn't.
Why amount-only routing isn't enough for property and public-sector AP
For property-management and public-housing finance teams, supplier-based routing maps directly onto how the organization is actually structured:
- Property and program owners approve the vendors tied to their area of responsibility — regardless of invoice size.
- Accountability is clearer. Routing by relationship means the person who actually knows whether the work was done is the one signing off, which is exactly what an auditor wants to see.
- Segregation of duties holds up. Pre-defined supplier-to-approver rules make it far harder for an invoice to land on the wrong desk, and easy to demonstrate that it didn't.
Amount thresholds still belong in the picture — they enforce the level of authority required. Supplier-based assignment answers a different and equally important question: which person, in which part of the organization, owns this relationship. You need both.
Where EZ Cloud fits
EZ Cloud supports both routing models in one workflow. AP users can assign an approver manually from the data-entry screen — the approver is emailed and the invoice appears in their Invoices Pending My Approval tab — and you can define automatic approver assignment by supplier name so the right person is routed the invoice the moment its metadata is complete, with a one-click override whenever the rule needs to bend.
A US housing authority runs this supplier-based routing alongside amount-based hierarchy in production — the broader picture is in our HACOV case study, and how approved invoices flow on into Yardi Voyager is covered on our Yardi integration page.
If your approval routing today is purely dollar-driven and AP is reassigning invoices by hand every morning, supplier-based assignment is the piece you're missing. It encodes the knowledge your team is already carrying — and stops it from being a single point of failure.