Skip to content
HNROS Help Center
English
Start free
Contents1. Permission matrix2. Segregation of duties3. Period locks4. Findings5. Checking source changes6. Who can see it, on the phone7. Limitations

Audit centre: permission matrix and period locks

Who is allowed to do what, which financial period is locked, and who opened a lock, when and why: the first questions of internal and external auditors are answered in one window.

The audit centre is read-only; it does not change any permission or lock. Changes are made in Settings › Users, Settings › Security gates, Settings › Corporate controls and the Accounting window.

1. Permission matrix

There are three views: Rights (user × permission), Window access (user × window) and Segregation of duties. Every cell shows whether the permission is present. With the filter you can see only those with critical rights, those with a segregation conflict, inactive users or those who have not signed in for 90 days, and search by user name. Inactive shows that the account is closed (“Account closed: the user cannot sign in. To reopen it, use Settings › Users › Activate.”); “No access for 90 days” is a separate badge and filter (“Inactive users (account closed)” and “No access for 90 days”). Clicking a user row opens the full list of warehouses, cash desks, last access and open permissions; the whole table can be downloaded as CSV. Last-access information comes from the access trail and is shown only to the Administrator.

Critical permissions are flagged separately: all permissions (system administrator), direct database query, acting past limits and gates, taking company backups, remote access, developer tools, bulk data import, card merging and record deletion.

2. Segregation of duties

Pairs of permissions that raise the risk of error and abuse when held by the same person are listed as warnings: entering purchase invoices and making payments, issuing sales invoices and entering collections, editing account cards and entering payments or collections, setting credit limits and entering sales documents, placing purchase orders and receiving goods, entering and deleting invoices, counting stock and approving count differences, entering cash and bank transactions and writing journal entries. System administrators are left out of this list; they already hold every permission and appear under critical permissions.

For each user with a conflict, a rule-compliant fix is suggested: the role template closest to the user’s permissions is found and the side that template does not need is turned off (for example collections left over from the old sales template, invoice entry and account record editing left from the old finance template, or goods receipt left from the old purchasing template). For a user who resembles no template, the side that turns off fewer permissions is suggested, or the executing side (payments, collections, goods receipt) when equal. "Fix to comply with the rule" in the user detail, or "Apply all suggestions" in the Segregation of duties view, turns off only the suggested permissions after a confirmation step; the user’s open session is refreshed immediately and the action is written to the user-management trail.

Only a system administrator applies the suggestion; a user viewing with the Audit permission sees it. If someone else changed the user’s permissions after the suggestion was shown, or the same suggestion is applied twice, nothing is changed and an "Suggestion has changed" warning appears. The account record rule counts only the permission to edit account records; viewing account statements together with collections is not a conflict.

3. Period locks

Five locks are watched on one screen: the document period lock (no invoice, delivery note or receipt can be entered before this date), the accounting period lock, the corporate lock date, the corporate period closing and the standard cost period freeze. The grid of the last 12 months shows in which source each month is locked; clicking a month lists its lock events in order with who made them, when and with what justification.

Opening a lock is not an error in itself; its justification and the records written while the lock was open are what get examined. Lock changes made from the desktop program land in the same trail. The change history of the document period lock starts with the server update; for earlier changes only the last person who changed it is shown.

4. Findings

High-risk findings: no document period lock is defined; the lock date has not been moved forward for months; the system administrator can enter documents in the locked period; invoices were written into the locked period after the lock was set; the lock was moved back or removed and invoices were written into that range. Other findings: an accounting period lock was opened (with how many records were written while it was open) or is still open; an older accounting period derived but not locked; a corporate period closing reopened; the corporate lock date moved back; a standard cost period freeze released. Every finding carries the user, time and justification.

5. Checking source changes

For a locked accounting period, press Check source changes: the accounting derivation runs as a dry run and counts source changes not yet reflected in the ledger (new, changed and deleted documents, with a few examples). No journal entry is written. A non-zero count means the source documents were altered after the lock. This check requires the Accounting permission.

6. Who can see it, on the phone

The permission matrix is visible to the system administrator and users with the Audit permission; period locks are also visible to users with the Accounting permission. The permissions are in Settings › Users › Bulk confirmation and audit. On the phone (Garden and Step) the matrix is shown as a user list after choosing a window, and period locks and findings appear as cards.

7. Limitations

The matrix shows permissions only; warehouse and cash-desk scope is written in the user details but is not reflected in the cells. Rejected write attempts (such as a document someone tried to enter in a locked period) are not tracked; only changes that actually happened are shown. The history of setting changes covers only changes made after this version.

Related guides