Legal Entity Customer Funding (AUS/NZL)

Activate User's Guide
Version
2025.4
ft:lastEdition
2025-10-14
Legal Entity Customer Funding (AUS/NZL)

Use the Legal Entity Customer Funding (AUS/NZL) wizard to add Australian or New Zealand Legal Entities to Dayforce. You can also update details for existing Australian or New Zealand Legal Entities.

For Australia, you can update the setup for Single Touch Payroll (STP) against the Legal Entity.

For New Zealand, you can update the setup for the Payday Filing against the Legal Entity.

For both countries, Default Customer Funding can be added when none exist.

Note: This wizard doesn't support making changes to existing Customer Funding details or adding additional nondefault accounts.

Before you begin

The following must be set up ahead of time to use this wizard:

  • Pay Groups for Australia or New Zealand.
  • Customer Bank Accounts.

Important notes

This wizard doesn't support making changes to existing Customer Funding details, or adding additional nondefault accounts.

Messages: Error, Warning, and Information

Activate sorts each generated message by severity:

Error codes

Actively incompatible with the data in Dayforce. If you have a data error, you must resolve the error before you can complete the installation.

Warning codes

Indicate nonstandard setup that could potentially cause an error in Dayforce. For example, if an earning code is defined as Hours x Rate and the data is amount only, the system creates a warning. However, you can still import the data into the system.

Informational codes

A notable occurrence of data in the system. For example, an informational note shows if codes are dropped from the YTD import.

Tasks

To access the Legal Entity Customer Funding (AUS/NZL) wizard:
  1. In Activate Central, click Build Dayforce and the Build Dayforce wizards show.
  2. Click Legal Entity Customer Funding (AUS/NZL) and the Intro page opens.
  3. Click the checkbox to confirm that all customer bank accounts exist in Dayforce.

    If all required customer bank accounts don't exist in Dayforce, click Back.

  4. Click Next.
To complete and upload the Legal Entity Customer Funding template:
  1. On the Legal Entity Customer Funding Data page, click Download.
  2. Select the location where you want to save the template document.
  3. Open the LegalEntityCustomerFundingTemplate_AUS_NZL.xlsx template on your computer.

    Note: The Activate release version shows in cell B3 on the Instructions tab of the template. This information helps you later determine the version of Activate you were using when you downloaded the template.

  4. On the LegalEntityCustomerFundingData tab, complete all columns with the Legal Entity data.

    Note: Instructions for populating the fields are in the section (below) and on the Instructions tab of the template.

  5. Click Save and close the document.

    You can use any file name for the template you upload. The file must be an Excel or CSV (Comma-Separated Value) document and contain the data in the required format.

    Important: Don’t change the name of the tab in the template. Activate uses the tab name to validate that the correct template is being uploaded. Also, don’t change the column headings.

  6. On the Load page, click Upload.
  7. Go to the completed Legal Entity Customer Funding Data Template document in the location where you saved it.
  8. Click Open. Activate validates the uploaded file.

    Note: If the file you uploaded has any errors, a Validation Failed message shows in red at the bottom of the page. You must correct the errors in the file on your computer and upload the file again.

    Note: When you upload an Excel file, Activate includes the name of the uploaded file into the name of the XML file it generates and loads to the Dayforce File Server. The format of the generated XML file name is <NamespaceName>_<Import Type>_<file name provided>_YYY-MM-DD_HHMM. This information makes it easier to audit files later.

  9. Click Next.
To review and confirm the data:
  1. On the Legal Entity Customer Funding Review page, review the information shown in the grid.
  2. To make updates to data on the page:
    • To correct errors in the grid, click in the field containing the error. Click Tab to move to the right and Shift+Tab to move to the left in the row. Use the scrollbars on the right side and bottom of the grid to go to other areas of the grid.
    • To save your changes in the grid, Save.
    • To delete a row, click the row and click Delete.
    • To save information in the grid to your computer, click Download File and save it to the location you want.
    • To upload the updated file from your computer, locate the file and click Upload File. The data in the file shows in the grid.
    • To remove changes in the grid that you don’t want to save, click Refresh.
    • To download a complete list of all errors from the data load process so you can review and correct them, click Download Errors File.
To install the legal entity information:

