Skip to content

Membership

A member’s bill earns points because of a setting that is not in any of these applets. The membership applets keep the members, the rules and the vouchers. The points themselves are written afterwards, by the backend, from a bill or invoice finalised in your sales or point-of-sale applet. This page says whose screen each applet is, what each one writes into the others, and where to look when the number on a member’s card is not what you expected. The Membership module explains the whole machinery. Each page listed at the foot of this one is the reference for one applet.

None of these applets posts a journal or moves stock. A points redemption or a voucher reaches your ledger only as a line on the bill it pays, under that bill’s own journal.

Which applet is whose

AppletWho opens itOpen it whenWhat it writes into the rest of BigLedger
Membership AdminMarketing and customer-service staffYou register a member, set up a point currency and its value, correct a balance, or look up why a member’s points are what they areMembers, which the till and the storefront look up. A member saved without a customer is linked to one found by login, phone or e-mail, or to a new customer. Manual adjustments write point lines with type ADJ
Commission SchemeWhoever designs sales-agent pay or a points promotionCommission or extra points should depend on branch, member class, item or document typeNothing by itself. The Sales Commission run reads it to pay money, and a scheduled points run reads it to write point lines
Voucher Management Applet V2Marketing and customer-service staffYou create vouchers, generate or import serial numbers, assign them to members, or trace one serialTickets. A ticket is marked redeemed when the bill that uses it is finalised, where that step is switched on for your tenant. The bill’s own settlement or discount line is what posts
Voucher ManagementThe same people, on tenants that installed the earlier buildAs V2, for vouchers, tickets and scanned events onlyThe same tables as V2
MLM Admin AppletWhoever owns a member-gets-member programmeYou run a referral programme and need to see who introduced whomThe referral tree. It pays nobody: an MLM-type commission scheme does, through the Sales Commission run
OCR Cash BillA reviewer in your loyalty teamMembers photograph receipts from other shops and earn points for themPoint lines when the reviewer presses FINAL, and only where its follow-on job is switched on

The setting that decides whether a bill earns points

When a bill is finalised, a follow-on job looks at it. On this standard path it writes points only when three things are true:

  • the bill carries a member;
  • its document type and status are the ones your company’s member-point configuration names;
  • the line has a point amount and a point currency, put there by a Pricebook price set with a Point treatment, or by the cashier redeeming points.

The company configuration is a record written through the company API. We searched every applet for a call to it and found none, in these applets or in Organisation. With no record, points are earned on finalised sales orders. In the live estate, almost every point earned from a document was earned on a cash bill, not on the sales order the default names. A retailer who leaves the default earns nothing at the till, and the first bill you test will show it.

Each company names one document type and one status. If GadgetSphere Sdn Bhd sets it to the cash bill, its walk-in sales earn points and its invoices to corporate buyers do not. The wholesale company, GadgetSphere Distribution Sdn Bhd, has its own record and can earn on invoices. Inside one company, points for the second document type are a manual adjustment or a CSV upload in Membership Admin, done by whoever owns the loyalty programme, against a list of the month’s invoices.

A company can delay the points. The company record has a number of days for point assignment. Above zero, Finalise queues the bill for that many days later instead. The points then arrive as an ADJ line with no source, and the company setting is read when the delayed job runs, not at Finalise.

Fixing the setting reaches back only in part. On the standard path the job runs once, when the bill is finalised, and a bill it skipped stays skipped. Two things do reach back. The scheduled Commission Scheme points run takes every bill of the configured type it has not yet processed, whatever its date. A bill still waiting on a delay is read with the new setting. For the rest, the backend has endpoints that re-run points for a list of bills or for a whole company. We found no applet that calls them, so ask BigLedger support, or credit the members by adjustment. Decide before you change the setting. A manual credit plus either a re-run or the commission run pays the same points twice.

What happens to the number on a member’s card

Every point is a line on the member’s Point Transaction tab in Membership Admin. A bill’s lines from the standard path name the document point-update job in their Source column. The balance the till shows is a stored figure, one per member and point currency, rebuilt from those lines each time a new line is written. Most of the time the two agree. Points Setup names the three moments they do not, and how a supervisor spots each.

The one that surprises people is a void. Where your void is set up for points, voiding a bill removes its points from the expiry schedule, but its point lines stay, and the balance is rebuilt from the lines. The member keeps the points, with one narrow exception that Points Setup describes. If a bill is voided and re-issued with the same member on it, the member earns twice.

The member on the bill is not always the customer

The till asks for a member. The invoice goes to a customer. They are two records, linked, and neither copies the other after the link is made. Points follow the member on the document. The e-invoice reads the identity on the customer record. A walk-in who joins at the till gives her identity-card number for the card. If her phone or e-mail matched a customer already on file, or she adds the number later, the number stays on the card and the e-invoice cannot see it. Only a customer the enrolment created itself carries the number across. Put the identity on the customer record as well, before the first e-invoice for her.

