Fix a Rejected BACS File
A BACS file that comes back from the bank or your bureau is almost always a format defect rather than a payment problem: records that are not exactly 114 characters, LF or CR line endings where CRLF is required, a UHF1 header label where the UTL1 trailer belongs, or a UTL1 total that does not reconcile with the payment records. Paste or upload the file below and you get the corrected copy back — the payments themselves are never altered.
Payment file
Drop a .txt or .bacs file in the box below, or paste its contents. The file is checked as soon as it arrives: if it cannot be read as a BACS payment file you are told why and charged nothing. The corrected file — the fix itself — is what you pay for.
Drag and drop your file here
Your file
No file yet. Drop or paste one and it is checked straight away — a file we cannot read as a BACS file is refused here, free of charge.
Frequently asked questions
- Why was my BACS file rejected?
- Almost always a format defect rather than a payment problem: records that are not exactly 114 characters, line endings the bank will not parse, a header label where the UTL1 trailer belongs, or a UTL1 total that does not reconcile with the payment records. Those are the defects the repair corrects.
- Will the repair change my payment amounts or references?
- No. Only the format is corrected — record widths, line endings, the UTL1 trailer label and totals, and the sort code and account number formatting of each record. Amounts, references and payee details are left exactly as they were.
- Is my file uploaded or stored anywhere?
- Not stored, no. A file you check on the homepage is held in memory only while the payment is made, and is deleted the moment your corrected copy has been downloaded.
- Do I need to rekey the file before resubmitting?
- No. Download the corrected copy, check the record count and total value in its UTL1 trailer against your own figures, and submit that file by the same route as before.