Known limitations

This page lists what Release 1.1 of Bitta Commission does not do, or does differently from what you might expect. Read it before you plan an implementation, and check it again when a new release is announced.

Settlement and payment

No live payroll integration. Payroll output is a payroll-ready export file with an acknowledgement step. The app does not connect to a payroll provider and is not a payroll or tax engine. Your payroll owner decides how the file is used. See Payroll export.
Pay groups settle in local currency. A pay group cannot have its own default currency in this release (BAA-PAYGROUP-CURRENCY). Participant payment currencies are handled by the Multi-currency module. See Multi-currency.
Generic export has no acknowledgement import. Acknowledgement and resend apply to payroll-ready exports only. Payments for Generic Export lines are recorded on the settlement lines with Record payment. See Settlements and pay groups.

Statements and approvals

Statements are delivered inside Business Central. Make available in Business Central records that the participant can read the statement in the client. The app does not email statements or publish them to an external portal. See Participant and manager statements.
Statements always need an approval policy. A statement cannot be delivered until an effective Statement approval policy has an approver who is not the submitter.
Dispute notes are hashed. The review note entered when a dispute is submitted is stored only as a hash. Use the Comments FactBox for text reviewers must read. See Disputes and holds.
Participant acceptance needs the Disputes module. Accept statement is available only when the Disputes module is on.

AI and simulation

No external AI provider. The only AI provider in Release 1.1 is a deterministic template that runs inside Business Central. It drafts and explains. It never changes plans, approves, posts or pays. See AI plan design assistant.
The design assistant does not create plans. A plan designer enters the drafted component and rates by hand.
Replay covers most models, not all. Scenario replay simulates flat, per unit, tiered and formula components and other previewable models. Components with other models are reported with BAA-SIM-MODEL, and period-close components are shown as calculated at close. See What-if and scenarios.
The forecast uses fixed rules. It projects from the trailing three periods, the open sales pipeline and current balances over a six-period horizon, with fixed probabilities per document type. You cannot change the horizon or the probabilities in this release.

Reporting and data

Consolidation does not convert currencies. Commission Multi-Company Consolidation shows each company in its own local currency. See Multi-company and copying configuration.
Company copy covers configuration only. Calendars, periods and Draft plans can be copied. Participants, transactions and ledgers cannot.
APIs are read-only. The commission API pages publish data for reporting. They do not accept writes.
Limited telemetry. The app emits one telemetry event for batch calculation runs. Other monitoring uses the run log, the operations tiles and support diagnostics. See Job queues, monitoring, and diagnostics.

Compliance

Bitta Commission records and applies the rules you configure, for example country policies, deferral policies and recovery limits. It does not provide payroll, tax, wage-law or accounting-standard advice. Your finance, payroll and legal owners decide policy.

Availability

The app targets Business Central 28 (runtime 17) and later.
An AppSource listing is pending. Contact Bitta Apps for access. See Pricing.