Known limitations

This page lists what Bitta Commission does not do, or does differently from what you might expect. Read it before you plan an implementation. Each item links to the guide page that covers the related feature.

Payroll, tax and payment

• Not a payroll or tax engine. Bitta Commission calculates commission and produces payroll-ready output. It does not calculate payroll, withholding or tax. Your payroll owner decides how the output is used. See Payroll-ready export.
• No live payroll connector. Payroll output is a file. Download export file downloads the payroll-ready CSV of a payroll batch. Payroll results come back through Import payroll acknowledgement, which applies a payroll JSON response after validating every line and total. The app does not connect to a payroll provider.
• Generic export has no acknowledgement import. Acknowledgement, resend and the consolidated payee view apply to payroll batches only. Payments for Generic Export lines are recorded on the settlement lines with Record payment. See Settle commission.
• Pay groups settle in local currency. A pay group cannot have its own default currency (BAA-PAYGROUP-CURRENCY). Settlement in participant currencies is part of the Multi-currency module. See Multi-currency.

Statements and plan documents

• Statements are delivered inside Business Central only. Make available in Business Central records that the participant can read the statement in the client. It does not send email or publish to an external portal. See Earnings statements.
• Accept statement needs the Disputes module. The Accept statement and Submit dispute actions on a statement are visible only while the Disputes module is on. See Commission disputes.
• Plan document channels are recorded, not transmitted. Distribute Plan Documents asks for a channel: Business Central, Email, Portal, E-signature or API. For every channel, the app records a delivery entry with that channel code. It does not send an email, publish to a portal, start an e-signature envelope or call an external system. Participants open the document with View Plan Document on My Plan Acceptance and respond there with Acknowledge, Accept, Reject or Comment. For an E-signature delivery, Accept requires a Signature Provider and Signature Reference that come from your own e-signature process. See Plan acceptance.

AI and forecasting

• No external AI provider. The only provider on Commission AI Setup is Deterministic Template (no external service). It runs inside Business Central and does not call an external AI service. See AI plan assistant.
• Forecasts use fixed inputs. Refresh Forecast builds a new forecast version from the trailing three periods of earnings, the open pipeline and current balance positions over a six-period horizon. The page has no field to change those two numbers. Forecasts are arithmetic projections, not earned amounts. See Payout forecast.
• Scenario replay does not cover every model. A component whose model the arithmetic replay cannot simulate is reported with BAA-SIM-MODEL. See What-if scenarios.

Multi-company

• Consolidation does not convert currencies. Commission Multi-Company Consolidation totals each company in its own local currency. Amounts are not converted across companies. See Multi-company setup.
• Company copy covers configuration only. Copy Configuration to Company copies calendars and periods and Draft plans. Existing records in the target company are skipped, and nothing is published or activated. Participants, source transactions and ledgers are not copied.

APIs and extensibility

• The APIs are read-only except one staging endpoint. The twelve reporting API pages (publisher bittaApps, group commission, version v1.0) do not allow insert, modify or delete. The exception is commissionSourceEvents (page 73570871), which accepts inserts only, to stage external transactions as commission sources. See API reference.
• Three subscribable events. Other extensions can subscribe to OnPlanVersionPublishedV1, OnImplementationAppliedV1 and OnSetupReadinessEvaluatedV1. All other events and interfaces are internal to the app. See API reference.
• Limited telemetry. The app sends one telemetry signal, BAACOMM-RUN-0001, when a commission batch run invocation finishes. Other monitoring uses the run log, the Role Center tiles and support diagnostics. See Job queue monitoring.

Compliance

Bitta Commission records and applies the rules you configure, such as country policies, accounting policies and recovery policies. Commission Cost Disclosure (ASC 340-40 / IFRS 15) is read-only, and your company and its accountants own the accounting conclusions. The app does not give payroll, tax, wage-law or accounting-standard advice.

Availability

• Bitta Commission is supported on Business Central online 28.0 or later and has no dependencies on other extensions. See Install and upgrade.
• To start, request a 30-day trial code; Bitta Apps supplies the extension package. See Pricing and trial.

Tell us what you need

Customer feedback sets the priorities for what Bitta Commission does next. Request a 30-day trial code or contact Bitta Apps through the same form to tell us which of these limits matter to you, or what else you need.

Related pages

• Release notes
• Troubleshooting