Most AP automation solutions can set up straight-forward invoice approval workflows based on invoice amount, GL code, and property. But not all let you configure accounts payable workflows triggered by a broad range of data elements.
Nexus, for example, can let you establish rules that automatically route invoices based on their:
- GL Category
- MTD Budget Comparison
- YTD Budget Comparison
- Yearly Budget Comparison
- Specific Vendor
- Contract Code
- Job Code
So, for example, you can have an accounts payable workflow that sends all over-budget invoices for specific job codes to George Abrams in Construction Finance.
You could also have a workflow that automatically routes invoices from specific vendors to specific stakeholders, bypassing “normal” approvers. This type of workflow is often used when a supplier needs early payment – and you want to make sure the invoice is seen, approved, and marked for payment quickly.