ADDACS — the Automated Direct Debit Amendment and Cancellation Service — tells you when a payer has changed or cancelled their Direct Debit Instruction.

When a payer notifies their bank of a change or cancellation, the bank forwards that information to you electronically via ADDACS. These messages are triggered by your customers, so they can't be eliminated — but acting on them quickly is what keeps your collections accurate.

Act within three working days. ADDACS messages should be actioned promptly — ideally the same day — to avoid collecting an incorrect amount or against a cancelled mandate, which risks an indemnity claim.

Common ADDACS reason codes

Reason codes tell you exactly what changed, so you know what action to take. Front2Bax helps you retrieve and process these messages as part of your routine, so your mandate data stays current.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

ARUDD — the Automated Return of Unpaid Direct Debits — tells you which collections were not paid, and why.

When a Direct Debit you submitted is not paid, the paying bank returns it via ARUDD with a reason code. You receive no notification for successful collections — only the unpaid items are reported — which is the essence of reconciliation by exception. ARUDD messages typically arrive in the working days following the collection.

Common ARUDD reason codes

The 90% rule: "Refer to payer" and "Instruction cancelled" together account for the vast majority of unpaid items. Processing your ADDACS reports promptly removes most of the cancellation-related failures before they happen.

Re-presenting unpaid items

Some unpaid items (such as a one-off "refer to payer") can be re-presented with proper advance notice. Others — for example where the instruction was cancelled — require a fresh mandate (a new AUDDIS) before you can collect again. Always check the reason code before deciding whether to retry.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

AUDDIS reports tell you when a new Direct Debit Instruction you submitted has been rejected by the bank — so you can fix it before any collection is attempted.

When you lodge a new mandate electronically via AUDDIS, the payer's bank validates it. If anything is missing, invalid or incompatible, the bank rejects it and reports the error back via an AUDDIS "Bank Rejected DDI" report, with a reason code telling you exactly what went wrong.

Fix before you collect: you cannot collect without a valid, lodged instruction. Resolving AUDDIS rejections as soon as they arrive prevents "No Instruction" failures (and ARUDD returns) later in the cycle.

Common AUDDIS reason codes

How to respond

Correct the underlying issue — usually a data error or an invalid/closed account — or obtain a new mandate, then resubmit the instruction. Don't attempt a collection until the instruction has been accepted and lodged. Processing AUDDIS reports promptly keeps your mandate base clean and your first collections on time.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

Before you collect a Direct Debit — and before you change an amount or date — you must tell the payer in advance. Getting advance notice right is a core scheme obligation.

Advance notice is the confirmation you give a payer of the amount to be collected and the date it will be taken. It gives the payer time to review the details, query anything that looks wrong, and arrange funds. It is required before the first collection and whenever the amount, date or frequency changes.

How long must the notice be?

The default period (the time allowed for the receipt of the advance notice by the payer) is a minimum of 10 working days plus postal time if being sent by post.

Getting it wrong

If you collect without sufficient notice, a payer may dispute the collection (you may see an "Advance Notice Disputed" outcome in your reports) and could be entitled to a refund under the Direct Debit Guarantee. Consistent, accurate advance notice protects both your payers and your organisation.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

Direct Debit failures are relatively rare, and most are avoidable. Reducing them protects your cash flow and keeps your collections clean.

Common causes of failure

• Refer to payer / insufficient funds — together with cancelled instructions, these make up the large majority of unpaid items.
• No valid instruction — collecting against a mandate that was never lodged or has been cancelled.
• Account closed or transferred — the payer's account details are no longer valid.
• Advance notice disputed — the payer says they weren't properly notified.
• Amount differs / not yet due — the collection doesn't match the notified amount or date.

How to reduce failures

• Process your ADDACS reports promptly (ideally same day) so you stop collecting against amended or cancelled mandates.
• Fix AUDDIS rejections before collecting — never attempt a collection against an instruction the bank rejected.
• Always give correct advance notice of amount and date, and of any changes.
• Validate bank details up front using current sort-code and account-validation data.
• Re-present unpaid items correctly, with proper notice, where it's appropriate to retry.

Reconciliation by exception: a strength of Direct Debit is that you only deal with the small percentage of items that don't succeed. Acting on your Bacs reports quickly is what keeps that percentage small.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

One of the reasons customers stay with Front2Bax for decades is flexibility: we would together with our clients to create schema files which means payment data from virtually any system can be imported, so you don't have to change how you work.

Works with what you already have

Front2Bax can process transactions from any accounting or payroll system capable of producing a csv. or txt. file - giving you complete flexibility in how you generate your payment data.

Tailored schema files

We configure a schema file tailored to your data layout, so Front2Bax knows how to read your specific file. That means you can keep exporting from your existing payroll or CRM in its native format, and Front2Bax maps it correctly every time — reducing manual handling and the errors that come with it.

Why it matters: reading your existing files directly removes re-keying, keeps your data accurate, and makes each submission quick and repeatable.

From file to Bacs

