Suggestions

Customers can currently use Create Ad-hoc Payment to make standalone payments (for example, final termination payments that are not processed via an Add To). While Affinity provides a payment preview during this process, it does not generate a formal payslip that can be issued to the employee. Customer Requirement The customer has advised that, for final termination payments, they are legally required to: make the payment on the employee's last working day; and provide the employee with an official payslip at the same time. The payment preview or screenshot is not considered a compliant payslip for this purpose. Requested Enhancement Provide the ability to generate a standard Affinity payslip for standalone Create Ad-hoc Payment transactions, similar to the payslip produced during a normal payroll or Add To process.

Currently, Affinity will calculate Annual Leave Loading based on Leave/Award parameters. Most Modern Awards have a requirement to pay the higher of leave loading or penalties that would've been paid if the leave was not taken. This is currently manually calculated and entered by Payroll. It would improve User experience, if the system made this comparison and paid the higher value. Refer Fairwork and the recent cases that have been reviewed for Woolworths. https://library.fairwork.gov.au/viewer/?krn=K600323

Created a number of Ad-Hoc Payments with varied Release Dates. Selected All. Create DC File. Apparently, this should not be done as then it creates 1 bank file and picks the Last release date. Where is the warning message? Why does the system allow you to create the DC File? Can this be improved with based on Release date?

API have brought up the below: When an adhoc is processed through Affinity and it automatically produces the ADHOCB to nett this off, the date of the ADHOCB in transaction date is the date the payment is made, however the adhoc normally relates to either a previous or current pay period. Is there anyway we can make the ADHOCB date the same transaction date as the adhoc payment itself. The reason is that if these dates are not the same, although it correctly netts off the payment, the ADHOCB entry keeps carrying forward.

A customer raised an issue in Ticket 115990 when an employee with XTAX goes on partial LWOP. The Processing Method PER will prevent the XTAX being deducted if LWOP is processed for the full period, but even if 1 hour is paid the XTAX will process at the amount the XTAX is set to in the Employees All/Ded, if the XTAX has a greater value than what's being paid it will cause a negative. Can we prevent the XTAX being processed if not enough Net Pay to cover it.

Would be helpful it the payment report shows a balance per pay point (refer rather than the cumulative balance (this is less important than a PPT balance and then an overall balance). It makes reconciliation easier to have a balance per bank file when there is bank file per ppt generated. For example, it auto sums on the right hand side joining all values together, where as if we could auto sum it and show the value per pay point.