4
PSA: I finally caught my dumb mistake with batch payment files
I spent 6 months manually fixing failed BACS transfers before I realized my sorting code column was formatted as text instead of numbers in the CSV template lol. My bank's test file showed everything fine but live runs kept bouncing about 12 payments a week. Anyone else have that moment where a tiny formatting issue made you look like a rookie for months?
3 comments
Log in to join the discussion
Log In3 Comments
morgan.rose18d ago
had a coworker who got burned real bad on this. she was handling payroll for this midsize company and kept having checks bounce for like 20 employees every month. turns out Excel was eating the leading zeros on their bank account numbers because the column just defaulted to number format. she spent weeks on the phone with the bank thinking it was their problem. the worst part is the bank's test files all had account numbers starting with 1 or 2 so zero issue there. her boss was not happy when they finally figured it out.
7
mason_lopez18d ago
Double down on that formatting thing because it gets even worse when you have leading zeros in account numbers. Excel strips those out automatically unless you pre-format the column as text, so you end up with account numbers missing the first digit or two. I had a buddy who spent a whole quarter chasing down failed payments before he realized his bank was rejecting everything because account numbers like "00123456" were showing up as "123456" in his export file. The worst part is that test files almost never catch this stuff since they usually use dummy data that works fine. You pretty much have to build a validation step into your workflow that checks every single field format before you hit send, otherwise you're just gambling with random failures every week.
4