Eligibility, aging, and holds

Earning commission and being allowed to pay it are two different moments. An eligibility policy decides when a calculated earning moves from Pending to Eligible, which is what settlement picks up. Aging rules, release conditions and eligibility holds add further control over overdue invoices, conditional pay and disputed or incomplete cases.

The New Eligibility Policy dialog explains the behavior before you save the policy.

Before you start

• Plans and components must exist. Eligibility policies are attached to a Draft plan component. See Plans, versions, and assignments.
• Creating policies requires the Bitta Commission Setup Administrator permission set.
• Anything other than "pay on posting, 100 percent, no hold days" needs the Cash-based eligibility and holds module (CASH_ELIGIBILITY). Switch it on in Commission Feature Management. See Turn features on as you grow.

Balance buckets

Every earning's amount moves through buckets, and each move is recorded as an append-only eligibility entry:

Bucket	Meaning
Pending	Earned, but the policy condition is not met yet.
Eligible	Ready for the next settlement.
Held	Kept out of settlement by an eligibility hold.
Payable, Settled	Selected into a settlement and then paid. See Settlements and pay groups.
Recoverable, Written Off	Negative amounts being recovered, or written off. See Clawbacks and recoveries.
Forfeited	Pending commission that will never be paid.

The earned amount always reconciles to pending plus eligible plus the later buckets. Forfeiture never deletes the earning.

Create an eligibility policy

1. Open Commission Eligibility Policies and choose New Eligibility Policy.
2. In Apply to Draft Component, pick the component that should use the policy.
3. Enter a new Code, a Description, and the Effective From and Effective To dates. The dates must cover the component dates.
4. Choose when commission Becomes Eligible:

Option	Behavior
On Posting	Eligible when the invoice is posted, or after Hold Days if you set them. The whole earning becomes eligible on the maturity date.
On Payment	Eligible Percent of each earning is released in proportion to customer payments applied to the invoice. The rest is released when the invoice is closed. Unapplying a payment moves the released share back to pending.
On Full Payment	The whole earning stays pending until the invoice is closed by payment, credit or write-off.

1. Read the Eligibility summary, which explains the behavior you are about to create, and choose OK.

The saved policy is Active and cannot be edited. To change it, create a new policy and attach it to a new draft plan version. Policy codes cannot be reused.

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 and never releases the same amount twice.

• Run it from the Commission Earnings page or from the Bitta Commission role center.
• Or let the job queue entry "Bitta Commission pending eligibility release" do it. Prepare Native Scanner Jobs on Bitta Commission Setup creates it on hold, and you set it to Ready.

Each release is dated on the event that caused it (for example the maturity date or the payment), not on the day you ran it.

Aging rules for overdue invoices

Aging rules act on pending commission when the customer is late paying.

1. Open Commission Aging Rules and add a rule per eligibility policy version.
2. Set Days Overdue Threshold (days past the invoice due date) and the Aging Action:
   • Flag records the overdue amount but does not block release.
   • Hold blocks release until the invoice is closed. Closing the invoice clears the hold.
   • Forfeit moves the remaining pending amount to Forfeited.
3. Turn on Include Credit Blocked if the rule should also apply, regardless of days overdue, when the customer is blocked.
4. Set Enabled.

Open Commission Aging and choose Evaluate Aging to evaluate all pending commission as of the work date, or let the "Bitta Commission commission aging evaluation" job do it. Register Scanner Jobs on Commission Source Capture Setup creates that job on hold. Repeated evaluations never double count. Invoices without a due date are never aged. You can add several rules with increasing thresholds to escalate from flag to hold to forfeit.

Release conditions

A release condition makes pending commission wait for a specific event. Open Commission Release Conditions and add a condition for an eligibility policy version:

Field	What it does
Condition Type	Manual Approval, Source Attribute Equals, Source Attribute Present, Cost Final or Payment Final.
Attribute Code / Expected Value	The source fact attribute to check for attribute conditions.
Expiry Days	Days after the earning date after which an unreleased amount is forfeited. Zero means no expiry.
Forfeit On Termination	Forfeits unreleased amounts when the participant status is Terminated.
Binding	Makes the condition the only release path. Set the policy hold days beyond the expiry window so maturity does not release the amount first.
Status	Only Active conditions release or forfeit.

Open Commission Pending Releases to work the queue:

• Evaluate Conditions releases amounts whose condition is met and forfeits expired or terminated amounts.
• Approve Release releases the remaining pending amount of one earning with a manual approval.
• Forfeit moves the remaining pending amount to Forfeited with a reason.
• Release Evidence opens Commission Release and Forfeiture Evidence, the append-only record of every decision.

Eligibility holds

A hold keeps commission out of settlement until someone releases it. Open Eligibility Holds and choose Place 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	All 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, select the hold, choose Release Hold and give a Release Reason Code. The commission then goes to the next settlement.

Placing a hold requires CASH_ELIGIBILITY and an administration scope over the participant. Holds that already exist keep governing settlement even if the module is later switched off. Dispute holds are covered in Disputes and holds.

Check eligibility for one earning

The calculation trace explains eligibility: the controlling policy, the payment behind each release, the next release date for a hold policy, the aging rule that blocked an amount, and any release or forfeit evidence. See Explain any earning.

Related pages

• Business Central sales sources
• Settlements and pay groups
• Earnings and the commission ledger