Vendor Invoice Overview
To access the Vendor Invoice function, simply navigate to the second option in the drop-down menu under the Data Entry section of Payables in Accounts mode. The Vendor Invoice screen is strategically placed for convenient access. It is specifically designed to facilitate the entry of Payables Vendor Invoice into the General Ledger.
A SapphireOne Vendor Invoice represents the financial obligation of your business to a Vendor and is recorded as a liability on your company’s balance sheet. Its primary purpose is to facilitate the payment process to the vendor through Vendor Payments. SapphireOne offers several methods to automate the Accounts Payable procedures for settling Payables Vendor Invoice. One such option is the generation of Electronic Funds Transfer (EFT) files and electronic remittance advice, which can be conveniently emailed.
Workflow functionality
SapphireOne incorporates a Workflow system that covers all data entry transactions, including the approval process for Payables Vendor Invoice. These invoices require electronic authorisation before utilising the Vendor Payment function for payment.
PDF Capture functionality
SapphireOne’s Vendor Invoice feature incorporates a convenient PDF Capture functionality. If you receive a Vendor’s Invoice via email in PDF format, you can effortlessly drag-and-drop the PDF into the PDF Capture function. This automated process eliminates the need for manual data entry as the system extracts relevant information such as the Vendor’s ID, Invoice Number, Date In, and other data directly from the PDF. Moreover, SapphireOne’s PDF Capture function, which also performs the data entry. The PDF is then automatically attached to the newly created Vendor Invoice using SapphireOne’s Document Management System, seamlessly attaches the PDF to the newly created Vendor Invoice, accessible through the Paperclip icon within the Vendor Invoice interface.
Updating General Ledger Accounts
The Vendor Invoice, is an integral part of the Accounts Payable module. It not only updates the sub-ledger control account for vendors but also influences the final payment process, thereby reflecting the appropriate changes in the General Ledger expense account accordingly. Notably, a Vendor Invoice in SapphireOne allows for the linkage of specific Job Projects at the line level, enhancing project management capabilities.
For example, let’s examine a Vendor Invoice totaling $330, allocated across three General Ledger accounts: $100 for delivery costs, $100 for marketing, and $100 for consulting. Each sub-ledger line, amounting to $100, may include associated GST values, such as $10, ensuring a balanced Vendor Invoice of $330. Once completed, the Vendor Invoice automatically updates the Vendor Sub-ledger, the General Ledger Control Account, and enables the generation of the comprehensive SapphireOne Vendor Balances Report, offering a detailed overview of vendor-related financial information.
Vendor Invoice – Details Page


