Most AP automation solutions can offer 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 approval workflow that sends all over-budget invoices – for specific job codes – to the manager that knows the job or project the best, instead of just a general AP manager.
Or, you could also have a workflow that automatically routes invoices from specific vendors to specific stakeholders, bypassing “the normal” approvers when a supplier needs early payment.
Having this type of workflow flexibility is critical for companies with 500 invoices or more a month because they often have a wide range of construction projects and approvers. And they need their workflows to be adaptable to the demands of the business.