Chapter 4 of 8Page 17 of 18

Configure

Capture posted sales

Calculate commission from what you actually posted: capture Business Central sales invoices and credit memos as source facts and review each one first.

updated: applies-to: 1.1.2.0

Bitta Commission calculates from what you actually posted in Business Central. Posted sales invoice and credit memo lines are captured as immutable source facts, which you review on the Commission Source Facts page. This page explains how native capture works, how you switch it on in the Native Capture group of Bitta Commission Setup, and what each source fact shows.

Before you start

  • Complete the guided setup first. See Run the guided setup.
  • Link each salesperson who earns commission to a participant. Capture keeps the salesperson code from the posted document. See Participants.
  • Changing capture settings requires the Bitta Commission Setup Administrator permission set. See Permission sets.

How native sales capture works

Capture has two parts that work together:

  • Posting hints. When a sales invoice or credit memo is posted through the standard Sales-Post routine, Bitta Commission writes a small notification hint after posting. Preview posting, posting with suppressed commits, and inventory pick or put-away postings write no hint. A failed hint never blocks the posting.
  • Recurring scanners. Three job queue entries scan the standard ledgers in bounded batches: a sales scanner, a cash scanner and a cost scanner. The scanners are the completeness control: if a hint was missed, the scanner still finds the posted document.

Each posted invoice line and credit memo line becomes one source fact. Credit memo lines are stored with negative quantity and amounts. The salesperson on the fact is the Salesperson Code on the posted document, independently of the user who posted it, and a linked return keeps the original invoice attribution. See Commission returns.

For margin plans, the cost scanner reads the value entries of each posted line. A later cost change creates a correction fact of type Cost Adjustment instead of editing the original fact.

Turn on native capture

  1. Search for Bitta Commission Setup and go to the Native Capture group.
Native Capture group on Bitta Commission Setup with Native History Start Date, Native Scan Batch Size, Native Scan Interval in minutes and Capture Posting Hints before capture is enabled
Step 1: the Native Capture group.
  1. Set Native History Start Date, the earliest posting date considered when the scanners start. Review Native Scan Batch Size (1 to 5,000 ledger entries per run), Native Scan Interval (Minutes) and Capture Posting Hints.
  2. Choose Prepare Native Scanner Jobs. The native sales, cash and cost scanner jobs, plus the pending eligibility release job, are created or refreshed in On Hold status. Capture is not enabled yet.
Message saying the native sales, cash and cost scanner jobs are prepared in On Hold status after Prepare Native Scanner Jobs
Step 3: scanner jobs prepared on hold.
  1. In Job Queue Entries, review the schedules of "Bitta Commission native sales scanner", "Bitta Commission native cash scanner" and "Bitta Commission native cost scanner", and set them to Ready.
Job Queue Entries listing the Bitta Commission native sales, cash and cost scanners and the pending eligibility release job
Step 4: review the scanner jobs and set them to Ready.
  1. Choose Validate Native Scanner Readiness. When exactly one sales, cash and cost scanner job exists with the current setup and a safe Ready or On Hold status, Native Scanner Ready is set. Validate while the jobs are On Hold or idle: a job that is waiting or running at that moment fails the check.
Message saying all three native source scanner jobs passed readiness validation
Step 5: readiness validated.
  1. Turn on Native Capture Enabled.
Native Capture group with Native Scanner Ready and Native Capture Enabled both switched on after scanner readiness
Step 6: native capture switched on.

NOTE

Native Capture Enabled is refused with BAA-NATIVE-SETUP until Native History Start Date is set and scanner readiness is validated. Run Prepare Native Scanner Jobs and Validate Native Scanner Readiness again if the jobs are missing, duplicated or in an unsafe state.

To capture right away instead of waiting for the next run, open Commission Source Facts and choose Capture Posted Sales. It processes one configured batch of posting hints and ledger scans.

Review captured facts

Search for Commission Source Facts. The page is read-only and shows the immutable, normalized event evidence used by commission processing.

Commission Source Facts list with source fact type, business date, source system code, document number, salesperson code, net amount and hashes for posted invoices and credit memos
Review the captured source facts.
Field What it shows
Source Fact Type, Source Event Type The business-event family and the lifecycle event.
Business Date, Posting Date The date used for commission processing and the original posting date.
Source System Code The system that supplied the event, for example NATIVE-SALES.
Source Document No., Source Document Line No. The posted document and line, kept for drilldown and reconciliation.
Salesperson Code The salesperson captured on the posted document.
Net Amount, Actual Cost Amount, Contribution Amount The preserved amounts, including margin.
Source Currency Code The currency of the preserved amounts.
Correction Root ID, Correction Sequence No. The correction chain that links an invoice to later corrections and returns.
Snapshot Hash, Entry Hash Hashes of the material evidence and of the stored fact.

Actions on the page:

  • Prepare Calculation prepares a calculation for the selected fact. See Calculate commission.
  • Earnings opens the earnings calculated from the fact.
  • Original and Return Sources and Correction Links show the invoice and its linked corrections.
  • Return Evidence shows the signed return delta of a linked credit memo.
  • Posted Sales Document opens the posted invoice or credit memo.

Users with a limited reporting scope only see facts that credited a participant in their scope.

Other sources

Service, project, resource, purchase and G/L adapters, recurring contracts, CSV import and the commissionSourceEvents staging API are set up on Commission Source Capture Setup. See External sources and the API reference.

If something goes wrong

  • A posted invoice has no source fact. Check that Native Capture Enabled and Native Scanner Ready are on, that the scanner jobs are Ready, and that the posting date is on or after Native History Start Date. Then choose Capture Posted Sales.
  • Capture Posted Sales stops. The action requires Native Capture Enabled and Native Scanner Ready. Failed or deferred lines stay in the retry workflow; review Commission Exceptions. See Exception handling.

What's next

Add imports, G/L rules and recurring sources: External sources.

// next step

Ready to try Bitta Commission?