Vendor Invoice – Transaction Area
- Vendor ID – When you enter a valid Vendor ID, SapphireOne automatically populates the invoice with the Vendor’s details from the Vendor Master File. This reduces manual data entry and helps ensure vendor invoices are recorded accurately and efficiently. If you enter a Vendor ID that has not been used before, SapphireOne will prompt you to create a new Vendor record. The procedure for creating a new Vendor is documented below.
- Invoice No – Please enter the vendor’s specific invoice number associated with this transaction. This number uniquely identifies the invoice and helps in accurate record-keeping and tracking of payments.
- Order Number: If applicable, please enter the Vendor Order Number. This field can accommodate alphanumeric characters and serves as an external reference.
- Date In: SapphireOne will automatically populate today’s date. To select an alternative date, click on the underlined Date In heading for a pop-up calendar or manually type in the desired date.he date.
- Period: SapphireOne will automatically enter the current Period or the Period relating to the manual date you entered.
- Different Period – Click on the underlined Period heading for a pop-up period list. Some periods may not appear on the list, as they may be locked (i.e. transactions for the period are complete).
- Total: Enter the Total Cost of the transaction, including Tax. If the Vendor is dealing in a foreign currency, the appropriate currency and tax will be displayed. These are set up in the Vendor’s Master File.
- Due: SapphireOne will automatically enter the due date according to the Vendor’s terms, which are set up in the Vendor Master File.
- Altering Date – This may be altered if required by clicking on the underlined Due Date for a pop-up calendar or manually typing in the date.
- Discount: SapphireOne will automatically enter a discount for the Vendor if one has been set up in the Vendor’s Master File.
- No Discount or Terms – If there are no terms or discounts set up for a Vendor, the Discount area will appear as 0.00%.
- Discount or Terms Applied – Once a Discount has been entered, the amount will be displayed as a percentage in the Discount field.
- Days: If set up SapphireOne will automatically enter the number of days for prompt payment discount, which is set up in the Vendor’s Master File.
- Memo: Enter any details relating to this transaction.
- Paperclip: Scan and attach any documents relating to the Vendor Invoice.
Establishing a New Vendor
- Enter a unique, previously unused Vendor ID.
- SapphireOne will prompt you to create a new record. Select Yes.
- A new Vendor Invoice (VI) entry screen will open. In the Vendor field, select New Vendor.
- In the “Create New Vendor” panel/dialog, enter the following (as required):
- Payment Default – Paid From (Bank) GL Account (lookup)
- Accounting Defaults – Default GL Expense Account (lookup)
- Save the new Vendor. You will be returned to the Vendor Invoice. Where applicable, the Paid From bank account will default in automatically, and the default expense GL account will be available (and may be applied for invoice coding), depending on your organisation’s intended configuration.
Setting Up a Vendor Discount
- Go to the Mode drop-down menu in the top left corner and select the Accounts option.
- In the top toolbar under Payables, select the Vendor Inquiry item.
- Open the Vendor for modification that you would like to set up the discount for.
- Go to the Page drop-down menu in the top left corner and select the Terms page.
- Go to the Discount area and enter the required discount details.
Applying a Discount to the Current Invoice Only
- By percentage – Simply type over the new percentage for the discount. SapphireOne will recalculate the dollar amount.
- By dollar amount – Select the button and manually type in the dollar amount (minus the $ sign) for the discount. SapphireOne will recalculate the percentage.
Vendor Invoice – Information Tab Area
The Vendor Invoice Information area provides supplementary details regarding the current entry. This section is for viewing purposes only and does not allow any modifications. The Information tabs automatically update depending on the transaction being viewed. There are seven primary tabs within the Vendor Invoice Information area, which include:
- Vendor Tab – This tab presents specific information about the vendor, including the Total Due based on the applicable terms, Credit Remaining, and any associated Warning Messages.
- Controls Tab – This tab provides a comprehensive overview of the transaction’s timeline, including the entry and posting dates, as well as the user responsible for each action. Additionally, it displays the total value of the allocation made for the transaction.
- Allocation Tab – This tab showcases linked data records associated with any allocations made for the transaction.
- G.L. Tab – This tab exhibits the General Ledger details for the account specified in the current invoice.
- Project Tab – If a project has been entered, the project details, including the Project Name, are displayed under this tab.
- Trans Tab – This tab exhibits the most recent 20 transactions. By selecting a historical transaction and right-clicking, you can perform the following actions: Copy Transaction, Copy Lines, or Open In Inquiry.
- Error Code Tab – Typically, error information is shown under the Controls Tab, providing concise details. However, if there is additional information regarding an error within a transaction, it will be displayed under the Error Code tab. This tab proves particularly valuable when dealing with multiple errors within a single transaction.
Vendor Invoice – Standing Transactions Area
The Vendor Invoice Standing Transactions area is utilized to establish recurring transactions and manage the frequency at which the record is created for each period. A Standing Transaction typically includes a start date and a finish date, defining the duration of the recurring transaction.
Standing Transactions Data Entry
- Scheduled – By default, the Scheduled drop-down menu in the Standing Transactions area is set to None indicating that no recurring schedule is currently assigned to the transaction. When the user clicks on the area displaying the word None, a fixed drop-down menu appears, offering the user various options for selecting the frequency of the standing transaction to be created. Within this menu, users can choose one of the frequency options listed below to set a recurring schedule.
- Other Than None – If a schedule other than None is selected, users will have an additional option to specify Start/NextDate and Stop Dates for the scheduled task.
- Scheduled Options – The Scheduled options in the Standing Transactions area offer flexibility in selecting the frequency of transaction creation. Users can choose from the following options:
- Monthly – This option enables the creation of the transaction on a monthly basis.
- 30 Day – Selecting this option enables the transaction to be created every 30 days.
- Fortnightly –:This option creates the transaction every two weeks.
- Weekly – This option sets the frequency to create the transaction every week.
- Yearly – Selecting this option creates the transaction once a year.
- Other –: By choosing this option, users can define a custom frequency for the transaction, specifying the desired number of days, weeks, or months between each transaction.n each transaction.
- Start/Next Date and Stop Date – When selecting any of these scheduled options, users must pay close attention to the Start/Next Date and Stop Date as provided by Sapphire One. It is important to note that the current computer date will be automatically populated in these fields. However, these dates may or may not align with the user’s specific requirements. Therefore, it is crucial to enter the correct dates carefully to ensure accurate scheduling.
- Date Picking Calendar – As these date headings are underlined SapphireOne offers options for choosing these dates through a date picking calendar or manual entry. Users can utilise the date picking calendar to easily select the desired Start/Next Date and Stop Date for the scheduled task. Alternatively, they can manually enter the dates as per their specific needs.
- Flexibility – SapphireOne offers users the flexibility to customise the Start/Next Date and Stop Date, allowing for personalised scheduling of recurring tasks based on individual preferences and business needs. This level of control empowers users to determine the duration and timing of their recurring transactions, ultimately enhancing efficiency and adaptability within the software.
- Disabling the Date function – Remember that setting the dates at 00/00/00 effectively disables the date function for either the Start/Next Date or the Stop Date.
Standing Transactions are generated only if the preceding period’s Standing Transactions have been successfully posted. In the case where a Standing Transaction’s Stop Date is left as 00/00/00, SapphireOne will continue to create the transaction until it is manually modified, stopped, or deleted by a user.
Vendor Invoice – Payment Area
Creating a Vendor Payment for a Vendor Invoice is not obligatory during the Vendor Invoice data entry process. However, SapphireOne offers the Payment Area as a convenient option for users to simultaneously finalise both the Vendor Invoice and the Vendor Receipt at the same time. This feature simplifies the procedure.
Since the essential Vendor’s information has already been entered into the Transaction Area for the Vendor, there is no need for additional data entry. Users only need to review and make adjustments to these Payment details as documented below if necessary, before saving the Vendor Invoice using the green tick
- Create Payment Checkbox – When this check box is selected the other data entry fields in this area will only then become active and ready to be edited by the user.
- Payment Intention – By selecting this Create Payment checkbox, users indicate their intention to create a Vendor Payment based on this Vendor Invoice.
- Paid From Data entry Field – This field will display the default bank account that is set up for the data file which should not normally be changed by the user.
- Other Bank Accounts – Select the
blue arrow next to the Paid To heading in the Payment area. A drop-down menu is presented which contains a list of available bank accounts from which the user can choose. This drop-down menu offers a convenient and organised way for users to select the desired bank account, ensuring the accurate allocation of funds. This functionality enhances efficiency and accuracy in allocating funds from the intended bank account within SapphireOne.
- Other Bank Accounts – Select the
- Payment Finalised Checkbox – If the payment is to be paid now select this check box.
- Create Vendor Reimbursement Checkbox – Select this option to flag the Vendor Invoice as a cash reimbursement. When the Vendor Invoice is paid and posted, SapphireOne automatically creates a Vendor Reimbursement (VR).
- Employee Dynamic Field – When the Create Vendor Reimbursement checkbox is selected, this dynamic field will be displayed, allowing for the assignment of an employee to the resulting Vendor Reimbursement (VR).
- Saving Comment – It’s important to note that when this Vendor Invoice is completed and saved, a corresponding Vendor Payment will not be generated until this Vendor Invoice has been posted.
Vendor Invoice – Destination Area
The Vendor Invoice Destination area serves as a storage space for the transaction lines comprising the invoice. This area can accommodate a range of line quantities, from a single line in accounts mode to potentially over a hundred lines in Inventory mode.
Destination area Data Entry
- Account – This field is linked, allowing the user to utilise the Wildcard search option for searching the Account ID.
- Account Name – After entering the Account ID, SapphireOne will display the corresponding Account name.
- Net Amount – Enter the Net Amount, which represents the amount excluding tax. Alternatively, you can press TAB and enter the Total Amount. SapphireOne will automatically calculate or reverse-calculate the tax as needed.
- Tax Code – Normally, tax codes should not be modified by the user as they are pre-defined and entered by SapphireOne based on their setup in other areas of the system. However, if necessary, the user can select a tax code from the drop-down menu or manually enter it. To change the tax code, simply overwrite the existing code. Tax codes are configured on a per-company basis and can be viewed or set up by accessing the following location:
- Amount – SapphireOne will automatically fill in this field with the appropriate tax amount based on the selected tax rate.
- Total – If the user enters the Net Amount, SapphireOne will automatically calculate and populate this field with the total amount, including the tax.
- Project – This field is linked, allowing the user to utilize the Wildcard search option to search for the Project ID.
- Project Name – Once the Project ID is selected, SapphireOne will automatically populate this field with the corresponding Project Name.
- Notes – Additional information related to each transaction line can be inserted in this field.
- Company – This button is visible only when multiple companies are set up in your SapphireOne data file. Clicking on it will direct you to a new screen where you can manage and allocate percentages or fixed amounts across the different companies.
The Vendor Invoice Transaction Footer is located at the bottom of the screen and provides a convenient overview of the essential details of a transaction. This area has a number of fields that automatically entered by sapphire one however there are several fields that allow user access . This area contains the following fields:
- Sequence – SapphireOne automatically generates a unique sequence number for each transaction.
- Batch – SapphireOne automatically calculates the batch total, which represents the sum of all Vendor invoices entered at any given time.
- Out of Balance – SapphireOne Accounting Software automatically generates the Out of Balance Total. The Out of Balance amount must be 0.00 to enable the saving of a record.
- Rules Level – This is a linked field. The User can click on the Rules Level and a pop-up Organisation Chart will appear. Select the Level you would like to apply and hit OK.
- Tag & Tag 2: Within SapphireOne Accounting Software, a user createable drop-down menu is available to enable users to mark a record with up to two tags. For all tags in SapphireOne please follow the procedure below to add or delete a tag.
- Adding a Tag –To add a new tag to the list, follow these steps.
- Enter the desired new name into the tag box on the screen.
- When you press the tab key an alert will be displayed.
- From the alert select the
button to confirm the addition of the new tag. - Check that the item has been added to the list, if not repeat the procedure above.
- Removing a Tag – To remove a tag from the list, follow these steps:
- Select the
arrow to display the items in the drop-down menu. - Hold down the Command key (MacOS) or Control key (Windows).
- Click on the name of the tag in the list that you wish to remove.
- An alert will be displayed, asking for permission to delete the selected tag.
- From the alert select the
button to confirm the deletion from the list of tags. - Check that the item has been removed from the list, if not repeat the procedure above.
- Select the
- Adding a Tag –To add a new tag to the list, follow these steps.
Custom Page
Custom Page Overview
SapphireOne’s Custom page features text fields designed for versatile, user-defined purposes. Each field is assigned a variable by SapphireOne, which is displayed as the default field heading label. Users can take note of the desired field or heading variable for customisation and modify it by navigating to Utilities Mode > Utilities Controls > Utilities Default Settings > Utilities Change Names. Detailed instructions on this process will be provided below.
The Custom page is organised into the following sections:
- Alpha – Allows letters and numbers, but cannot be used for arithmetic functions
- Real – Allows numbers only, and can be used for arithmetic functions
- Date / Time – Date fields store date values and can be used for date functions, while Time fields store time values and can be used for time functions
- No Heading Defined – Features eight alphanumeric fields that cannot be used for arithmetic functions
- Text – Accepts letters, numbers, and special characters, but cannot be used for arithmetic functions
The data entry fields in these Custom Pages can also be employed in Sapphire Custom Reports, Quick Reports, Custom Inquiries, 4D View Pro, and 4D Write Pro Reports, just like any other data entry fields within SapphireOne.
The example Custom Page below is from an Asset Inquiry; however, the process for customising this page remains the same, irrespective of the function in which the Custom Page is located.


