Reward Types

Where did this figure come from? Our Gold member paid RM 3,649 for a RM 3,999 phone. Where did the other RM 350 go, and does anybody still owe anything? Three things can lower what a member pays at a GadgetSphere till, and each one reaches the bill by a different road: member pricing changes the line’s price, points are a balance the member spends, and a voucher is a ticket that is scanned and later marked used. They differ in what happens after the bill, where the figure comes from when someone asks, and what is left outstanding. This page is for whoever designs the programme and whoever has to explain its numbers afterwards.

Meet the bill this page follows

A GOLD member buys a flagship smartphone at GS-PEN-01, a GadgetSphere Sdn Bhd (GS) branch. The phone is RM 3,999. Three rewards apply:

Member pricing. A Gold price set takes 5% off: RM 199.95.
Points. The member pays RM 100 with 10,000 GSPTS, at GadgetSphere’s rate of 100 GSPTS to RM 1.
A voucher. The member hands over a RM 50 birthday voucher.

The card pays the remaining RM 3,649.05. The same bill also earns the member new points, at Gold’s double rate, on what the phone line comes to after its discount. A line takes one price set for its price and its points, so Gold gets both only because the cashier applies the Gold price from the item’s promotion list (the two ways to build it). A SILVER member pays the full RM 3,999 on that line and earns 1.5 points per ringgit on it.

Most groups use points earned and spent at the till far more than vouchers. That is why the points section below is the longest.

The three, side by side

	Member pricing	Points	Voucher
Decided	When the line is added, by the price set that matches	Earned when the line is added; written to the member by a job after `FINAL`	When the serial is scanned; the ticket is marked used by a job after `FINAL`
The figure, when someone asks	Stored on the bill line, with the price set’s name in its description	Stored point lines on the member, plus a stored running balance	The ticket record, with the bill it was redeemed on
Left outstanding	Nothing	Every point not yet spent or expired	Every ticket issued and not yet redeemed
In the books	The sale is already lower	Earning posts nothing; spending lands where the button you used sends it	As payment, in a cashbook; as a line, like any other line

None of the three is recalculated later. Each figure on this page is a stored record, written at the time of the sale or by the job that follows it, so changing a price set, a rate or a voucher afterwards changes nothing on bills already finalised. The one exception is what an unspent point is worth: the till values the balance at today’s rate, so a rate change revalues every point not yet spent.

Member pricing: settled on the line, nothing left to owe

A price set with a Member Class rule is what turns a class into a price. When the cashier adds the phone, the till looks for the highest-priority price set whose rules match. It writes the result into the line, so the member pays less at once and nothing remains to be honoured later. The line keeps two traces of what happened:

The amounts. At the till the price set’s name goes into the line’s discount description, and an ABSOLUTE price set rewrites the unit price itself. A sales invoice writes the same price set as a unit discount. So the Gold price prints as a discount on an invoice and sometimes as a price on a cash bill.
The name, and nothing else. No document records which price book priced it. Six months later the line’s description is the only answer to “which promotion was this?”

Pricing schemes are a different thing. A pricing scheme is a price list (“Retail”, “Wholesale”), and it has no member class. A scanned line is priced on the branch’s default scheme, or on POS General’s Default Pricing Scheme where the branch names none. A scheme matters to members in one way: an item’s entry in it can carry its own points, or a price in points with a cash top-up, for every member on the bill. When an entry awards its own points, the till ignores the price set’s points for that item, campaign included.

Attach the member before the first scan. When a cashier picks a member from the member list on a bill that already has lines, the till does one of two things. It empties the lines, or, if POS General is set to keep lines when the customer changes, it works out every line’s price set and points again. A price the cashier typed over the top can be lost that way, and no record shows that a person chose it (one group found this out as a below-cost bill).

The job that stays with you. Whoever maintains the price book finalises one test bill per class at one branch after every price-set change. They read the discount description on the line, not the total on the till screen. Price and points also compete: a line takes one price set for both. So a campaign price set with a higher priority replaces Gold’s price and Gold’s points on that line (program design works an example).

Points: a promise you carry until it is spent

Points are the only one of the three that leaves a debt behind the bill.

