Home > Tutorials

Invoicing Scenario 1


This document outlines the various components to configure your invoicing to support the scenarios outlined:
  • Invoice a regional office
  • Invoice the location direct

Getting There:

[N/A ] –>


There are two aspects to all invoicing management to keep in mind - these will be combined to deliver each of the desired scenarios as detailed in this brief tutorial.

You'll recall that a master client is configured with NO "Charge To Code", and that a sub-client does in fact have a value for "Charge To Code".

master client sub client

The Client "V-02" indicates that Client "VM-0001" is its master in the hierarchy. Head Office will be configured as NOT providing rostering services and will not appear on the scheduling workbench for rostering.


Service Charges

The other factor that seperates master from sub is that relating to charges for services:

The master client (Head Office) is always configured with the details of all charge rates for all services provided (as below).

charge rates

The sub-client will have charge codes & individual rates only for those services where the sub-client has a different charge rate to that of the master (Head Office) (as below).

charge rate

What is evident in this sample configuration is that the sub-client has all the same charge codes as the master client, and hence the charges will always be those that are defined at the sub-client level.

In the case of D3, the above example shows both the master and sub-client with the same rate for the D3 charge code - this will create a maintenance overhead when you change the rate relating to the Sunday service - the sub-client should not have the D3 code defined, as the system will pick up the D3 code and rate from the master.

If neither the sub-client or master client have the charge code defined, then the system charge code as defined in "casual services" will be charged for the service. For example there is no charge code for D6, and hence the charges will default to the value set at the system level.

A further note is that whilst we're demonstrating the details at the Casual Services tab, the operations are exactly the same principle for Repetitive Services.

Also ensure that both the sub-client and master client have the same fee schedule as well as the same invoicing cycle, otherwise the system will not function as expected.

Top of Page

Work at each outlet, and invoice Head Office

Ensure that the outlet has defined a "Charge to Code" equal to the value of its Head Office.

Top of Page

Invoice head office for all bar 2 sites, which you are to invoice directly


You are contracted to work at each outlet, and you are to invoice head office for all bar 2 sites, which you are to invoice directly.

Top of Page

The charge rate is the same for all bar 2 sites, where the service charge rates are different for each site.


The charge rate for a typical service is the same for all bar 2 sites, where the service charge rates are different for each site.

Top of Page

Scenario 2


You deliver the same service at all sites, expect at one of the sites you deliver a further service which has its own service charge rate.

Top of Page

Sample casual services definition

This definition will not work!

charge code

In this configuration everything appears fine, other than the "Apply Award Based Charges" is not checked and hence the system will not invoke the fee interpreter, and hence the service will not be charged out.

Top of Page

See Also

SACL - whole business example

Top of Page