We use cookies to analyze traffic and to support advertising. With your consent we also enable analytics and marketing cookies, and may use business data partners to identify business visitors. You can accept, reject, or choose which categories to allow. See our Privacy Policy.
Your browser is sending a Global Privacy Control signal. We treat that as an opt-out, so marketing and business data partners stay off — including if you choose “Accept all”. You can still switch them on yourself under Manage settings.
Always on
Needed to deliver the pages you ask for, to keep the site secure, and to remember this privacy choice.
Measures traffic and how pages are used, so we can see what is working and what is not.
Off by browser signal
Supports advertising — reaching you on other sites and measuring whether a campaign worked. It also loads our contact form, which is hosted by Microsoft Dynamics and reports your visit to Microsoft. Leave this off and you can still reach us by email.
Off by browser signal
Lets business data partners identify the company a visitor is browsing from, so we can tell which businesses are interested in our apps.
This is the user acceptance testing script for CommissionCentral, one scenario at a time.
It is the detailed test pass that Phase 12 · Validation & UAT of the
implementation checklist runs before go-live. Business users and
testers work the rows below in a sandbox. They record each outcome, and document the sign-off at
the end.
Each scenario row links to the step-by-step
use-case walkthrough or usage page that shows how to run it. This page
stays a thin, trackable script — it does not repeat those steps.
How to use this checklist
Set each row’s Status to one of Not Run · Pass · Fail · Blocked · N/A.
Fill in Tester and Date for each row when you run the test.
Use Evidence / Notes to record proof: a posted document number, a commission ledger entry
number, a report output, or a screenshot reference. The checklist is then also the audit trail
of the acceptance test.
Each row starts as Not Run. Copy the tables into your test tracker, or edit them in place,
and keep them current.
Work the sections in order. The calculation scenarios (B) create the ledger entries that the
ledger (D) and payment (E) sections then use. Start with
UC-01. It creates the building blocks (a plan, a
rate rule, an agent assignment) that the later scenarios use again.
Section G states the app’s deliberate edge-case behaviors as tests. Read the expected result
before you record a “failure” there as a defect. Those behaviors are specified, not accidental.
Prerequisites
Before you start UAT, make sure that:
You use a sandbox or a dedicated UAT company — never production.
Commission Setup is configured (see the setup card), or the
sandbox demo data is loaded. Demo data creates plans, agents, a 60/40 split,
a network template, and a manager team. It posts no sales documents — the testers post
the documents themselves.
The Commissions Enabled master switch is ON. It is OFF by default.
A valid License Key is stored, or the built-in trial is active. See
Licensing.
The four permission sets are assigned to the real test users by
role: TigCM Comm. Admin (admin/implementer), TigCM Comm. Manager (sales managers),
TigCM Comm. Finance (finance/payroll), TigCM Comm. Rep (reps).
The configured values (defaults, thresholds, caps, toggles, G/L accounts, journal) persist and show correctly.
Not Run
A2
Licensing
Run Check License Key on the setup card (see Licensing).
The stored key validates and the action reports the license as valid.
Not Run
A3
License gating
With no valid license (key removed / trial expired), post a commission journal or payment batch, then post a sales invoice.
Explicit commission/payment posting is blocked with a clear message; in-transaction calculation is skipped silently — the sales invoice still posts, with no commission entry. Mark N/A if a lapsed license cannot be simulated.
Not Run
A4
Master switch
Turn Commissions Enabled OFF, post a sales invoice to a commissionable customer, then turn it back ON.
No commission entry is created while the switch is off; the sales document posts normally.
Not Run
B · Calculation scenarios
#
Area
Test
Expected result
Status
Tester
Date
Evidence / Notes
B1
Flat rate
UC-01 — one agent at 100% on a 5%-of-sales plan; post a $10,000 invoice.
One entry, commission $500, status Calculated.
Not Run
B2
Tiered waterfall
UC-02 — tiers $0–$100k @ 3%, $100k–$250k @ 5%; $80k prior cumulative; post a $100k invoice.
$20k @ 3% ($600) + $80k @ 5% ($4,000) = $4,600, with one detail row per tier segment.
Not Run
B3
Multi-agent split
UC-03 — 60/40 split on a 4% plan; post a $25,000 invoice.
The line posts through the single gateway and appears as a commission ledger entry.
Not Run
D2
Adjustment
Use Adjust Entry on a ledger entry; enter a delta amount and a reason code, then post (see Ledger & audit).
An append-only adjusting entry posts; the original entry is unchanged; the reason code is required.
Not Run
D3
Reversal
UC-06 — post a credit memo against an invoice with a $500 Calculated entry.
Original flagged Reversed; a new offsetting −$500 entry posts; the two net to $0.
Not Run
D4
Status lifecycle
Walk an entry through Calculated/Pending → Payable with Release (see Ledger & audit).
Release promotes eligible entries to Payable, stamping Released By / Released DateTime; in Review approval mode entries wait for this step, in Automatic it happens immediately.
Not Run
D5
Hold / release
Place On Hold on an entry, confirm a payment batch skips it, then Release from Hold.
Payment suggestion excludes the held entry; releasing returns it to the status it held before.
Not Run
D6
Open the source
On a posted sales invoice, run Find entries; and on a ledger entry, run Show Source Document (see Ledger & audit).
Find entries shows a Commission Ledger Entries row with the right count and opens the filtered list; Show Source Document opens the posted document.
Not Run
D7
Audit report
Run the Commission Audit report over a tiered entry (see Reporting).
The report reproduces the entry and its per-tier detail (rule, method, rate, basis, gross profit, overrides, reversal cross-references) from stored data — nothing recalculated.
Not Run
D8
Summary report
Run the Commission Summary report over a period that contains a reversal and a draw advance (see Reporting).
Each salesperson shows a status breakdown; the grand totals equal the summed rows; the reversal reduces the net payable total; the draw advance appears in Draw Advances and not in gross commission.
Not Run
E · Payments & settlement
#
Area
Test
Expected result
Status
Tester
Date
Evidence / Notes
E1
Payment cycle
Run a payment batchSuggest Lines → Release → Post over Payable entries.
Suggest gathers only Payable entries for the period/filter; Release locks the batch; Post settles each entry to Paid and links it to the batch.
Not Run
E2
A/P settlement
UC-10 — an External Vendor agent’s Payable entries; run and post a payment batch.
A purchase invoice is created for the vendor (one per vendor per batch); entries become Paid with the A/P Document No. referenced.
Not Run
E3
Payroll settlement
Post a batch paying an Internal Employee or Manager agent.
Payroll general-journal lines (debit Commission Expense, credit Commission Accrual) land in the configured COMM-PAYJ journal batch for payroll to post downstream.
Not Run
E4
Draw netting
UC-07 — draw balance $1,000; the agent earns $800; run and post a payment batch.
Draw offset $800, net payable $0, draw balance falls to $200.
Not Run
F · Agents, networks & managers
#
Area
Test
Expected result
Status
Tester
Date
Evidence / Notes
F1
Split validation
On a customer, enter agent assignments whose splits do not total 100%, then correct them.
Validation blocks active splits that don’t sum to exactly 100% per customer/ship-to scope; a single agent defaults to 100%.
Not Run
F2
Network auto-assign
With Networks Enabled, create a new customer whose attributes match a Commission Network.
The most specific matching network’s agents + splits are copied onto the customer automatically.
Not Run
F3
Salesperson fallback
Post an invoice for a customer with no active agent assignment but a Salesperson Code on the document.
Commission falls back to the document salesperson at 100%.
Not Run
F4
Manager commission
UC-08 — a manager at 2% over a rep who earns $500.
A separate manager-type entry of $10 (2% × $500) is created.
Not Run
F5
No recursive chains
Review a manager-team setup where the manager is also managed, and attempt a self-managing team line (see Manager teams).
Manager chains are not recursive — a manager’s commission entry does not itself generate further manager entries — and a manager cannot manage themselves.
Not Run
G · Edge cases & negative tests
These behaviors are deliberate. The expected result below is the specified behavior,
not a defect. A row “fails” only if the app does something other than the stated behavior.
#
Area
Test
Expected result
Status
Tester
Date
Evidence / Notes
G1
No matching rule
Post a sales invoice for which no rate rule matches.
The document posts normally; no commission entry is created; a warning is logged. Not every sale is commissionable — this is not an error.
Not Run
G2
Reversal of Paid
Post a credit memo against an invoice whose commission entry is already Paid.
The reversal proceeds: an offsetting entry posts, the original stays Paid but carries the reversed flag, and the Activity Log warns for manual reconciliation.
Not Run
G3
Draw exceeds earnings
An agent with a draw balance larger than the commission earned; run a payment cycle.
Draw offsets only up to the earned amount; net payable is $0 (does not go negative); the remaining draw balance carries forward.
Not Run
G4
Same-day tier boundary
Post two invoices on the same day that together cross a tier boundary, in a known order.
Cumulative tier position uses already-posted entries at the time each invoice processes — posting order determines which invoice consumes the lower tier, so amounts may legitimately differ by order. This is the V1 design.
Not Run
G5
Assignment expiry
Let an agent assignment expire mid-period, then post documents before and after the expiry date.
Commission is calculated only for sales posted while the assignment was active; no retroactive recalculation when assignments change.
Not Run
G6
Commissionable minimum
Post one document below the Commissionable Min. Amount and one at/above it (see Commission Setup).
The below-minimum sale earns no commission; the at/above sale earns normally.
Not Run
G7
Period cap
Earn commission beyond Max Payable per Period for the configured Cap Period, with a draw balance outstanding.
The excess is deducted (Cap Deduction) so the period’s net payable does not exceed the cap; the cap applies before draw netting — Net Payable = max(0, (Commission − Cap) − Draw).
Not Run
G8
Cash % boundary
Under an On Payment plan, pay an invoice to exactly the Cash % Threshold.
The entry qualifies for promotion — the test is ≥ the threshold, not strictly greater.
Not Run
G9
Plan effective dates
Post a document dated outside a plan’s effective window.
That plan’s rates are not applied — the engine falls through to the next matching rule, or no commission (G1) if none.
Commission Payable, Commission Outstanding, Commission Paid This Month (month-to-date), Active Plans, Agent Assignments, and Open Payment Batches show correct amounts/counts, each drilling into the correctly filtered list.
Not Run
H2
Card roll-ups
Open a Salesperson/Purchaser card and compare its Balances to the ledger (see Reporting).
Outstanding, Payable, and Paid Commission YTD reconcile to that agent’s commission ledger entries by status.
Not Run
H3
Rep access
Sign in as a user holding only TigCM Comm. Rep and open commission ledger entries (see Permissions & roles).
The rep can read commission data. V1 caveat: enforced own-only row isolation is deferred — a rep can see other reps’ amounts unless tenant security filters restrict them. Confirm access works; do not log the visibility as a defect.
Not Run
What this checklist does not cover
The rows above test only the shipped V1 behavior. The deferred Reporting & BI items are on the
roadmap and have no rows here: the manager dashboard, the commission summary report, the
salesperson self-service portal (and its per-rep row isolation), and the Power BI dataset/OData
feed. See Reporting. Do not test for them.
UAT sign-off
Complete this section to satisfy the implementation checklist’s Phase 12 exit criterion
(“UAT sign-off documented” — see the Implementation checklist).
