Create an earning only when the active controlled catalogue does not already provide the required organisation input. A custom earning is an organisation definition; it is not a replacement for a pack-generated statutory line.

Before you begin

Select the organisation and open Transactions. Confirm the earning’s business purpose, who supplies its amount, effective date, currency, payroll treatment, and whether it is recurring or limited to one pay run.

Steps

  1. Open custom transactions

    Select Custom transactions.

  2. Choose an earning category

    Select New custom transaction, then choose the approved earning tax category offered by the archetype catalogue.

  3. Enter the definition identity

    Enter the identity fields, including a unique transaction code and name. Add a description so a reviewer can identify the input.

  4. Set the value model

    Choose the value model offered for that archetype and supply its required amount, units, rate, percentage, or basis details.

  5. Review availability and treatment

    Set the effective dates, supported currency, permitted entry actions, payslip visibility, and any required reporting details. Review the fixed payroll treatment before saving.

  6. Preview and resolve errors

    Review the payroll treatment preview and resolve validation messages such as “Transaction code already exists.” or a missing required amount.

  7. Save the draft

    Select “Save draft”. Review the resulting Draft definition; publish it only after the payroll and statutory effects have been checked.

What to check

The custom list should show the earning with “Draft” status, its code, value-and-entry summary, and effective date. After publication, the status changes to “Published” and the definition becomes available only in the entry contexts selected in its policy.

Important boundaries

An earning’s taxable or reporting treatment is a configuration decision requiring payroll-owner review. Paydae calculates from the saved definition; it does not certify the organisation’s tax interpretation. Controlled catalogue entries and generated statutory outputs remain outside this editor.

Common problems

Transaction code is already used

Choose a distinct code rather than editing a controlled item.

Value model is incomplete

Check for a missing amount, unit, rate, percentage, or basis.

Required category or model is not offered

Use the controlled catalogue action or document the gap for the pack owner; do not invent a custom statutory output.

Related guidePayroll transactionsRelated guidePublish a custom transactionRelated guidePayroll preparation checklist