When the legal entity information is complete in Activate, you must install the data in Dayforce.

  1. On the Legal Entity Customer Funding Review page, click Load.

    The Review & Load page opens with a list of the steps to complete and an estimate of how long the installation usually takes. During the installation, the current step in the process is bolded so you can monitor the progress.

  2. Click one of the following:

    • Add Email and enter your email address to be notified when the installation process ends instead of waiting for it to finish.
    • Next when the installation is complete.

    Activate Central opens. The name of the wizard now shows in green text and there's a green checkmark to the left of the wizard’s name. The current day, date, and time of completion are shown, along with your name as the user who completed the wizard. The environment in which the installation was applied (Stage, Config, or Train) also shows.

    Note: If you want to add more information, click I want to add more. See Executing a Rollback When Using the “Add More“ Feature in the Payroll Wizards in the payroll wizards.

To verify that the template loaded successfully in Dayforce:
  1. Log in to Dayforce.
  2. Go to System Admin > Background Jobs > Job Logs.

    If you see a job called Legal Entity Import with a status of Complete, the import was successful.

  3. Review the Debug Information to verify that the count for Number of record(s) inserted is correct.

  4. Go to Org Setup > Org Payroll Setup > Legal Entity.

    You should see the legal entities from your data load updated with the details from your Activate templates, and the following defaults applied to any new legal entities:

    • Active = Yes
    • Legal Entity Status = Active
    • No Back Office = No

    You should also see the following defaults under Customer Funding Identifiers when the Bank Account information was included in the Activate template:

    • Is Default = Yes
    • Name = <Legal Entity Name>
    • Reference Code = <Legal Entity Reference Code>
    • Effective Start =1/1/1950
To load more data
  1. Access the Legal Entity Customer Funding (AUS/NZL) wizard. (See instructions above.)
  2. Upload the updated Legal Entity Customer Funding template. (See instructions above.)
  3. When a message indicates that the validation was successful, click Next.
  4. If no errors exist on the Legal Entity Customer Funding Review page, install the data in Dayforce. (See instructions above.)

Results

Fields populated in Dayforce

The data uploaded from the Legal Entity Customer Funding template populates the fields on the following pages in Dayforce.

Fields populated in Dayforce from the Legal Entity Customer Funding template
Field in Template Field in Dayforce Page in Dayforce

Reference Code

Reference Code  Org Setup > Org Payroll Setup > Legal Entity
Name Name
Description Description
Operating Country Operating Country
Federal Business ID Federal/Business ID Number
Effective Start Date Effective Start
Process for Employment Process for Employment
Address 1 Address Org Setup > Org Payroll Setup > Legal Entity, Address tab
Address 2 Address Line 2
Postal Code Zip / Postal Code
Country Country Code
State/Region State / Province
City City
Customer Bank Account Customer Bank Account Org Setup > Org Payroll Setup > Legal Entity, Identifiers tab
PAYG Ref Number PAYG Employer Reference Number Org Setup > Org Payroll Setup > Legal Entity, Taxation Parameters tab
Tax Office Contact Name

Australia - Payer Contact Name

New Zealand - Name of the Payroll Contact Person.

Org Setup > Org Payroll Setup > Legal Entity

Australia – STP Parameters tab

New Zealand – Payday Filing Details tab

Tax Office Contact Phone

Australia - Payer Business Telephone Number

New Zealand - Work Phone Number of the Payroll Contact Person
Tax Office Contact Email

Australia - Payer Email Address

New Zealand - Email of the Payroll Contact Person
IRD Number PAYE Intermediary IRD Number Org Setup > Org Payroll Setup > Legal Entity, Payday Filing Details tab
STP Branch ID Branch ID Org Setup > Org Payroll Setup > Legal Entity, STP Parameters tab
STP Payroll Run By Payroll Is Run By  Org Setup > Org Payroll Setup > Legal Entity, STP Parameters tab
STP Other Parent Legal Entity Use Another Parent Legal Entity
STP Run by Intermediary Payroll Is Run By
Registered Agent Number Registered Agent Number
Intermediary ABN Intermediary/Registered Agent ABN
Intermediary Contact Name Intermediary/Registered Agent Contact Name
Intermediary Contact Email Intermediary/Registered Agent Email Address
Intermediary Contact Phone Intermediary/Registered Agent Business Telephone Number

Next steps

Review the data in on the Dayforce Org Setup > Org Payroll Setup > Legal Entity page.

Complete the next wizard, as appropriate.

