/fa/compliance-mappings
Overview
The page rendersComplianceMappingEditor inside a RequirePermission gate for fa.category-mappings.view. The page header describes the purpose as: “Map GR compliance event categories (audit, fines, training, etc.) to FA expense accounts so compliance costs post to the correct general ledger accounts.”
The route has no additional permission wrapping in fa.tsx beyond what the component provides.
Who it’s for
Requires permission:fa.category-mappings.view (enforced within the component via RequirePermission)
Before you start
- GL accounts must be configured in the Chart of Accounts.
- GR compliance event category definitions must exist.
- You must hold the
fa.category-mappings.viewpermission.
Steps
1
Navigate to Compliance Cost Mappings
Go to
/fa/compliance-mappings.2
Review existing mappings
The
ComplianceMappingEditor displays current category-to-account mappings.3
Add or update a mapping
Select a GR compliance event category and assign it to the appropriate FA expense account.
4
Save changes
Confirm or save the updated mappings as supported by the editor.
Key concepts
ComplianceMappingEditor— Primary editor component for managing category-to-account mappings.- Cross-core dependency — This page bridges GR (Governance & Risk) and FA (Finance & Revenue) cores via the Platform Integration Layer.
Related
Finance & Revenue
Finance & Revenue core overview.
Governance & parity
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/fa.tsx
- src/cores/fa/pages/ComplianceMappingPage.tsx
- src/cores/fa/components/ComplianceMappingEditor.tsx