Troubleshooting

Most Bitta Commission errors start with a code such as BAA-FEATURE-OFF or BAA-LICENSE-CAPACITY, followed by a sentence that says what to do. This page gives a first-response checklist, explains the codes you are most likely to meet, and shows how to collect diagnostics before you contact Bitta Apps support.

First-response checklist

1. Read the code. Note the full message, the page and the action you chose. The prefix tells you the area: FEATURE (modules), LICENSE, FINANCE or SCOPE (access), WFL (approvals and workflow), STM (statements), DSP (disputes), SETTLE and PAYGROUP (settlement), RUN (calculation and periods), SETUP (setup and import), COPY and PKG (copying and packages), AI and SIM.
2. Check the module. If a page opens but its actions are refused, the module may be switched off. Check Commission Feature Management.
3. Check the license. Open Bitta Commission Setup and look at State, Valid Through and Payee Limit.
4. Check your access. Confirm your permission set and your commission user scope in Commission User Scopes. Many actions need scope over the participant, and finance documents need a finance-wide scope.
5. Refresh and retry once. Many actions check the record's exact version. If someone else changed it, close the page, reopen it and try again.
6. Do not work around history. Never try to fix a result by editing ledger rows. Use a correction, a reopen request or a new version instead.

If the problem remains, collect diagnostics (see the end of this page).

Modules and setup

Code	Cause	What to do
BAA-FEATURE-OFF	The action belongs to a module that is switched off in this company.	A Setup Administrator switches the module on in Commission Feature Management. See Turn features on as you grow.
BAA-FEATURE-ADMIN	Only a Setup Administrator can switch modules.	Ask a user with BAA Comm Setup Admin.
BAA-FEATURE-STATE	The module is already on or off.	No action needed.
BAA-SETUP-IMPORT-HEADER, BAA-SETUP-IMPORT-SHEET	The workbook does not match the template.	Download the template again and keep its sheet name and header row. See Import setup from Excel.
BAA-SETUP-IMPORT-BLOCKED	Some rows have errors.	Review the findings, correct the file and import again.
BAA-NATIVE-SETUP	Native capture needs a history start date and validated scanner readiness.	Run Prepare Native Scanner Jobs and Validate Native Scanner Readiness on Bitta Commission Setup.

License

Code	Cause	What to do
BAA-LICENSE-AUTHORITY	No verified current license exists for this company and environment.	Activate or refresh the license. See Activate a license.
BAA-LICENSE-PRODUCTION, BAA-LICENSE-SETTLEMENT, BAA-LICENSE-ACCOUNTING	The license state (Suspended, Expired, Revoked) does not allow new output.	Renew the license with Bitta Apps, then choose Refresh License.
BAA-LICENSE-CAPACITY	Active participants exceed, or would exceed, the licensed limit.	Deactivate participants you no longer pay, or ask Bitta Apps for a higher limit. See License lifecycle.
BAACOMM-PUB-LICENSE-BOOTSTRAP-001	The app could not build the environment identity for licensing.	Contact Bitta Apps support with the code.

Access and scope

Code	Cause	What to do
BAA-FINANCE-SCOPE	Settlement, accounting, currency and remittance documents need finance-wide access.	Add a Finance (all participants) scope for the user.
BAA-WFL-SCOPE	The record or approval is outside your commission scope or not assigned to you.	Check Commission User Scopes and the approval assignment.
BAA-SIM-SCOPE	Scenario design needs setup administration or finance-wide scope.	Assign the scope or ask a finance user.
BAA-AI-SCOPE	You have no scope to the participant of the earning.	Ask a user with scope, or add the scope.

See Roles and permissions.

Approvals and workflow

Code	Cause	What to do
BAA-WFL-POLICY	There is no single effective approval policy for the document type, or its stages are incomplete.	Create one in Commission Approval Policies, and make sure dates do not overlap.
BAA-WFL-SELFAPPROVAL	The requester tried to approve their own request.	Another user must approve.
BAA-WFL-SEGREGATION	The user already decided this request.	Another user must decide.
BAA-WFL-ROUTING	The stage could not resolve an enabled approver.	Check the approver user on the policy is enabled.
BAA-WFL-STALE	The document changed after the request was created.	Submit the document again.
BAA-WFL-BULK-LIMIT	The request is above the bulk approval limit.	Decide it individually.

See Approvals and notifications.

Statements and disputes

Code	Cause	What to do
BAA-STM-SOURCE-001	The settlement is not frozen or its evidence is incomplete.	Freeze the settlement first.
BAA-STM-STATE-001	The statement changed or is in the wrong status for the action.	Reopen the statement and check its status.
BAA-STM-PAID-001	A settlement behind the statement still has payable or held amounts.	Complete the payment channel first.
BAA-STM-DISPUTE-001	A dispute on the statement still awaits a decision.	Decide the dispute first.
BAA-DSP-DEADLINE-001	The statement dispute window has passed.	Contact your manager or finance.
BAA-DSP-AMOUNT-001	The amount to review exceeds the selected line or statement.	Reduce the amount.
BAA-DSP-HOLD-OUTPUT-001	An affected payroll-ready export awaits acknowledgement.	Record the acknowledgement, then apply the hold.
BAA-DSP-RESOLVE-004	The routed correction is still being approved or processed.	Check again after it completes.

See Participant and manager statements and Disputes and holds.

Settlement and calculation

Code	Cause	What to do
BAA-SETTLE-VENDOR	A participant in an Accounts Payable pay group has no effective vendor link or vendor number with matching currency.	Complete the participant's payee setup.
BAA-PAYGROUP-EMPTY	The pay group has no members effective on the cutoff date.	Add members or change the cutoff.
BAA-HOLD-PAYSHEET	A paysheet hold is on the settlement.	Release it on Eligibility Holds.
BAA-RUN-BATCH-PERIOD	The period is not open for calculation.	Open or reopen the period. See Period close and reopen.
BAA-RUN-BATCH-BASELINE	An incremental batch needs a completed full baseline.	Run a full batch first.
BAA-RUN-BATCH-OVERLAP	Another batch for the same plan version and period is still active.	Let it finish or cancel it.

See Settlements and pay groups and Calculation runs and schedules.

Copying, packages and AI

Code	Cause	What to do
BAA-COPY-LINE-002	The target company refused a copied item.	Assign BAA Comm Setup Admin in the target company.
BAA-PKG-DEPENDENCY	A plan package needs a definition that is missing or does not match exactly.	Align the target configuration and import again.
BAA-IDEM-CONFLICT	An idempotency key was reused for a different operation.	Start the action again from the page.
BAA-AI-DISABLED, BAA-AI-CONSENT	The AI capability is switched off or has no Active consent.	Enable it and accept the consent in Commission AI Setup. See AI plan design assistant.

Collect support diagnostics

1. Open Commission Support Diagnostics and choose Collect.
2. Look for lines with a Severity Code of WARNING or BLOCKING. They often point straight at the cause, for example a missing setup, a job queue entry in error, or no entitlement.
3. Choose Export Package to download the sanitized text file.
4. Send it to Bitta Apps support with the error code, the page and action, and the time it happened.

The package contains no participant names, amounts or activation codes. See Job queues, monitoring, and diagnostics.

Related pages

• Known limitations
• Job queues, monitoring, and diagnostics
• Audit and security
• Exceptions and data quality