Troubleshoot a hidden Accounting menu or action
Identify whether a missing screen is caused by permissions, inactive integrations, configuration or record state.
What this feature does
Identify whether a missing screen is caused by permissions, inactive integrations, configuration or record state. It forms part of Britixo Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.
How the module flow works
The module checks permissions before adding sidebar children and before many controller actions. A user may therefore receive access denied even when a direct URL is known.
Vendor management is shown by this Accounting module only when the separate Purchase module is not active; when Purchase is active, vendor workflows can be provided there instead.
A missing approval action can also mean no approval workflow has been configured or the current user is not the assigned approver.
Step-by-step workflow
- Confirm the user's staff account and role.
- Compare the missing action with the permission list.
- Check whether the relevant optional module is installed and active.
- Open the record and inspect its status and ownership.
- Review required settings, accounts and mappings.
- Retest with the same user after correcting the exact dependency.
Important fields and decisions
What happens after completion
After the action is saved, Britixo keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.
- Open the saved record and confirm its final status.
- Review the source reference and every debit and credit line where ledger data was created.
- Use the relevant register, ageing, reconciliation or report to verify the wider effect.
Controls, checks and common mistakes
- Do not grant administrator access merely to reveal a menu.
- Do not activate an optional module solely to expose a tab.
- Use a test user to validate role changes.
- Record permission changes in the organisation's access review.
- Use the least destructive correction available and record the reason for material changes.
- Do not bypass a permission, approval or closed-period control by changing unrelated data.
