Advanced
AI plan assistant
Draft commission plan components from plain language with the in-app assistant, which runs inside Business Central with consents, labeled drafts and audits.
updated: applies-to: 1.2.0.0
Bitta Commission includes a governed assistant that turns a plain-language description into a draft plan component, plus two related assistants: Explain this earning on the earning card and Ask about this dispute on the dispute card. Every answer is a labeled draft for a person to review. The assistants cannot create, change, approve, post or pay anything, and every call is audited.
NOTE
The only provider is Deterministic Template (no external service). It builds drafts from fixed templates inside Business Central and does not contact an outside AI service. The call audit records this as External Service Used cleared.
Before you start
- All three assistants belong to the AI plan drafting module. Switch it on in Commission Feature Management. While it is off, Generate Draft is unavailable, the earning and dispute assistant actions are hidden, and every call is refused with BAA-FEATURE-OFF, whatever Commission AI Setup and the consents say. Drafts are never activated automatically. See Optional modules.
- Commission AI Setup, Commission AI Consents and Commission AI Call Audit open only for a user with the Bitta Commission Setup Administrator permission set. Other users get BAA-ORG-SETUP-AUTH. Only that user can prepare, accept, renew and withdraw consents.
- Generating a plan draft requires the Setup Administrator permission set or a Finance (all participants) user scope (otherwise BAA-SIM-SCOPE). Earning explanations and dispute answers require scope to the participant concerned (BAA-AI-SCOPE).
Set up the assistant
- Search for Commission AI Setup and open it. In the Provider group, review the settings:
| Field | What it does |
|---|---|
| Provider | The provider implementation: Deterministic Template (no external service). |
| Processing Region | The processing region recorded on consents. |
| Data Region | Recorded on consents. Calls stop when the configured data region differs from the consented one. |
| Model Family | Recorded on consents. Calls stop when it differs from the consented one. Blank means the provider code. |
| Consent Review Months | How many months after acceptance a consent must be reviewed. Zero means 12. |
| External Endpoint Configured, Data Movement Disclosure Acknowledged | Apply only to a provider that calls an external service. The Deterministic Template provider does not, so you leave them cleared. |
| Maximum Prompt Length | The maximum length of a prompt after redaction. A new setup uses 4,000 characters; the minimum is 200. |
- In Capabilities, switch on what you want: Earning Explanations Enabled, Plan Design Assistant Enabled and Dispute Inquiry Assistant Enabled.
- Choose Prepare Consent Requests. The app creates a consent in Administrator Approval Pending status for each capability that has no draft, pending or active consent, and opens Commission AI Consents.
- Review each consent and choose Accept Consent. Its status becomes Active, and the app records who accepted it, when, and the review date.
Each capability needs the module, its switch in Commission AI Setup and an Active consent for EXPLAIN-EARNING, DESIGN-ASSISTANT or DISPUTE-INQUIRY. Otherwise the call stops with BAA-FEATURE-OFF, BAA-AI-DISABLED or BAA-AI-CONSENT.
Consents
A consent is recorded per company and per capability. It fixes what the capability may send and how its output is handled.
| Field | What it records |
|---|---|
| Status | Only Active permits calls. Other states are Draft, Administrator Approval Pending, User Consent Pending, Withdrawn, Expired, Suspended and Rejected. |
| Provider Resource Mode Code, Model Family, Processing Region Code, Data Region Code | What the consent was granted for. |
| Allowed Data Categories | For plan design and explanations: plan, component and period codes, amounts, rates, precision, dates and eligibility trigger. For dispute inquiry: dispute status, category, priority, scope and resolution codes, dispute dates, statement status, period codes, component and measure labels, amounts and rates. |
| Prohibited Data Categories | For plan design and explanations: participant names, customer identifiers, document numbers, salesperson codes, free-text comments, disputes and attachments. For dispute inquiry: participant names, participant and customer identifiers, dispute and document numbers, salesperson codes, free-text comments and attachments. |
| Human Review Required | Output is a draft that needs human review. |
| Review At, Review Overdue | When the consent must be reviewed, and whether an Active consent is past that date. |
| Policy Hash | The hash of the field allowlist consented to. |
- Renew Consent creates a pending successor for the current provider, model family and data region. Accepting it expires the earlier version, so one consent stays Active.
- Withdraw Consent stops calls for the capability immediately.
- If you change the provider, model family or data region, calls stop with BAA-AI-CONSENT-PROVIDER, BAA-AI-CONSENT-MODEL or BAA-AI-CONSENT-REGION until you renew the consent.
Draft a plan component
- Search for Commission Plan Design Assistant and open it.
- In Plain-language description, describe the behavior, for example "pay 3% up to 50000 and 5% above".
- Choose Generate Draft.
- Read Draft (AI-generated, review required). It proposes a model, rate table rows with band bounds and percents, the validation to apply and a boundary test for each threshold, and it ends with the audit reference and the number of redactions.
Nothing is created. A plan designer enters the component and rate table in the plan editor, validates the version, and routes it through approval and publication as usual. See Commission plans.
TIP
Treat the draft as a starting point. Check it against your written plan document before you enter anything.
Explain an earning and ask about a dispute
- On the Commission Earning card, the Explain This Earning FactBox shows a Status line that tells you whether explanations are enabled and consented. Choose Explain this earning to open the draft in AI Draft. It describes the model, plan version, component and period, how the credited base and cumulative entitlement moved, the rounding and the eligibility trigger. Draft Explanation keeps the latest draft for your session only. For the full calculation record, see Explain any earning. To see which credit rules decided the rate, choose Why This Rate? on the same card; it reads the recorded calculation evidence and is not part of the assistant. See Why this rate?.
- On the Commission Dispute card, Ask about this dispute offers three questions: where the dispute stands, what amounts are under review, or what happens next. After you read the draft, you can add it as a comment; the dispute itself is not changed. Prepare inquiry consent creates the consent for a setup administrator to accept. See Commission disputes.
What happens on every call
- The app checks the AI plan drafting module, the capability switch and the Active consent, and that the consent covers the configured provider, model family and data region.
- It builds the prompt only from the allowlisted fields of the capability.
- It replaces participant names and numbers, other identifiers and email addresses with [REDACTED], and refuses a prompt longer than Maximum Prompt Length (BAA-AI-PROMPT).
- It calls the provider and labels the result: "DRAFT, AI-generated. Review before use. This text cannot change, approve, post or pay anything."
- It appends a row to Commission AI Call Audit. On Commission AI Setup, choose Call Audit to open it.
The call audit is append-only. Each row shows when the call was made, the capability, the provider, the outcome, External Service Used, the target, the user, the consent, the redaction count, the prompt and response lengths, and hashes of the allowlist, prompt and response. The prompt and response text are not stored. For how this evidence fits the wider audit trail, see Audit and security and Known limitations.
What's next
Run more than one company: Multi-company setup.