Default Variable Values
In the default variable values defined by SapphireOne, the first number signifies the position of the field within the group, while the second number denotes the maximum number of characters for the data entry field.
For instance, ASAlpha_1_20 indicates that it is the first data entry field in the group and can hold up to 20 characters. Similarly, ASAlpha_8_80 shows that it is the eighth data entry field in the group, with a capacity for a maximum of 80 characters.


To modify the headings on a Custom Page:
- Write down the exact names of the headings you wish to modify.
- Navigate to Utilities Mode > Utilities Controls > Utilities Default Settings > Utilities Change Names. Keep in mind that when performing this procedure, you will be warned that only one user should be logged into the data file.
- Upon accessing the Utilities Change Names function, a dialogue box will appear. Then, refer to your list of names and scroll down the list to find the headings you want to modify.
- For each heading:
- Highlight the name.
- Enter your new name in the lower data entry field.
- Click the Update button to save the changes in SapphireOne.
Action Page
Action Page Overview
The Action Page in SapphireOne serves as access to a comprehensive hub for managing and organising tasks, meetings, and notes, seamlessly integrating actionable items with relevant records and transactions. By providing access to a wide array of features such as Calendar Reminders, Meeting Invites, Alarms, Emails, To-Do Lists, and various types of Notes, the Action Page ensures that users can efficiently coordinate their activities within a centralised platform.
One of the key advantages of the Action Page is its ability to link actions directly to specific records or transactions, enhancing the accessibility and relevance of alerts throughout SapphireOne. This integration allows users to set up actionable alerts that are contextually tied to their organisational data, ensuring that important tasks and notifications are not only visible but also directly connected to the pertinent information. By leveraging these capabilities, users can improve their productivity and maintain a well-organised workflow, all within the intuitive environment of SapphireOne.


