Native GRC Features in Business Central
Business Central offers foundational capabilities that form the basis of a GRC framework, essential for the optimal functioning of AWH GRC
How does AWH GRC extend these native features?
See a detailed comparison of Business Central alone vs Business Central + AWH GRC across governance, risk, and compliance dimensions.
Compare BC vs BC + AWH GRCBuilt-in capabilities you already have
These native Business Central features provide traceability, accountability, and privacy controls out of the box. AWH GRC builds on them to deliver governed processes, enriched evidence, and centralized oversight.
Source Codes
All entries posted in Business Central are automatically assigned to a source code so the origin of transactions can be tracked.
This info can be consulted directly from the AWH GRC process interface, allowing an integrated and centralized view of audit information.
Reason Codes
Reason codes are used to indicate why a particular entry was created.
This info can be consulted directly from the AWH GRC process interface, allowing an integrated and centralized view of audit information.
Change Log
Allows tracking who, when, and what was modified in any table.
This info can be consulted directly from the AWH GRC process interface, allowing an integrated and centralized view of audit information.
Data Classification (GDPR or similar)
Integrated tools to mark fields with sensitive data and comply with privacy regulations.
This info can be consulted directly from the AWH GRC process interface, allowing an integrated and centralized view of audit information. The classification of fields is also reported.
Master Record Blocking
Business Central allows blocking master records (customers, vendors, items, employees, contacts, etc.) to prevent transactions based on the status of each entity (debts, conflicts, approvals, inactivity). The "Privacy Blocked" field restricts the processing of personal data in compliance with GDPR, preventing marketing campaigns, business transactions, and non-essential processing of personal information.
It is recommended to include blocking fields in the Change Log configuration to audit who performs blocks/unblocks and when. When managed through AWH GRC, the reason can be registered or inferred from context.
Segregation of Duties (SoD)
Through the permissions system and permission sets, it is possible to ensure the same user cannot, for example, create a vendor and issue a payment.
Responsibility Centers
Separate purchase and sales operations by independent management units so assigned users only view and manage documents related to their administrative area.
Approval Workflows
Native workflows ensure that critical decisions (such as credit limits, sales discounts, or purchase orders) go through approval.
Integrate Business Central approvals with AWH GRC to extend the approval flow with tasks that help complete end-to-end processes.
Document Archiving
Automatic document archiving in Business Central helps ensure the record of the operation's origin is not lost.
With AWH GRC, you can continue to view the processes associated with these documents even after the operation has been completed.