The Payment Manager is there to provide BACS files to external BACS software or upload to banking software

The process works on the basis of a queue. Payment records are added to the queue ‘On Hold’, as a user processes a Payslip or activates another process that creates a BACS record.

A user processes the queue by taking the payment records off hold, either in bulk or any manual selection. A payment record yet to be processed from a payslip appears in the list with a zero value. As the queue is processed, the value is inserted (in case users re-process payslips). By pressing Output, the system then creates a BACS file in the desired bank format in a ore-determined folder. There is a default bank layout, but any layout can be used for any Output. If a payment record does not contain sufficient detail to create a valid line in the specific bank layout, the system holds onto that record, marks it in red and does not include it in the relevant file

The most frequently used process is the creation of a BACS file for Net Pay. However, the same process can be used to create BACS files for Advances (there is a full solution for Advances) one-off Payments (for any reason), Loans and Dividends. Users can let the queue build through the week and release all the payment records in one file, or release them in any other sequence that matches their payroll process

The queue can be filtered based on Agency, Company or Department to narrow down those you want to pay to match how timesheets arrive.

There is a history of every payment, searchable by PaymentRun ID, Contractor, Agency, Company and Department. With relevant access, users can re-create a BACS file from any historic record