Legal Entity Customer Funding template fields

All templates have the same basic structure:

  • Instructions tab: Helps you understand the purpose of the data and complete the fields in the template.
  • Data tab: Contains headers for the data to be included in the template. The headers remain the same, but you can change the column order. If you add more columns, Activate ignores them.

All number ranges in the templates include the numbers at both ends of the range.

For information on the fields in the template, click here.
Reference Code (Required)
Field information for the Reference Code field
Order Data Type Description Examples Why This Is Needed
1 String1 between 1–256 characters.

When updating an existing legal entity, use the current Reference Code for the legal entity.

If the Reference Code doesn’t already exist, a new legal entity will be created, which will require some conditional fields to be populated.

 XYC_CO_AUS Used to identify if the legal entity already exists and requires updating, or if a new legal entity needs to be created. The Reference Code is then used in Dayforce Imports & Exports.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Name (Conditional)
Field information for the Name field
Order Data Type Description Examples Why This Is Needed
2 String1 between 1–256 characters.

The name of the legal entity, which is shown on employees' earning statements and tax forms.

Required when creating a new legal entity.

 XYC Co (AUS) Used in various forms and reports.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Description
Field information for the Description field
Order Data Type Description Examples Why This Is Needed
3 String1 between 1–512 characters. A simple description of the legal entity. XYC Company (Australia)  
Operating Country (Conditional)
Field information for the Operating Country field
Order Data Type Description Examples Why This Is Needed
4

Accepted Values:

  • AUS
  • NZL

The country where the legal entity is operating.

Required when creating a new legal entity.

 AUS
NZL		 Used to identify which country specific settings are required for various legislative reporting to the ATO or IRD.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Federal Business ID (Conditional)
Field information for the Federal Business ID field
Order Data Type Description Examples Why This Is Needed
5 Numeric. Unique value between 1–20 characters.

The unique federal identifier or business number for the legal entity in this operating country AUS: Australian Business Number (ABN) NZL: New Zealand Business Number (NZBN) or Inland Revenue Department Number (IRD).

Note: This field is required when creating a new legal entity.

 12345678901
123456789

Australia:
ABN is required for STP Reporting

New Zealand:
Either NZBN or IRD can be used here. The IRD Number required for Payday Filing reporting should be entered in a separate field dedicated for this purpose.
Effective Start Date (Conditional)
Field information for the Effective Start Date field
Order Data Type Description Examples Why This Is Needed
6 Date. Excel right justified date format or Excel text format yyyy-mm-dd.

The date the legal entity became active.

Note: This field is required when creating a new legal entity.

 1992-01-16  
Process for Employment
Field information for the Process for Employment field
Order Data Type Description Examples Why This Is Needed
7

Accepted Values:

  • Regular Payroll
  • Contractor Payroll
  • Pensioner Payroll

Recommended if the legal entity is going to be used to pay contractors or pensioners.

No selection is treated as a regular payroll.

    

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Address 1 (Conditional)
Field information for the Address 1 field
Order Data Type Description Examples Why This Is Needed
8 String1 between 1–64 characters.

The street number and street name of the legal entity's registered address.

Note: This field is required when creating a new legal entity.

 1234 Main Street  

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Address 2
Field information for the Address 2 field
Order Data Type Description Examples Why This Is Needed
9 String1 between 1–64 characters. Additional address information associated with the legal entity's registered address, if applicable. In some cases, this information is used to include a unit/suite/apartment number if not already included in the Address line. Unit 33  

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Postal Code
Field information for the Postal Code field
Order Data Type Description Examples Why This Is Needed
10 Numeric. 4 characters. The postcode of the legal entity's registered address. 3000  
Country (Conditional)
Field information for the Country field
Order Data Type Description Examples Why This Is Needed
11

Accepted Values:

  • AUS
  • NZL

The country of the legal entity's registered address.

Note: This field is required when creating a new legal entity.

 AUS
NZL		  
State/Region (Conditional)
Field information for the State/Region field
Order Data Type Description Examples Why This Is Needed
12 Accepted Values:State/Region Accepted Values.2

The State/region code of the legal entity's registered address. See below for valid State/Region accepted values.

