Routable supports configurable approval workflows, including multiple levels and levels requiring approval from any or all listed members. Its product page describes conditions involving fields such as vendor, department, and accounting dimensions. The conditions available to a particular workflow can depend on the connected system and configuration. Source: Routable approval workflows.
The design question is what each approval is supposed to establish. Adding more approvers does not help if everyone assumes another person reviewed the invoice.
Assign a purpose to each review
Separate the business checks involved in a payment.
One reviewer may confirm that goods or services were received. Another may confirm the coding or budget. A further review may be required under the company’s authority policy.
Write these responsibilities down before configuring the route. The approver should know what evidence is required and when to return the item for clarification.
Avoid using approval as a substitute for missing information. If the reviewer cannot identify the recipient, amount, or reason for payment, the case needs clarification before authorization.
Match rules to the available data
A condition can only route reliably when its source field is populated consistently.
If the business uses department-based approval, establish who assigns the department and what happens when it is absent or incorrect. Apply the same review to location, project, or other dimensions.
Test a bill with missing data. The test should establish whether it enters the intended exception path, rather than silently reaching an inappropriate reviewer.
The accounting integration guide explains how to examine the fields on which those rules depend.
Understand “any” and “all”
A level requiring any listed approver is operationally different from a level requiring all of them.
Use the choice to express the actual authority policy. A group of interchangeable reviewers may serve a different purpose from two independent reviews.
Consider a fictional process in which one department manager confirms receipt and a finance reviewer checks the amount. That is a description of two responsibilities, not a recommendation that every business use two levels.
Test whether the configured sequence reflects those responsibilities, including cases where the same person holds more than one role.
Review the actual approval queue
Routable’s help documentation identifies Needs approval under Payables, with views for Needs my approval, Needs team approval, and All. It describes opening the payable and selecting Approve to authorize it. Source: Approving payables.
The queue is also a management tool. Review which items are waiting, how long they have waited, and what information is preventing a decision.
Do not measure success only by how quickly items leave the queue. A rapid approval with no meaningful review can conceal a process problem.
Account for international amounts
Routable’s approval documentation states that international-payment approval is triggered using the estimated USD amount of the payable. Source: International approval note.
If your authority policy uses amount thresholds, include a foreign-currency case in testing. Confirm which figure is used and how the team should handle any material change relevant to its policy.
Do not assume that entering a foreign-currency amount produces the same routing as an identical numeric amount in dollars.
Plan for unavailable approvers
Document who maintains approval rules and how absences are handled. Include both new bills and items already awaiting approval.
A change to future routing should not be assumed to repair every existing item. Follow the documented account process and verify the result on the affected payable.
Routable advertises administrative approval-bypass capability. Treat its use as an exception governed by the company’s authority policy, with a reason and review record. Source: Routable workflow features.
Confirm what happens after approval
Approval does not by itself establish bank delivery. The next step depends on the payable’s state and scheduling.
Use the payment status guide to explain that distinction to staff. For imported runs, apply the same authorization policy to the CSV payment process rather than treating a spreadsheet as permission to pay.
A good workflow leaves an understandable record of who reviewed what, which exception occurred, and why the payment proceeded.