AP Check Approval for Sage 300
SOX Check Approval extends the Sage 300 check management process.
Checks for one or more companies are approved by executives from an easy-to-use, central console. Payment batches are prepared by staff and submitted for approval. Two levels of executive approval are required. Unapproved checks are removed from the payment batch and approved checks are released for printing and distribution. A complete audit log is maintained of all submission and approval activity.
New for 2015: Option to send email notifications to submitters and approvers. Integration with Altec doc-link included. Ability to submit multiple System batch types for approval.
|Features and Benefits - Extended Payment Batch List|
|•||Accounts Payable Payment Batch List and Payment Entry functions are replaced with versions that restrict the entry, approval and printing of checks.|
|•||A "Submit for Approval" button puts a batch into the "Check Creation in Progress" state, which stops further modification of the batch by staff.|
|•||When a payment batch is submitted for approval, the batch and its entries are copied from the source company into an Approval Database that is managed by the Check Approval Console.|
|•||When a payment batch of type System is submitted for approval, a prompt will allow users to change the type to Generated - so that another payment batch can be generated during the approval process.|
|Features and Benefits - Console|
|•||Companies and batches are displayed in an easy-to-use tree view.|
|•||A 2-level approval process is performed by 2 different Sage 300 ERP users.|
|•||When a batch is approved, unapproved checks are removed from the batch and the batch is released for printing in the source company.|
|•||An audit log of all approval submission and approval activity is maintained.|
|Features and Benefits - Setup|
|•||A system administrator can set up executive access and passwords, which are then encrypted and stored in the Sage 300 ERP shared folder.|
|•||A "payment codes excluded" list is maintained per company. These codes are excluded from the approval process. For example, a "wire transfer" may be part of a payment batch and has already been sent - it is not, therefore, a check to be printed.|
|•||A status display is available to assist administrators. All batches and all checks can be displayed in a grid.|
|•||The check approval database tables are created programatically.|
|•||Sage ERP Accpac version 6.0 or Sage 300 2012 or 2014|
|•||A single executable program works with all platforms|