Customer/Supplier Transactions

When importing journals, sales invoices and purchase invoices it allows transactions to still be imported to nominal accounts that are hidden, which shouldn't be able to happen as they are hidden as we don't want them to be able to be posted to.

I'm raising this on behalf of a client who would like to see the below changes on the financial transaction import routines. Username - it would be better if this defaulted to the user doing the import. Posting Date - this should default to the da...

Invalid Report to show transactions that have non-existent nominal codes as at present postings go to suspense

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

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 using the Import Customer Transactions routine to import sales receipts, there is no option to specify which bank account should be used. The default bank account is used. When you enter a sales receipt via the Enter Customer Receipt routine,...

It is possible to upload transactions with FX rate of lt; 1.00000 even the account you importing into is base currency, thus potentially putting the Control A/C out of balance.

On all Sage 200 versions prior to 2011 if purchase ledger invoice authorisation was enabled for all (£0.00). Imported invoices were not looked at and were imported as Authorised. On version 2013 onwards this core functionality changed and if PL in...