Publishing is an organisation-controlled lifecycle action for a saved custom transaction. It does not publish a controlled catalogue item or a generated statutory output.

Before you begin

Open Transactions → Custom transactions. Confirm the definition is yours, has Draft status, and has a unique code, valid effective dates, supported currency, approved tax category, entry policy, value model, and reporting details. The selected archetype fixes the payroll treatment.

Steps

  1. Open the draft

    Open the Draft custom definition from the list.

  2. Review its configuration

    Review its identity, value model, entry policy, effective dates, payroll treatment preview, statutory reporting buckets, payslip/audit settings, and change reason.

  3. Save corrections

    Save any corrections with “Save draft”.

  4. Start publication

    Use the definition’s “Publish” action.

  5. Confirm the payroll effects

    Read the confirmation, including the canonical payroll effects, statutory-basis bindings, required dependencies, and version impact. Acknowledge it only after the payroll owner has reviewed those effects.

  6. Verify publication

    Return to the custom list and confirm the definition is “Published”.

What to check

The row should show “Published” status and the intended availability. A later change may require a successor Draft version rather than editing the published version in place. Confirm the published version is the one selected when entering a recurring or pay-run transaction.

Important boundaries

The “Controlled catalogue” is “Pack managed” and “Read only”; it has no publish action. “Generated statutory outputs” are generated results and are not publishable. Publishing a custom input does not submit a return or output to an authority.

Common problems

Publish is missing or disabled

Verify that the row is a custom Draft and that required fields validate.

Definition has a statutory-output identity

Stop; statutory outputs must come from the active pack.

A published change is needed

Create the successor version requested by the editor and preserve the effective-date boundary.

Related guidePayroll transactionsRelated guideAdd an earningRelated guidePayroll preparation checklist