Province Loyalty Scheme System

Items flagged above the approval thresholds (or without a threshold). Everything within the limits was final-approved by the Sales Manager and never reaches this queue.

Re-runs the current approval thresholds over the last 100 decided submissions and shows how each one would be routed. Read-only — nothing changes.

Net sales (sales − returns) from the uploaded sales reports.

Fill in the retailer's scheme details. It will go to the Sales Supervisor first.

Each plan is a principle group (1–5 principles, summed) + a salesman code set + a role, with the monthly 80/90/100 amounts, an over-100 bonus cap and a quarterly amount. A Sales Rep earns on their own code; a Supervisor/Manager earns on the sum of the code set (matched to their assigned codes — a manager covering two sets earns both). Bonus = over-target amount × 0.35%, capped. Download the template. Re-importing overwrites the same plan (principle group + codes + role).

Role and Salesman Code also filter the run below; Principle Group filters the plans list only.

Choose a month (monthly incentive + bonus) or a quarter (quarterly incentive, no bonus). The run uses net sales from the uploaded reports against the monthly targets. Mark each person Paid once the incentive is settled.

Each setup defines the tiers (Scheme Amount / Month → Scheme Reward + Display Reward) for one Brand and one customer-code prefix, e.g. GT Bippi applies to Bippi schemes for customers whose code starts with GT. Setups are submitted by the Sales Manager and approved by the Commercial Director. Each setup takes effect from its Effective Month: a new scheme uses the tiers that were effective in its Start Month, so older setups keep serving older start months until the Director marks them Superseded.

Add the tiers, then submit for Director approval.

The master Brand list used by the New Scheme form, Scheme Setups and the sales report mappings. Renaming a brand updates it everywhere (schemes, tier setups, mappings, rules). Disabling a brand hides it from new submissions only — existing schemes keep working. Other is built-in and always available.

The guardrail for delegated approvals, per Brand + Customer Code Prefix. A scheme submission that complies with its tier, stays at or under the tier total, or whose Total Rewards % is within the Maximum Total Rewards % is final-approved by the Sales Manager; above the maximum it is flagged for the Director. Display Allowances use the customer's prior 3 months of net purchases as the base. Claims within the Maximum Total Final Rewards % (Final Rewards ÷ Total Purchase) can be approved by the Finance Manager; above it, by the Director. Anything with no matching row here always goes to the Director. Every change is recorded in the audit log.

Controls how uploaded sales invoices fill in scheme purchase amounts. Each mapping says: invoices with this Principle count toward this Brand, for invoice months inside the effective range. Unmapped principles are never counted — they appear in the Unmatched report instead.

Duplicate customers, uncovered salesman codes, unmapped principles and stale uploads — fix these before trusting reports or connecting the Intelligence Service.

Threshold changes, Director decisions on flagged items, claim decisions and API token changes — newest first (last 200).

The customer master list used by New Scheme and Display Allowance forms.

Add accounts, assign a Salesman Code to each Sales Rep, and assign the codes covered by each Supervisor, Manager, Accountant and Sales Admin (they only see schemes under their assigned codes; a Sales Admin with no codes assigned sees everything). Visible Brands limits which brands a Supervisor or Manager sees on the Sales Dashboard.

Add or edit the master Salesman Code list. Use one code per line, format like S017 or MM001.

Monthly sales target per Salesman Code + Principle + Year (Jan–Dec). Brand targets are the sum of the principles mapped to each brand — they drive the Supervisor/Manager achievement header on the Sales Dashboard and the Sales-team Incentive. Download the template (Principle, Salesman Code, then Jan…Dec). Re-importing the same code + principle + year overwrites it.

Connect a Telegram bot so the team gets instant alerts for rejections and comments. Create a bot with @BotFather in Telegram (send /newbot), then paste the token here.

With a System URL set, Telegram messages contain only the alert type, the submission ID and a link to open the system — never customer names or amounts. Leave empty to keep sending the full alert text (e.g. for LAN-only use).

Tokens give the future LMM Intelligence Service read-only access to schemes, tiers, approval history, thresholds and the data-quality report under /api/v1/… (send Authorization: Bearer <token>). Bank details, phone numbers and photos are never exposed. A token is shown only once at creation.