Configuration

Membership setup is short, and most of it happens in one applet. What takes the time is understanding which parts are not in that applet: the company setting that decides which document awards points has no screen at all, the point amounts on a bill come from a price book or a commission scheme, and expiry is a scheduled job rather than a rule you write. This page puts the pieces in the order a new tenant meets them; the applet pages carry the field-by-field detail.

The order that works

Step	What	Where	Detail
1	Companies, branches, locations	Organisation	Members, adjustments and point transactions are branch-scoped
2	A card-number rule	Membership Admin → Field Settings	Running number, IC number or mobile number — without one a member cannot be saved
3	Member classes and labels	Membership Admin	Optional; see Member Setup
4	A points currency and a points-to-money rate	Membership Admin → PTS CCY Module, PTS to CCY Config	See Points Setup
5	The company’s member-point document configuration	Company API — no screen	Which document type and posting status award points; defaults below
6	Where the point amounts come from	Pricebook POINT treatment, or a Commission Scheme membership-points treatment, or OCR Cash Bill	See Rewards Setup
7	The counter	POS General — `SHOW_MEMBER`, a `MEMBER_POINT_DISCOUNT` item, `DEFAULT_PRICEBOOK`	Members are looked up, earn and redeem here
8	The scheduled processors	Scheduler	Expiry, expiry reminders, the commission-scheme points run, birthday gifts
9	Members	Membership Admin — one at a time or by CSV	Last, because every earlier step is something a member record refers to

The setting with no screen

The backend awards points for a document only when three things are true at once (MembershipPointsTxnService.docTypeValid, L640–L646): the document header carries a member, its server document type equals the company’s award_doc_in, and its posting status equals the company’s in_doc_status. Those two values live in the company configuration row (bl_fi_mst_comp_config_hdr, type MEMBER_POINT, code DEFAULT), which neither Membership Admin nor Organisation shows. When the row is absent the defaults are INTERNAL_SALES_ORDER and FINAL (MemberPointConfigUow, L16–L19, L71–L95). A GadgetSphere branch whose members buy at the till therefore has to set award_doc_in to the cash-bill document type through the company API, or its bills will never earn a point — and nothing on any screen will say why.

What is not configurable, because it does not exist

No automatic tier upgrade. A member class is assigned by hand (or by CSV). No processor moves a member between classes on spend, visits or time.
No expiry rule screen. Each point lot carries its own validity dates; a scheduled processor expires the lots whose end date has passed. See Expiry Rules.
No ledger posting. The membership point document types are declared with amount and quantity signum 0 (ServerDocTypes L56–L57) and JournalPostingTypeHandler has no entry for them. Points are not a liability account in BigLedger; if you want one, it is a manual journal.
No pricing scheme per member class. Member pricing is a price book rule, not a pricing-scheme link — see Rewards Setup.

What success looks like

Create one member at GS-KV-01 with class STANDARD; confirm a card number was assigned.
Use Add Point Adjustment to post +100 GSPTS with a Valid Date To a year out; check the Point Transaction and Points Expiry tabs.
At a POS terminal with SHOW_MEMBER on, ring up a bill for that member. If the company’s award_doc_in matches the cash bill, a REWARD line appears after FINAL; if not, nothing does.
Redeem 50 points on a second bill; the balance drops and the bill shows the points settlement or the points-discount line.
Void the second bill; the redemption is reversed.