Skip to main content
Invoice approval workflows
Alina avatar
Written by Alina
Updated over a week ago

Invoice approval workflows enable budget management and oversight by allowing designated individuals to approve invoices before payment.

In this article:


Approval phases and workflows

There will often be times when invoice approval is required to ensure work accuracy and completion by the right people in the law firm. These crucial checkpoints are known as approval phases.

Approval phases can be chained together to form approval workflows, where different individuals are assigned to approve the invoice at each phase. Approval workflows are then applied to invoices to control the invoice's progression.

When an invoice goes through an approval workflow, it progresses through each approval phase sequentially. Once all phases are completed, the invoice is forwarded to the Finance team for payment.


Set up invoice approval workflows

1. If you're a LawVu Administrator, go to Settings > Approval workflows.

2. Customize your workflow:

  • Click on New Workflow and give it a name

  • Create and name the first phase in the workflow.

  • Choose approvers from the menu on the right. You can choose one or more individuals or teams and specify whether it's sufficient for anyone in the group to approve the invoice or if everyone in the group must approve it.

  • Add other phases to the workflow if needed by selecting the + icon.

You can also assign approval workflows to teams. To create a team, navigate to the Teams tab. Once formed, you can assign the team to any approval workflows you've set up.


We recommend locking phases that must always apply. Once locked, the phase cannot be edited by users.

Optionally, you can set up conditions for when you want your approval to apply. For detailed instructions, refer to the section Set up conditional rules for your workflows below in this article.

3. Apply the workflow to one or several matter types by clicking Assign workflow and then selecting the matter types to which you want the workflow applied.

If you need to reuse a workflow, you can quickly duplicate it from the ellipses menu:


Set up conditional rules for your workflows

Conditional approval workflows enable you to create and assign workflows based on more than just approvers and phases. These workflows can be tailored to specific scenarios, such as when invoices are over a certain amount or when third-party invoices require a different approval processes.

Setting up conditional rules for your workflows is a three-step process: first, define the primary condition and determine who will approve invoices when the condition is met ("Yes") and when it is not met ("No").

Click on the flag icon next to the phase, and select a condition from the list of available fields:

The available conditional fields are limited to LawVu fields of the following types: Dropdown, Look-up fields, Single checkbox, Numerical and currency fields, and Radio buttons. Custom fields are not supported.

The LawVu fields that can be used for conditional logic are:

  • Invoice fee

  • Fee value

  • Department

  • Region

  • Potential liability

  • Due date is critical

  • Hours per week

  • Duration

  • Litigious

  • Litigious outcome

  • Urgent

Choose what happens when the condition is not found (e.g., when the field is removed from a matter type, the field library or is left blank). You can choose to skip to the next phase of the workflow or send the invoices to one or more allocated approvers:

3. Click on the "+" sign next to "No" to create a workflow for cases where the primary condition is not met.

Watch this animation to see how I configured varying approvers based on whether the fee value exceeds a specific amount:


Sending invoices for approval

When an invoice requiring approval has been posted, the approver will receive an email and an in-app notification.

If the approver declines the invoice, they can provide a reason, and a notification is sent to the legal service provider.

Once a workflow is applied, it needs to be approved or declined. It can’t be voided or restarted.


Check the status of your invoices

You can track the status and history of your sent invoices for approval by using the Invoice details pane located on the right-hand side of the invoice.


This helps you easily see if there are people who still need to approve the invoice or if it's already been approved or declined.


FAQs

Invoice Workflows

Who approves invoices if there is no approval workflow?

If no approval workflow is applied to a matter, the matter owner approves the invoices. Business users who are matter owners can approve invoices through the Business Portal.

Who can be set as an approver in an invoice workflow?

Any user with a LawVu license can be an approver.

What permissions are needed to approve invoices?

Any user with a LawVu license can approve and does not need a permission to review and approve invoices.

What happens if an approver is deactivated in LawVu?

If an approver is deactivated, the Matter Owner (MO) becomes the default approver. If the deactivated user was the only approver in a phase, the MO takes over. If there are multiple approvers and one is deactivated, the workflow will continue to the next phase without that approver's input.

What happens if an invoice is moved to a different matter with a new approval workflow?

If an invoice is moved to a different matter, it will follow the approval process of the new matter type, even if the old process had already started. The invoice will be routed through the new approval workflow associated with the new matter type.

Can delegates approve invoices as well?

Yes, delegates of the designated approver can also approve invoices. However, if they are removed as a delegate, they will lose this ability.

Conditional Logic

What happens if no value is entered in the matter field for conditional approval routing?

If no value is entered in the matter or contract field designated for conditional approval routing, the condition will be considered "not met" (No), adhering to the workflow configured for this scenario.

What if the field is completely removed from matter details?

If the field is removed from the matter details, the workflow will follow the flow set in the "If this condition is not found" section:

Are there field / types that do not work in conditional logic?

Yes, all custom fields, including these LawVu fields—Third Party, Is Signed, and Contract Value—cannot be set as conditional fields.

What happens if multiple values are selected for the conditional logic field in the matter?

If multiple values are selected for the conditional logic field in the matter, the workflow will follow the rules set in the "If this condition is not found" section.

Did this answer your question?