Advanced Approvals

Modified on Tue, Nov 10 at 4:39 PM

Advanced Approvals mimic the workflow for a Single Approval, with two main differences.

1. An invoice can have multiple approvers

2. An invoice can have various conditions for which it requires approval (called "approval policies").

Creating a policy

Conditions

Policies can be defined across any layer of hierarchy:

Account
Location
Group
Company

Configurable Field	Description of requirements and clarifying remarks
Vendor	Specify one vendor and all invoices from that vendor will get held in Pending Approval.
Accounting Vendor ID	Specify the Accounting Vendor ID that vendors are mapped to (ex. Sysco).
Min. Total	Specify a number and all invoices with invoice_total above that minimum threshold will be held in Pending Approval.
Max. Total	Specify a number and all invoices with invoice_total below that maximum threshold will be held in Pending Approval.
Department	Specify one Department and all invoices from that Department will be held in Pending Approval.
GL Account	Specify one GL Account and all invoices from that GL will be held in Pending Approval.
GL Name Contains	Specify a string (ex. Food).
GL Name Does Not Contain	Specify a string (ex. Fixed Assets).
GL Number Contains	Specify a string (ex. 5400).
GL Number Does Not Contain	Specify a string (ex. 73350).
Received directly from Vendor?	Specify a boolean, Yes or No. If yes, all invoices that are sent directly from a vendor (via EDI, FTP, or email) will get held in Pending Approval. If no, all invoices that are not sent directly from a vendor will get held in Pending Approval.
Has unmapped items?	Specify a boolean, Yes or No. If yes, all invoices that contain unmapped items will get held in Pending Approval. If no, all invoices that do not have unmapped items will get held in Pending Approval.
Has no other policies	Single selection. Catch all that will funnel all invoices that do not have any other approval policies applying to this policy.
Has a PO Number?	Specify a boolean, Yes or No. If yes, all invoices that have PO Number will get held in Pending Approval. If no, all invoices that do not have PO Number will get held in Pending Approval.
Policy	Specify one or many existing approval polices, and all invoices that meet those policies will get held in Pending Approval. This is usually paired with a new condition. Also known as "Sequential Approvers" or "Hierarchal Approvers," which means: after one policy has been approved will this other policy get triggered. Consider this use case: As a CFO, I only want to be alerted that an invoice requires my approval after everyone else reporting to me has already approved the invoice.
Item SKU	Specify a string (ex. ABC123).
Tag is	Specify a string (ex. Taxable).
More added frequently...	We are continually enhancing our offerings; please reach out if you need something new!

In the example below, this "Test Policy" will be:

This policy triggers:

Any condition in this group can match

Total is greater than or equal to

5000

AND

Vendor is

5280 PRODUCE, INC

Scope is all locations:

Potential Approvers

These invoices need to be approved by a pre-defined set of users.

In this case, Mary and Sarah will get emails alerting them that they have invoices requiring their approval and see those invoices in their "Your Approval" queue. Both must approve them to satisfy the policy based on the "Minimum Approvers" setting. If you only need one of them to approve, set to 1.

Fallback Approvers and Automatic Approvals

Setting a fallback approver escalates the policy if it has not been approved within the set days. In the example below, Mark will receive the invoice to approve after 1 day, and then James will receive it after 3 days.

You can also configure the policy to approve the invoice automatically if it is uploaded by one of the configured approvers.