Pharma trade runs on two currencies — bonus units and credit — and both leak when managed by memory. A 10+1 applied three different ways is margin gone; credit extended by relationship is the off-season's bad-debt list. xMatix governs both: schemes as one definition applied everywhere, credit as a limit enforced at order time.
Bonus schemes, priced by rule
Quantity slabs, bonus units, value discounts — defined once with eligibility, validity and stacking rules, applied identically in the rep's offline order, the stockist portal and the back office. The server recomputes every synced order as the authority, so a stale device can't invent a deal. Scheme spend accrues in a consumption ledger tied to order lines, with budgets visible while the scheme runs.
Claims from evidence, not archaeology
Scheme settlements and expiry-return claims generate from the ledger and the batch records — every claim line traceable to its orders and batches, decided line by line, settled into credit notes. The quarterly claims fight becomes a reconciliation with a short exception list.
Credit that protects the season's margin
Limits and terms gate at order time — on the beat and on the portal — with an approval path for deliberate exceptions. Collections capture on visits against specific invoices; ageing ties to the ledger; and the rep sees the counter's outstanding before taking the next order, which is when credit discipline actually happens.
Common questions
How are pharma bonus schemes kept consistent?
One governed definition — slabs, bonus units, eligibility, validity — priced identically in every channel, with the server recomputing synced orders as the authority and every application accruing to a consumption ledger.
Can scheme spend be tracked against budget during the scheme?
Yes — budgets and utilisation are live: spend by geography, stockist and SKU accrues as orders happen, so overrun risk is visible while the scheme can still be adjusted.
How does credit control work on the beat?
The counter's limit, terms and current outstanding are on the rep's device; over-limit or overdue orders gate at capture with an explicit approval path. Policy enforces itself where the order happens.
How are expiry and scheme claims settled?
From evidence — claims reference the batches, invoices and order lines they arise from, take line-level decisions and settle into credit notes automatically on approval.