Bacs Direct Credit bulk files: submit payroll and supplier payments before the three-day cycle begins

Bacs Direct Credit is widely used for payroll, pensions, expenses, refunds and business-to-business payments. The service is built for high-volume scheduled credits rather than urgent same-day transfers, so file preparation, submission dates and approval controls matter before the three-day processing cycle starts.

Direct Credit is designed for regular bulk credits

Pay.UK says Bacs Direct Credit is used by more than 150,000 organisations for wages, salaries, pensions, expenses, insurance settlements, dividends, refunds and B2B payments.

Use it where payment date is known in advance and volume makes manual Faster Payments inefficient.

Plan around the standard three-day Bacs processing cycle

Bacs works through input, processing and entry days on working days. Payment files therefore need to be submitted before the intended credit date rather than on that date.

Weekends and bank holidays are non-processing days. Payroll calendars should calculate backward from employee payday.

Validate the beneficiary file before submission

Check sort codes, account numbers, amounts, references and payment date. Use payroll or ERP controls to prevent the same beneficiary appearing twice unexpectedly.

Separate file creation from final submission approval where possible. The bulk file can move millions of pounds in one action.

Many businesses submit through a Bacs-approved bureau

Pay.UK says more than half of organisations making Bacs, Direct Debit or Faster Payment submissions use approved bureaux instead of direct submission. A bureau can simplify access for SMEs or lower-volume users.

Keep the bureau's role clear: it can transmit the file, but the employer or business still needs internal approval over who is paid and how much.

Review rejected or unpaid credits after processing

Invalid or closed beneficiary accounts can cause credits to fail or return. Use the Bacs or bureau reports to identify exceptions and arrange controlled replacement payments.

Do not resend the whole file because one employee failed. Replacement items should be tied to the original failed payment to avoid duplicates.

Match the batch total and exceptions to the bank

Keep the approved file total, processing report and bank debit together. The accounting ledger should show which payroll or supplier run the batch settled.

Investigate differences immediately. A bulk-payment process is efficient only when finance can trace the total back to individual beneficiaries.

Worked example: payroll is due Friday. Because Bacs uses a three-day cycle, the file may need to be submitted on Wednesday as input day, processed Thursday and credited Friday, assuming all are working days. If Friday is a bank holiday, the entire timetable changes. Payroll should calculate dates from the target credit day rather than reuse last month's upload date.

Use a control total before and after submission. If payroll expects 420 payments totalling £812,450, the bureau or bank confirmation should show the same count and value. A matching total does not prove every account is correct, but a mismatch immediately identifies a file or transmission problem.

Keep an emergency Faster Payments process for individual exceptions, not for replacing a whole file casually. If one employee bank account rejects, pay that employee separately after verification. Re-uploading or reconstructing the entire payroll batch under time pressure creates much larger duplicate-payment risk.

Protect service-user and bureau credentials as payment credentials. Staff who can create or submit Bacs files should use named access, multi-factor controls where supported and immediate offboarding on role change. A bureau can strengthen processing standards, but it cannot compensate for weak internal user governance.

Review beneficiary reference quality. Payroll and supplier recipients often use the bank reference to identify what they received, so a structured reference can reduce support queries and supplier reconciliation problems. Bulk payments should be efficient for the beneficiary as well as for the sender.

Keep rejected-credit reason codes in the beneficiary master. If an employee payment fails because the account is closed, require re-verification before another file includes that beneficiary. Repeatedly resubmitting stale details wastes time and can create payroll complaints.

For supplier Bacs batches, align the value date with contractual terms. Paying two days early because the file was submitted early is different from submitting early for a due-date credit. Treasury should understand how the bank or bureau uses the requested payment date.

Maintain a submission calendar with the last safe input day for every payroll and major supplier run. A calendar that already accounts for UK bank holidays is more reliable than staff counting backwards manually each month, especially around Christmas and Easter.

Archive the original approved file in a tamper-evident location where practical. If a payroll or supplier dispute later arises, finance should be able to reproduce exactly what was authorised, not only what the current ERP happens to show after later master-data changes.