The same split decides where points go. Re-issue a bill to a company’s account, and the points go to whichever member the new bill carries, or to nobody if it carries none.

When two applets seem to do the same job

A Pricebook Point treatment or a Commission Scheme points treatment. Use the Pricebook for the ordinary earning rate: the points are on the bill line from the moment the cashier rings it up. Use a Commission Scheme for a rule the Pricebook has no rule type for, such as one on the document type, or for points worked out on the whole bill’s amount. Its points arrive later, from a run that must be scheduled in the Scheduler. Both read the same document type from the company setting. With no record, the commission run takes sales orders in any status, not only finalised ones.

Voucher Management or Voucher Management Applet V2. They write the same tables. V2 adds, among others, the Recurring Voucher and Import Tickets menus. Open the one your tenant installed. The V2 page documents both, and the earlier build’s page lists where they differ.

MLM Admin or the referral code on a member. The referral code on a membership card is a separate mechanism, and MLM does not read it. A programme that pays uplines needs MLM Admin’s tree and an MLM-type scheme.

When something looks wrong

What you seeUsual causeWhere it is fixed
A member’s bills earn no points, everThe company configuration names another document type, or there is none, or the points follow-on job is not switched on for your tenant or companyOrganisation, through the company API
Some bills earn and some do notThe lines that earned nothing had no point amount: no price set matched themPricebook
The till offers more points than the member’s lots add up toA lot has passed its end date and the expiry run has not been, or a bill was voidedPoints Setup
A ticket used on a bill still reads as not redeemedIt was outside its redeemable dates when the bill was finalised, which skips it with no message, or the redemption step is not switched on for your tenantVoucher Management Applet V2
A recurring voucher was never createdThe recurring-voucher run creates none todayMake each period’s voucher by hand or by import
An MLM invitation is still at Created after the runThe send failed, or the program has two active endpoint linksMLM Admin
A receipt is FINAL and the member got no pointsThe OCR follow-on job is not switched on, or its company, branch or Pricebook is not setOCR Cash Bill

The symptom, cause and fix guide walks each of these in full, starting with a member who says their points are missing.

What none of these applets will do, and who does it instead

  • Move a member up a tier. A member class is set by hand. Whoever owns the programme decides who moves, on a fixed date each period, and changes the class in Membership Admin. No report joins sales to members, so the decision starts from an export; Reports says which. They know the round is done when every member who met the threshold carries the new class.
  • Put a points liability in your accounts. Points post nothing. Someone in finance values the outstanding balances at each month end and records the movement by manual journal. What you owe your members gives the procedure and the check that proves it.
  • Check that a referral scheme is lawful. MLM Admin pays any tree ten levels deep. The programme owner takes the scheme design to a legal adviser before the first invitation goes out. The MLM Admin page says what to bring.
  • Notice an unusual adjustment. Manual adjustments write no audit-trail entry and raise no alert. Somebody who does not work a till reads the month’s ADJ lines, by their creator, since delayed bill points are ADJ lines too. The Membership Admin page says what they are looking for.

Check that a member’s bill earned points

This takes a minute, and is worth doing after any change to the company setting or to an earning rule.

  1. Finalise a bill at the till with a member on it, for an item that earns points.
  2. In Membership Admin, open that member and go to the Point Transaction tab.
  3. You should see a REWARD line for that bill’s branch, with the point-update job in its Source column, and the member’s balance up by the same amount. A follow-on job writes it, so it can appear a little after the bill. If your company delays point assignment, look instead for an ADJ line that many days later.

No line at all, with no delay set, means the bill was skipped: check the company setting first. A line with the wrong number points at the Pricebook price set that matched.

Where to go next

Every page in this section

Reference for the Membership Admin applet: member records and cards, member classes, labels and label lists, point currencies and point-to-money / point-to-point conversion, manual point adjustments, points expiry, suspensions, referrals and MLM links, CSV uploads and the membership report.
Master data for rule-based sales commission and membership-point schemes: who qualifies (header and line rules), how much is earned per level (treatment), plus the Sales Groups and tiered Pricing Models the schemes reference.
Reference for the MLM Admin applet: referral programs, the members enrolled in them as participants, the upline-to-downline lineage tree the sales-commission run walks, invitations sent through contact-centre channels, and the entity contacts and QR links that bring new downlines in.
Reference for the Voucher Management applet: vouchers (settlement, discount, rewards, product), the ticket serial numbers generated or imported under them, the rules and treatments that decide where a voucher applies, recurring vouchers, scanned events, and the coupon endpoints POS General and CP Commerce call to look up and redeem a serial.
Reference for the earlier build of the Voucher Management applet — vouchers, tickets and scanned events, with one route per rule kind — behind the registry row VoucherManagementApplet; everything it shares with the V2 build is documented on the V2 page.
Back-office console for the receipt-to-points pipeline: members photograph a third-party cash bill, AWS Textract extracts it, the server matches the merchant and the line items, and a price book converts the matched lines into membership points.

6 pages — this list is read from the folder when the site is built, so it cannot fall behind what is in it.