10.18: Difference between revisions
From Arizona Citizen Voice
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
'''>>>Navigational Buttons<<<''' | '''>>>Navigational Buttons<<<''' | ||
* '''[[Index of Attributes]]''' | * '''[[Index of Attributes]]''' | ||
* '''Previous Attribute - | * '''Previous Attribute - [[10.17]]''' | ||
* '''Next Attribute - | * '''Next Attribute - [[10.19]]''' | ||
__FORCETOC__ | __FORCETOC__ | ||
=== ' | |||
=== Jamie's Story === | |||
No examples are available to illustrate governance gaps for this attribute. | |||
=== Election Anomalies === | |||
No examples are available to illustrate governance gaps for this attribute. | |||
Revision as of 09:36, 22 August 2026
Control Activities
Principle 10 - Design Control Activities
Attribute 10.18 - When designing transaction control activities, management evaluates information processing objectives to meet the entity's objectives and mitigate related risks.89 Information processing objectives may include the following:
- Completeness - All transactions and events that occur have been properly recorded.
- Accuracy - Data relating to transactions and events are properly and timely recorded.
- Validity - All recorded transactions and events actually occurred, are related to the entity, and were executed according to prescribed procedures.
>>>Navigational Buttons<<<
- Index of Attributes
- Previous Attribute - 10.17
- Next Attribute - 10.19
Jamie's Story
No examples are available to illustrate governance gaps for this attribute.
Election Anomalies
No examples are available to illustrate governance gaps for this attribute.
