Manage and troubleshoot
License lifecycle
Understand Bitta Commission license states, salesperson capacity and the daily refresh, what a lapsed license blocks, and what keeps working for your data.
updated: applies-to: 1.2.0.0
Bitta Commission checks a verified license immediately before it produces new commission, settlement or accounting output. This page explains the license states and capacity limits, how the license is refreshed, and exactly what stops and what keeps working when a license lapses. To activate a license for the first time with the code Bitta Apps issues, see Activate a license.
Before you start
- The license actions on Bitta Commission Setup need the Bitta Commission Setup Administrator permission set assigned to you in the current company. Other users can read the license fields but cannot change them.
- Each company is licensed on its own. A license is bound to the product, your Microsoft Entra tenant, the environment and the company, and the app verifies its signature before it accepts it.
- The subscription includes every module. For prices and for adding salespeople, see Pricing and trial or contact Bitta Apps.
Check the license status
- Search for Bitta Commission Setup in Tell Me, open it and scroll to the License group. State, Valid Through, Payee Limit, Company Limit and Diagnostic show the verified license. Diagnostic never shows license identifiers or the activation code.
- To compare companies, search for Commission Company Readiness. It lists every company you can reach with its License State and License Valid Through.
License states
| State | Meaning | New output | New active participants |
|---|---|---|---|
| Uninitialized | No verified license exists in this company yet. | Refused | Refused |
| Trial | A verified trial issued by Bitta Apps is in effect. | Allowed | Up to 5, even if the license shows a higher limit |
| Active | A verified subscription is in effect. | Allowed | Up to the Payee Limit |
| Grace | The license is past its expiry but inside its grace window, for example when the daily refresh could not reach the license service. | Allowed | Refused |
| Suspended, Expired, Revoked | The license no longer authorizes output. | Refused | Refused |
On Bitta Commission Setup, State shows only Trial, Active or Grace. When there is no license, or it is Suspended, Expired or Revoked, State is blank and Diagnostic gives the reason. Commission Company Readiness shows the stored state.
"New output" means new positive commission, settlement output and accounting output. A trial starts only when you activate a publisher-issued code, never on installation.
What a lapsed license blocks
The app rechecks the license immediately before each output-producing action, not only when you sign in. Without a verified license in the Trial, Active or Grace state:
- Calculation of new positive commission, in calculation runs and period closes.
- Settlement output: settlements, payroll-ready exports, AP exports and generic export files.
- Accounting output: accounting proposals, G/L posting, payroll posting and AP invoices.
A missing, Suspended, Expired or Revoked license is refused with BAA-LICENSE-AUTHORITY. The codes BAA-LICENSE-PRODUCTION, BAA-LICENSE-SETTLEMENT and BAA-LICENSE-ACCOUNTING are additional checks that apply only after a Trial, Active or Grace license is found.
The same actions are also refused with BAA-LICENSE-CAPACITY when the company has more active participants than the license allows.
What keeps working
The license controls new output only. It does not lock you out of your data:
- Reducing corrections still run. A correction that is linked to earlier output and reduces the amount, such as a return or a clawback against an earning, is allowed after a lapse.
- Your records stay. The license checks never delete or change commission data. Pages and reports that only read existing records are not license-checked.
- Standard posting is not affected. Business Central posting outside Bitta Commission does not depend on this license.
Capacity
- Active participants. Every participant with the status Active in the company counts, not only the ones you are adding. Activating a participant, or creating active participants in the guided setup, is refused with BAA-LICENSE-CAPACITY when the total would exceed the limit. The guided setup checks the limit earlier: on its Who earns step it shows Salespeople your license allows, Salespeople already earning and New salespeople selected, and Next is refused when the selection would exceed the limit. In the Grace, Suspended, Expired and Revoked states, no new participant can be activated.
- Output rechecks the count. If the company has more active participants than the license allows, for example after moving from a trial to a smaller subscription, calculation, settlement and posting are refused until you deactivate participants you no longer pay or obtain a higher limit.
- Companies. A subscription license is accepted in an additional company only while the number of companies already using it is below the Company Limit. A license in Grace is accepted only in companies that already use it.
TIP
Before a trial ends, review Commission Participants and deactivate test or demo participants, so the active count fits your subscription.
Keep the license current
After a direct activation, the app creates one recurring job queue entry:
| Setting | Value |
|---|---|
| Description | Refresh Bitta Commission license |
| Job Queue Category Code | BAACOMMLIC |
| No. of Minutes between Runs | 1440 (daily), starting 24 hours after activation |
| Maximum No. of Attempts to Run | 3 |
| Rerun Delay (sec.) | 900 |
A renewal from Bitta Apps is picked up by this job, or immediately when you choose Refresh License, which skips the retry wait the scheduled job uses. If a refresh fails, the message says whether the license service timed out, rejected the request, reported a conflict, received too many requests or was unavailable, and ends with a reference code. Send that reference code, never the activation code, to Bitta Apps.
License actions
| Action on Bitta Commission Setup | What it does |
|---|---|
| Refresh License | Refreshes the current verified direct license now. |
| Import Offline License | Imports a signed offline license file from Bitta Apps without storing the raw file. |
| Deactivate License | After you confirm "Deactivate the current license and remove its automatic refresh job?", deactivates only the current verified direct license and removes its refresh job. |
| Reconcile License Restore | Records an audited reconciliation for the single verified license that is pending review after an environment restore or copy. |
| Recover Direct License History | Authenticates a retained license history row with its stored credential. Recovered history does not authorize operations. |
| Export History Recovery Request, Import History Attestation | Used with the Bitta Apps license administrator when the original credential is not available. An attestation cannot activate a license. |
Error codes
| Code | Meaning |
|---|---|
| BAA-LICENSE-AUTHORITY | A verified current license is required and was not found for this company and environment. |
| BAA-LICENSE-PRODUCTION | The license state does not allow positive commission production. |
| BAA-LICENSE-SETTLEMENT | The license state does not allow settlement output. |
| BAA-LICENSE-ACCOUNTING | The license state does not allow accounting output. |
| BAA-LICENSE-CAPACITY | The active participant count would exceed, or already exceeds, the licensed limit. |
| BAA-LICENSE-FEATURE | The license does not authorize Commission Core output. Contact Bitta Apps. |
| BAA-LICENSE-COMPANY | An administrative license command ran outside the exact current company. |
| BAA-LICENSE-RESTORE | A restore reconciliation needs verified current evidence. |
| BAACOMM-PUB-LICENSE-ADMIN-001 | The user does not have BAA Comm Setup Admin in this company. |
| BAACOMM-PUB-LICENSE-NOAUTH-001 | Deactivate License found no verified direct license to deactivate. |
| BAACOMM-PUB-REFRESH-NOT-ELIGIBLE-001 | Refresh License found no verified direct license to refresh. |
For other symptoms, see Troubleshooting.
What's next
Keep the background jobs healthy: Job queue monitoring.