Santander rejected my Xero batch payment file: causes and fixes

Updated 17 October 2026

Santander Connect rejects an imported payment file when a mandatory field is empty or a field holds a character it does not accept. With batch payment files exported from Xero, the causes Xero users have reported since January 2026 are an empty debit account reference on the first row and a blank line at the end of the file. Both take a minute to fix in a text editor once you know where to look.

Open the file in Notepad or another plain text editor before you change anything, not in Excel. Excel can drop the leading zeros from sort codes and account numbers such as 040605, and Santander then reads them as the wrong number of digits.

Which Santander file did Xero give you?

When you export a batch payment from a Santander UK account, Xero creates the file in a Santander format rather than a generic BACS file (Xero Central, "Pay multiple bills"). Santander Connect imports two kinds of file, each with its own specification, and the first line tells you which one you have:

A line starting ,,,08, is a standard bulk payment file. The first row is the debit record for your account, and every row after it starting ,,,09, is one payment. Santander sends these as Faster Payments.
A line starting PAYMENT,HEADER, is a BACS payment file. Each payment is a line starting PAYMENT,MULTIBACS,, and the last line starts PAYMENT,TRAILER,. These go through the three-day BACS clearing cycle.

Causes 1 and 2 below apply to the standard bulk file, and cause 3 to the BACS file.

Cause 1: the debit account reference on the 08 row is empty

In a standard bulk file, field 9 of the 08 row is the debit account reference: up to 18 characters that identify the batch on your own statement. In the 2018 edition of Santander's specification this field was optional, and a blank one was filled with the first 16 characters of the file name. The June 2025 edition shows it filled in on the sample "bulk payment debit record with mandatory fields" and marks the field mandatory for that record. Xero users reported in January 2026 that Santander had made a mandatory change to its bulk import checks from 12 January, and that files with nothing in this position were being rejected.

The reference goes straight after the fifth comma that follows 08. Using the sample record from Santander's specification, a rejected row and a corrected row look like this (each row continues with commas to 85 fields):

Without a reference: only commas between 08 and the account number

,,,08,,,,,,,,,09012211223344,,,,,,24082012,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

With the reference added: PayAug is the debit account reference

,,,08,,,,,PayAug,,,,09012211223344,,,,,,24082012,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Type only letters, numbers and spaces, keep it to 18 characters, and do not add or remove a comma anywhere. Every row in this format has exactly 85 fields, so one extra comma moves every later value into the wrong column.

Cause 2: a blank line at the end of the file

Santander's BACS import specification says a file "must not contain a blank line after the trailer record", and Xero users reported in January 2026 that the standard bulk file is now rejected for the same reason. A trailing blank line is invisible unless you look for it:

Open the file in Notepad and press Ctrl+End to jump to the very end.
If the cursor sits on an empty line below the last payment, press Backspace until it sits at the end of the last payment row.
Save the file under the same name and import it again.

Cause 3: an empty trailer in a BACS payment file

The last line of a Santander BACS file is the trailer: PAYMENT,TRAILER,, then the total value of the payments, then the number of payments. Santander's specification marks both numbers as optional, but in November 2024 a Xero user reported that Santander had started rejecting files whose trailer read PAYMENT,TRAILER,, with the message "Invalid Record Total information", and that adding the total and the count fixed it. The example in Santander's own specification has both:

An example BACS file from Santander's specification

PAYMENT,HEADER,11032025,HGWEEKLYWE0903,0005,,
PAYMENT,MULTIBACS,09022212345678,N WINCH,239282,01234567,1906.28,14032025,REDSKY LTD,
PAYMENT,TRAILER,0000000001906.28,1

The same specification sets other rules for this format that can cause a rejection:

Your BACS Service User Number has to be registered with Santander Connect before you can import BACS payments at all.
Single payments and multiple payments cannot be in the same file.
In a file of multiple payments, every payment must use the same debit account and the same payment date, and every payment needs a payment reference.
The header's creation date cannot be later than today.
There must be no blank line after the trailer.

