Chapter 4 of 8Page 17 of 22

Configure

Eligibility rules

Decide when earned commission can be paid: on posting, when the customer pays, after hold days or when a hold is released, plus payment discounts, unapplied payments, aging for overdue invoices and holds.

updated: applies-to: 1.2.0.0

Bitta Commission separates earning commission from being allowed to pay it. The Commission Eligibility Policies page lists the versioned policies that decide when a calculated earning moves from pending to eligible, which is what settlement picks up. This page explains each column on that page, how to create a policy with New Eligibility Policy, how pending amounts are released, and how aging rules and eligibility holds add control for overdue invoices and open cases.

Before you start

  • Creating a policy requires the Bitta Commission Setup Administrator permission set. See Permission sets.
  • Anything other than On Posting, 100 percent and zero hold days belongs to the Cash-based eligibility and holds module. Switch it on in Commission Feature Management. See Optional modules.
  • The setup wizard's When it's earned step creates an eligibility policy for you: When the sale is posted, When the invoice is posted, When the customer pays or When the invoice is fully paid, with an optional Wait this many days first. Finish attaches the policy to the plan's components and switches on the Cash-based eligibility and holds module when your choice needs it. See Run the guided setup.

What the policies page shows

  1. Search for Commission Eligibility Policies and open it. The page is read-only and lists every policy version.
Commission Eligibility Policies list with code, version, eligibility trigger, eligible percent, hold days, effective dates and status
Step 1: the eligibility policies of the company.
Column What it shows
Code, Description, Version No. The policy and its version.
Eligibility Trigger The event that makes earned commission eligible.
Eligible Percent The percentage of earned commission that becomes eligible.
Hold Days The days before earned commission becomes eligible.
Payment Discount Treatment For On Payment and On Full Payment policies: what a payment discount the customer took does to the commission.
Unapplication Behavior For On Payment and On Full Payment policies: what happens when a payment or credit memo is unapplied after commission was released.
Allow Negative Eligibility Whether linked negative eligibility movements are allowed.
Effective From, Effective To The dates the policy version covers.
Status Draft, active or retired.

The core calculation uses On Posting, 100 percent eligibility and zero hold days. When you switch on the Cash-based eligibility and holds module, Bitta Commission adds a CASH-COLLECTED policy ("On Payment, 100% of collected cash") if it does not exist yet. A policy the setup wizard created for When the invoice is posted shows the trigger On Invoice: commission on an invoice becomes eligible once the invoice posting date, plus any hold days, has passed.

Create an eligibility policy

  1. Choose New Eligibility Policy. Enter a new Code, a Description, Effective From and, optionally, Effective To. The dates must cover the dates of the component that will use the policy.
  2. Choose when commission Becomes Eligible:
Option Behavior
On Posting Eligible immediately, or after Hold Days if you set them. The whole earning stays pending until the hold ends.
On Payment Eligible Percent of each earning becomes eligible in proportion to customer payments applied to the invoice. The rest becomes eligible when the invoice is closed. With the default Unapplication Behavior, an unapplied payment moves the share back to pending.
On Full Payment The whole earning stays pending until the invoice is closed by payment, credit or write-off. With the default Unapplication Behavior, if an unapplied payment reopens the invoice, the release moves back to pending and is released once when the invoice closes again.
New Eligibility Policy dialog with code, description, effective dates, Becomes Eligible set to On Payment, Eligible Percent and the Eligibility summary
Step 2: a new policy that pays on customer payment.
  1. For On Payment and On Full Payment, choose the Payment Discount Treatment and the Unapplication Behavior. For On Posting they stay at Ignore and Reverse Eligibility.
Field Option What it does
Payment Discount Treatment Ignore The discounted share is released when the invoice closes, as if it had been paid.
Payment Discount Treatment Reduce Eligible The same share of the commission is removed: a 2% payment discount removes 2% of the commission.
Unapplication Behavior Reverse Eligibility The released share moves back to pending. An amount already paid out becomes recoverable when the plan has a recovery policy.
Unapplication Behavior Hold Recovery Also reverses the release; an amount already paid out becomes recoverable and waits for a manual review before it is recovered.
Unapplication Behavior Net Future Reverses the release and leaves an amount already paid out as a negative balance that nets against the next payouts.
Unapplication Behavior Manual Review Reverses nothing automatically.
  1. Read the Eligibility summary, which explains the behavior you are about to create, and choose OK.

The saved policy is Active and immutable. A policy code can never be reused, so existing policy history cannot be overwritten. When the dialog is opened for a component from the setup checklist, Apply to Draft Component shows the Draft component that will use the new policy.

NOTE

Becomes Eligible, Hold Days, Eligible Percent, Payment Discount Treatment and Unapplication Behavior only appear while the Cash-based eligibility and holds module is on. Without it, any policy other than On Posting, 100 percent and zero hold days is refused with BAA-FEATURE-OFF.

Credit memos and payment-based policies

