Use a custom deduction for an organisation-owned withholding or deduction that is not already represented by the active controlled catalogue. Statutory deductions generated by the engine are not authored here.

Before you begin

Select the organisation, open Transactions, and confirm the deduction code, amount source, effective date, currency, entry policy, and intended payroll treatment with the payroll owner.

Steps

  1. Open custom transactions

    Select Custom transactions.

  2. Choose a deduction category

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

  3. Enter the definition identity

    Enter a unique code, name, and description.

  4. Set the value model

    Choose a value model offered for that archetype and complete the required amount, units and rate, percentage, or basis fields.

  5. Review availability and treatment

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

  6. Preview and resolve errors

    Review the validation and payroll treatment preview. A pre-tax deduction must use a valid statutory-basis binding; an incomplete basis or value model must be repaired before saving.

  7. Save the draft

    Select “Save draft”, then review the Draft row and publish it through the custom transaction lifecycle when the definition is approved internally.

What to check

The custom transaction list should show the deduction’s code and “Draft” or “Published” status. In a permitted payroll entry context, confirm that the selected employee or pay run shows the deduction and that the calculated preview reflects it. The engine result, not a hand calculation, is authoritative.

Important boundaries

Do not use a custom deduction to imitate PAYE, NSSA, or another generated statutory output. Check the controlled catalogue first and preserve the active pack’s treatment. Official filing remains outside Paydae.

Common problems

Transaction code already exists

The code collides with another definition.

Pre-tax or statutory-basis validation appears

The definition needs a supported basis binding; do not bypass it by changing the label.

Controlled catalogue item is read only

Follow its displayed action instead of creating a duplicate custom deduction.

Related guidePayroll transactionsRelated guidePublish a custom transactionRelated guideIncorrect payroll total