Skip to main content

Understanding transaction fields

What each field means when creating or editing pay transactions.

Updated over 3 months ago

When you create or edit a pay transaction (except for leave taken), you'll see several fields that determine how the transaction is calculated and displayed.

Transaction fields (in order of appearance)

Date

This defaults to the current period end but can be manually changed.

Depending on your system settings, the date may appear next to the transaction on the payslip.

Type

Determines which pay code is being used (e.g. Ordinary time, which is a work code).

Select the appropriate pay code from the dropdown list.

Units

Used to assign an amount of a particular thing. Units could mean hours, days, weeks or quantity.

This ties into how the pay code is valued.

Example: 40 hours of ordinary time.

Rate

The dollar amount per unit (e.g. an hourly rate for a work code).

This ties into how the paycode is valued.

Example: $25.00 per hour.

Value

The total dollar value of the pay code, determined by units Γ— rate.

Example: 40 hours Γ— $25.00 = $1,000.00

Costing

Each transaction can be manually altered in the way that it is costed.

This will supersede any default costing associated with the transaction.

Use this to allocate the transaction to specific cost centres, jobs or activities.

Payslip note

Whatever is entered here will show on the payslip next to the transaction itself.

Use this to provide additional context for the employee about the transaction. Some payslip settings will omit this detail from appearing on the payslip and will remain internal only.

Leave transactions

The leave and termination wizard has different fields and options, which vary by country. Refer to the Processing leave in payroll article for details on leave transactions.

Did this answer your question?