A credit memo applied to an invoice is never counted as a customer payment. Cash on the prepayment invoices of the same order counts toward the final invoice. With the return policy setting Netting Basis = Customer Ledger Application on Commission Return Policies, an applied credit memo reduces the commission instead, shown as Credit Memo Netted. This netting only works with an On Payment or On Full Payment policy: plan validation reports BAA-PLAN-NETTING-TRIGGER for a component whose policy has another trigger. See Credit memo netting.

Commission carried over for an invoice that was still open when you started with Bitta Commission (Open Invoice Commission Balances) waits for that invoice to be fully paid, whatever the component's policy says. See Commission paid outside Business Central.

Release pending commission

Pending amounts are released by Release Pending Eligibility. It checks matured hold days, customer payments applied to the invoice and closed invoices as of the work date. It is safe to run repeatedly: every release is an append-only eligibility entry, so repeated runs never double count.

  • Run it from Commission Earnings, where a message reports how many releases were recorded, or from the Bitta Commission Role Center.
  • Or schedule it as the job queue entry "Bitta Commission pending eligibility release". The setup wizard's Finish creates it and sets it to Ready. Otherwise Prepare Native Scanner Jobs on Bitta Commission Setup creates it in On Hold status, and you set it to Ready. See Capture posted sales.
Commission Earnings with the message reporting how many pending eligibility releases were recorded after Release Pending Eligibility
Release pending commission on demand.

Earnings under an active aging hold are skipped until the hold clears.

The job works through a worklist of invoices whose payments or applications changed, and sweeps all pending commission once per release date. It commits after every Release Batch Size earnings, set on Bitta Commission Setup (default 100, from 1 to 10,000), so a failure never undoes the rest of the run. Each run of the job, and each manual Release Pending Eligibility, is logged on Commission Release Log with what it checked, released or netted and which earnings failed. The manual run processes the worklist first. On Commission Release Log, Run Release Now runs the job for the work date and Worklist shows the customer ledger entries waiting for the next run.

The Payment Status FactBox on Commission Earnings, and the Invoice Payment group on the Commission Earning card, show how much of the invoice (with the prepayment invoices of its order) the customer has paid in cash (Collected %), the Last Payment Date and whether the invoice is still open (Invoice Open). Credit memos and payment discounts are not cash. Users without access to customer ledger entries see no payment data there.

Aging rules for overdue invoices

Search for Commission Aging Rules and add a rule per payment policy version:

  1. Set Days Overdue Threshold, the days past the invoice due date.
  2. Choose the Aging Action: Flag records the overdue amount, Hold holds it until the invoice closes, Forfeit forfeits it, and Reduce reduces it. For Reduce, set the Reduction Type (Percent of the earning or Fixed Amount per earning) and the Reduction Value.
  3. Turn on Also Apply When Customer Is Credit Blocked if the rule should also apply, regardless of days overdue, when the customer is blocked, and select Enabled.
Commission Aging Rules list with payment policy, days overdue threshold, aging action, also apply when customer is credit blocked, and enabled
Aging rules for overdue invoices.

Open Commission Aging and choose Evaluate Aging to evaluate all pending commission as of the work date. Repeated evaluations never double count, and holds clear automatically when the invoice is settled. Register Scanner Jobs on Commission Source Capture Setup creates the job "Bitta Commission commission aging evaluation" on hold. Aging rules never change amounts that are already released.

A reduction moves to Forfeited, never exceeds the amount still pending, and is reversed at the next evaluation if the rule is disabled, deleted or no longer reduces. For example, a rule at 60 days overdue with Reduce, Percent and 25 reduces a pending commission of 100.00 to 75.00. If the customer then pays, the 75.00 is released when the invoice closes.

For conditional pay, Commission Release Conditions keeps pending commission pending until a source fact attribute, final cost, final payment or a manual approval is present, and forfeits it after the expiry days or when the participant is terminated. Work the queue on Commission Pending Releases.

Eligibility holds

A hold keeps eligible commission out of settlement until it is released. Open Eligibility Holds and choose Place Hold.

Eligibility Hold dialog with hold type, participant, component, source fact, earning, settlement and reason code fields
Place an eligibility hold.
Hold Type What it keeps out
Source One source document, including its returns and corrections.
Earning One earning.
Component One component, for one participant or for everyone.
Participant, Compliance, Missing Data, Management The commission of one participant.
Paysheet A whole settlement batch. It cannot be submitted or frozen while held.

Every hold needs a Reason Code. To release, choose Release Hold and give a Release Reason Code; the commission becomes available to the next settlement.

WARNING

A Compliance or Management hold must be released by someone other than the person who placed it, unless that person is an administrator and the hold is not on their own commission (see Approval policies), and a Missing Data hold needs a Release Note describing the data that was supplied. A frozen or later settlement batch can no longer be held.

Placing a hold requires the Cash-based eligibility and holds module. Dispute holds are covered in Commission disputes. The Commission reports shows where these pages appear.

What's next

Route plans, statements and settlements to a second person: Approval policies.

// next step

Ready to try Bitta Commission?