My ideas

I have a customer who requests some toggle-ability on some labels in the Summaries -Is there any way in the Sales Summary and Purchases Summary that the Customer Codes can show Customer Names instead ? It would be good if this could be toggled as ...

We have many orders where we produce a product for a customer on one order, but the customers require the delivery of the orders to be sent to multiple sites. For example, a major retailer may place an order for bespoke items for a national roll-o...

When trying to add members into companies or company access into users its all in ID order and not in alphabetical name order. Would be good if this could be updated for quick adding purposes

In Business Intelligence, currently there are no cubes that link between the Stock History & Nominal To be able to analyse Nominal Postings behind Stock transactions/movement i.e. drill into a stock item history (any or all movements) and view...

Something I am asked for by almost every single site i visit (and it's something that really irritates me too actually) is why do we to enable scrolling on all the list views? Surely it should be ticked as default? If there is a list then you will...

Every Sage 200 customer gets confused by the Current vs Historical transactions in the nominal transaction enquiry screen, and the 'brought forward balance' shown, as they assume that this relates to financial year. Obviously they can by shown to ...

When adding an item on to a Sales Order, with the Comment line item type, there is a tick box for 'Show on customer documents' which is always ticked by default. Customers who prefer to use comment lines for internal notes have to manually untick ...

A batch change function within the program (mainly 200 Std Online) would be ideal for those people with 1000s of customers and suppliers who may need to amend or append different analysis codes for their customers or suppliers. This could also be ...

The system lets transaction dates through with any dates, it does not look at the transaction date validation rules in ASM

currently sage will import with no warnings if the nominal account doesn't exist, this has resulted in journal corrections being required