Business Unit Category
Add an email signature
Coding Restrictions
Create new Business Unit
Custom Fields on Line Items
Customised labels
Date formating
Default delivery address
Division Management
Editing Email Templates
How to hide cost codes
Invoice email forwarding – Microsoft 365
SMTP & Email Sending
T&C on your PO Template
Invoice Processing Help Category
Auto reject supplier invoices
Auto rejecting of invoices issue
Finding an order or invoice
How to create a credit note
Invoice email forwarding – Microsoft 365
Invoice export colours
Invoice Inbox
Invoice List View
Invoice matching
Invoice Processing Explained
Month end cut offs
Negative Order Balance
Setting up Autopilot
Supplier Matching
Waiting for a GRN
Purchase Orders Category
Adding a product to an order
Adding documents to an order
Bulk importing orders
Close Orders Automatically
Closing an order
Copy PO to Buyer
Creating a Purchase Order
Deleting a PO
Duplicate Order Prevention
Editing an order
Finding an order or invoice
GRN an order
Grouped Purchase Orders
Import Line Items
Negative Order Balance
PO Template Editing
Purchase Order Numbering
Purchase Order PDF
Purchase Order Prefix
Purchase Requisition Number
Quick Create a Purchase Order
Send PO to Supplier
Supplier order acceptance
What is a purchase order?
This guide is designed to help you plan your roll out of Zahara. It explains principles and has a matrix of the different elements of Zahara. Click the link below in blue to
The biggest challenge for a lot of new Zahara customers is how to get the structure right to suit your business. There is no wrong or right way. Our recommendation is to understand the different elements and how they all fit together in Zahara. This is why the PDF guide above has to be read. The ‘rules of thumb’ though are as below:
Business Units are generally companies in your accounts system. They are designed to align with what you already have. So if you have 6 x companies in Sage or Xero, create 6 x corresponding Business Units in Zahara. They can be used in other ways as well. Users are allocated to a Business Unit and the Divisions inside the BU. Business Units can be secured and hidden from users who aren’t members.
Divisions are the natural groupings of people inside the organisation. This could be remote offices or departmental functions like IT, Marketing or Finance. The main thing with our Divisions is that you allocate people to the Division and then create approval workflows for that Division. Nobody has an individual spend limit, the Division has the approval workflow as a group. You can create both invoices and Orders where the Division value is separate per line item. This facilitates purchases with multiple Budget allocations or multiple concurrent approvals.
Projects are a horizontal ring-fencing of spend, that sits across the Divisions. You can restrict which Divisions can spend against the project. Each line item of a Purchase or Invoice can have a separate Project code making them versatile values.
Projects are a horizontal ring-fencing of spend, that sits across the Divisions. You can restrict which Divisions can spend against the project. Each line item of a Purchase or Invoice can have a separate Project code making them versatile values.
Call them what you want and use them in any way you want, Zahara’s costs codes are a line-level analysis field that can be used for different things like Department Codes or Trackign Categories. You know what you need.
You can create custom fields for Purchases and Invoices and their values can be used in workflows. It could be you want a buying category – like Opex & Capex or it could be you need to record a vehicle registration number for every invoice. These values are “above the line” though.