Once imported, your transactions are validated, the correct processing date is applied (either read from the file or chosen at submission), and the file is transmitted securely to Bacs and authorised with your digital certificate.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

Paperless Direct Debit lets customers set up a Direct Debit over the phone, online or face to face — no signed paper form required. Front2Bax supports this through AUDDIS.

Instead of capturing a wet signature and posting an instruction, you capture the payer's details and authority electronically, then lodge the new Direct Debit Instruction with their bank via the Automated Direct Debit Instruction Service (AUDDIS). Once the bank validates and lodges it, the Direct Debit is live.

Front2Bax and AUDDIS

Front2Bax processes AUDDIS Direct Debit Instructions and can automatically generate these records when required, so paperless set-up slots straight into your normal submission routine.

The benefits: faster first collection, fewer keying errors, no paper to store, and a smoother experience that builds customer confidence in your organisation.

Keep your authority

With paperless sign-up you still need to capture and retain evidence of the payer's authority. Combined with advance notice. this keeps you compliant and protected should a collection ever be queried.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

Christmas, Easter and the May bank holidays are the times collections are often late. A little planning keeps your cash flow on track.

The challenge

Clusters of bank holidays compress the available working days. Because Bacs doesn't process on those days, both your submission deadline and your funding date move — and it's easy to miss a cut-off if you're working to normal-week assumptions.

Practical steps

• Map the working days around each holiday period and identify the true submission deadline for each collection date.
• Submit early. You can send files up to 30 days ahead — ideal when key staff are on leave.
• Set the right date. When submitting in advance, ensure the intended processing date is contained in the file or chosen at submission, otherwise it defaults to the standard 3-day cycle.
• Keep your Bank Holidays file updated in Front2Bax so date calculations are correct.
• Tell your payers if a collection date will differ, honouring your advance notice obligations.

Need a hand? Our support team can help you plan submission dates around any holiday period — just get in touch ahead of time.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

Bacs only processes on banking working days. Weekends and bank holidays shift your dates — so an accurate processing calendar is essential.

When Bacs is open

Bacs operates Monday to Friday during the payment services window and does not process at weekends or on bank holidays. Every step of the 3-day cycle — input, processing and entry — must fall on a working day, so holidays push collection and credit dates later.

Working backwards

Always work back from the date you need funds to move. Remember the file must reach Bacs two working days before the collection/credit date. If a bank holiday falls within that window, submit earlier to compensate.

Keep your files current: Front2Bax uses an updatable Bank Holidays file (BankHolidays.bax) so your processing schedule calculations stay accurate. Download the latest from the elseWare Downloads area, along with the eISCD sort-code and account-validation files.

Submitting ahead

You can submit up to 30 days in advance, which is the safest way to cover holiday periods when staff may be away — just make sure the correct processing date is in the file or selected at submission.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

Good record keeping is both a scheme expectation and your best defence if a collection is ever queried. Knowing what to keep — and for how long — keeps you compliant and audit-ready.

What to keep

• Direct Debit Instructions — evidence of the payer's authority to collect, whether captured on paper or electronically.
• Advance notice records — proof of what you told the payer and when.
• Submission and report history — input reports, AUDDIS/ADDACS/ARUDD messages and the actions you took.

How long to keep it

You should retain a valid mandate for as long as the Direct Debit is live and keep evidence of authority and notice for a sensible period afterwards so you can respond to any indemnity claim. Always check the current scheme rules and your sponsoring bank's guidance for specific retention requirements and apply normal GDPR principles to payer data.

Is bank data "sensitive"? Bank account details are personal data and should be looked after carefully, but they are not special-category (sensitive) personal data under GDPR — normal data-protection rules apply.

How Front2Bax helps

Because Front2Bax is on-premise, your payment data stays within your own IT environment under your own security policies. It keeps a clear, auditable history of submissions and the Bacs reports you receive, so you can demonstrate what was collected, when, and on what authority.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

Both Direct Debit and Direct Credit run on a fixed three-working-day cycle. Understanding it is essential for planning collections, payroll and cash flow.

The three days

• Input (Day 1) — the latest day a Service User or bureau may submit a payment file to Bacs for that cycle. Files are transmitted during the payment services window.
• Processing (Day 2) — Bacs delivers the files to the recipient (paying) banks, which process each payment.
• Entry (Day 3) — payments are simultaneously debited from the paying accounts and credited to your account.

So a file submitted on Monday is processed Tuesday and settles Wednesday; a file submitted on Thursday settles the following Monday.

Key rule: the latest a file can be sent is two working days before the collection day. To collect on a Wednesday, the file must reach Bacs by the Monday. Send it later and the collection will be late.

The payment services window

Bacs is open during the payment services window, opening at 07:00am and closing at 11:00pm every working day. Bacs does not process at weekends or on bank holidays, so these must be factored into your planning.

Submitting in advance

You can submit files up to 30 days in advance of the processing date — useful over holiday periods when key staff may be away. If you submit early, the correct processing date must either be contained in the file (with the software configured to read it) or selected at the point of submission. If no date is supplied, collections default to the standard 3-day cycle.

Beyond day three

