Ideas

Showing 98

Validate transaction import for nominal codes that do not exist in sage

currently when you import customer/supplier transactions and it contains a nominal code that does not exist in sage, it allows the import to go ahead with no warnings and posts it to suspense. I think it should allow more strict validation and rej...

Guest over 9 years ago in Nominal 0 Idea Accepted - Gauging Support

7 VOTE

Allow import of previous year journals

Client has a 150 line prior year journal to post but the import nominal transaction only allows the current year. Would like a prior year import equivalent

Guest over 9 years ago in Nominal 0 Idea Accepted - Gauging Support

7 VOTE

ODBC Connectivity

It would be a good idea to add ODBC connectivity so that the underlying SQL database can be directly queried from Excel

Guest almost 10 years ago in ODBC 0 Idea Accepted - Gauging Support

5 VOTE

Ability to clear and rebuild future financial years

Currently if looking to extend the current financial year beyond the end of the first period of the next year and you are shifting you year-end date accordingly moving forward the process to achieve this in Sage 200 is very laborious (extract from...

Guest about 7 years ago in Accounting Periods 0 Idea Accepted - Gauging Support

5 VOTE

add supplier transaction nominal validation

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

joanne scott about 7 years ago in Customer/Supplier Transactions 0 Idea Accepted - Gauging Support

5 VOTE

Ability to import Monthly Budgets against projects

This was previously logged as a Wish. Need to have the ability to import Monthly Budgets against projects. At present they have to be entered manually.

Guest over 7 years ago in Project Accounting 0 Idea Accepted - Gauging Support

6 VOTE

Single URN for Nominal Ledger Transaction Import

When a nominal ledger journal is imported using the standard Sage 200 nominal ledger import routine, could the system use a single URN for the entire import rather that giving each individual line it&s own URN?

Guest over 9 years ago in Nominal 0 Idea Accepted - Gauging Support

4 VOTE

Import journal transactions template usernumber field to be made mandatory:

When we use the import transactions functionality to upload a journal via the .csv template http://desktophelp.sage.co.uk/sage200/sage200standard/Content/CSV%20samples/NominalTransaction%20CSV.csv I have noticed that the UserNumber field is not ma...