Cause 4: a character Santander does not accept

Both specifications list the characters allowed in free-text fields such as payee names and references, and a file containing anything else is rejected. The standard bulk format allows letters, numbers, spaces and a short list of punctuation that includes full stops, hyphens, slashes and brackets. The ampersand is not on that list, so a payee called "Smith & Sons" fails. The BACS format's list is shorter: capital letters, numbers, full stop, hyphen, slash, ampersand and space.

Commas cause a different failure. Both formats are comma-separated, so a comma inside a payee name splits it into two fields and pushes every later value out of place. Xero's own help says to make sure the bills you pay "don't include special characters, as this can cause errors". If a supplier's name in Xero contains an ampersand or a comma, change it on the contact before you create the batch, or edit the file.

Other checks Santander makes on a standard bulk file

From the June 2025 specification:

A bulk payment must be in a file of its own, with the 08 debit row first and one 09 row per payment after it.
The debit account on the 08 row (field 13) is 14 digits: your six-digit sort code followed by your eight-digit account number, with no spaces or hyphens.
Each payment needs the currency (GBP), the amount written like 1250.00, the payee's six-digit sort code and eight-digit account number, the payee's name and a payment reference of up to 18 characters.
The payment date on the 08 row is written ddmmyyyy, for example 24082025.

A payment (09) row from Santander's specification

,,,09,,,,,,,,,,,,GBP,1250.00,,,,,,,,090222,,,,,,55667788,,DaviesB,,,,Salary,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Fix a Santander file with Bank-Bridge

Bank-Bridge is FourFourFive's free tool for preparing bank upload files from the payment files Xero exports.

For Santander, Bank-Bridge reads either the standard bulk file from Xero (the one starting ,,,08,) or a BACS Standard 18 file, and gives you back a standard bulk file:

You type your batch reference once and Bank-Bridge writes it into field 9 of the 08 row.
It removes the blank line from the end of the file.
From a Santander bulk file, every other character is left exactly as Xero wrote it, including the payment date.
From a BACS Standard 18 file, it builds the 85-field file using the payment date you choose, and replaces commas, quote marks and apostrophes in names and references with spaces so the columns stay in place. A BACS file holds only 18 characters of each payee's name, so longer names arrive shortened, and where a payment has no reference of its own your batch reference is used.

The conversion runs in your browser, so the payment file is not uploaded to FourFourFive. Bank-Bridge does not produce Santander's BACS format (the PAYMENT,HEADER file), so use the trailer fix above for that one, and it does not remove ampersands, so check payee names first.

See Bank-Bridge Create a free account

If Santander still rejects the file

Santander's specifications give a support line for payment file imports, 0333 207 2317. Have the exact error message from Connect and the first two rows of the file to hand. On the Xero side, the request for a Santander-compatible export ("Batch Payments - Export file in a Santander-compatible format") is still marked "submitted" on Xero Product Ideas, and in October 2026 one user reported being told by Xero support that it could not customise the export file. Until that changes, the file needs one of the fixes above before every import.

Paying from NatWest, Revolut or Monzo instead? See Xero batch payments to NatWest Bankline, Revolut and Monzo.

Sources

Santander, Santander Connect Standard payment import specification (6020236 JUN 25). Field 9 debit account reference, the 85-field layout, the bulk debit and credit record samples, character set
Santander, Santander Connect Standard payment import specification (60 20 236 AUG 18). The 2018 edition, in which a blank bulk debit reference defaulted to the file name
Santander, Santander Connect BACS payment import specification (6020273 APR 25). Header and trailer records, the blank-line rule, BACS SUN registration, character set
Xero Central, Pay multiple bills. Santander UK export format and the special characters warning
Xero Product Ideas, Batch Payments - Export file in a Santander-compatible format. User reports from November 2024 (trailer totals) and January 2026 (the 12 January change)