How PraisePal Works: Points, Budgets, and Credits
Connects credits, budgets, points, and redemptions so admins understand the end-to-end flow.
PraisePal separates giving recognition from redeeming rewards, so teams can celebrate often without unpredictable costs. This article explains how the pieces fit together.
What this is
Three things work together to make recognition flow smoothly:
In day-to-day use, people usually see two point views: allowance (for giving recognition) and earnings (for redeeming rewards). Admins control how allowance is allocated, while earnings are accumulated from activity such as received recognitions, celebrations, or manual point grants.
Why it exists
Recognition programs fail when appreciation and spend controls are treated as the same thing. PraisePal separates those concerns so teams can keep recognition frequent without losing budget visibility.
That separation gives you cleaner controls:
- Budgets set how points are distributed for giving.
- Earnings show what an individual has available to redeem.
- Billing and credit state controls whether gift card redemption is currently eligible.
It also improves auditability. Point issuance and redemption are recorded, so admins can trace where points came from and what consumed them when a refund or policy review is needed.
How it works (high level)
Point-bearing recognitions require givers to have sufficient allowance to give away. When someone sends recognition with points, each specified recipient receives earnings points, and the giver has their allowance deducted.
When someone redeems a reward, the system checks their earnings balance and reward eligibility rules. For gift cards, workspace eligibility also matters: subscription status and billing setup can block redemption, and workspaces may require prepaid credits.
In product calculations and billing snapshots, `100 points = US$1`.
Point consumption for redemption is tracked oldest-first. Redemptions start as pending and are fulfilled internally by PraisePal. If a redemption is refunded, points are returned and restored.
Finally, recognition allowance cycles are refreshed on a monthly cadence, while earned points remain available until redeemed or manually adjusted.
Recognition vs rewards
Recognition is peer or manager appreciation: who did something notable, why it mattered, and who should see it. When points are attached, they move from the giver’s monthly allowance into recipients’ earnings.
Rewards are the redemption side: someone chooses an item, the system checks their earnings balance and eligibility, and points are consumed to fulfill that choice. Admins configure which rewards exist; finance and billing rules can affect whether gift card redemption is available at a given time.
Programs stumble when “thank you” and “here’s what you can buy” are treated as one lump. PraisePal separates giving capacity from individual balances so recognition stays frequent and sincere, while redemption stays predictable for finance.
Common misconceptions
- “Recognition points and reward points are the same wallet.” They connect, but allowance (for giving) and earnings (for redeeming) are different balances with different jobs.
- “If I can’t redeem, I also can’t give recognition.” Giving depends on allowance and permissions; redemption depends on earnings plus catalog and eligibility rules. One can work when the other is blocked.
- “More recognition always means higher company cost.” Recognition uses budgets you set; redemption consumes individual earnings and, for gift cards, follows your credits and billing setup.
Example: one cycle in practice
A manager with a 500-point monthly allowance sends a 40-point recognition to 3 people. That action consumes 120 points of allowance. Each recipient receives 40 earnings points.
One recipient later redeems an 80-point reward, which consumes 80 points from their earnings balance. If the redemption is refunded, those consumed entries are restored and the user's earnings increase back accordingly.