This video gives an overview of Task-Based security and how it works:

You will want to decide whether to configure secure approval workflow or batch authorization. In both cases, Threshold IDs are configured and saved at the system level, then applied to checkbooks. A Threshold ID allows you to save a series of threshold ranges, associated with users’ Task IDs and default signatures in the way that works best for your company.

Secure Approval Workflow

Secure Approval Workflow allows approval at the transaction level; before check/ EFT batches can be printed and processed, designated users are assigned to approve payments within customized threshold ranges:

  1. A designated GP user creates a payment batch.
  2. The user must then ‘Request Approval’ on that batch to start the workflow process. This can be done from the following GP windows:
    • Edit Payment Batch
    • Edit Vendor Payment
    • Build Payment Batch
    • Print Payments
    • Approvals can also be requested on all created batches from the Mekorma Payment Batch Status List.
  3. Approvers will receive email and/ or text notification that payment batches need approval (within their assigned threshold range).
  4. Approvers can access GP from any location. Payments are listed by Vendor in the Mekorma Approval List, and it is possible to view all vouchers that have been applied to each payment. If you have a document management system that integrates with GP and provides you with access to scanned invoices from this screen, that information will also be available.
  5. Payments at the Vendor level can be rejected and removed from the batch. Approvers can provide a detailed message back to the requester as to why those payment should not be processed and how to proceed.
  6. Once approval has been given, the Requester will be notified via email that the batch can be processed.
  7. The Mekorma Audit Log keeps a record of all payments and which GP user approved them.

Authorization

Authorization happens at the batch level. 1 – 2 users (Mekorma Batch Authorizers) can be assigned to authorize any payment batch before it is able to be printed/ processed. Signatures can be associated with customized threshold ranges.

  1. An authorized user creates a payment batch.
  2. The user must then Request Authorization on the batch. This can be done from the following GP windows:
    • Edit Payment Batch
    • Edit Vendor Payment
    • Build Payment Batch
    • Print Payments
    • Authorization can also be requested on all batches created at the company level, from the Mekorma Payment Batch Status List.
  3. Designated Authorizers will receive email and/ or text notification that payment batches need authorization.
  4. From the Mekorma Payment Batch Status list, authorizers can access GP to review details about the number of transactions in the batch and the total dollar amount.
  5. Once the authorization has been given, email notices go back to the Requester and the batch can then be processed.
  6. The Mekorma Audit Log keeps a record of all batches and which GP user authorized them

Follow this link for complete instructions on how to configure Task-Based security once you have installed Mekorma.

Last modified: 2019/10/23

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Please do not use this for support questions.
Contact Mekorma Support

Post Comment