Exceptions and data quality

Commission problems should surface as work items, not as silent gaps. Bitta Commission records failed source rows, calculation problems, unmapped postings and similar issues as governed exceptions with an owner, a due time and an action trail. Data quality rules stop bad rows before they become source facts, anomaly rules flag unusual results, and the integrity sweep checks that stored ledgers still match their hashes.

Before you start

• Decide who owns exceptions in your team. Every exception can be assigned to an enabled Business Central user.
• Set the exception SLA on Commission Run Operations Setup: Error Exception SLA (Hours) for blocking, critical, error and high severity exceptions, and Warning Exception SLA (Hours) for the rest. See Calculation runs and schedules.

Commission Exceptions

Open Commission Exceptions (also available from the Bitta Commission role center). Each row shows:

Field	What it shows
Status	Open, Acknowledged, In Progress, Waiting, Resolved, Closed or Ignored.
Severity Code / Quality Code / Error Code	The severity, the source-quality classification and the stable technical code.
Safe Summary	A description that excludes protected source data.
Source Batch ID / Source Batch Line No. / Source Fact ID	The affected source row or fact.
Occurrence Count	How many times the same condition occurred for this row. The app does not create duplicates.
Owner User Security ID	Who is responsible.
Resolution Due At / Overdue	The SLA due time and whether it has passed.
Approval Required / Disposition Code	Whether a governed approval is needed, and the latest disposition.

The Source details group shows the linked staging row: document number, entry number, staging status and inclusion decision, when you have permission to read it.

Work an exception

1. Choose Acknowledge to record that you have seen it.
2. Choose Assign and select the Owner.
3. Choose Start when you begin investigating, or Wait if you are waiting for evidence or someone else.
4. Fix the cause, for example correct the source data, add a missing account mapping or link the salesperson to a participant.
5. Choose Resolve and enter a Resolution code and Reason code. Then Close it.

If the exception does not need action, choose Ignore and give a reason. Reopen brings back a resolved or ignored exception. Every action appends evidence on Commission Exception Action. Use Show Overdue to focus on items past their due time.

Where exceptions come from

Typical sources include native capture that could not complete (for example a missing ledger entry or a foreign document without a currency factor), rows quarantined by data quality rules, calculation runs that completed with exceptions, and accounting proposals that posted to suspense because no account mapping applied. The Error Code tells you which.

Data quality rules

Data quality rules check staged source rows before they are accepted.

1. Open Commission Source Capture Setup and turn on Quality Rules Enabled.
2. Open Commission Data Quality Rules and add rules:

Field	What it does
Source System Code / Source Fact Type Code	The rows the rule applies to. Blank means every system or fact type.
Rule Type	Required Field, Required Attribute, Range or Referential.
Staging Field No. / Attribute Code	The staging field or typed attribute the rule reads.
Minimum Value / Maximum Value	The accepted range for a Range rule. Values exactly at the bounds pass.
Reference	The master data the value must exist in for a Referential rule, for example a customer or currency.
Outcome	Quarantined holds the row. Warning records the failure but accepts the row.
Status	Only Active rules run.

Quarantined rows wait on Commission Source Review with the reason QUALITY- followed by the rule code, where you can release or exclude them. See Imports, G/L rules, and recurring contracts. A quality failure never overrides a row that was already excluded.

Commission Quality Outcomes is the read-only, hashed record of every failed evaluation: when, which rule, the outcome, a safe summary without source values, and the batch and line.

Anomaly rules

Anomaly detection is part of the Simulation and forecasting module (SIMULATION). It looks for unusual results in calculated earnings and raises alerts for review. It never changes earnings.

1. Open Anomaly Rules and choose Add Default Rules to add the standard rules with their default thresholds.
2. Adjust each rule: the Detector Code (OUTLIER-AMOUNT, DUPLICATE-SOURCE, NEGATIVE-BALANCE, UNUSUAL-RATE, UNEXPECTED-ZERO, MISSING-CREDIT or ABRUPT-CHANGE), Threshold Factor, Minimum Amount, Minimum History Count, Lookback Days, Severity Code and default owner. Turn on Enabled.
3. Open Commission Anomalies and choose Run Detection. Every enabled rule runs over the last 30 days. Existing alerts are never duplicated. The job queue entry "Bitta Commission anomaly scan", created on hold by Register Scanner Jobs, can run it on a schedule.

Each alert shows the observed and expected values, the accepted range, an Explanation and the detector's Proposed Disposition Code. Choose Acknowledge, Dismiss as False Positive or Apply Proposed Disposition. The evidence of the alert is kept in every case. Open Earning goes to the earning concerned.

Integrity sweep

The integrity sweep samples recent entries in every commission ledger (source facts, credits, attainments, earnings, tiers, eligibility, balances, settlements, accounting, audit and aging) and checks that each stored hash still reproduces. It is read-only.

1. Open Commission Business Continuity.
2. Set Sweep Sample Size (how many recent entries per ledger to verify).
3. Choose Run Integrity Sweep.

The result is logged on Commission Integrity Sweep Log with the sampled count, mismatch count and a detail hash. Choose Ledger Results to see Commission Integrity Sweep Results per ledger, including the most recent entry that failed verification.

Related pages

• Imports, G/L rules, and recurring contracts
• Troubleshooting
• Audit and security