Earning. The till works out the phone line’s points from the price set (or the item’s scheme entry) when the line is added, and stores them on the line. After FINAL, a job writes a REWARD line to the member. That only happens when the bill’s document type and posting status match the company’s member-point configuration. With no configuration it defaults to the sales order at FINAL, so a company that sells on cash bills earns nothing until it is set. It is set through the company API, with no screen, so ask your BigLedger contact if you do not call the API yourself. Where companies have set it, they have almost always named the cash bill.

Auto Apply Points From Pricebook is a server backstop: it fills points into lines that arrived with none. It changes nothing about points the till already worked out.

The balance. The figure the till offers is a stored running total, updated as each point line is written. It is not recalculated from the member’s point lots at the moment of sale. It goes on counting a lot after the lot’s end date until the expiry run sweeps it (points expiry explains what that does to the books).

Spending: two buttons, two different bills.

	Member-points settlement	Add Point Discount
What it puts on the bill	A payment line, beside cash and card	A negative line on the points-discount item
Rate	The rate in PTS to CCY Config	A fixed 100 points to RM 1, whatever your rate
Where it lands in the books	The GL account of the cashbook named on the points settlement method, plus a cashbook line in that cashbook	The points-discount item’s GL code for the company, or the company’s default sales code if the item has none
Checked against the balance at `FINAL`	No; the till caps it at no more than the balance it loaded when the member was picked	Yes, against the stored balance, when the bill is finalised from the bill screen with a member on it. Not every way a bill reaches `FINAL` asks for the check, so do not treat it as the only control: grant the right to finalise drafts narrowly, and have a supervisor read the day’s `REDEEM` lines against members’ balances

Either way, the job after FINAL writes a REDEEM line for the points spent, under the same document-type test as earning. On a company whose configuration names a different document, the redemption is accepted and the points are never taken off the balance. This is a known issue, reported to engineering.

Voiding the bill does not give spent points back, and the points the bill earned stay in the balance the till offers. A Point Adjustment on the member is the correction. A company that delays the award by a number of days gets its points as adjustment lines that never expire.

In the books, earning posts nothing. If the phone line comes to RM 3,799.05, Gold’s double rate earns 7,598.10 GSPTS, and no journal records them. The promise exists only in the membership records until finance values it (what you owe your members).

The job that stays with you.

Finance carries the liability every month-end.
Whoever runs the tills chooses one redemption button and writes it into the counter instructions; the two convert at different rates unless yours is 100 to 1.
Whoever owns the chart of accounts decides where redeemed points land. If the points settlement method names the branch’s cash cashbook, every points payment lands there as money that is never banked. If the points-discount item has no GL code of its own, redemptions are netted into sales.

Vouchers: a ticket, marked used by a job after the bill

A voucher is a record in Voucher Management with one ticket per serial number. At the till the birthday voucher’s serial is scanned. The till’s voucher payment takes only Settlement vouchers, through a VOUCHER or COUPON settlement method; a Product voucher goes on the bill as a goods line. After FINAL a job marks the ticket redeemed, with the bill and branch on it. It does that only when:

the ticket is on the right kind of line (a settlement voucher on a payment line, a product voucher on a goods line);
the ticket is assigned to the bill’s customer, unless the voucher allows anonymous use;
the moment falls inside the ticket’s redeemable dates.

A ticket that fails these tests is left unredeemed, and the bill shows no message. Whether your tenant’s FINAL starts this job at all depends on its trigger configuration, so check a finalised bill’s ticket before you rely on it.

Where the figure comes from. The Voucher Redemption report in Sales Report lists tickets by redemption, joined to the bill line they were redeemed on. A ticket redeemed directly, from the back office or a web store, has no bill, so its document columns are empty. That route checks only that the ticket was not already redeemed, not its dates.

In the books. The product has no voucher liability account. A voucher taken as payment lands in the GL account and cashbook of its settlement method, the same way a points payment does. A gift voucher sold over the counter reaches the ledger through the bill it was sold on.

Birthday vouchers. The birthday gift run, scheduled in the Scheduler applet, gives members of the listed classes either points or one new ticket of each listed voucher. Tickets go to the customer record the member is linked to. The run keeps no record of whom it has gifted, and we have no record of it running in production yet.

The job that stays with you.

The promotion’s owner caps a voucher campaign by the number of tickets generated, not by the limit fields (program design explains why).
The same person counts redemptions against that number each morning of the campaign.
Somebody expires the leftover tickets when it ends: nothing moves a ticket to EXPIRED on a schedule.

