Known limitations

This page lists what Bitta Commission does not do, or does differently from what you might expect. It applies to Release 1.2 (version 1.2.0.0). 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 or by e-mail. Make available in Business Central records that the participant can read the statement in the client. Send by E-Mail places a PDF in the Business Central e-mail outbox; it is sent from there, not instantly, and it needs an e-mail account for the Commission Statement scenario. Only approved or already delivered statements are e-mailed. There is no external statement portal. See Email statements.
• Word layouts are not the default. The statement and remittance advice Word layouts (Letter and A4) must be selected in Report Layouts. The remittance advice is attached to a statement e-mail only when you send from the Commission Settlement card with Attach Remittance Advice turned on.
• 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.

Rules and calculation

• Set Rate needs the Line Rate model. Set Rate credit rules price lines only on Line Rate components. Plan validation reports a Set Rate rule on any other model. Deduct From Base works on every model. See Line rates and margin pools.
• Line Rate cannot carry modifiers. Hurdles, caps, floors, weights, gates, pairs, accelerators and end-dating are refused on a Line Rate component.
• Line estimates price Line Rate components only. Other components are listed on Commission Line Estimates with a note that they are priced on the cumulative period base. See Estimated commission.
• Standard exclusions are added only on the main creation paths. Components created on the component editor, by the setup wizard (as you choose on What doesn't count) or by a template get them. Components created by import or API do not. Components from Release 1.1 are listed for review in Commission Season Readiness instead. See Crediting and splits.
• The order release block is not built in. The estimate flags missing costs and missing rates, but Bitta Commission does not stop an order from being released. A companion app can use the estimate API to do that. See Developer events.
• Quota pacing is a straight line. Expected to date is the elapsed share of the quota period. Seasonal pacing curves are not available. See Quotas and targets.

Payments and eligibility

• Late-payment reductions are not shown on the aging page. An aging rule with the Reduce action lowers pending commission, but Commission Aging has no column for the reduction amount. See Eligibility rules.
• Customer Ledger Application netting needs payment-based eligibility. Plan validation refuses this netting basis unless the plan's eligibility is On Payment or On Full Payment. See Credit memo netting.

Accounting and administration

• Scheduled accrual is local currency only. Earnings in another participant currency stay on the at-settlement path, and an accrual needs an accounting policy with the Expense When Earned recognition mode. See Commission accruals.
• Agent remittance groups by payee. Commission Agent Remittance groups lines by payee participant and shows the payee's vendor. It does not combine several payees that share one vendor.
• Replacing the salesperson on customers needs Apply immediately. A transition saved as a draft and applied later does not change the customer cards. See Sales hierarchies.

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 and the six Power BI API queries (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.
• No packaged Power BI template. Release 1.2 publishes the API queries a report needs, not a ready-made report. The attainment query has no attainment percentage column; divide the accumulated value by the target value in your report. See Power BI.
• Only the documented events can be subscribed. Other extensions can subscribe to the public events listed on Developer events. All other events and interfaces are internal to the app.
• 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.
• Bitta Commission 1.2.0.0 is the current version on Microsoft AppSource. To start, request a 30-day trial code. 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
• Roadmap
• Troubleshooting