The Action Page enables users to manage actions by using the add
or delete
buttons. To add or delete an action, simply click the corresponding button.
Diary Area
The Diary Area in SapphireOne provides users with a comprehensive range of options to customise their actions. It includes the following functionality:
- Sequence – SapphireOne automatically generates a unique sequence number for each action.
- Title – Enter a title for the action.
- Type – Choose from the customisable drop-down menu to input a type. This will subsequently become a permanent type within the drop-down.
- Action – Utilise the user-customisable drop-down menu to input an Action. This will then become a permanent action within the drop-down.
- User – SapphireOne automatically inputs the user creating this action, though it can be modified if necessary.
- Private – If this checkbox is selected, SapphireOne will only permit the specified user to view or modify this action.
- Status – The user has three options: Open, Hold, and Completed.
- Open – Action is open and active.
- Hold – Action is active, but no alarms will be active.
- Completed – Action is now Inactive and won’t be displayed in any list of actions.
- Tag – Choose from the customisable drop-down menu to input a type. This will subsequently become a permanent type within the drop-down.
- Link – When created within a transaction or record, SapphireOne automatically generates a link to the transaction or record. When created from the Options Menu, Palette, or Workbook, users must select an item or function from the drop-down menu to link the action. There are 12 items on this list, ranging from Clients to Manager.
Check List Area
SapphireOne offers a user-friendly checklist tool to create and track actions, allowing users to check off completed items as they progress.
Dates and Times Area
- Start/Finish – Set a Start and Finish time for the action, or select the checkbox for an all-day option.
- Completed – Entering a completion date for an action deactivates it, and it will no longer appear in the action lists.
Alarm Area
Ensure you never miss a task again by setting up alarms to send reminders to the designated email at specified dates and times. Users can also receive notifications through SapphireOne Workflow.
Recurring Area
If necessary, the alarm can be set to recur at specified intervals chosen from the Type drop-down menu which contains an exhaustive list of interval options. Additionally, the recurring period can be defined by date.
Notes Area
This area can be used to make permanent notes or reminders when dealing with contacts. When you click on the clock button, a timestamp will be created at the beginning of the notes section. [Command or Control] places it at the end, and you can input the note straight away. The functionality is as follows:
- Right-Click context menu – Users can also customise the font, style, size, colour, and background colour of the text in the Notes area by selecting the desired text and choosing the options available from the right-click context menu
- Green Clock Button – Include a date and time stamp.
- Font Size Buttons – Modify the font size.
- Expand
button – Maximise the notes screen for unobstructed editing. You can click the same expand
button again to minimise the notes.
Invite Attendees Area
In the event module, you can invite multiple attendees to your event and track their acceptance or rejection of the invitation. You can also send them email notifications if their email addresses are provided. Additionally, you can manage and track attendees RSVP status in real-time.
In conclusion, the Action Page in SapphireOne stands as a pivotal tool for enhancing organisational efficiency and productivity. By offering access to a centralised platform that seamlessly integrates tasks, meetings, and notes with relevant records and transactions, it empowers users to maintain a streamlined and well-coordinated workflow. The ability to link actions directly to specific data points ensures that alerts are not only accessible but also contextually relevant, providing users with the insights needed to make informed decisions. As organisations continue to navigate complex operational landscapes, the Action Page remains an indispensable resource for optimising task management and fostering a more organised and productive environment within SapphireOne.
Documents Page
Documents Page Overview
The Documents Page centralises document and information storage for transactions and master tables, streamlining organisation and management for easy access and improved efficiency.


