Bitta Commission guide
License lifecycle
License states, participant and company capacity, refreshing and restoring a license, and exactly what a missing or lapsed license blocks and what keeps working.
status: verified applies-to: 1.1.2.0rev: 1
Bitta Commission checks a verified license before it produces new commission, settlement or accounting output. This page explains the license states, the capacity limits, how to keep a license current, and exactly what stops and what keeps working when a license lapses. To activate a license for the first time, see Activate a license.
Before you start
- License actions on Bitta Commission Setup require the Bitta Commission Setup Administrator permission set. Other users can see the license fields but not change them.
- Each company is licensed on its own. A license is bound to the product, the Business Central environment and the company, and the app verifies its signature before it accepts it.
- The subscription is priced per active salesperson and includes every module. See Pricing. For renewals and more salespeople, contact Bitta Apps.
Read the license status
Open Bitta Commission Setup and look at the License group:
| Field | What it shows |
|---|---|
| State | The verified license state (see below). |
| Valid Through | When the current verified license ends. |
| Payee Limit | The maximum number of active participants. |
| Company Limit | The maximum number of companies the subscription covers. |
| Diagnostic | A safe diagnostic code. It never shows license identifiers or the activation code. |
Set Up Bitta Commission also shows the state, expiry date, days remaining and payee limit on its first step, and Commission Company Readiness shows the cached license state of every company.
License states
| State | New output | New active participants |
|---|---|---|
| Uninitialized | Refused. No verified license exists in the company. | Refused |
| Trial | Allowed | Up to 5 active participants, even if the license shows a higher limit |
| Active | Allowed | Up to the Payee Limit |
| Grace | Allowed | Refused. You can keep working with the participants you have. |
| Suspended, Expired, Revoked | Refused | Refused |
"New output" means calculating positive commission, creating settlement output (settlements, payroll-ready exports, AP exports) and creating accounting output (posting proposals and posting).
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 setup wizard, is refused with BAA-LICENSE-CAPACITY when the count would exceed the limit.
- Output checks capacity too. The app counts active participants again each time it produces output. If the company has more active participants than the license allows, for example after a trial ends at a lower limit, calculation, settlement and posting are refused with BAA-LICENSE-CAPACITY until you deactivate participants you no longer pay or obtain a higher limit.
- Companies. A subscription license is accepted in a new 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
| Action on Bitta Commission Setup | When to use it |
|---|---|
| Refresh License | Updates a license that was already verified through direct activation. |
| Import Offline License | Imports a signed offline license file from Bitta Apps. The raw file is not stored. |
| Deactivate License | Deactivates the direct license and removes its refresh job, for example before you move to another environment. |
| Reconcile License Restore | Records an audited reconciliation when a verified license is pending review after an environment restore. |
| Recover Direct License History, Export History Recovery Request, Import History Attestation | Used with the Bitta Apps license administrator to recover license history. Recovered history never authorizes operations on its own. |
After a direct activation, the app creates the job queue entry "Refresh Bitta Commission license", which runs daily. A renewal from Bitta Apps is picked up by that refresh or by Refresh License. If a refresh fails, the message says whether the license service timed out, rejected the request, reported a conflict or was unavailable, with a reference code. Wait and try again, or send the reference code (never the activation code) to Bitta Apps.
What a lapsed license does not block
The license controls new commercial output. It does not lock you out of your data:
- Existing commission records stay in the company, and you can still open them and run reports on them.
- Linked corrections that reduce an amount already produced, such as a return against an earlier earning, are still allowed, so clawbacks and returns can be processed after a lapse.
- Standard Business Central posting outside Bitta Commission is not affected.
Error codes
| Code | Meaning |
|---|---|
| BAA-LICENSE-AUTHORITY | No verified current license was 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 was run outside the exact current company context. |
| BAA-LICENSE-RESTORE | A restore reconciliation needs verified current evidence. |
How it works behind the scenes
- The app accepts a license only after verifying its signature and its binding to the product, tenant, environment and company.
- It rechecks the license immediately before each output-producing action, not only at sign-in.
- Activation codes are converted to a secret value immediately and never stored. Raw license files and payloads are not kept.