Multi-company and copying configuration

Many Business Central customers run more than one company. Bitta Commission keeps each company's commission data separate, and gives you three tools to work across them: Commission Company Readiness to compare companies, Copy Configuration to Company to reuse calendars and draft plans, and Commission Multi-Company Consolidation to report earnings across companies. Commission Migration Setup records how a company moves from a legacy commission process.

Calendars, periods and Draft plans can be copied to another company.

Before you start

• Commission data is per company. Plans, participants, earnings, settlements and statements never move between companies on their own.
• Each production company needs its own license activation. The license is bound to the environment and company, and your subscription sets a Company Limit. See License lifecycle.
• Copying configuration requires the Bitta Commission Setup Administrator permission set in the current company and in the target company.
• Consolidation reads only the companies your user can read.

Compare companies

1. Open Commission Company Readiness.
2. Review one row per company:

Field	What it shows
Company name, current company	Which company the row describes.
Readable	Whether your permissions allow reading commission setup there.
Country/Region	From Company Information, used to resolve the country policy.
Setup exists, implementation path, setup state and stage	How far guided setup has progressed.
Entitlement state and expiry	The cached license state of the company.
Last calculation run and its status	When the company last calculated commission.
Data schema version, app version	The commission data version recorded by the last install or upgrade.
Active participants, Draft plan versions	Counts that help you plan the copy.

1. Choose Refresh to read the facts again.

Copy configuration to another company

The copy reuses calendars, periods and Draft plans so a new company does not start from scratch.

1. In the source company, open Commission Company Readiness.
2. Choose Copy Configuration to Company.
3. On Copy Configuration to Company, fill in:

Field	What it does
Target Company	The company that receives the configuration. It must differ from the current company.
Include Calendars and Periods	Copies commission calendars and their periods through the setup services of the target company.
Include Draft Plans	Exports each Draft plan version as a plan package and imports it as a new Draft plan in the target company.

1. Choose OK. The copy runs in a background session in the target company.
2. Choose Copy Requests to follow it. Commission Company Copy Requests shows the status (Requested, Running, Completed or Failed), the number of lines, and how many items were copied, skipped or failed.
3. Choose Lines to see each calendar, period or plan with its Result Code, the Package Hash of a copied plan and the record created in the target company.

Existing records are skipped with the result BAA-COPY-EXISTS, so running the copy again is safe. Nothing is published or activated in the target company. After the copy, complete the target company's setup, participants and assignments, then validate, approve and publish its plans there.

If a copy fails

Result	What to do
BAA-COPY-INPUT-001	Only a Setup Administrator can copy configuration.
BAA-COPY-INPUT-002, BAA-COPY-INPUT-003	Choose an existing target company other than the current one.
BAA-COPY-INPUT-004	Select calendars, Draft plans or both.
BAA-COPY-LINE-002	The target company refused the item. Assign BAA Comm Setup Admin to the user in the target company and run the copy again.
BAA-COPY-PARTIAL	Some lines failed. Open Lines, fix the cause and run the copy again; existing items are skipped.
BAA-COPY-SESSION-001	The background session could not start. Try again later.

A plan line that fails with a BAA-PKG code could not be imported as a package. BAA-PKG-DEPENDENCY means a definition the plan requires is missing in the target company or does not match exactly. Review the failed line, align the target company's configuration with the source, and copy again.

Report across companies

Open Commission Multi-Company Consolidation, set From Date and To Date (or choose This Year or Previous Year) and choose Recalculate. The page lists earnings and the net movement into the Eligible, Payable, Held and Settled buckets per company and month, plus a company total. Each company stays in its own local currency; amounts are not converted. Every build writes export evidence. See Role centers and reports.

Record a migration from a legacy process

Commission Migration Setup records how a company takes over commission from a legacy system or spreadsheet.

Field	What it does
Migration Mode	Fresh starts commission history at the opening date. Parallel Run compares results with the legacy system until the parallel run through date. Cutover requires reconciled legacy control totals and a sign-off before the cutover date.
Opening Date	The first date on which Bitta Commission is the system of record. Fresh and Parallel Run need an open commission period that covers it.
Parallel Run Through Date, Cutover Date	The end of the parallel window, and the date after which the legacy system is read-only.
Legacy System Reference	The legacy system or spreadsheet used for reconciliation. Do not enter secrets.
Control Total Amount, Control Total Count	The legacy control totals in company currency.

1. Choose Check Prerequisites to run the checks for the selected mode and see every open finding.
2. For a cutover, choose Record Reconciliation to record the control totals with a sign-off reference. The app stores an evidence hash over the totals, reference, sign-off, user and time.

The last check result appears in Last Check Result Code and in the support diagnostics. To bring legacy participants, plans, rates, quotas and opening balances in, use the Excel import. See Import setup from Excel.

Related pages

• Implementation paths and templates
• Role centers and reports
• License lifecycle
• Calendars and periods