Documents Area
The Documents Page simplifies file management by allowing various document types to be attached via drag and drop, including PDFs, spreadsheets, photos, and more. It provides a centralised location for document and information storage for transactions and master tables, streamlining organisation and management for easy access and improved efficiency.
Documents can only be attached once the corresponding record has an assigned ID.
Documents List Screen Options
There are eight buttons on the Document List screen, as follows:
- Open
– Allows viewing of the currently selected document. - Update
– Prompts the user to import a new version of the selected document while maintaining links to any associated transactions. - Scan
– Accesses a scanner for scanning documents directly into the data file and linking them to the current transaction (requires a compatible scanner with software). - Save
– Saves the currently selected document. - Link Document: Enables linking of the selected document to other transactions in the data file, presenting a popup for user selection.
- Link Document
– Allows linking of an existing document in the data file to the current transaction or record, displaying a popup with a list of documents to choose from. - Link Existing Document
– Allows linking of an existing document in the data file to the current transaction or record, displaying a popup with a list of documents to choose from. - Delete
– Deletes the currently selected transaction or record. - Add
– Displays a search function for selecting a document from the local computer or device.
Details Area
The Details area allows users to add a custom name, description, and tags to each document, enabling easy search and location of specific documents. These details can be customised to meet the specific needs of the user or organisation, further improving the efficiency and organisation of the Documents Page.
Last Modified Area
The Last Modified section displays the date and time when the document was last modified, as well as the user who made the changes. This feature helps maintain accountability and enables efficient tracking of document modifications.
History Area
The History area records changes made to the document, including the date, time, and user who made the changes. This provides a valuable tool for tracking and managing document revisions.
Links Area
The Links area allows users to record links to other places where the document has been attached. Links can be added or removed using the (+) and (-) buttons, providing an efficient way to manage and organise related documents.
Notes Area
The Notes area allows users to add any relevant notes related to the document. Clicking the green clock button will add a date/time stamp, further improving document tracking and management.
Workflow Page
Workflow Page Overview
Before setting up any workflow functions, the Organisation Chart must be setup first. please read the article titled Organisation Chart.
The Workflow Rules function in SapphireOne enables users to establish rules and procedures for the approval and processing of transactions. You can create Workflow Rules in the following location: Utilities Mode > Utilities Controls > Utilities Controls Inquiries > Utilities Controls Workflow Rules.


