Purchase Ledger (Suppliers)

One of the major issues with the Suggested Payment Run routine in Sage 200 is when posting payment and creating a bank file. If there are errors with any of the suppliers on the run, (incorrect BIC or IBAN etc.) Payment run still completes with th...

I find the whole Payment processing laborious, extremely time consuming and out of date. Instead of Printing a suggested Supplier Payment report , then having to amend, then printing another report and so on, it would be good to have all the Suppl...

Hi We do not use the BACS as a payment function. The fast-approaching changes that are taking place with the Santander banking platform mean that we cannot create and import payment files. Please develop a Faster payment File option for creating p...

Currently e-banking uses an ini file in C:\ProgramData\Sage\Sage EBanking - our client's AVD environment has 2 servers that will sign the user into the server with the lowest load, so this file is not updating on both machines when updated. The ma...

would be beneficial for all multi currency companies

Doing credit control for a larger organisation it is easier to put everything into a spreadsheet where we can put notes that can be seen by all line managers, not everyone has access to Sage. But once done we are then having to put the notes onto ...

When we add customers or suppliers, the code we assign to their account is based on their company name. Sometimes these entities change their names and then it would be really useful if there was a way to change their account code too.

If there is a confidential supplier, we would like to restrict visibility for invoices raised on that account

Add the due date to supplier transaction enquiry as its own column

Could an approvals style routine be build in to allow a senior user to approve any bank detail changes please? The audit log is good but it doesn't prevent changes and so issues could arise before anyone is aware.