Troubleshooting

Most Bitta Commission refusals start with a code such as BAA-FEATURE-OFF or BAA-LICENSE-CAPACITY, followed by a sentence that says what is wrong. This page shows you how to check your setup in one pass and lists the codes you are most likely to meet, with the fix for each.

First response

• Read the code. Note the full message, the page and the action you chose. The part after BAA- names the area, for example FEATURE (modules), LICENSE, FINANCE (finance scope), WFL (approvals), STM (statements), DSP (disputes), SETTLE (settlement), RUN (calculation runs and periods) or COPY (configuration copy).
• Check the module. If a page opens but its actions are refused, the module may be switched off in Commission Feature Management.
• Check the license in the License group of Bitta Commission Setup: State, Valid Through, Payee Limit and Diagnostic.
• Check your access. Confirm your permission set and your scope in Commission User Scopes.
• Never edit ledger rows to work around a result. Use a correction, a reopen request or a new plan version instead.

Check setup with the setup checklist

1. Search for Bitta Commission Setup Checklist and choose Check Setup. It checks every setup area again and keeps passed checks visible. Switch on Include Operational Verification to also check approvals, financial numbering, posting, real runs and reconciliation.
2. Review the lines. Status is Passed, Needs attention, Waiting for your first pay cycle or Not checked, and Check, Finding and How to Fix say what to do. The Readiness Code column is hidden by default; it holds the code support asks for.

3. Select a finding and choose Fix Selected Check, or the How to Fix link, to open the setup page that fixes it. Then return and choose Check Setup again.

Check	Readiness Code	Fix
Company and implementation path	BAA-PATH-HC-001	Open guided setup and select the implementation path.
Core feature and trial or subscription	BAA-PATH-HC-002	Confirm a current Trial or Active license on Bitta Commission Setup.
Currency, calendar and open period	BAA-PATH-HC-003	Set Calculation Precision and Default Calendar Code, and create an Open period.
Commission numbering	BAA-PATH-HC-004	Choose Prepare Commission Numbers on the checklist.
Selected earners and dated mappings	BAA-PATH-HC-005	Create the participant's effective active version and Sales Earner mapping.
Commission sources	BAA-PATH-HC-006	Review native capture, its history start date and scanner readiness.
Plans, rates and assignments	BAA-PATH-HC-007	Complete the plan version, rates and dated assignments. Then finish the setup wizard, or choose Try Again on its Results step; it approves and publishes the plan.
Accounting and reconciliation, finance document numbering	BAA-PATH-HC-010, BAA-PATH-HC-015	Complete Commission Posting Setup and account mappings. Requires the Accountant permission set and a Finance (all participants) scope.
User access and approvals	BAA-PATH-HC-011	Add dated user scopes, then configure separate maker and checker users in Commission Approval Policies.
Background jobs and retention	BAA-PATH-HC-012	Review the prepared jobs in Job Queue Entries.

Two checks need your first real pay cycle and show Waiting for your first pay cycle after the setup wizard: BAA-PATH-HC-009 (the first settlement is created and frozen) and BAA-PATH-HC-014 (the first commission run is completed and reconciled with zero differences). Nothing needs fixing; they pass after your first commission run and settlement. When you chose not to post to the general ledger in the wizard, BAA-PATH-HC-010 and BAA-PATH-HC-015 pass with "Not used: G/L posting is off."

Setup wizard: commission is not running

When Finish on Set Up Bitta Commission cannot complete every step, the salespeople and plan it created are kept, the Results step shows Commission is running turned off, and What was done names the problem. Fix it, then choose Try Again; the wizard continues where it stopped.

Message or symptom	Cause	What to do
Finish is not available on the Review step	The review has rows that need attention.	Fix the rows the review shows, then return to the Review step.
"Plan ... could not be started: ... Fix this, then choose Try Again."	A Go Live step stopped with an error.	Fix what the message names, then choose Try Again.
"Plan ... is not ready to publish yet: ..."	The plan has a blocking validation finding.	Open the plan with Review Created Plan, fix the finding, then choose Try Again.
"Plan ... could not be published. Its status is ..."	The plan version did not reach Published.	Open the plan to see why, fix it, then choose Try Again.
"Sales capture could not start: ..."	Native capture of posted sales is not ready.	Fix the reason given, then choose Try Again.
BAA-SETUP-POST-JOURNAL, BAA-SETUP-POST-SERIES, BAA-SETUP-POST-SOURCE, BAA-SETUP-POST-ACCOUNTS	A G/L posting choice is missing, or the expense and liability accounts are the same.	Complete the G/L posting fields. While commission is not running you can change them on the Results step. Then choose Try Again.
What was done includes "Guided setup is not ready for review yet: ..."	A guided setup check did not pass. This does not stop commission from running.	Choose Check Configuration and fix the finding it shows.