Once you’ve set up the Workflow Rules, they can be viewed from most Inquiry Lists in SapphireOne when a transaction is opened for viewing or modification. The Workflow Rules Page displays the rules applicable to the currently opened transaction. Users can view this page with the following restrictions:
- User Access – Although all users can view the Workflow Rules relevant to the currently opened transaction on screen, they are not allowed to modify the Workflow Rules.
- Workflow User – When the user responsible for performing a task for the transaction accesses the Workflow Rules Page, they can approve or reject the transaction for further processing.
In Management mode, you can access the Workflow Centre from the main menu: Management Mode > Management Analysis > Management Workflow Centre.
To access this function, users must have the Workflow Centre item selected or ticked on the menus page in their User Access file. The Workflow Centre provides a list of all transactions in the data file that have a workflow restriction incorporated into them. This feature allows users or groups of users to manage all transactions with a workflow restriction or error placed on them.
A Workflow Rule must be set up before entering any transactions. The rule is embedded into the transaction itself upon entry and will persist even if the workflow rule related to the transaction is removed. If a workflow rule is modified and there are existing transactions that need the updated workflow rule applied to them, these transactions will have to be deleted and re-entered under the new Workflow rule.
Setting Workflow Rules in SapphireOne
Once you’ve created the stages, you can assign the appropriate user or group of users to each stage. SapphireOne allows for the creation of any number of groups with multiple users within each group, enabling various workflows and approvals to be applied to different transaction types or departments within a company. You can also set a time limit for each stage, which facilitates automated reminders to be sent to users who haven’t yet approved or notified the workflow rule.
SapphireOne has the capability to generate email notifications and reminders to be sent to users at each stage of the workflow process. These email notifications can be customised to include specific information about the transaction, such as the transaction ID, date, and amount.
Once a workflow rule has been created and applied to a transaction, it will be displayed on the Workflow Rules Page for that transaction. The user responsible for approving or notifying the workflow rule can access the Workflow Rules Page and take action accordingly. Once all stages of the workflow rule have been completed, the transaction will be authorised and can proceed to the next stage in the process.
Overall, setting workflow rules within SapphireOne provides a powerful tool for companies to manage their approvals and authorisation processes while also improving their efficiency and accuracy in handling transactions.
Workflow Example
Imagine you’ve set up a workflow rule with five stages. To progress from Stage 1 to Stage 2, it requires approval from a minimum number of users authorised to approve Stage 1, which could be set to 3 out of 5 users, for example. These authorised users can be assigned to a level within Stage 1, and you can choose to assign a type to the level, such as User, Level, or Creator. For each type, you can enable or disable checkboxes for Authorisation Required, Hierarchical Authorisation, and Email Notification.
Another example could be a workflow rule for Leave Requests. Stage 1 might involve an employee entering a Leave Request, which then moves directly to Stage 2, where the manager is notified. Stage 3 could involve HR approving the leave, and Stage 4 could be notifying the original creator (employee) whether their leave has been approved or not.
When a new transaction is created with a workflow rule, it will have an error status of “WF” and cannot be printed, converted, emailed, or posted until it has been authorised by the assigned user, group, level, or creator. If a transaction is rejected, it will remain in the list with an ongoing “WF” error status. It can then be left as is or deleted as needed.
For each rule that includes a Workflow entry, a user or group of users must be designated with a restriction, which will result in them generating all or some transactions with an error code of WF.
Moreover, a user or group of users must be set up to approve these transactions. The selection is made using the two checkboxes: ‘Authorisation Required’ and ‘Hierarchical Authorisation’.


Workflow Rules Details Page
The Change button, as seen in the screenshot below, is directly linked to the Organisation Chart function found in the Controls drop-down menu. The Organisation Chart function serves as a means to organise multiple users within a hierarchical group. This feature is further documented in a separate article on the Organisation Chart.


Details Area
The available options are as follows.
- Sequence – SapphireOne will enter a sequentially generated number, and it cannot be altered.
- Title – Enter a Name or Title for this workflow entry.
- Tag – Enter a Tag if required. Keep in mind that this list of tags can be set up by the user as needed.
- Company – SapphireOne should enter the company, but if it doesn’t, enter the company manually.
- Department – Enter a department if required.
- Transaction – Choose from the extensive list of transactions when the blue arrow is selected. For every type of transaction, the user can set up individual rules as needed.
- Rules Trigger – Next, select a rule from the Rules Trigger list box to be applied. Once the selected rule is violated, the workflow function will become active and activate the Workflow function.
- Transactions – The first three rules will generate a WF error if the user tries to Create a New Transaction, or Modify or Delete a transaction.
- Above $ – This option will generate a WF error when any transaction exceeds a specified dollar amount.
- Average Cost – Any transactions below average cost will generate a WF error.
- Credit Limit and Stop – These two options will generate a WF error when the conditions are met.
- Negative stock – Any transaction that takes inventory into a negative stock level will also generate a WF error if this option is selected.
- Leave Request – If any user makes a leave request, a WF error will be displayed, alerting the HR officer.
- Tracking Notes – This will generate a WF error, used to alert the user responsible for managing tracking notes.
- Bank Details – This is linked to SapphireOne’s G/L accounts that are bank accounts.
- Floor Price – When this option is selected, a WF error will be sent to the chosen user, allowing them to approve or disapprove the sale.
Workflow Stages
- Stages – Next, set the number of hierarchical stages that must be navigated before the WF error is removed. Each stage will occupy a column in each row in the flow list. Up to 6 stages or levels of authorisation are provided, although managing 6 levels could be challenging. To simplify it, entering the number 3 here will set up three columns in the flow area below with default headings.