For Direct Credit, day three is the end of the process. For Direct Debit collections, settlement on day three is really the midpoint: the reporting cycle continues, with unpaid items returned via the ARUDD report in the days that follow. Organisations running Direct Debit at scale should plan operationally around this fuller cycle.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

The Direct Debit Guarantee is the consumer protection at the heart of the scheme. It is one of the main reasons payers trust Direct Debit — and it carries clear obligations for Service Users.

What the Guarantee provides

The Guarantee applies to all Direct Debits and protects payers in the following ways:

• If the amount or date of a Direct Debit changes, the organisation must give the payer advance notice before collecting.
• If an error is made in the payment by the organisation or the bank, the payer is entitled to a full and immediate refund from their own bank.
• The payer can cancel a Direct Debit at any time by contacting their bank.

Indemnity claims: where a payer claims a collection was incorrect or unauthorised, the bank can raise a Direct Debit Indemnity Claim. Keeping valid mandates and honouring advance notice is the best protection against claims.

Your obligations as a Service User

• Always give the required advance notice of the amount and date, and of any changes.
• Only collect amounts the payer has been notified of.
• Hold a valid Direct Debit Instruction for every collection.
• Act promptly on cancellation and amendment messages so you don't collect in error.

Meeting these obligations keeps you compliant with the Direct Debit Scheme Rules and maintains payer trust in your organisation.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

AUDDIS — the Automated Direct Debit Instruction Service — lets organisations set up new Direct Debit Instructions electronically instead of posting paper mandates to the bank.

How it works

With AUDDIS, the Service User keeps the original signed (or electronically captured) instruction and sends the details electronically via Bacs to the payer's bank, which validates and lodges the instruction on the payer's account. Once lodged, the Direct Debit goes "live" and you can start to make collections.

Since 2008 it has been mandatory for all new organisations submitting directly to Bacs to use AUDDIS.

How you can optimise your AUDDIS process

• Lodge instructions before you collect — submit each new AUDDIS instruction far enough ahead of the first collection to allow it to be validated and lodged. Collecting against an instruction that hasn’t yet gone live is a common cause of avoidable failures.
• Act on AUDDIS rejections promptly — monitor your AUDDIS reports and resolve any rejected instructions as soon as they arrive. Fix the underlying issue, or obtain a fresh mandate, before attempting a collection so problems are caught at set-up rather than as unpaid items later.
• Validate account data at the point of capture — check the sort code and account number using current validation data (such as Front2Bax’s eISCD and account-validation files) when you take the mandate, and capture a unique payer reference. Clean data up front prevents most setup rejections.

Front2Bax & AUDDIS: Front2Bax processes AUDDIS Direct Debit Instructions and can automatically generate these records when required, supporting fully paperless Direct Debit set-up.

AUDDIS and the wider family

AUDDIS sits alongside two related Bacs messaging services: ADDACS (for amendments and cancellations to existing mandates) and ARUDD (for unpaid collections). Together they keep your mandate data accurate and your collections clean.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 100+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.

Bacs is the UK's long-established system for moving money directly between bank accounts — the backbone behind salaries, supplier payments and the Direct Debits most of us pay every month.

Bacs stands for Bankers' Automated Clearing Services. It was first set up in 1968 and, since 2018, has been operated by Pay.UK, the organisation responsible for the UK's retail interbank payment systems alongside the Faster Payment System and the Image Clearing System. Pay.UK writes and maintains the Direct Debit Scheme Rules and monitors the scheme.

The two Bacs schemes

Bacs runs two complementary payment schemes:

• Direct Debit — a "pull" payment. With prior authorisation from the payer, an organisation collects money from a customer's account. Used for subscriptions, memberships, utility bills and other recurring income.
• Direct Credit — a "push" payment. An organisation pays money out to a recipient's account. Used for salaries, supplier invoices, pensions and refunds.

Front2Bax handles both. Organisations use it to pay employees' salaries, settle suppliers' invoices and collect customers' Direct Debits.

Who can use Bacs?

Organisations that collect or make Bacs payments are known as Service Users and need a Service User Number (SUN), typically issued by their sponsoring bank after checks on integrity, financial standing and administrative capability. With a SUN in place you can submit directly to Bacs using Bacs-approved software such as Front2Bax or use a Bureau Service that can submit on your behalf.

Why it matters: Bacs is secure, reliable and cost-efficient — transaction costs are a fraction of card fees, and reconciliation is by exception, meaning you only deal with the small percentage of items that don't go through as expected.

How submissions reach Bacs

Payment files are transmitted to Bacs over a secure, encrypted channel (Bacstel-IP) and authorised electronically using a digital certificate. Front2Bax manages this securely from within your own IT environment as an on-premise solution.

Ready to submit with confidence?

Front2Bax has powered secure Bacs submissions for 150+ corporates and bureaux since 1995. Talk to our team about getting set up.

Get in touch

This information is provided as general guidance. The Direct Debit Scheme Rules are published and maintained by Pay.UK; always refer to the current scheme documentation and your sponsoring bank for definitive requirements.