Accounting & Bookkeeping · How-to guide

Troubleshoot a hidden Accounting menu or action

Identify whether a missing screen is caused by permissions, inactive integrations, configuration or record state.

Audience: Administrators and support staffFeature: TroubleshootingModule v1.4.5
Feature pathSetup → Staff → Roles and Accounting
Before you beginThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Administrator or relevant configuration access. A related screen can remain hidden when an optional module is inactive, a source record is in an ineligible status, the selected account is inactive or the user is not an assigned approver.

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

  1. Confirm the user's staff account and role.
  2. Compare the missing action with the permission list.
  3. Check whether the relevant optional module is installed and active.
  4. Open the record and inspect its status and ownership.
  5. Review required settings, accounts and mappings.
  6. Retest with the same user after correcting the exact dependency.

Important fields and decisions

Role permissionThe main menu is permission-aware and each submenu has a separate capability.
Optional module statePurchase, warehouse, payroll, manufacturing, Omni Sales and fixed-equipment tabs require their source modules.
Record statusApprove, refund, void or delete actions can be restricted by current status.
Configuration dependencyA form may require accounts, categories or mappings before the action becomes usable.

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.
Accounting and data safetyDeletion, reset, void, refund, mapping, journal and reconciliation actions can change financial history. Use approved access, retain supporting evidence and validate the result in the General Ledger or relevant control report.