Packages Included in 2cloudnine Payroll General Ledger
This Configuration Guide to the 2cloudnine Payroll General Ledger Extension covers the following package, which must be installed only after you have successfully completed the Pre-Installation checklist, detailed later in this document. Following this guide in sequence will ensure the correct installation and configuration of the General Ledger Extension package.
Important Information
Only an authorised Salesforce System Administrator or Partner should be actioning any installation,
configuration items, and tasks.
There may be compulsory and optional configuration items and tasks that need to be completed pre and
post-installation of the package. These will be highlighted in the checklists given in this document, with
further details given within this document.
It is required that you complete the installation and configuration of the main 2cloudnine Payroll
packages before attempting to install the General Ledger Extension Package. You can do so by following
the steps given in the Configuration Guide To 2cloudnine Payroll Suite. This will ensure that any
prerequisite/base configuration needed for the General Ledger has also been completed.
The installer will be responsible for ensuring all these configuration items and tasks are completed within
a reasonable timeframe of the package being installed. Please ensure you have familiarised yourself with
all of the requirements before installing the package, and ensure you have sufficient time and resources
available. Failing to do so can negatively impact the User experience and stability of 2cloudnine Payroll
and General Ledger.
This guide should always be accessed from Salesforce and used via your web browser. This will ensure
you are viewing the most recent version of the document. Further, downloading the document and
opening it with desktop programs, such as Adobe, has been found to cause errors when copying and
using the scripts provided for data updates. These errors do not occur when viewed through a browser.
Read First: How to Use this Configuration Guide
What is covered by this Configuration Guide?
This Configuration Guide outlines the ‘out of the box’ setup of 2cloudnine General Ledger Extension, including built-in customisations to the customer-required processes and data. Where customisation is built into the product, we will cover how to install and configure it correctly. Where, during the sales process and discovery, it is identified that the need for further customisations outside of those built by the 2cloudnine General Ledger Extension will be required, this would not be covered by this Configuration Guide.Discovery and Configuration Guide
This Configuration Guide is meant to be used in conjunction with the Discovery Workbook. Through Discovery, you will assess the customer needs and identify what 2cloudnine General Ledger requirements and functionality are required to meet those needs. Please note that General Ledger now has its own separate Discovery Workbook. Once we have established the work required, we can then use the Configuration Guide to establish what configuration needs to be completed.Task Types
- General Salesforce Setup
- Custom Settings, Metadata Types, and Setting Configuration
- Wizards and Scripts
- Schedule Jobs
- Records Creation
- Page Layouts and Other User Interfaces
- Base Data / Records Set Up
- Baseline Testing
- Security Set Up
- Data Migration
Task Classifications
This Configuration Guide is made up of a series of tasks that are either compulsory or optional and must be completed to successfully use the 2cloudnine General Ledger Extension. Each task is allocated 1 of 3 possible classifications, which are:- Compulsory must be completed regardless of whether the organisation will use the related functionality. Example: it is a Compulsory task to create the General Ledger records during the setup process, to use with 2cloudnine Payroll.
- Conditionally Compulsory must be completed if the organisation is choosing to use a specific functionality within the 2cloudnine General Ledger Extension. When a task is Conditionally Compulsory, we will detail the condition(s) that make it compulsory. Example: if the organisation is going to use the 2cloudnine General Ledger Extension functionality to split revenue by Department, it is a Conditionally Compulsory task to create the required Accounting Segments for Assignment Departments. If the organisation does not use the functionality, the users will not have to complete the task.
- Optional tasks will only need to be completed to use an optional feature of 2cloudnine General Ledger. In these cases, there is often a Default behaviour(s) built into the 2cloudnine General Ledger, and if the organisation wishes to use the Default behaviour(s), they don’t have to do anything else. Where an organisation is not going to use the Default behaviour(s), an optional task will be set.
1. Pre-Installation
Prerequisites
Before you can install the 2cloudnine General Ledger Extension package, you must (at a minimum) already have 2cloudnine Payroll, 2cloudnine Time2Pay Extension, and the 2cloudnine Data Creation packages installed and configured. Refer to the Configuration Guide for these here:Before you get started, you will need to know the following:
To assist with a successful configuration of your 2cloudnine General Ledger package, it’s important to make sure you have already gained the required information for the following questions :- What Accounting/Finance System is the client importing into?
- The type of files required to be exported from 2cloudnine (Payroll, Invoice, and Client) – make sure
you get a sample import file from the client. This will make it easier to create the file export.
- Payroll – Cost of Payroll Journal
- Invoice – Invoice Journal (Cost of Sales)
- Client file – this is used so the client doesn’t have to re-enter or update client records in their Accounting system. Not mandatory, some clients might want to manually enter this information.
- The Chart of Accounts. This can be imported into the Accounting Segments > Natural Accounts.
- Does the data need to be split by Departments, or Cost Codes (Cost Centres)?
Note
- The Payroll Journal and Accounting Invoices can only be exported at the summary level with the standard 2cloudnine General Ledger Package.
- When exporting Accounting Invoices from 2cloudnine Payroll, the Client’s Name or the GL Client Number must match with what is in their Accounting system. If it doesn’t match, then the file may fail.
2. Installation and Configuration Checklist
Installation and Configuration Checklist
The following checklist summarises the tasks that are to be performed to install and configure 2cloudnine General Ledger Extension. A higher level of detail on what is required can be found by following the link to each specific task. Each task should be completed in the sequence below to ensure seamless installation and configuration of the packages.| Task | Requirement | Completed |
|---|---|---|
| Package Installation | ||
| Installing Packages | Compulsory | |
| Installation Process | Compulsory | |
| Salesforce Apex Settings (Setup) | ||
| Perform Synchronous Compile on Deploy | Compulsory | |
| Automations for Payroll & Leave Accrual Journals | ||
| Enable Apex Class Access | Compulsory | |
| Activate the General Ledger Flows | Compulsory | |
| Page Layout Assignments | ||
| Page Layout Assignments | Compulsory | |
| Activate Flows for Automation of Assignment Costs | ||
| Employment Cost Creation Flow | Optional | |
| Create General Ledger Records | ||
| Create General Ledger Records | Compulsory | |
| Detail Accounting System Setup in the Custom Settings | ||
| Check the Accounting System Setup | Compulsory | |
| Define the Accounting/Finance system for General Ledger | Compulsory | |
| Populating the “GL Customer ID” | ||
| Only for Invoicing Clients | Conditionally Compulsory | |
| Creation of Assignment Departments | ||
| Automatic assignment of the Accounting Assignment Departments | Optional | |
| Review Pay Code OnCost Calculations | ||
| Enable OnCost Calculations/Reporting for Pay Codes | Compulsory | |
| Testing the GL Cost of Payroll and Leave Journals | ||
| Testing the GL Cost of Payroll and Leave Journals | Compulsory | |
| Regenerate a Payroll Journal | ||
| Regenerate a Payroll Journal | Compulsory | |
| Test Accounting Invoices (only for Invoicing Orgs) | ||
| Test Accounting Invoices (only for Invoicing Orgs) | Conditionally Compulsory | |
| Create Export Reports | ||
| Create Export Reports | Optional | |
| Payroll OnCost Reports | ||
| Payroll OnCost Reports | Compulsory | |
| Using Assignment Departments to split Default posting Accounts (Alternative Customisations) | ||
| Step 1: Create all State and Department combinations as Department Accounting Segment Values | Optional | |
| Step 2: Add formula fields to the Accounting Segment Object | Optional | |
| Step 3: Further refinements | Optional | |
| Cost Code Splits | ||
| Cost Code Splits | Conditionally Compulsory | |
| Add Picklist Values and Update Assignment record | ||
| Add new Industry and Risk Classification Picklist Values | Compulsory | |
| Update the Assignment record | Compulsory | |
| Alternate GL Payroll Journal processing options (Optional Customisations) | ||
| Option 1 - Align Accounting Departments to Assignments and use the standard Payroll Journal creation process (14 hours work) | Optional | |
| Option 2 - Customer manually extracts source Pay Transaction Data and creates their Payroll Journals outside of 2cloudnine Payroll (8 - 12 Hours) | Optional | |
| Option 3 - Customer extracts source Pay Transaction Data using Custom integration and creates their Journals outside of Payroll (12 - 18 Hours) | Optional | |
| Creating AU Oncost Distribution Records | ||
| AU Payroll Costs Distribution Records and Reporting | Optional | |
3. Package Installation
Installing Packages
Please make sure to install the required package now before completing any further configuration. You can proceed further only once the required package has been installed.Installation Process
When you install a managed package, you need to select the correct option of either a), b), or c) below, to ensure access to the Package is provided to the Profiles as needed:- Install for Admins Only
- Install for All Users
- Install for Specific Profiles - To manually select which Profiles you will be applying the security to.
4. Salesforce Apex Settings (Setup)
Perform Synchronous Compile on Deploy
To enable the above setting in the Org: Go to Setup > Apex Settings >- Tick Perform Synchronous Compile on Deploy (see Figure 1).
- Click Save .
5. Automations for Payroll & Leave Accrual Journals
Enable Apex Class Access
- Go to Setup > Developer Console .
- Select Query Editor and paste the following text (see Figure 2):
- SELECT ProfileId FROM User WHERE Alias = ‘autoproc’
- Click the Execute button.
- After the query runs, copy the Profile ID that appears in the results to another document.
- In your Salesforce browser tab, clear the URL after .com
- Paste this URL /_ui/system/user/ProfileApexClassPermissionEdit/e?profile_id=00e2v000003cNu3AAE
- Update the Profile ID listed above in red to be the one you copied earlier from Step 4.
- Push across the following Available Apex Classes to Enabled Apex Classes (see Figure 3).
- Select Save .
Activate the General Ledger Flows
As part of the automations within the General Ledger Extension package, there is a Flow that can be activated to automatically create the Cost of Payroll Journals and Leave Accrual Journals after a Pay Batch is progressed to a status of Payment File Released. Go to Setup > Flows- Scroll through the list of Flows until you get to the following Flow:
- GL - Create Cost of Payroll and Leave Accrual Journal
- Open the Flow mentioned above.
- Click the Activate button.
- Once activated, Journals will automatically get created after a Pay Batch has reached the status of ‘Payment File Released’.
- The Leave Liability Rate on the Payee Leave Rule must be populated with an appropriate hourly rate (see Figure 4).
- Once populated, all future Leave Accrual Pay Transactions will use this rate within the Leave Liability Rate field. The Leave Liability Total field will also now reference the Leave Liability Rate x Leave Accrual.
- After the Pay Batch has reached the status of Payment File Released, the Total Leave Accrual values on the Leave Accrual Pay Transactions will be allocated across the Payment Pay Transactions. See the following example of Pay Transaction Distribution records against a Payee Pay Batch (see Figure 5).
6. Page Layout Assignments
The following updates to Page Layout Assignments are required in your Org. These Page Layouts do not come automatically assigned in the Package. As a minimum, the following Profiles require updates:- System Administrator Profile
- 2cloudnine Payroll User Profile
- Any other custom profiles created for ‘back office’ users.
Assignment
- Click the Edit Assignment button.
- Using the table below, for each Record Type detailed, assign the listed Page Layout Name.
- When complete, select the Save button.
7. Activate Flows for Automation of Assignment Costs
To enable the automatic creation of Assignment Costs, you need to activate the two Flows that are included within the General Ledger Extension package.Employment Cost Creation Flow
This configuration is optional and is only necessary to allow Employment Cost Template Groups to be used in an Org for the automatic creation and population of Assignment Cost records against Temp Assignments. Once enabled, this Flow will auto-fill Assignment Cost records that are generated when using the Employment Cost Template Group to auto-create and relate Assignment Cost records within Temp Assignment records. Also, if the Employment Cost Template Group is updated in the Assignment record, this Flow will ensure that the existing related Assignment Cost records aren’t deleted, but instead set to Inactive. This allows any existing OnCost Transactions that have been created to retain the link to the original Assignment Cost records. Go to Setup > Flows- Open the Flow labelled GL - Set/Update Assignment Cost Records (this Flow Template is included in the General Ledger Package).
- Select Save As .
- From the Save As pop-up window, complete the following fields:
- Enter a name for the new Flow in Field Label (i.e. GL - Set and Update Assignment Cost Records) (see Figure 6).
- The Flow API Name field will auto-populate based on the value entered into the Field Label.
- Select the Show Advanced link below the Description field.
- Ensure the Type selected is ‘Record-triggered flow’.
- Ensure the checkbox for Template is not ticked (see Figure 6).
- Click Save .
- Once saved, and returned back to the Flow Builder page, select the Activate button in the top right-hand corner to enable the Flow.
8. Create General Ledger Records
The next step is to create various records that represent your General Ledger within 2c9 Payroll. The creation of these General Ledger records may take a while and must be done before proceeding further to the next section. If there is a large number of records to be created, it is recommended to create these records with the use of a data load tool. To assist with the creation of the General Ledger records, you can review the information provided in the General Ledger Key Information document. Please refer to the QRG General Ledger - Key Information.Important Notes(Records creation)It is important to create the records using the above QRGs before proceeding further with the
remaining configuration in this document.
9. Detail Accounting System Setup in the Custom Settings
Check the Accounting System Setup
Before completing this step, you will need to ensure the Accounting System Setup record has been created. For more information on how to create an Accounting System Setup record, please refer to the QRG Accounting System Setup - Create record.Define the Accounting/Finance system for the General Ledger
This step is required so 2cloudnine Payroll can use the Accounting System Setup Id to know which Accounting System Setup record needs to have the post Pay Batch steps performed automatically to create the Accounting Payroll Journals.- Go to Setup > Custom Settings .
- Click the Manage button next to GL Configuration .
- Click the New button at the top, which applies as a Default Org Wide Setting (if you select the New button underneath the black line, it applies only to the logged-in user).
- Default Account System Setup Id = the Accounting System Setup Id.
- Run Processes post Pay Batch Completion = TRUE.
- Once complete, click Save .
10. Populating the “GL Customer ID”
Only for Invoicing Clients
This is only required if the Client records are being synced into the Accounting System. For Accounting Invoices to work, the GL Customer ID field on the Account needs to be populated. In the General Ledger Extension package, we include a text field on the Account that is used to hold the Customer ID. Note that we do this to allow a customer to create their own Autonumber field. Once a customer has created their own unique Autonumber field, you need to create a Flow that populates the GL Customer ID field and ensures that this is always kept in sync. It would also be recommended to create a validation rule to ensure that once a value is inserted into this field, this value is unable to be changed.11. Creation of Assignment Departments
Automatic assignment of the Accounting Assignment Departments
In many cases, the creation of the Accounting Assignment Department records will need to be automated (e.g. there will be revenue splits defined in an HR system that need to be imported into 2c9 Payroll). In such cases, Users will need to implement an automation, such as a Flow to support the automatic creation and maintenance of the Assignment Department records upon the creation of Assignments.12. Review Pay Code OnCost Calculations
Enable OnCost Calculations/Reporting for Pay Codes
To enable accurate OnCost calculations and reporting, Pay Codes must be configured with the ‘AU Payroll Tax Reportable’ field selected by default. To check and make sure that the Pay Codes have been set up with the ‘AU Payroll Tax Reportable’ field, follow the steps below:- Go to the Pay Codes Object.
- Select a relevant Pay Code record.
- To mark all Pay Transactions generated with this Pay Code as Payroll Tax Reportable, ensure the ‘AU Payroll Tax Reportable?’ checkbox field has been selected.
- To ensure any relevant Tax Report Exceptions have been detailed, review the ‘AU Payroll Tax Report Exceptions’ field with any relevant exceptions.
- To mark Pay Transactions generated against this Pay Code as WorkCover reportable, ensure that the ‘WorkCover Reportable?’ checkbox field has been selected.
13. Testing the Cost of Payroll and Leave Journals
After completing a Pay Batch through to the stage of Payment File Released, you should now be able to review if a Payroll Journal and a Leave Accruals Journal have been created automatically.- Navigate to the Accounting Payroll Journal Object.
- Confirm there is a Payroll Journal listed for your Pay Batch that has just completed.
- Open the Payroll Journal and confirm the Accounting Payroll Journal Lines match the amounts in your Pay Batch, and contain the Accounting Segments/Departments.
14. Regenerate a Payroll Journal
To regenerate a Payroll Journal that has been previously created, ensure that the Recreate GL Journals & PT Distributions Flow is deployed in your Org. Go to Setup - Flows, search and find the Recreate GL Journals & PT Distributions flow.- Open the Flow, and click the Run button.
- The Recreate GL Journals & PT Distributions Screen Flow will appear.
- Select which option you would like to process, either A or B .
- In the Pay Batch section, search for and select the Pay Batch you would like to regenerate the Payroll Journal for.
- Select Next, and follow the Wizard until you finish.
- Once the Payroll Journal has been generated, you will see that the original Payroll Journal is deleted and replaced with the new Payroll Journal.
15. Test Accounting Invoices (only for Invoicing Orgs)
After checking the above setup and the required records have been created accurately, you can now test the creation of Accounting Invoices. To learn more about how to create Accounting Invoices, please refer to the QRG Create an Accounting Invoice.16. Create Export Reports
To export the data from 2cloudnine Payroll into an external Accounting System, you will need to create a Custom Report for each type of file format required. This might include Cost of Payroll Journals, Cost of Sales Journals, and Client Detail Exports, to name a few. You will need to liaise with the Client to attain the current formats required to be imported into their external financial software. These custom reports may also require Custom Report Types created before the Reports are created within the standard Reports functions. Depending on the specific requirements, there may be a requirement for these reports to be automatically exported via custom integration. If this is needed, please discuss it with the 2cloudnine Integration team for their assistance.17. Payroll OnCost Report
The 2cloudnine General Ledger Package includes a standard Payroll OnCost Report. It contains information from the Pay Batch, detailing Allowance Pay Transactions and Payment Pay Transactions. This includes summaries for Pay Totals and Superannuation Totals, Earnings, WorkCover, and Payroll Tax for Superannuation, followed by summaries for Total WorkCover and Total Payroll Tax. Go to App Launcher > Reports > GL AU OnCosts Report- The Report uses default filters to detail all Pay Transaction Distributions for the Current Financial Quarter, with a Record Type of AU Payroll Costs.
- If you require the reporting Period to be changed, please update the Filter from the Current Financial Quarter to the required period to be reported, and ensure it’s saved to replace the existing report or saved as a new report to be run in addition to the default one.
- Assignment
- Industry
- Location
- Pay Code
- Pay Code Detail Fields - WorkCover Reportable, Payroll Tax Reportable, amounts calculated
- Original Pay Transaction
- Pay Transaction for Superannuation
18. Using Assignment Departments to split Default Posting Accounts (Alternate Customisations)
If you have a requirement to split GL Earnings Posting Accounts based on the Assignment Department values, this can be achieved by completing the following steps. Example Customer requirement:Step 1: Create all State and Department combinations as Department Accounting Segment
Values
Create Accounting Segment Department records for all of the combinations of Department and State that are required. Here is an example of one of them:
Step 2: Add formula fields to the Accounting Segment Object
Add 3 custom formula fields onto the Accounting Segment Object. Below are the steps and screenshots of an example field to assist with this process. Go to Setup > Object Manager > Accounting Segment > Fields & Relationships- Select the New button.
- Choose Formula and select the Next button (see Figure 8).
- Provide a Field Label, which will auto-populate a Field Name, and choose Formula Return Type of Text (see Figure 9) and select the Next button.
- Create a formula that outputs the Earnings Natural Account number for the specific Accounting Segment Value (see Figure 10). Please note that the Segment Value field is the Primary field in the object, and in Salesforce, this Primary field has an API reference of ‘Name’.
Important Notes(Example syntax)This is one example of the syntax you can use, but there are other ways to use the formula syntax to
achieve the same result.
- Populate the following optional fields (see Figure 11):
- Description
- Help Text
- Tick one of the radio buttons under Blank Field Handling as per your requirement.
- Click Next.
- Determine which Profiles require access to this field and access to all values in this field. Users need to determine if you want to add this new formula field onto your existing Page Layouts (recommended). This provides visibility of the results of this formula field when viewing a record.
- Repeat steps 1-7 to create the additional 2 formula fields for Superannuation and Payroll Tax as required and outlined in the Example Customer requirement table above, as well as any additional formula fields required.
Step 3: Further refinements
Now that you have completed this step, you will be able to reference these new fields in Reports.Important Notes(Custom Report Types)Any Custom Report types already created will need to have these new fields added into the Custom
Report Types in order for them to be used within Reports and Dashboards.If necessary, you can create a Custom Formula Field on the Accounting Payroll Journal Lines Object in
place of the standard Natural Account field that outputs the values of the Custom Fields. Here is an
example of the formula logic that you would use to achieve this (see Figure 13).
19. Cost Code Splits
Earlier in this document, we created Accounting Segment records including Assignment Department and Cost Code records. It is important to note that Assignment Departments are used to split the costs related to an Assignment record (as mentioned earlier), whereas Cost Codes are used to split the costs detailed on Timesheet records. Cost Codes are most commonly populated automatically through third-party scheduling software. They are added to the Timesheet Item records. As an example, when Timesheets are sent from the external scheduling software to 2cloudnine, they are sent in the form of Timesheet Items and Cost Codes Splits, where 20% of the Timesheet Entries can belong to Cost Code 7000, 20% to Cost Code 5000, and the remaining to Cost Code 2000.20. Add Picklist Values and Update Assignment record
Add new Industry and Risk Classification Picklist Values
The Industry and Risk Classification picklists by default contain only a few values. This is because each client’s requirements around managing industry and risk classifications are different. To add a new Industry: Go to Setup - Object Manager - Employment Cost Item - Fields & Relationships - Industry- Select the button View Industry Picklist Value Set .
- Select the New button.
- Input the new values required, ensuring you press enter between each value.
- Select the checkbox Add the new picklist values to all Record Types that use this Global Value Set and then select Save (See Figure 14).
- Select the button View Risk Classification Picklist Value Set .
- Select the New button.
- Input the new values required, ensuring you press enter between each value.
- Select the checkbox Add the new picklist values to all Record Types that use this Global Value Set and then select Save (See Figure 14).
Update the Assignment
Go to the Assignment record and complete the steps below:- Populate the following fields (see Figure 15):
- Location
- Industry
- Risk Classification
- Employment Cost Template Group
- Click Save .
21. Alternate GL Payroll Journal processing options (Optional Customisations)
This customisation is often suitable where a Client wants to break down their Cost Of Payroll Journals at a lower level than the Accounting Department, based on data related to the Assignment, Employee or Client. IMPORTANT : The estimates provided here do not include the time it takes to complete the core General Ledger Integration Setup.Option 1 - Align Accounting Departments to Assignments and use the standard Payroll
Journal creation process (14 hours work)
Note: this method supports splits by Cost Code as well as by Assignment.- Add a new field on the Accounting Segment Object which is a lookup to the Assignment.
- Every time a new Assignment is created, insert a new Accounting Segment (Record Type = Department) record for this Assignment. (Would suggest completing this requirement with the creation of a Custom Flow).
- Once Step 2 is complete, create a new Accounting Assignment Department record linked to the Accounting Segment just created with a Split of 100% (would suggest completing this requirement with the creation of another Custom Flow).
- Ensure the Accounting System Setup is configured to split the journals by Department.
- Include Formula fields on the Accounting Payroll Journal Line object that provide lookups to the values related to the Assignment record that the customer is looking to break their journals into (e.g. Employee, Client, etc).
Option 2 - Customer manually extracts source Pay Transaction Data and creates their
Payroll Journals outside of 2cloudnine Payroll (8 - 12 Hours)
- Create Custom Report Types that support the data to be extracted as required by the Client. If there are breakdowns that they want to achieve that you are unable to support using a single Report Type, then extract the source data for them using separate reports (e.g. Cost Code breakdowns).
- Create a series of reports using these Custom Report Types allowing a Client to manually extract this data. It will be the responsibility of the customer to ensure that they have a process to ensure the data they are extracting is not missed or duplicated. We would suggest that this should be done using the Pay Batch (with a status of Payment File Released) as a filter for the exports.
Option 3 - Customer extracts source Pay Transaction Data using custom integration and
creates their journals outside of Payroll (12 - 18 Hours)
- Assuming that the customer has purchased a custom integration, then an integration process can be created that automates the extraction of the detailed Pay Transaction data on a scheduled basis as CSV files. If this data is to be extracted to a structured external data source, then an additional fee would be charged to cover the cost of the additional work to be completed.
- As each extract is completed, a field on the Pay Transaction would be updated to mark that it had been successfully exported which provides a greater degree of control over Option 2. The process would also be automated and not require a User to process it.
22. Creating AU Oncost Distribution Records
In order to create AU Oncost Distribution Records, the On-Cost must be defined on the Assignment before processing it in a Pay Batch. The creation of the AU Oncost Distribution records is an automatic process that occurs once a Pay Batch Status reaches the status of Payment File Released. This triggers a Platform Event to run and create Pay Transaction Distribution records autonomously with a Record Type of ‘AU Payroll Costs’ (See Figure 16). A Pay Transaction Distribution record will be created for every applicable Pay Transaction where the related Pay Code is either AU Payroll Tax Reportable or WorkCover Reportable. Pay Transaction Distributions are related to both the Pay Batch and Assignment records.
AU Payroll Costs Distribution Records and Reporting
The following screenshot (See Figure 17) shows the Pay Transaction Distribution record and the level of detail available for reporting purposes.
