Frequently Asked Questions

However your plan defines them — daily, weekly, monthly, or custom cut-offs like every 1st and 16th. Each run can execute automatically or sit in draft until your finance team reviews the report and approves release.

Yes. Rank-qualified rates, deeper matching generations for higher ranks, and rank maintenance conditions (personal volume, active legs) are all configurable from your plan document.

The system supports clawback: the refund generates reversal entries that deduct the paid commission from the member's wallet or future payouts, with the full trail visible on their statement. Whether you claw back, absorb, or partially reverse is your policy — we configure it, not decide it.

Yes — every product carries its own point value separate from price. RM100 product with 60 PV, promo items with bonus PV, zero-PV accessories: all standard.

Yes — time-boxed PV multipliers, fast-start windows and campaign bonuses can be scheduled with start/end dates so they switch on and off without manual intervention.

If your plan allows it, yes — multi-position setups (e.g. by package tier) are supported, and positions can be linked under one login so the member switches views instead of juggling accounts.

Configurable per your plan: compress the downline upward (roll-up), hold the position vacant, or reassign. What matters is that it's a defined rule executed consistently — not an admin improvising in the database.

Yes — member records, genealogy relationships, ranks and wallet balances migrate in from CSV/Excel or a database export. We verify the imported tree and balances against your old records before cutover, and you sign off before going live.

Failed items come back flagged in the payout report instead of disappearing. The amount returns to the member's wallet, the member is prompted to update their bank details, and the admin re-queues the payment. Nothing is silently lost.

Yes — minimum withdrawal, flat or percentage admin fee, and withdrawal windows (e.g. every Friday) are all configurable, and every deduction is itemised on the member's statement.

Yes — configurable deduction lines (admin fees, and any withholding your accountant instructs) are applied at payout and itemised. What to deduct is a question for your tax adviser; making the system execute and document it is ours.

Yes — stockist roles with stock allocation, stockist pricing and sub-ordering are a common part of Malaysian direct-selling builds. Tell us how your physical distribution works and we configure around it.

Yes — tree moves, manual adjustments, payout approvals and setting changes are logged with who, what and when. When a distributor disputes something six months later, you have the record.

Yes — runs generate in draft: your team checks the totals against expectations, drills into any member's calculation, then approves for release. Nothing pays out un-reviewed unless you choose full automation.

You run a parallel test: we execute a real historical cycle through the new engine and you compare the results line-by-line against what you actually paid. Launch happens after the numbers match — not before.

Your compensation plan in whatever form exists — formal document, old system settings, or notes on how you calculate by hand. We confirm the structure, flag ambiguities, and give a fixed quote and timeline before writing code.

A standard single-structure build usually takes a few weeks after the plan is confirmed; hybrid and migration projects take longer. The specific timeline comes with your quote.

Honest answer: no — we build software, we're not licensing consultants. The AJL licence from KPDN is your company's responsibility and deserves proper legal advice. What we provide is a system whose records and reports support running a licensed, compliant operation.