Accounting › Financial Controls
Control Frameworks
The published framework a control is claimed against. Naming COSO does not make a control effective, but an auditor asks which, and a control mapping to none is one nobody outside the company recognises.
Where to find it
- Module: Accounting
- Group: Close & Compliance
- Section: Financial Controls
- Screen: Control Frameworks
Address in the console: /accounting/control-frameworks
List · 6 columns · 6 fields on its form · 2 of them required
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Code | Code | code |
| Name | Text | name |
| Authority | Text | authority |
| Version | Text | version |
| Controls | Number | control_count |
| Active | Yes or no | is_active |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Code required | Text | ||
| Name required | Text | ||
| Authority | Text | ||
| Version | Text | ||
| Active | Yes or no | ||
| Description | Long text |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.