Modules, setup and access

Code	Meaning	Fix
BAA-FEATURE-OFF	The module of the action is switched off in this company.	A Setup Administrator switches it on in Commission Feature Management. See Optional modules.
BAA-FEATURE-ADMIN	Only a Setup Administrator can switch modules on or off.	Ask a user with the Bitta Commission Setup Administrator permission set.
BAA-ORG-SETUP-AUTH	The page or action needs the Bitta Commission Setup Administrator permission set.	Assign it to the user in this company.
BAA-NATIVE-SETUP	Native capture needs a history start date and validated scanner readiness.	Fill in Native History Start Date, then run Prepare Native Scanner Jobs and Validate Native Scanner Readiness. The setup wizard does this for you when it goes live. See Job queue monitoring.
BAA-SETUP-IMPORT-HEADER, BAA-SETUP-IMPORT-SHEET, BAA-SETUP-IMPORT-BLOCKED	The workbook does not match the template, or rows have errors.	Use the downloaded template unchanged, correct the rows and import again.
BAA-FINANCE-SCOPE	Settlement and accounting documents need finance-wide access.	Add a Finance (all participants) scope for the user.
BAA-WFL-SCOPE	You are outside the permitted workflow scope, or the approval is not assigned to you.	Check Commission User Scopes and the approval assignment.

License

Code	Meaning	Fix
BAA-LICENSE-AUTHORITY	No verified current license exists for this company and environment.	Activate the issued code or refresh the license.
BAA-LICENSE-PRODUCTION, BAA-LICENSE-SETTLEMENT, BAA-LICENSE-ACCOUNTING	The license state does not allow new commission, settlement or accounting output.	Renew with Bitta Apps, then refresh the license.
BAA-LICENSE-CAPACITY	The license does not allow more active participants.	Deactivate participants you no longer pay, or ask Bitta Apps for a higher limit.
BAACOMM-PUB-LICENSE-ADMIN-001	You do not have the Setup Administrator permission set in this company.	Ask an administrator to assign it.

For every license code and state, see License lifecycle.

Approvals and plans

Code	Meaning	Fix
BAA-WFL-POLICY	No single effective approval policy with complete stages exists for the document type (plan, statement, settlement or accounting posting).	Configure one in Commission Approval Policies with dates that do not overlap.
BAA-WFL-SELFAPPROVAL	The requester tried to approve their own request, or a policy stage routes the request to its requester.	Another approver must decide it. If the requester is the stage approver, change the stage on the Commission Approval Policy page.
BAA-WFL-SELFAPPROVAL or BAA-WFL-SCOPE for an administrator	You hold BAA Comm Setup Admin, but the request affects your own commission: a participant linked to you has an assignment, earning or settlement line in its scope. The administrator approval right does not cover it, whether you raised the request or it was not assigned to you. Only a SUPER user may decide such a request.	Leave it to its other approvers. Show all open requests in Commission Approval Work Queue does not let you decide it either. See Approval policies.
BAA-COR-REQ-FOUR-EYES, BAA-COR-MANUAL-FOUR-EYES, BAA-CRD-OVERRIDE-SOD, BAA-DISCRETIONARY-SOD, BAA-SCORECARD-SOD, BAA-HOLD-INDEPENDENT-RELEASE, BAA-RUN-REOPEN-SECOND-USER	You requested, submitted or placed the item, so you can't approve or release it. An administrator gets the same refusal when the item affects their own commission (for a period reopen: when they have an earning in the period).	Ask another user to approve it.
BAA-WFL-DELEGATION	The delegate is you or the requester, or has no active delegation from you. An administrator delegating a request they were not assigned must choose a stage approver or another administrator whose own commission the request does not affect.	Choose another delegate.
BAA-WFL-SEGREGATION	You already decided on this request. One person can't decide a request twice, administrators included.	Another approver must decide.
BAA-WFL-ROUTING	The stage did not resolve enough eligible approvers.	Check that the stage approvers are enabled users.
BAA-WFL-STALE	The request version or document evidence is stale.	Reopen the document and submit it again.
BAA-WFL-BULK-LIMIT	The request amount is above the bulk approval limit.	Decide it individually.
BAA-PLAN-VALIDATION	The plan version has blocking validation errors.	Fix the first finding shown and validate again. See Commission plans.
BAA-PLAN-IMMUTABLE	Approved or later plan content cannot change.	Choose Create Successor on the plan version and change the new Draft.

Periods, statements and settlements

