A solution to assist you in your Sarbanes Oxley compliancy requirements

Clients First has designed and built an enhancement suite for Microsoft Dynamics NAV to assist with your companies Sarbanes Oxley compliance requirements.

The primary functionality of this enhancement ensures that the person who enters journals in NAV is NOT the same person who posts them.  This is part of the concept of ‘segregation of duties’ and is a key requirement in order to achieve a positive outcome with your SOX audit.

This enhancement covers: Standard GL Journals, Recurring Journals, Payment Journals, Cash Receipt Journals, Adjustments to Bank Reconciliations, Sales Journals, Sales Credit Memos,  Purchase Journals, Fixed Asset GL Journals.

 

Please click the Chat Bubble below to find out more.  Although the specification shown here is in the Classic Client, the solution is also available in the Role Tailored Interface.

Purpose

The Purpose of this modification is to segregate and secure that separate individuals must enter or post journals in Microsoft Dynamics NAV – to support Sarbanes Oxley requirements.

 

 

Business Rules/Functional Requirements

In order to trace the individual who has Entered a Transaction, and then secure against that same person posting the transaction; additional fields and security must be added to NAV. 

 

clip_image002

 

  1. The fields above, Entry User ID, Entry Date and Entry Time are not editable, and are automatically inserted when records are created into the table.  If the record is modified in any way, the Entry User ID, Entry Date and Entry Time are updated to reflect the new owner of that entry. 
  2. The Posting Routine must be enhanced to block posting of any entries where the Entry User ID is the same as the posting users id.
  3. The Entry User ID, Entry Date and Entry Time must be posted to the resulting G/L Entry – for future audit purposes.

clip_image004

 

 

System Created Entries:

clip_image006

 

Must be created with a User ID of “SYSTEM” since the user has no ability to modify or adjust the entry.

 

clip_image008

The Recurring journals must include the same logic / processing rules.

 

clip_image010

The close income statement function feeds a General Journal batch with the entries.  These will follow the same rules as the General Journal example.

 

clip_image012

The Deposit lines will each bear a Entry User ID.  The same rules apply enforcing that the Entry User must not be the same person as the Posting User.

 

clip_image014

The Payment Journal must process according to the same logic / rules.  The Suggest Vendor Payment must mark the lines with the User ID who is executing this payment.  Upon Printing, the entries are modified with the Check number – this will modify the entries and store the printing User ID as the Entry User. 

 

clip_image016

Cash Receipts journals must respect the same processing logic as other journals.  Entry User is blocked from the Posting User.

 

clip_image018

The Bank Rec Worksheet must respect the same Entry User Logic, – ONLY IF Adjustments are being posted as a result of posting this Bank Rec.  The adjustments are owned by the Entry User that keyed them in.

 

clip_image020

Sales Journals

 

Sales Invoices (by the Entry User ID on the Sales Header).  On the Invoice lines, if multiple lines exist, any modification or addition of any line will change the Entry User ID on the Sales Header.

 

Sales Credit Memos (by the Entry User ID on the Sales Header).  On the Credit Memo lines, if multiple lines exist, any modification or addition of any line will change the Entry User ID on the Sales Header.

 

clip_image022

 

Purchase Journals

 

Purchase Invoices (by the Entry User ID on the Purchase Header).  On the Invoice lines, if multiple lines exist, any modification or addition of any line will change the Entry User ID on the Purchase Header.</font >

 

Purchase Credit Memos (by the Entry User ID on the Purchase Header).  On the Purchase Credit Memo lines, if multiple lines exist, any modification or addition of any line will change the Entry User ID on the Purchase Header.

 

clip_image024

Fixed Asset G/L Journal

 

 

clip_image022[1]