Overview

Approvals sit at the Division level and Divisions are designed to be flexible, but are really the natural groupings of people in your organisation. If you are a typical business with Marketing, Sales, HR then the Divisions would be perfect for this. If you are a retail chain then perhaps each Division will be a store with the respective users assigned accordingly. So first off, create your Divisions and assign the users. Then set your “Head of Division”. This is useful as it’s a variable in Zahara and can allow you to create the perfect approval process in one Division and then copy it over to other Divisions.

1

Typical Purchase Approval

A typical purchase approval is usually layered on the values. As the value of the order increases, more people are involved in the approval. Here is a typical approval process that we use in our demonstrations:

 

Step 1
Head of Division
all
Step 2
Business Unit Head
> £1000
Step 3
CFO
> £10000
Step 4
CEO
> £25000
Step 5

Send confirmation email
Step 6

Send PO to supplier

The above example is a good approval process where you simply use the Net or Gross conditions on the steps. You can also apply a condition to the “send PO to supplier” step. Perhaps create a custom field of “Type” and only do Step 6 if the field value is “Purchase Order” as opposed to Amazon or Credit Card or Online.

 

2

Inclusive & Exclusive Approvals

What do we mean by this? If you have 3 approval steps and the third step is for say the CEO, and she is only to approve if the value is over $100,000, then you would typically add a condition on the step of Gross Value > $100,000.

If you wanted to jump straight to that approver for a $100,000 approval, then that might be called exclusive – ie – we don’t care for the opinion of the approvers at steps 1 and 2. So to cut out the Steps 1 & 2, we would simply add an AND to their condition as shown below:

workflow step

This step is evaluated and skipped if it returns false. The workflow then goes onto the next step in the process and evaluates that one. You could have a workflow with 10 steps and each one is evaluated as false. It would still succeed and reach the end of the workflow and be treated as complete. This means you should be able to achieve any outcome you desire.

Our advice is to try to keep the workflows to a minimum per Division, but be efficient with the steps and use all of the logic that’s available to you and build up your conditions to suit.

3

Invoice Approvals

Invoice approvals can be different in that there are two distinct types – Order and No Order. Zahara can allow you to create two separate invoice approval processes. Each one would have a condition set at the top. Remember, if you use a condition to select the approval process, you need to set the default approval to Automatic.

4

"No Order" - Invoice Approval


With the “No Order” approval, set the condition to Order – “Order Not Exists” as shown above.

You might then create an approval process for this Division that largely copies the approval from the Order, with the same approvers and thresholds.

5

Order Exists - Handling Exceptions



In the above example, the approval will only trigger if the Order invoice difference is Greater than £10 or more than 5% of the order value. This difference approval can mean that all invoices that match the order can be approved straight away and even exported into the accounts system as a step (Xero / QuickBooks Online / Sage Sync). There is also a condition of Invoice Exceed Order which can be very effective. 

6

Ad Hoc Invoice Approvals

The approvals above are rules based. A new invoice lands in Zahara, it is evaluated for an approval process (based on its Division and any approvals set) and the choice of approval or approver is pre-set as the rules and logic kick in. This is the road to automation. You need to think of the rules you need now and possibly in the future if you are to work towards hands-free processing.

There comes a time though when you need to take over. The rules have worked but you need someone to take a look at an invoice as well. Make sure Ad Hoc invoice approvals are enabled in your business settings. (Business > Settings > Workflows) –  You can then select an approver from a list and choose the outcome of the approval. 

 

You will then see the extra settings.  Multiple select your finance users from the list that can use this feature and send invoices out for approval. Set the “Reply To” address – perhaps this will be the email address for the finance team or a particular user in finance. Set the from address, as per your SMTP settings – so if you use Zahara’s SMTP make sure this is an @myzahara.net email address.

Then set the subject for your Ad Hoc invoice approvals – Save your settings

Using Ad Hoc Approvals

Using Ad Hoc approvals is very easy. From your invoice, click the people icon as shown below. Choose an approver and determine the outcome if it’s approved.

Treat as Complete – If you send an invoice to Tony for approval and he approves it- is that the end of it or are you wanting to send it on to other people afterwards? Perhaps there are multiple lines to approve. “Treat as complete” means that if Tony approves it, and you set it as “Treat as complete” then you will see the Green approve icon. If however, you don’t tick this, you will see a flashing orange icon. The flashing icon means its been actioned so you now need to look at it.

Sending for approval 

Firstly, click into your invoice by clicking the invoice number. You will now see this new icon …

ad hox invoice approvals

Click the people icon …

adhoc invoices

  1. Select your approver – just the approver you want.
  2. Select the approval type – standard, Must Edit or Can Edit
  3. Select the outcome – Email Me – will email you the outcome, Treat as complete – see above
  4. Click Send

Now the approver will receive the approval email, the history will be updated and the icon will stay orange until actioned.  

Finalising the approval 

If you didn’t click “Treat as Complete” you can manually change the invoice status to Green when you are happy that the invoice has been approved. ad hox invoice approvals change

Use the … menu to Change the status in the list to Green (Approved) or Red (Rejected)
7

Approval Email Template

The wording of your  Emails including the approval email is edited in the Approval template as shown below. You access this under the Business > Settings menu. 


You can change the wording and drop in any placeholders you need from the Insert menu.

The Approve and Reject buttons are preset and styled to work with both Outlook and the rest of the mail systems like Gmail / Office 365 that support later versions of HTML and CSS. You can also display line items inside the email – to show the approver the breakdown of the order or invoice. 


8

Choosing a workflow from the list

By default, the user wouldn’t choose a workflow. They will have the approval process pre-set for them. However, by providing them with the Admin role, the approval list will be accessible. If you want the users to be able to choose a workflow from the drop-down list, they have to have the Admin role.

So to get tothis…

workflow dropdown

They need this …

admin role

 

9

Default Workflow Explained

In the Division you can set the default workflow for both the Purchase and the Invoice. This could be a specific workflow or you will notice the option of automatic. Usually, you would specify one workflow and all Purchases or invoice will use that workflow. 
 
If you have more than one workflow available then you can automatically select the correct workflow based on the conditional entry point to start the workflow – as in the example below: 

So in the event that there were two or more Invoice workflows with the Conditional Start enabled, you would use Automatic Invoice Workflow – as shown below. 

10

Group Approvals

With approvals you usually want somebody to take ownership and to take action. Group Approvals are for those who have a team of people where anyone in the team can approve. Perhaps it’s a project team or a flat authority. You can create a workflow step where you select “Group Approval”. This means you can send an approval to a group of people and choose how to allocate it in the group.

The options are:

  • “Broadcast” – everyone gets the approval email and the first one to approve does the approval. This is literally “Broadcast” to everyone in the group.
  • “Round Robin” –  which means we send in an order. So if you have Bob, Dave & Sue in the Group, the order would be Bob to get the first one, then Dave to get the second approval request and Sue to get the third one. Bob would then get the fourth one and so on.
  • “Dynamic”  – This is where we take into account who is the fastest approver, who is actually working and not set on absence, and who has the least approvals to do. We created an intelligent algorithm to decide the best person to approve it in the group.

Time-Outs

You can also select a “Time Out” for the Round Robin & Dynamic option – this means that if the approver hasn’t taken action in the allotted amount of hours then it will go onto the next person in the group.

Epic Fail 
There are handlers in the Group approval for things like everybody being off and anything to avoid a perpetual loop. In one of these circumstances, we will fail the approval and leave you with a warning so you can take action.

 

Next Approval Article – click here