Code	Meaning	Fix
BAA-RUN-BATCH-PERIOD	The period is not open or reopened.	Open the period, or request a reopen. See Close a period.
BAA-RUN-BATCH-BASELINE	An incremental batch needs a completed full baseline.	Run a full batch first.
BAA-RUN-BATCH-OVERLAP	Another batch for this plan version and period is still active.	Let it finish or cancel it.
BAA-STM-SOURCE-001	Statement generation needs complete frozen settlement evidence.	Freeze the settlement first.
BAA-STM-DISPUTE-001	A dispute on the statement still awaits a decision.	Decide the dispute first.
BAA-STM-PAID-001	A settlement behind the statement is not paid yet.	Complete the payment first.
BAA-DSP-DEADLINE-001	The statement dispute deadline has passed.	Contact your manager or finance.
BAA-HOLD-PAYSHEET	The settlement batch is on hold.	Release the paysheet hold before you submit or freeze it.
BAA-SETTLE-VENDOR	A participant in an Accounts Payable pay group has no effective vendor link with matching currency.	Complete the participant's payee setup.
BAA-ACC-PAYROLL-ACCOUNT	The posting setup has no payroll clearing account.	Set it in Commission Posting Setup. See Commission accruals.

Rates, deductions and payments

Code or symptom	Cause	What to do
BAACOMM-PUB-CREDIT-RULE-TIE-002	Two matching Set Rate rules have the same priority and specificity but a different rate or rate basis.	Choose Create Successor on the plan version and change a priority or a condition in the new Draft. Use Why This Rate? to see both rules. See Why this rate?.
BAA-CRD-DEDUCTION	A Deduct From Base rule has neither a Deduction % nor a Deduction Attribute Code.	Enter one of them.
BAA-CRD-AGREEMENT-OVERLAP	Two customer agreements for the same bill-to customer and component overlap.	Change the dates so the agreements follow each other. See Customer agreements.
BAA-CRD-VALUE-LIST-IN-USE	The value list is used by a plan version that is no longer Draft.	Create a new value list and use it in a Draft successor.
Set Rate rule has no effect	The component's model does not price each line.	Use the Line Rate model. Plan validation reports this. See Line rates and margin pools.
A line is paid zero with an exception	No rate row, margin band or commission cost fits the line, and No-Match Handling is Zero Rate With Exception.	Add the missing row, band or cost, then correct the earning with a correction request.
BAA-COR-NETTED-ON-APPLICATION	The return policy reduces commission when the credit memo is applied to the invoice, so the credit memo is not calculated as a return.	Apply the credit memo to the invoice and let the release job net it. See Credit memo netting.
A posted credit memo did not reduce commission	Under Customer Ledger Application nothing happens until the credit memo is applied, and only with an On Payment or On Full Payment eligibility policy.	Apply it to the invoice. Check the eligibility policy.
BAA-COR-REQ-DATE-RANGE	Effective Date To is earlier than Effective Date on a correction request.	Correct the dates.
BAA-COR-REQ-RECALC-APPROVER	Approve or Queue Recalculation on a correction request needs the Bitta Commission Recalculation Approver permission set. SUPER does not include it.	Assign the permission set to the approver. See Permission sets.
BAA-EXTSETTLE-INVOICE	The invoice of an external settlement has no customer ledger entry.	Enter the number of a posted sales invoice. See Commission paid outside Business Central.
BAA-ACC-AP-GET-LINES	A settlement line can no longer be added to the purchase invoice, or the invoice is not open or has no vendor.	Choose Get Commission Lines again on an open purchase invoice with a vendor. See Pay through Payables.
BAA-STM-EMAIL-NONE	The settlement has no generated statement to send.	Generate the participant statements first.
Statement e-mail SKIPPED	No e-mail address, no e-mail account for the Commission Statement scenario, the statement is not approved yet, or its participant is outside your access.	Read the reason on Commission Statement E-Mail Log. See Email statements.
BAA-DRAW-RECOVERY-OVERDUE	A scheduled advance recovery was still outstanding after its Recover On date when the period closed.	Review the participant's draw balance and recover or waive the amount.

Copy, AI and repeated commands

Code	Meaning	Fix
BAA-COPY-LINE-002	The target company refused a copied item.	Assign BAA Comm Setup Admin in the target company and copy again.
BAA-AI-DISABLED, BAA-AI-CONSENT	The AI capability is off or has no Active consent.	Switch it on and accept the consent. See AI plan assistant.
BAA-IDEM-CONFLICT	An idempotency key was reused for a different operation.	Start the action again from the page.

Collect diagnostics for support

If the problem remains:

1. Search for Commission Support Diagnostics. It collects its facts when it opens.
2. Check the lines with Severity BLOCKING or WARNING. They often point at the cause, for example missing setup, a job queue entry in Error or no entitlement.

3. Choose Export Package and send the file to Bitta Apps support with the code, the page, the action and the time. See Job queue monitoring.

What's next

Know what the app does not do: Known limitations. For version history, see Release notes.