Financial Audit & Fintech Ops — Operational Setup

How the 16 domain screens split across 4 sub-groups, ModuleGuard gating, and finaudit entitlement activation.

Operational Setup

Financial Audit & Fintech Ops screens split into two titled groups, following the enterprise governance/operational rule used across every add-on.

Two groupsAdministration & Access (admin only) — Roles, Audit & Fintech Ops Team (staff master)
Operational Setup — the 16 domain screens, split across 4 titled sub-groups, open to any user holding a FINAUDIT domain role

How the 16 screens split across the 4 sub-groups

Sub-group	Screens (in sidebar order)
Audit Rules & Compliance Setup	Audit Rules Registry · AML & Sanctions Config · Chart of Accounts Audit · Regulatory Reporting Setup
Transaction Audit & Reconciliation	Invoice Matching Audit · Multi-Source Audit & Reconciliation (Bank Reconciliation) · Fraud Detection & Anomaly Audit · Ledger Variance Audit
Treasury & Liquidity Operations	Cash Flow Forecast · FX Exposure & Risk · Credit Risk & Limits · Liquidity Buffer
Payments & Clearing Execution	Payout Routing Rules · Chargeback & Dispute · Settlement & Clearing · Financial Escrow

Every screen lives under the URL prefix /finaudit/<screen-slug>, e.g. /finaudit/fa-bank-reconciliation.

ModuleGuard & entitlement

Every FinAudit screen is wrapped in <ModuleGuard>, which enforces two checks in order:

Level 1 — Entitlement (paywall). The tenant must have the finaudit package active. If not, the screen renders a locked/upsell state instead of its content.
Level 2 — Governance/operational split. Roles (fa-roles) and the Staff master (Audit & Fintech Ops Team, fa-finaudit-staff, i18n key faStaffTitle) are admin-only (isModuleAdmin) and sit in the “ADMINISTRATION & ACCESS” sidebar group; the 16 operational screens are open to any staff member holding a FINAUDIT domain role, regardless of which specific role, and sit in the “OPERATIONAL SETUP” sidebar group.

Order matters

In both the app sidebar and the My Apps / DemoPageV2 showcase, the Administration & Access group renders first, then the 4 operational sub-groups in the order shown above.

Package activation

A tenant admin activates the add-on from Settings → Add-Ons by granting the finaudit package (label “Financial Audit & Fintech Ops”). Once active, an admin assigns FINAUDIT domain roles to staff from the Audit & Fintech Ops Team screen — an employee can carry a FINAUDIT hat alongside hats in other domains (multi-hat assignment). Once a staff member holds a FINAUDIT role, the module appears in their sidebar under Add-On Modules and in My Apps.

Pages in this section

Frequently Asked Questions

Who can see the Roles and Staff screens?

Only tenant admins (isModuleAdmin). They sit in the ADMINISTRATION & ACCESS sidebar group, separate from the 4 operational sub-groups.

Can a non-admin FINAUDIT user see any of the 16 screens?

Yes — all 16 operational screens are open to any staff member holding a FINAUDIT domain role. Which actions they can take within each screen still depends on their specific capabilities.

What happens if the package isn’t activated?

ModuleGuard’s Level 1 check blocks every screen in the add-on with a locked/upsell state, regardless of the user’s role.

Can one person hold both a FINAUDIT role and a role in another add-on?

Yes — roles are assigned per domain as independent “hats”. A person can be, for example, both a Treasury Analyst here and hold an HR role elsewhere in the same tenant.

Is there separate master-data setup outside the 16 screens?

No — the “Operational Setup” sidebar grouping refers to the section holding all 16 domain screens directly; the first sub-group (Audit Rules & Compliance Setup) doubles as the module’s master-data/configuration layer (audit rules, AML/sanctions config, chart of accounts, regulatory reporting).