Note: This field is required when creating a new legal entity.

    
2 Accepted values for State/Region
Accepted Values State / Region Name Country Name
AU-ACT Australian Capital Territory Australia
AU-NSW New South Wales Australia
AU-NT Northern Territory Australia
AU-QLD Queensland Australia
AU-SA South Australia Australia
AU-TAS Tasmania Australia
AU-VIC Victoria Australia
AU-WA Western Australia Australia
NZ-AUK Auckland New Zealand
NZ-BOP Bay of Plenty New Zealand
NZ-CAN Canterbury New Zealand
NZ-CIT Chatham Islands Territory New Zealand
NZ-GIS Gisborne New Zealand
NZ-HKB Hawke's Bay New Zealand
NZ-MBH Marlborough New Zealand
NZ-MWT Manawatu-Wanganui New Zealand
NZ-NSN Nelson New Zealand
NZ-NTL Northland New Zealand
NZ-OTA Otago New Zealand
NZ-STL Southland New Zealand
NZ-TAS Tasman New Zealand
NZ-TKI Taranaki New Zealand
NZ-WGN Wellington New Zealand
NZ-WKO Waikato New Zealand
NZ-WTC West Coast New Zealand
City
Field information for the City field
Order Data Type Description Examples Why This Is Needed
13 String1 between 1-64 characters. The Suburb/City of the legal entity's registered address.    

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Customer Bank Account
Field information for the Customer Bank Account field
Order Data Type Description Examples Why This Is Needed
14 String1 between 1–128 characters. The reference code for the customer bank account to be used as the default account for this legal entity. XYZ_CO_DFLTACCT Used to identify an existing bank account configured in Dayforce, and apply this account to the default Customer Funding Identifier for this (Payroll Setup > Bank Accounts).

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

PAYG Ref Number
Field information for the PAYG Ref Number field
Order Data Type Description Examples Why This Is Needed
15 String1 between 1–20 characters.

The PAYG Employer Reference Number for third party payments to the Australian Taxation Office (ATO).

This field is required when creating a new legal entity.

 654134786 Used in Australia when PAYG payments are made to the ATO via Third Party Payments.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Tax Office Contact Name (Conditional)
Field information for the Tax Office Contact Name field
Order Data Type Description Examples Why This Is Needed
16 String1 between 1–128 characters.

The name of the payroll contact for the ATO or IRD.

This field is required when doing any of the following:

  • Creating a new legal entity.
  • Updating an existing AUS legal entity with no STP Parameters.
  • Updating an existing NZL legal entity with no Payday Filing Details.
 Sally Smith

Contact details for the legal entity's payroll contact, to output in legislative reporting to country Tax Offices:

Australia:
Single Touch Payroll (STP) reporting to the Australian Taxation Office (ATO)

New Zealand:
Payday Filing reporting to the Inland Revenue Department (IRD).

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Tax Office Contact Phone (Conditional)
Field information for the Tax Office Contact Phone field
Order Data Type Description Examples Why This Is Needed
17 String1 between 1–128 characters.

The phone number of the payroll contact for the ATO or IRD.

This field is required when doing any of the following:

  • Creating a new legal entity.
  • Updating an existing AUS legal entity with no STP Parameters.
  • Updating an existing NZL legal entity with no Payday Filing Details.
 0488 999 999

Contact details for the legal entity's payroll contact, to be output in legislative reporting to country Tax Offices:

Australia:
Single Touch Payroll (STP) reporting to the Australian Taxation Office (ATO).

New Zealand:
Payday Filing reporting to the Inland Revenue Department (IRD).

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Tax Office Contact Email (Conditional)
Field information for the Tax Office Contact Email field
Order Data Type Description Examples Why This Is Needed
18 String1 between 1–128 characters.

The email address of the payroll contact for the ATO or IRD.

This field is required when doing any of the following:

  • Creating a new legal entity.
  • Updating an existing AUS legal entity with no STP Parameters.
  • Updating an existing NZL legal entity with no Payday Filing Details.
 sally.smith@xyc.com

Contact details for the legal entity's payroll contact, to be output in legislative reporting to country Tax Offices:

Australia:
Single Touch Payroll (STP) reporting to the Australian Taxation Office (ATO).

New Zealand: Payday Filing reporting to the Inland Revenue Department (IRD).

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

IRD Number (Conditional)
Field information for the IRD Number field
Order Data Type Description Examples Why This Is Needed
19 Numeric between 8–9 characters.

The Employer Inland Revenue Department Number (IRD Number).

