Payroll transactions
How do controlled, custom, and generated payroll items differ?
The three tabs4 sections
The Transactions screen separates pack-owned controls, organisation-owned definitions, and results generated by the payroll engine. The correct tab determines whether you assign, enter, edit, or simply inspect an item.
The three tabs
At Transactions, the tabs are:
- Controlled catalogue — pack-managed, read-only items. Open an item to read its interaction, information source and available action; the item count depends on the active pack.
- Custom transactions — organisation-authored definitions with draft and published versions. New custom transaction opens a builder with approved tax-category archetypes, which determine payroll treatment.
- Generated statutory outputs — PAYE, NSSA and other calculated results. These are not definitions to copy, edit, publish or retire. Use View generated statutory outputs to open Documents → Statutory.
Use the action stated by the pack
For a controlled item, follow its “Available action”: assign recurring input on the employee record, enter a controlled event in a payroll run, record a controlled event, manage employee information, or view a generated result. Do not create a custom duplicate simply because the controlled item is not editable.
For a custom definition, use its entry policy to decide whether it belongs on an employee record, in one payroll run, or both. A published definition may then appear in the permitted input workspace.
What to check
On the custom tab, check the Status, Archetype and Availability filters and the effective date. On the controlled tab, verify the pack context and read-only state. For a calculated result, check Documents → Statutory or the generated statutory results in payroll review.
Important boundaries
A custom transaction can describe an organisation input; it cannot author a statutory output owned by the pack. Paydae’s generated result is evidence for review and export, not proof that an authority filing has been submitted.