Import/ Export

it would be better if this defaulted to the user doing the 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?

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

Sage appears to look for the excel executable to create data exports, rather than generating the data and allowing the OS to direct the file according to the users spreadsheet default. Version 12.00.0035

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

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

Export headers on CSV files

When importing Sage 200 Customer or Supplier transactions, it is possible to specify a Source (Module) number in the 16-90 range to the Excel import file. At present, when the transactions have been imported, the description of Sources 16-90 will ...

When creating new company, program automatically creates reporting categories with codes 001 etc. Should be able to import reporting categories with overwrite existing option so users can use their own reporting category structure. Currently progr...

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...