This field is required when doing either of the following:

  • Creating a new legal entity in New Zealand.
  • Updating an existing NZL legal entity with no Payday Filing Details.
 654789654 Required in New Zealand for Payday Filing reporting.
STP Branch ID (Conditional)
Field information for the STP Branch ID field
Order Data Type Description Examples Why This Is Needed
20 Numeric. 1–999.

A unique 3-digit Branch ID to identify the legal entity for the STP parameter.

This field is required when doing either of the following:

  • Creating a new legal entity in Australia.
  • Updating an existing AUS legal entity with no STP Parameters.
 333 Required in Australia for Single Touch Payroll (STP) reporting.
STP Payroll Run By (Required)
Field information for the STP Payroll Run B field
Order Data Type Description Examples Why This Is Needed
21

Accepted Values:

  • Use Information Provided
  • Default Legal Entity
  • Other Parent Legal Entity

Options include:

  • Use Information Provided = An employee of the legal entity, or a Registered Agent / Intermediary runs payroll.
  • Default Legal Entity = Assign the entity to an existing default parent legal entity.
  • Other Parent Legal Entity = Assign the entity to a nondefault parent legal entity.
Use Information Provided Identifies who is responsible for processing the Pay Run and providing STP data to the Australian Taxation Office (ATO).

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

STP Other Parent Legal Entity (Conditional)
Field information for the STP Other Parent Legal Entity field
Order Data Type Description Examples Why This Is Needed
22 String1 between 1–256 characters.

The reference code of the legal entity to be assigned as the other parent legal entity for STP reporting.

This field is required if STP Payroll Is Run By is set to Other Parent Legal Entity.

   Only required when there's a business requirement to have multiple parent entities in the same environment.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

STP Run by Intermediary (Conditional)
Field information for the STP Run by Intermediary field
Order Data Type Description Examples Why This Is Needed
23

Accepted Values:

  • YES
  • NO

Options include:

  • YES = A STP submission is run by a Registered Agent, an authorized business intermediary, or a parent/business intermediary for other legal entities.
  • NO = STP run by a company employee.

This field is required if STP Payroll Run By is set to Use Information Provided.

 NO  
Registered Agent Number
Field information for the Registered Agent Number field
Order Data Type Description Examples Why This Is Needed
24 String1 between 1–128 characters. The Registered Agent Number issued by the Tax Practitioners Board (TPB) when associated with the Intermediary ABN.    

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Intermediary ABN (Conditional)
Field information for the Intermediary ABN field
Order Data Type Description Examples Why This Is Needed
25 String1 between 1–128 characters.

The Australian Business Number (ABN) for an entity that is authorized to make statements on behalf of the employee.

This field is required if STP Run by Intermediary is set to YES.

  Used to acknowledge the receipt of the payroll file, certain processing inquiries, and general correspondence. Mandatory when the payroll event data is supplied by a registered agent.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Intermediary Contact Name (Conditional)
Field information for the Intermediary Contact Name field
Order Data Type Description Examples Why This Is Needed
26 String1 between 1–128 characters.

The name of the authorized contact person for the business intermediary or the registered agent.

This field is required if STP Run by Intermediary is set to YES.

   Used for acknowledgment of receipt of the payroll file, certain processing inquiries, and general correspondence. Mandatory when the payroll event data is supplied by a registered agent.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Intermediary Contact Email (Conditional)
Field information for the Intermediary Contact Email field
Order Data Type Description Examples Why This Is Needed
27 String1 between 1–128 characters.

The email address of the authorized contact person for the Business Intermediary or the registered agent.

This field is required if STP Run by Intermediary is set to YES.

  Used to acknowledge the receipt of the payroll file, certain processing inquiries, and general correspondence. Mandatory when the payroll event data is supplied by a registered agent.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &

Intermediary Contact Phone (Conditional)
Field information for the Intermediary Contact Phone field
Order Data Type Description Examples Why This Is Needed
28 String1 between 1–128 characters.

The telephone number for the contact person for the business intermediary or the registered agent.

This field is required if STP Run by Intermediary is set to YES.

   Used to acknowledge the receipt of the payroll file, certain processing inquiries, and general correspondence. Mandatory when the payroll event data is supplied by a registered agent.

1 Special characters accepted in the string include: alphanumeric, space, period, apostrophe, dash, number symbol #, comma, underscore, forward slash /, parentheses (), &