Sage 200 UKI Ideas Portal

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 reject it or at least warn that it doesnt exist. Pegasus Opera has more strict posting and importing validation checks!

  • Guest
  • Jul 20 2016
  • Idea Accepted - Gauging Support