Daily use
Exception handling
Work commission exceptions with owners and due times: failed or held source rows, suspense postings, unrecovered draws and the data quality rules behind them.
updated: applies-to: 1.1.2.0
Commission Exceptions is the Business Central page where Bitta Commission records problems that need a person: source rows that failed validation or are held for review, conflicting event keys, accounting postings that went to suspense, draw balances that were not recovered, and archive restores that do not match their manifest. Each exception has an owner, a due time and an action trail. This page shows you how to work the list, where exceptions come from, how data quality rules stop bad source rows, and how to report what still needs attention.
Before you start
- Open Commission Run Operations Setup and check the Exception SLA group. Error Exception SLA (Hours) (default 24) applies to exceptions with severity BLOCKING, CRITICAL, ERROR or HIGH. Warning Exception SLA (Hours) (default 72) applies to every other severity. A value of zero uses the default.
- The Commission Exceptions page is included in the Bitta Commission Processor, Accountant, Auditor, Setup Administrator and Support permission sets. See Permission sets.
Work the exception list
- Search for Commission Exceptions in Tell Me, or choose it in the Calculate and Review group of the Bitta Commission role center. The Open Exception Count tile opens it filtered to unresolved exceptions.
- Read the row. The list is read-only; you change an exception only through its actions.
| Field | What it shows |
|---|---|
| Status | Open, Acknowledged, In Progress, Waiting, Resolved, Closed or Ignored. |
| Severity Code | The operational severity, which selects the SLA. |
| Quality Code / Error Code | The source-quality classification and the technical error code. |
| Safe Summary | A summary that excludes protected source payload content. |
| Source Batch ID / Source Batch Line No. / Source Fact ID | The affected staging row, and the accepted source fact when there is one. |
| Occurrence Count | How often the condition occurred. A repeat raises the count instead of adding a row. |
| Owner User Security ID | The user responsible for the exception. |
| Resolution Due At / Overdue | The due time stamped from the SLA, and whether it has passed (shown in red). |
| Approval Required / Disposition Code | Whether a governed approval is required, and the latest disposition. |
The Source details group shows the linked staging row of the selected exception, such as Source Document No., Staging Status and Inclusion Status Code. Source Details Status says Available, Unavailable or Read permission required.
- Choose Show Overdue to see only unresolved exceptions past their due time. Show All removes that filter.
- Run the actions in order. Each one opens the Commission Exception Action dialog, where a Reason code is mandatory.
| Action | Available when Status is | Result |
|---|---|---|
| Acknowledge | Open | Acknowledged |
| Assign | Any unresolved status | Sets the Owner. You pick an enabled Business Central user. |
| Start | Acknowledged or Waiting | In Progress |
| Wait | In Progress | Waiting, for evidence or coordination |
| Resolve | Open, Acknowledged, In Progress or Waiting | Resolved. A Resolution code is also mandatory. |
| Close | Resolved | Closed |
| Ignore | Any unresolved status | Ignored, as an explicit governed decision |
| Reopen | Resolved or Ignored | Open again, with the resolution cleared |
- Fix the cause, for example correct the source data or add an account mapping. Then choose Resolve and Close.
Every action, creation and recurrence appends an entry to the exception's action history with the status change, the reason code and an evidence hash.
TIP
The No Open Exceptions step of the period close checklist counts exceptions that are Open, Acknowledged, In Progress or Waiting and belong to the period's runs or source facts. Clear them before you close. See Close a period.
Where exceptions come from
| Origin | Error Code | What to do |
|---|---|---|
| A source row fails validation | The row's validation error code | The row is quarantined on Commission Source Review. Correct the source data. |
| A source row is held for review | BAA-SRC-STATE (Quality Code SOURCE-HELD) | Choose Release and Accept or Exclude on Commission Source Review. |
| An event key exists with different source evidence | BAA-SRC-DUP-CONFLICT (Quality Code HASH-CONFLICT) | The row is rejected. Check both versions at the source. |
| An accounting proposal has no effective account mapping | BAACOMM-ACC-SUSPENSE-001 | Add the mapping, then create the suspense reclassification. |
| A draw balance was not recovered at period close | BAA-DRAW-RECOVERY-DEFERRED | Review the draw. Earnings stayed within the protected amount. |
| An archive restore does not match its manifest | BAA-OPS-RESTORE-MISMATCH | Check the archive and restore again. |
Source and archive restore exceptions get severity ERROR and the error SLA. Suspense and draw exceptions get severity WARNING and the warning SLA.
Suspense postings
When a posting proposal finds no effective account mapping for an earning, the amount is posted to the Suspense Account No. and Suspense Bal. Account No. of Commission Posting Setup, and a governed exception is raised for that suspense entry. If Suspense Account No. is blank, the proposal is blocked instead. After you add the mapping, open the posting proposal on Commission Accounting Proposal and choose Create suspense reclassification. It moves the suspense entries to their now-resolvable accounts and resolves the exception with resolution code RECLASSIFIED. See Commission accruals.
Data quality rules
Data quality rules check extended, imported and external source rows before they are accepted.
- Open Commission Source Capture Setup and turn on Quality Rules Enabled.
- Open Commission Data Quality Rules and add rules. Only rules with Status Active run.
| 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 of a Range rule. Values equal to a bound pass. |
| Reference | For a Referential rule, the master data the value must exist in: Customer, Vendor, Item, Salesperson, Resource, Project, G/L Account or Currency. |
| Outcome | Quarantined holds the row for review. Warning only records the failure. |
A Quarantined failure holds an included row with the reason code QUALITY- followed by the rule code; an excluded row stays excluded. Held rows wait on Commission Source Review for Release and Accept or Exclude. Every failure is recorded on Commission Quality Outcomes. See External sources.
Report open exceptions
Choose Exception Report in the Calculate and Review group of the role center to run the Commission Exception Report. It never changes data.
| Option | What it does |
|---|---|
| From Date / To Date | Limits large changes and failed exports to a date range. |
| Stale Hold Days | Reports open holds older than this many days. Default 30; zero skips the check. |
| Large Change Threshold | Reports earning entries at or above this absolute amount. Zero skips the check. |
| Include Resolved Queue Exceptions | Adds resolved, closed and ignored exceptions from the list. |
Besides the exception list, the report adds negative eligible-plus-payable positions, stale holds, large changes, blocked settlement lines, overdue disputes and failed exports, each with a severity, age, owner and recommended action code such as RETRY_EXPORT. See Commission reports.
What's next
Show sales reps what a deal is worth before they close it: Estimated commission.