Not a reward: the commission scheme’s points

A Commission Scheme with a Membership Points treatment is another way to earn points. A scheduled run awards them on qualifying documents, for rules a price set cannot express. It reads the same member-point configuration to choose its documents. The points it creates are spent like any others.

What each one costs, and who carries it

Which reward a programme should lead with is a commercial decision. Its owner makes it with finance, and this page will not make it for you. Each option has its own costs:

	Member pricing	Points	Voucher
When the cost is taken	On every member bill, immediately	When earned, as margin promised away, even if the points are never spent	When the ticket is redeemed, for the tickets you chose to issue
Outstanding after the bill	Nothing	The unspent balance, which finance must value	The unredeemed tickets
What the member must do	Be attached to the bill	Build a balance and choose when to spend it	Keep the ticket and bring it back in its dates
What the counter must get right	Attach the member first	One redemption button	Scan the right serial on the right line

Member pricing is the simplest to account for and gives the member nothing to come back for. Points bring the member back, and you carry a debt that only finance can size. Vouchers cap the cost by the tickets you issue, and each one has to be managed by hand to expire.

When it goes wrong

What you see	Usual cause	What to do
The till showed points, and the member’s Point Transaction tab has nothing	The company’s member-point configuration names another document	Set it for that company through the company API, or ask your BigLedger contact; finalise a test bill
A member spent points and the balance did not drop	The same configuration (a known issue, reported to engineering)	Set the configuration; take the points off by negative Point Adjustment
A member says the Gold price disappeared halfway through the bill	The member was picked after the lines were scanned, and the lines were cleared or re-worked	Attach the member first; re-key the bill
The same points bought RM 100 on one bill and a different amount on another	The cashiers used both redemption buttons with a rate other than 100 to 1	Pick one button and put it in the counter instructions
The cash cashbook will not reconcile with the bank deposits, out by exactly the points or vouchers taken	The points or voucher settlement method names the branch’s cash cashbook	Give those settlement methods a cashbook of their own, which finance clears
A voucher was accepted at the till and still reads `UNREDEEMED`	Outside its redeemable dates at `FINAL`, not assigned to the bill’s customer, on the wrong kind of line, or no redemption job on your tenant	Check the ticket’s dates and assignment; ask BigLedger support about the trigger configuration
Points earned under a campaign were no higher than usual	The item’s pricing-scheme entry awards its own points, or the campaign price set ranks below Gold’s	Check the item’s scheme entry, then the price sets’ priority

A member who says their points are missing gets the walk-the-chain procedure before anybody adjusts anything.

How you know a reward worked

Finalise one test bill at a branch with all three rewards, then check, a minute later:

Member pricing. The phone line’s discount description names the Gold price set.
Points. The member’s Point Transaction tab in Membership Admin shows a REWARD line for the points earned and a REDEEM line for the points spent. Both are written by the job after FINAL, not by the till.
Voucher. In Voucher Management → Ticket Management, the ticket reads REDEEMED with the bill’s number.
The books. The cashbooks named on the points and voucher settlement methods each show a line for the bill, and they are the cashbooks your accountant expects.

If all four hold, the three roads are set up the way you intended. Repeat the check after any change to a price set, the member-point configuration or a settlement method.

How reward types fit with the rest of membership

What must exist first. Member classes; a price book with a Member Class rule, named as the terminal’s default price book; a points currency and its rate; the company’s member-point configuration; the points-discount item or a points settlement method; and VOUCHER or COUPON settlement methods, each with a cashbook. The configuration hub puts them in order.

What becomes possible. One set of classes drives all three: Gold gets its price, its points rate, its voucher rules and its birthday gift from the same class. Pick it once on the member, and every road follows.

Which one, when. Use member pricing instead of points when the benefit should arrive on every bill without the member doing anything. Use points when the member should build something up. Use a voucher when the benefit is dated, counted, or given to one person rather than a class. Use the commission scheme rather than a price set for earning rules a price set cannot express.

What breaks elsewhere. A promotion price book set as a terminal’s default stops the tier prices and the tier points together. Repointing the member-point configuration also changes which documents the commission scheme’s points run reads. A points or voucher settlement method on the cash cashbook shows up in bank reconciliation, not in membership.

What it is used alongside. A customer record. Birthday vouchers and the voucher assignment check follow the customer, not the card (the member who is not the customer).