FAQ & Troubleshooting

Two things must both be true: the module is enabled (Settings → Manage Modules, module_bplo = 1) and your role holds the base Business Licensing (eBOSS) permission (bplo). Without the base permission the entire group is hidden even when the module is on.

Actions are gated by their own permission. For example, approving a clearance needs bplo_clearances_review, reconciling a payment needs bplo_payments_reconcile, and signing a permit needs bplo_permits_sign. Check the role in Settings → Roles against the permission matrix.

The issuance gate has unmet conditions. Open the Gate Check for the application — it lists every blocker: an open blocking requirement, an unresolved or external-unverified clearance, a FAILED inspection, a missing approved assessment, an unsettled bill, an active hold, or no valid signatory. Clear each, then generate.

This is intentional four-eyes control — the person who prepared the assessment cannot approve it. Have a different officer who holds bplo_assessments_approve approve it. Above a configured amount a second approval is also required. The same separation applies to fee-set activation (author ≠ activator).

An approved assessment is immutable by design. To change the figures, supersede it (needs bplo_assessments_approve) — that creates a fresh DRAFT version you can recompute; the old figure is kept for audit.

The GL posting is deferred when the Finance module is disabled — the payment stays RECONCILED and the entry is retried later, so reconciliation is never blocked. Enable Finance and confirm the cash/revenue account numbers in Settings (bplo_finance_cash_account, bplo_finance_revenue_account_default) and that the accounting codes on your fee rules resolve to real accounts.

Expired is a derived status computed at read time from the validity date — it is never written onto the permit. The expiry-sweep job only notifies officers of lapsed permits; it does not mutate status. To keep a business current, process a renewal.

Only publicly-issued permits verify. A permit still in GENERATING, SIGNED or VOID was never issued and returns the same non-enumerating "not found" as an unknown code. Confirm the permit is ISSUED/RELEASED and that you are using the correct permit number or the exact QR link (which carries the tenant's company_key).

The migration installs a generic starter set so the module runs immediately. Before go-live, replace it with your approved ordinance values — your requirement rules and your Revenue Code fee rates (see Getting Started → Step 4).

The portal shows only businesses the customer owns or represents. If theirs isn't listed, they submit a "claim a business" request; a BPLO officer approves it in Owner-Portal Claims (bplo_portal_claims), which binds them to the business and brings it into scope.