Lloyds TSB Bacs format as disappeared

Hi Everyone

Customer has just upgraded to SE version 3.01 .00 from VFP and is getting "unable to locate BACS format - Check option settings". In Payroll Set Options they had Lloyds TSB as the BACS system and the same in Purchase Set Options . These options are no longer available, can only see Lloyds, have selected that option but it creates a csv file which their bank is rejecting as the format has changed from the last submission, I see there was a case logged in relation to Lloyds TSB but can't see if there was a resolution, KB3639324. There isn't much info on the KB .

Has anyone found a work around for this missing bacs format, please ?

Kind Regards

DKB

Find more posts tagged with

Comments

Panos Pamboukakis

Hi ya,

Please try changing the BACS software option in PL and Payroll to "BOS Commercial" and give it another go !

DDiskel

Hello Panos

Sorry , I should of said we tried that already and the reject reason is that beneficiary is mandatory.

However , if we import one supplier it works ,but fails when we import two suppliers.

Do you know what information you have in the Supplier terms under Banking.

I have Bank Account , Sort code Payee Name , Ref/Roll No and Bacs Ref . Not sure if I am missing anything ?

Panos Pamboukakis

In our case, the BACS File Format of "BOS Commercial" on Opera3 v3.01.00, was an exact match of what was "Lloyds TSB" on the older version. I have attached a working copy sample of BOS Commercial containing demo data.

The file extension is *.OUT, but I had to change it to .TXT,

Z_PLBACS_BOS_COM.OUT.txt

so it can be attached here on Infor site. The three lines in the file are correct.

richardd

Hi, are you sure this is not the padding issue fixed in Opera 3 SQL SE 3.01.02.

SCR08991, SCR09035

If you check the lines of the bacs file in notepad ++ are they padded out correctly? From memory they need to be padded with blanks to 80chars. Later version of SE fixed this issue

Rick

DDiskel

Hi Ya

Not sure why it keeps failing with two suppliers ? The import works when we try one supplier.

Kind Regards

DKB

DDiskel

@richardd Does the new version of SE have the Lloyds TSB format as a drop down in Purchase set options please ?

richardd

If the 2 suppliers have smaller PAYE names then it's the bug previously mentioned

Rick

richardd

Just taken a peek. TSB not in the list, just "Lloyds"

ben-calpin

The Lloyds format issue caused us an issue, however Pegasus fixed the format for us in 3.01.04

Thanks

Ben

tina-murray

I had this with a customer yesterday - set the bacs software to Lloyds.comm in pl set options - it failed on import BUT then found when they went into their lloyds banking software they were selecting a template the bank had created for them, got them to select the top option (bacs, csv or something similar) and it imported fine

hope the helps

john-patterson

Hi, our customers has now upgraded to 3.02.00 from a version before the Lloyds BASC issue was introduced.

Thank you, Tina your post works for the PL but not for the Wages BACS export. See email from the customer below: Any help on this would be appreciated?

"So, we have managed to import PL batches into Lloyds successfully, but still have problems with payroll – saying the same on all attempts by all of us that we do not have the entitlements. Therefore that proves it is payroll specific. One question we have is how would the bank know the difference – both payroll and PL batches are a list of beneficiary names, bank account numbers, sort codes and values. It can’t even be down to personal or business accounts as some supplier payments are into personal accounts."

DDiskel

Hello John

Is the customer selecting the CSV file in the actual Banking Website or what option are they selecting when they are uploading ?

DKB

john-patterson

Thanks, I dialled on site and managed to get enough info to send to Pegasus.

They replied with: SCR Opera-9410 - KB3671649 this will be fixed in v3.02.02

DDiskel

Hi John

Thank you , we have just upgraded our customer to 3.02.00 and the purchase side works, but we wont get to test the payroll one until the end of the month.

Please keep me posted if you upgrade to 3.02.00 and payroll doesn't work , I will also update this call once our client has tried the upload.

DKB

James Docherty

Hi just to let you know the issue when you use the Lloyds Comm, which replaced the Lloyds TSB style is that it puts a space after the account no at the top! This is why its getting rejected by the bank

If you manually remove the space, the bank accepts it. Pegasus have cnfirmed this will be fixed in 3.02.01, realsed towards the end of this week & will include the fix for NEST enrolemnt file issue

Thanks

richardd

BACS File Format of "BOS Commercial" on Opera3 v3.02 worked for us too using Barclays format - BACS - UK TDP during import using Barclays portal

Thanks for all the updates to this post

Rick

john-patterson

Hi, we are still having problems with this but only one site now.

After the upgrade to 3.02.00, their original PL BACS had gone so I got them to select the Lloyds.comm. They select the top one in the portal but that fails "no valid transactions in the payment batch"?

James Docherty

Hi John, do you have a space after the account nuber at the top in the CSV file? Also they need to in their banking software stop using the one named "Pegasus" & use the top option BACS BATCH CSV

Copyright © 2025 Infor. All rights reserved.