Business Central sales sources

Bitta Commission calculates from what you actually posted in Business Central. Posted sales invoices and credit memos are captured as immutable source facts, each carrying the salesperson, customer, item, amounts, cost and a hash of the evidence. This page explains how native capture works, how it is switched on, and which other Business Central documents can feed commission.

Native capture is switched on only after the scanner jobs pass readiness validation.

Each posted invoice line and credit memo line becomes one immutable source fact.

Before you start

• Finish the guided setup so that Bitta Commission Setup exists. See Guided setup wizard.
• Link each salesperson who earns commission to a participant. Capture keeps the salesperson code from the posted document, and calculation resolves the participant from that link. See Participants and payees.
• Changing capture settings requires the Bitta Commission Setup Administrator permission set. See Roles and permissions.

How native sales capture works

Capture has two parts that work together:

1. Posting hints. When a sales invoice or credit memo is posted through the normal posting routine, the app writes a small notification hint. Preview posting, posting with suppressed commits, and inventory pick or put-away postings do not write hints. A failure to write a hint never blocks the posting.
2. Recurring scanners. Three job queue entries scan the standard ledgers in bounded batches: a sales scanner, a cash scanner (customer payment applications) and a cost scanner (value entries). 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 exactly one source fact. Credit memo lines are stored with negative quantity and amounts. Posted shipments and return receipts do not create commission facts on their own. Scanning the same document again does not create a duplicate.

Salesperson attribution

The salesperson on the source fact is the Salesperson Code on the posted document header, not the user who posted it. A credit memo linked to an original invoice keeps the original invoice attribution, so a return reduces the commission of the person who earned it. See Returns and corrections.

Cost and margin

For margin-based plans, the cost scanner reads the value entries of each posted line, including later cost adjustments, item charges and revaluations. A later cost change creates a signed correction fact instead of editing the original fact. Expected cost and actual cost are kept separately.

Turn on native capture

1. Open Bitta Commission Setup and go to the Native Capture section.
2. Set Native History Start Date. Posted entries dated before this date are ignored when the scanners start.
3. Review Native Scan Batch Size (1 to 5,000 ledger entries per scanner run) and Capture Posting Hints.
4. Choose Prepare Native Scanner Jobs. The app creates or refreshes the sales, cash and cost scanner job queue entries, plus the pending eligibility release job, in On Hold status.
5. Review the job schedules in Job Queue Entries and set them to Ready.
6. Choose Validate Native Scanner Readiness. When exactly one sales, cash and cost scanner exists with the current setup, Native Scanner Ready is set.
7. Turn on Native Capture Enabled. The app refuses this until a history start date is set and the scanners are ready.

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

Review captured facts

Open Commission Source Facts to see every accepted fact. The page is read-only.

Field	What it shows
Source Fact Type	The business-event family, for example Sales Invoice or Sales Credit Memo.
Business Date / Posting Date	The date used for commission processing, and the original posting date.
Source System Code	The adapter that supplied the fact, for example NATIVE-SALES.
Source Document No. / Line No.	The posted document and line, kept for drill-down and reconciliation.
Salesperson Code	The salesperson from the posted document.
Net Amount, Actual Cost Amount, Contribution Amount	The preserved amounts, including margin.
Source Currency Code	The document currency. Blank means local currency.
Correction Root ID / Correction Sequence No.	The chain that links an invoice to its later corrections and returns.
Snapshot Hash / Entry Hash	Hashes of the material evidence and of the stored fact.

Useful actions on the page:

• Prepare Calculation starts a calculation for the selected fact. See Calculation runs and schedules.
• Earnings opens the earnings calculated from the fact.
• Original and Return Sources and Correction Links show the invoice and its linked credit memos.
• Return Evidence shows the signed return delta for a linked credit memo.
• Posted Sales Document opens the native posted invoice or credit memo.

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

Other Business Central sources

Open Commission Source Capture Setup to turn on additional native adapters. Each one is off until you switch it on, and the extra scanners only run while Native Capture Enabled is on in Bitta Commission Setup.

Setting	What it captures
Service Capture Enabled	Posted service invoices and credit memos, as Service Invoice and Service Credit Memo facts.
Project Capture Enabled	Project ledger sales entries, as Project Event facts.
Capture Project Usage as Cost Evidence	Project usage entries as excluded cost evidence for profitability measures.
Resource Capture Enabled	Resource ledger usage, as Resource Time facts attributed through the participant link.
Purchase Capture Enabled	Posted purchase invoices and credit memos, with purchaser attribution.
G/L Capture Enabled	G/L entries that match a G/L source rule.
Recurring Capture Enabled	Subscription events derived from invoices that match a recurring contract.

After you enable adapters, choose Register Scanner Jobs. The job queue entries are created on hold. Set them to Ready when you are ready to capture. G/L rules and recurring contracts are covered in Imports, G/L rules, and recurring contracts.

Snapshot policy

The Snapshot Policy field on Commission Source Capture Setup decides when the organization and plan evidence is hashed:

• At Calculation (default): no snapshot is taken at capture.
• At Capture: the app records the effective plan assignments for the salesperson on the business date. Later master data changes do not alter that snapshot. Review snapshots in Commission Source Snapshots.

What happens behind the scenes

• Source facts are append-only. They cannot be edited or deleted. Corrections, returns and cost changes are new facts in the same correction chain.
• Each fact stores a payload hash and an entry hash, so later evidence can be compared to what was captured.
• Scanner cursors only move forward after a batch is accepted. A failed batch leaves the cursor unchanged and the scanner retries.
• A foreign currency document without a positive currency factor is refused rather than guessed.

If something goes wrong

• A posted invoice has no source fact. Check that Native Capture Enabled is 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.
• The fact has no participant. The salesperson on the document is not linked to a participant. Fix the link, then calculate. See Exceptions and data quality.
• A return was held. The credit memo could not be matched to exactly one original sale. See Returns and corrections.

Related pages

• Imports, G/L rules, and recurring contracts
• Eligibility, aging, and holds
• Calculation runs and schedules
• Explain any earning