Hi Ana, 

because each install is made up of a unique set of modules and setup work flows; there is not a One-size, fits all template. The best practice for this effort is as follows:

Gather a stakeholder from each team that uses Sage 500 ERP, such as warehouse personnel, accounting staff, report writers and so on. Build a test plan based on the day to day workflows for each team. The goal is to represent a set of transaction scenarios to cover your critical processes and as many outlying processes as possible. Be sure to include any reports you run at period end and routinely. 

Since you have customizations, work with your Sage partner or third party developer, if you need assistance with scenarios to verify whether customizations are working.

Review your imports or any automated processes and include testing for those as well.

Schedule sufficient time for the testing effort and plan to repeat testing as issues are addressed.

Hi Ana, 

because each install is made up of a unique set of modules and setup work flows; there is not a One-size, fits all template. The best practice for this effort is as follows:

Gather a stakeholder from each team that uses Sage 500 ERP, such as warehouse personnel, accounting staff, report writers and so on. Build a test plan based on the day to day workflows for each team. The goal is to represent a set of transaction scenarios to cover your critical processes and as many outlying processes as possible. Be sure to include any reports you run at period end and routinely. 

Since you have customizations, work with your Sage partner or third party developer, if you need assistance with scenarios to verify whether customizations are working.

Review your imports or any automated processes and include testing for those as well.

Schedule sufficient time for the testing effort and plan to repeat testing as issues are addressed.