- Single Stage – If only a single level of approval is required, leave the Stage set at 1 for a single level of approval. The flow area below will display just one item across the entire row, as seen to the right.

- Multiple Stages – If more stages or levels are required, enter a number from 2 to 6. The additional stages will be added as extra columns in the flow area, as seen to the right.
- Notes – Any notes for this workflow rule can be entered here.
Now that we have created a rule for a transaction, we need to select how it is to be applied. In the Flow area, enter the Users or the Level of users to whom the rule will be applied.
Flow Area
- New Button – To enter in a new event the following procedure must be followed.
- Column or Stage Selection – The user must first select the column and then click the New button
in the top right-hand corner of the Flow area. SapphireOne will place the word “User” in the column that was selected. - Multiple Stages – Repeat the procedures above for each column or stage in the workflow function. From now on, once one of the stages in the line has been selected, it will change to the orange colour, as seen below.
- Column or Stage Selection – The user must first select the column and then click the New button

- Stage Selection – The user must now select each stage in sequence and set up the following details for every stage.
- Stage – SapphireOne will add a suffix of the stage number to the name “Stage”. The user may then enter a column heading name for the stage if required.
- Type – The user has 2 choices here: Approve or Notify. If “Approve” is selected, the user will have to go through the approval process before the Workflow error is removed for them. If “Notify” is selected, the user will only have to open the transaction for viewing.
- Number – The number entered here indicates the number of users that have to approve this transaction before the WF error is removed from the transaction. Zero means none, and 5 means five. Be careful here, as the default is usually not wanted, so a number will have to be manually entered.

Party Group
For each stage, this area sets up the users and the tasks they are to perform for this Workflow function.
- Type – This will determine how the workflow rule will be applied as follows.
- User – When this option is selected, a data entry field will be displayed, allowing the user to enter a selected user’s ID, linking the rule to a single chosen user. Once a user ID has been selected, SapphireOne will display the selected user’s ID.
- Level – When this option is selected, the Change button will be displayed. When it is clicked, SapphireOne will display the organisational chart, allowing the user to select an organisational level for this rule to be applied to. Once a level has been selected, SapphireOne will display the name of the level selected.
- Creator – When this option is selected, SapphireOne will allow the creator of the transaction to process the transaction.
- Authorisation Required checkbox – This checkbox is crucial in relation to the Workflow Rules function. When selected, SapphireOne will enforce the WF error for the selection made in the Link radio buttons. If it is not selected, SapphireOne will allow the user to create and save transactions as listed without a WF error as normal. However, they will also receive the active message pop-up dialogue when there are transactions within SapphireOne created by other users that meet the criteria set up in the Workflow rule.
- Selected – Restricted saving of the selected transactions with WF error.
- De-Selected – All transactions saved normally and permission to approve selected transactions.
- Hierarchical Authorisation Checkbox –If this checkbox is selected, SapphireOne will allow anyone above the level that has been entered for the stage to authorise the transaction.
- Notes – Finally, enter any notes for this workflow entry.
Checking for WF Transactions
User Work Flow Alert – For any user required to approve workflow transactions, there will be an additional button displayed at the right-hand end of the toolbar, as seen here
.
When the user clicks this button
, SapphireOne will display an alert dialogue indicating how many workflow transactions require their attention for processing.
Organisation Levels and Mixed Permissions
Note that the Organisation Levels referred to here are from the Organisation Chart function in the Controls drop-down menu.
When Organisational Levels are used when setting permissions for Workflow Rules, the Levels are not hierarchical. In the level above, a user will not have automatic authorisation permissions granted. If this were allowed, everyone above the working level would be viewing authorisation alerts, including the General Manager or CFO.
Authorisation may only be assigned at a particular level by selecting the Authorisation Required checkbox for any user or groups of users in SapphireOne.
If authorisation permission is to be set at the User Level, the users should not have the Rules Level set in their user file on the first page of a User Inquiry (Details Page). Care will also have to be exercised when Organisation levels are used with users on a user-by-user basis.
Probably the most common error when setting up this function is the creation of a conflict. For example, authorisation has been granted for Sales Managers and Authorisation Required for the user SapphireOne Sydney, who is also in the Sales Managers group. That is a direct conflict that must be avoided at all costs, as the user has been included as part of the Sales Managers level.
Do not mix permissions. Ensure that a specific user who is not allowed to authorise transactions does not also form part of any organisational level that may authorise transactions.
Workflow In Operation (Restrictions)
When a user creates a transaction and saves it, SapphireOne determines if a workflow rule should be enforced. If a rule is broken and the checkbox has been selected, SapphireOne proceeds to save the transaction with a status of “err” for error. The error code will be “WF” for Workflow, meaning that a user with appropriate authorisation must approve the transaction in order to remove the error code and enable further processing, as documented on the previous page.
From SapphireOne’s setup, there are two types of users who will require authorisation or be able to authorise transactions:
- User who initiates or creates the Transaction – The user’s ID will be recorded by SapphireOne, and they will be the only user to receive the Active Message pop-up for the transactions they create. Until a user actually creates a transaction, they will not receive any Active Message authorisation pop-ups. OR Specific Users, for example, SONE0 SapphireOne Syd, i.e., a new staff member whose transactions management wants to check before processing. They will also only receive the Active Message pop-up for the transactions they create.
- User Level – This is different, as it refers to a group of users who share the same Rules Level set in the first page of their User Access Inquiry. Once a transaction has been created by a single member of the Rules Level Group, all users in the same group will receive the Active Message pop-up. For example, if there is more than one user with a Level of Sales Manager set in their user file, they would all be presented with the Active Message pop-up.
Workflow In Operation (Approvals)
The rules for approvals follow the same logic as for restrictions, only in reverse. Some planning will be required when setting up the rules to ensure the desired outcome is achieved. If organisational chart levels are used throughout, and you have 100 sales staff and 1 sales manager set to authorise transactions, the Active Message pop-up will be displayed to all 101 users. This may not be the desired outcome, as it could lead to inefficiencies and unnecessary notifications for some users.
To prevent this issue, it is crucial to carefully plan and set up the Workflow Rules according to your organisation’s structure and requirements. You may choose to have specific users or levels to handle approvals, or you may implement a more hierarchical approach to ensure that only the necessary users are notified and involved in the approval process.
By carefully considering the organisational structure and the roles of each user in the Workflow Rules, you can create an efficient and effective approval process that meets the needs of your organisation without causing unnecessary confusion or delays in transaction processing.
Setting Up Rules
The Authorisation Required checkbox must only be selected for users who are permitted to authorise transactions.
There are three options for selecting users when setting authorisation rules, which are detailed below:
- User by User Basis: The user ID of each individual user must be entered. This option can be used in two ways: for a specific user who is authorised to approve transactions, or for a new staff member whom management wants to monitor by checking all transactions they create before further processing.
- Organisational Level Basis: This option can be used when a group of users is selected from the organisational chart. For example, all sales staff could be set up so that any transaction they create requires authorisation. However, it should be noted that this could create a problem where all sales staff are presented with an “Active Message” for every transaction created by any user in the sales staff group, which could become annoying.
- User Who Starts Transaction: This is likely the best option for setting authorisation rules. By not selecting the “Authorisation Required” checkbox, SapphireOne will require that all transactions be authorised, but only the user who created the transaction and any user with the checkbox selected will be presented with the “Active Message” popup.
Two Events per Rule
As shown below, for every rule set up, there must be a minimum of two events established. One that necessitates authorisation and one that doesn’t, as shown below. It’s not enough to have a WF error on a transaction; there must be at least one staff member who can authorise any WF transactions that are created.
Examples

