Payroll and Super Check

Payroll and Super Check API

Payroll and Super Check validates a person's details against payroll records, superannuation records, or both in a single call. Each field you send comes back as matched or unmatched against each source, so employment and super details can be confirmed in one step with the person's consent.

One call covers both sources, with separate consent for payroll and for super, and a result block for each
Name and date of birth, middle name, address, email, phone and employer ABN each returned as matched or unmatched

Get API access Talk to us

For developers

After the technical detail?

For the technical detail, go to the API documentation. It holds the request and response schema, the integration guides and the error codes for this endpoint.

Request and response schema
Minimum requirements and consent

View developer documentation

Accounts start in the sandbox. Production keys are issued once the account is approved.

Encrypted in transit and at rest Handled under the Australian Privacy Principles

What the check gives you

Confirming the employment and super details a person gives you

Lending, tenancy and onboarding decisions often rest on employment details the customer has stated. Payroll and Super Check takes the details you hold, with the person's consent for each source, and reports field by field whether they match payroll records and superannuation records. This is the combined call; Payroll Check and Super Check run each source on its own.

Whether the person is on record

The person result is matched when the first name, last name and date of birth match the source, and unmatched otherwise, for each of payroll and super.

Whether the other details agree

The middle name, address, email address, phone number and employer ABN each return matched or unmatched against each source.

Consent per source

Payroll consent and super consent are sent separately, and at least one is required.

Two result blocks

The response carries a super block and a payroll block, each with the same set of field results.

Reading the result

What each answer means for the record in front of you

Every field you sent comes back matched or unmatched, per source. The person result is the one that says whether the record exists.

Matched

The field agrees with the source

The value you supplied matches the payroll or superannuation record for the person.

Unmatched

The field does not agree

The value you supplied does not match the record, or, for the person result, no record was found for the name and date of birth.

What it costs

A monthly subscription, drawn down as you run checks

Your subscription is credited to your account each month and each check consumes credits from it. If you go past the included amount, further checks are charged at a per-check rate. The rate depends on the volume you commit to, so the sales team is the fastest way to find where your business lands.

Volume-based pricing
No lock-in contract

How billing works

Subscribe monthly, spend it as credits

The monthly subscription arrives as credits on your account.
Each check draws down credits as it runs.
Checks beyond the included credits are billed per check.
Higher monthly volume moves you to a lower rate.

Talk to sales about volume

Related checks

Others in Payroll and Super Check

Payroll Check and Super Check run each source on its own with the same fields and results.

Payroll Check API Super Check API

All Payroll and Super Check endpoints

Questions

Questions we get asked about Payroll and Super Check

Do we need a developer to implement this?

Yes. Payroll and Super Check is a REST endpoint that takes a JSON request and returns a JSON result, so a developer connects it to your application or onboarding system. A sandbox with a deterministic test dataset is provided at no usage cost, so the integration can be built and tested before production keys are issued.

What does our system need to send?

The first name, last name and date of birth, and at least one of super consent or payroll consent. Optionally a middle name, an address with street, suburb, state and postcode, an email address, a phone number in 0NSN format and the employer ABN.

What comes back?

A super block and a payroll block. Each carries a matched or unmatched result for the person, the middle name, the address, the email, the phone and the employer ABN.

Is consent required?

Yes. The request carries a consent flag for each source, and at least one must be true.

What happens if a source is unavailable?

The check returns a 503 response with the message Third Party Unavailable. The documentation shows how to simulate this in the sandbox.

Where does the data come from?

Payroll records and superannuation records. The reference documentation does not name the providers or publish a refresh cycle.

Are the details we send stored by Global Data?

Personally identifiable information sent in a request is not stored or retained unless it is needed to process that request. Query data is stripped of PII before it is kept for audit. Data in transit and at rest is encrypted, and retention follows the Australian Privacy Act and the Australian Privacy Principles. Global Data is not a credit bureau and does not create an access footprint on any record.

Getting started

The first step to access is a conversation

New accounts begin with sandbox access, and production API keys are issued once the account has been commercially approved.

Get API access Talk to us

Call 03 9948 4089, 9am–5pm AEST Monday to Friday

Encrypted in transit and at rest

Handled under the Australian Privacy Principles

ISO 27001 Certified