Configure
Crediting and splits
How Bitta Commission decides who gets credit for a sale before commission is calculated: crediting rules, rate and deduction rules, credit splits, additive credit, caps and overrides.
updated: applies-to: 1.2.0.0
Crediting decides who receives credit for a sale before Bitta Commission calculates any commission. This page shows you how to refine the default credit with crediting rules, credit splits, additive credits and caps, how to test a rule against a captured sale, and how to review the result in Credit Explorer. Credit rules can also set a line's commission rate or reduce its commissionable base: see Customer agreements.
Before you start
- Rules, additive credits and caps are maintained with the Bitta Commission Crediting Configuration permissions, which are part of the Bitta Commission Plan Designer and Bitta Commission Setup Administrator permission sets. See Permission sets.
- Crediting rules belong to a plan component and change only while the plan version is Draft. See Commission plans.
- A component without crediting rules credits every captured line to the salesperson's mapped participant. A new component created on Edit Commission Component, by the setup wizard or by an industry template starts with standard exclusion rules, so it does not credit G/L account lines (such as freight and fees), item charges or fixed assets. The setup wizard uses your choices on its What doesn't count step, and templates that pay on fees keep G/L account lines. See Standard exclusions and customer agreements below.
Default crediting
For posted sales, the Salesperson Code captured on the source fact identifies who sold. Native sales credit uses that salesperson's participant mapping, independently of the user who posted the document, and linked returns keep the original invoice attribution. When a posted line has a Commission Salesperson Code, that salesperson is credited for the line instead of the document salesperson. See Participants and Capture posted sales.
NOTE
After an upgrade from Release 1.1, components that have no line-type exclusions are listed on Commission Season Readiness with the finding LINE_TYPE_EXCLUSIONS, and Commission Plans shows a notification. Until you decide, such a component keeps the Release 1.1 behaviour and does not credit G/L account, item charge and fixed asset lines. Choose Add Standard Exclusions to let the component's rules decide (the component must be in a Draft plan version), or Keep Crediting All Lines to credit every captured line; only a Bitta Commission Setup Administrator can choose the second. Plans are never changed automatically.
Set up crediting for a component
- Search for Component Crediting Rules and open it. Each component shows its Plan Version, Version Status and the number of Credit Rules, Additive Credits and Caps.
- Select a component of a Draft version and choose Crediting Setup. Component Crediting Setup opens. Set the two fields in the General group:
| Field | Option | What it does |
|---|---|---|
| Precedence | Priority | The lowest priority number wins, then the most specific rule. |
| Precedence | Most Specific | The highest specificity wins, then the lowest priority. |
| Unassigned Handling | Error | The run stops when the component matches a source but no participant resolves. |
| Unassigned Handling | Route to Unassigned | The credit is held on the unassigned credit worklist. |
A remaining tie between rules with different outcomes is blocked. Copy from Predecessor copies the credit rules, additive credits, caps and setup from the component with the same code in the predecessor plan version.
Credit rules
In the Credit Rules part, add a rule with a Code, Description, Priority, Outcome and Credit Type:
- Outcome:
- Include credits the source and Exclude keeps the component from crediting it. The winning Include or Exclude rule decides.
- Set Rate sets the commission rate of a credited line, with Rate %, Rate Basis and an optional Rate Attribute Code. The first matching Set Rate rule wins. Set Rate works on components with the Line Rate model. See Line rates and margin pools.
- Deduct From Base reduces the commissionable base of a credited line, with a Deduction % or a Deduction Attribute Code. Every matching deduction applies, together at most 100 percent.
- Credit Type: Revenue, Non-Revenue (shadow) or Quota-Only, written when an Include rule wins.
- Stop Processing: when the rule matches, rules with a higher priority number are not evaluated. It only stops later rules with the same purpose: inclusion, rate or deduction.
- Effective From, Effective Through and Status: only Active rules take part.
Choose Conditions to open Credit Rule Conditions. Each condition compares an Attribute, such as Document Type, Customer No., Customer Posting Group, Item No., Item Category Code, Location Code, Territory, Salesperson Code, Dimension Value, Net Amount or Custom Attribute, using an Operator such as Equals, In List, Between, Starts With, Greater Than, Blank or Within Territory. For lists, separate values with a vertical bar. The Specificity Score comes from the conditions: exact matches weigh more than lists, prefixes and ranges.
Release 1.2 adds:
- the attributes Bill-to Customer No., Bill-to Differs, Line Type, Line Account No., Order No., Reason Code, Return Reason Code, Source Code, Line Discount %, Inv. Discount Amount, Effective Discount %, Line Salesperson Code, Doc. Rate Override %, Ship-to Code, Ship-to Post Code and Ship-to Country/Region. See Capture posted sales;
- Line Margin %: the margin of the line, 100 x (net amount - cost) / net amount, on the net amount after line and invoice discounts and the cost known at capture. It is blank when the line has no cost or a zero cost, and a blank margin only matches Blank, Not Equals and Not In List, so a below-cost rule (for example Line Margin % Less Than 0) never fires on a line without cost;
- Source Journal Batch: the general journal batch a customer ledger entry without a posted sales document was posted from, for example a short-pay credit memo; blank for posted documents;
- the operators In Value List and Not In Value List, which compare with a named list on Commission Value Lists: put the list code in Value 1;
- a Value Name column that shows the name of the code you entered, such as the customer name, item description, dimension value name or the values of a list.
Standard exclusions and customer agreements
Two actions on Credit Rules maintain rules for you. The rules they generate are shown on the page but cannot be edited there.
- Add Standard Exclusions: choose the lines this component should not credit, such as G/L account lines, item charges, fixed assets, resources or specific freight and fee accounts. Each choice becomes an Exclude rule; run it again to change or remove them.
- Customer Agreements: set a rate and a base deduction per bill-to customer, for sales billed to that customer on behalf of a different sell-to customer.
See Customer agreements for both, for named value lists, and for worked examples of Set Rate and Deduct From Base.
NOTE
If a component has Exclude rules and its own Include rules, its Include rules work as an allow list: a line that matches no Include rule is not credited, even when no Exclude rule matches it. Add an Include rule without conditions if every line that is not excluded should be credited. The app shows a notification when this applies.
Credit types matter for measures. Without a scope, a measure counts Revenue and Quota-Only credit and ignores Non-Revenue credit. Change this per measure on Measure Credit Scopes.
Additive credits and caps
The Roll-up, Team, Overlay and Manager Credit part gives extra credit without reducing the primary credit. Each line has a Kind (Rollup, Team, Overlay or Manager), a Credit Percent and a Base. Overlay lines find specialists by the resolved territory, or by item category or item for a named specialist. See Manager overrides.
The Credit Caps part limits the credit a participant can receive from the component in one credit period. Leave Participant No. blank to cap every participant without a specific cap. Only Active caps limit credit.
Test credit rules
On Component Crediting Setup, choose Test Source Fact. In Test Credit Rules, enter the Source Fact Entry No. of a captured sale. The Result field shows whether the component credits it, which rule wins and why. The test only reads data.
To see the rate waterfall and the deductions of a single line, use Why This Rate?: on Commission Line Estimates for an open quote or order, and on the Commission Earning card, the Commission Earnings list or the Commission FactBox of a posted sales invoice or credit memo for a posted earning. See Why this rate?.
Share a sale with credit splits
- Search for Commission Credit Splits, or choose Credit Splits on the plan version card. Add a rule with the Salesperson Code, the Partner Participant No., an optional Plan Code (blank applies to every plan that credits the salesperson), the Split Percent, the dates and a Description, and set Status to Active.
Each partner receives its percent and the salesperson keeps the remainder. The split percent must be greater than 0 and less than 100, active partner shares for one salesperson must total less than 100 percent, and every credited participant needs an active 100 percent assignment in the plan version. Only Active rules apply; Draft and Retired rules are ignored. Returns reverse the original split automatically.
NOTE
An Active split rule keeps its salesperson, partner, plan, percent and start date, and it cannot be deleted. Set an end date or retire it, then create a new rule.
Override and unassigned credit
- Credit Overrides gives the primary credit of one source fact to another participant. On Credit Override, enter the source fact, plan version, optional component, From Participant No., To Participant No., Reason and Evidence Reference, and choose Submit for Approval. Another user approves it. The requester cannot approve their own override unless they are an administrator and the override does not affect their own commission (see Approval policies). If the source was already credited, approving the override queues a correction, so the approver also needs the Bitta Commission Recalculation Approver permission set; the override then takes effect through the correction or recovery run.
- Unassigned Credits holds credit that matched a component but resolved no participant, credit above a cap, and proportional return reversals. Assign raises a credit override for approval, Release releases the credit so it is never paid, and Audit shows the audit rows.
Review crediting results
Search for Credit Explorer. It lists every credit entry with its Credit Strategy Code (blank for primary credit, or ROLLUP, TEAM, OVERLAY or MANAGER), Credit Type, the From Participant No. whose credit produced an additive credit, the Split Percent, the Credit Amount, Cap Applied and whether an override chose the recipient. Rule Traces shows the recorded decisions: CLASSIFY, OVERRIDE, ADDITIVE, ADDITIVE-SKIPPED, CAP and UNASSIGNED.
To explain a single earning end to end, see Explain any earning. The Commission reports lists where these pages appear.
What's next
Decide when earned commission can be paid: Eligibility rules.