For every rule created, there must be at least two events set up: one that requires authorisation and one that does not. It is important to have at least one staff member who can approve any WF transactions that are created. From the Organisation Chart referred to above we will discuss three scenarios.
Scenario 1
- Sales Staff – Set up users performing sales or purchases in the AccPayableStaff level.
- The Authorisation Required checkbox is selected.
- Sales Managers- Set up one or more users as Sales Managers in the AccPayableMan level.
- The Authorisation Required checkbox would not be selected.
- End result – All sales staff will create transactions with a WF error requiring the Sales Manager to approve them. The Active Message alert will be displayed to the user who created the transaction and the Sales Manager. Even if another user modifies the transaction, only the user who created the transaction and the Sales Manager will receive notification messages.
Scenario 2
- User Who creates the Transaction- For the user who creates the transaction.
- The Authorisation Required checkbox is selected.
- Sales Managers- As above, set up one or more users as Sales Managers in the AccPayableMan level.
- The Authorisation Required checkbox would not be selected.
- End Result – All Sales staff will create transactions with an WF error requiring the Sales Manager to approve them all. The Active Message alert will be displayed to the user who created the transaction and the Sales Manager. Even if another user modifies the transaction the only user who receives notification messages will be the user who created the transaction and the Sales manager.
Scenario 3
- User – If necessary for any created transaction, a specifically selected user may be set up to receive notifications about all transactions with workflow errors. This Sales Staff user must not have a Level of Sales Staff set in their user file, or a conflict will arise.
- Select User from the Change button options.
- The Authorisation Required checkbox is selected.
- Sales Managers – Set up one or more users as Sales Managers in the AccPayableMan level.
- The Authorisation Required checkbox would not be selected.
- End Result – Only the Accounts Manager and the entered user will receive any alerts for Workflow.
Ensure that only one user has been granted authorisation privileges and does not belong to any other group or organisational level. If two specific users or levels have authorisation privileges, all of them will have to authorise transactions before the WF error code is released, unless they are part of an organisational level.









