Daily / Meal Allowance
Define daily, breakfast, lunch, dinner or shift-specific employer benefit values.
GP connects employee identity, benefit policy, cafeteria transactions, employer subsidy, employee contribution, vendor settlement and management reporting in one governed workflow.
Company pays its share. Employee tops up the rest.
Eligibility and funding rules are deterministic and auditable, while AI monitors exceptions and explains patterns.
Define daily, breakfast, lunch, dinner or shift-specific employer benefit values.
Apply fixed subsidy, percentage contribution or company-funded allowance with employee top-up.
Control meal windows, eligible counters, categories and allowed transaction frequency.
Different policies can apply by location, employee category, shift, department or other approved grouping.
Support client-defined expiry, monthly pools, daily resets and controlled carry-forward logic.
Temporary allowances can be assigned to visitors, hosted meals or specific workplace events.
Benefit access follows authorised employee status rather than depending on ad-hoc manual updates.
| Employee event | System action |
|---|---|
| New joiner | Create eligibility from the authorised effective date and map the employee benefit group. |
| Mid-month joiner | Activate daily benefits from join date or apply policy-based pro-rata for monthly allowances. |
| Site / department transfer | Close the old rule set and apply the new site, cost-centre and benefit policy. |
| Shift / grade change | Re-evaluate meal windows and benefit group according to the approved policy. |
| Lost / replaced card | Block the old NFC token and map the replacement without losing valid employee entitlement history. |
| Suspension / exit | Stop eligibility at the approved status or last-working-date cut-off. |
| Rehire | Create a fresh lifecycle event and apply current policy rather than silently reusing stale entitlement. |
The rules engine keeps financial and eligibility decisions predictable even when the employee experience feels instant.
Rejected or adjusted transactions can show the actual reason — inactive employee, wrong site, outside meal window, insufficient benefit, duplicate transaction or restricted category.
Authorised administrators can manage temporary access or controlled fallback workflows when identity sync, badge replacement or connectivity creates an operational exception.
AI assists with prediction, exceptions and management insight while the actual entitlement and money movement remain governed by explicit rules.
This prevents separate spreadsheets from becoming different versions of the truth.
| Ledger field | Purpose |
|---|---|
| Employee / Site / Cost Centre | Attribute benefit and spend to the correct organisational structure. |
| Vendor / Counter / Timestamp | Identify where and when the transaction occurred. |
| Meal value / Employer subsidy | Separate gross meal value from company-funded benefit. |
| Employee contribution | Record top-up or employee-funded amount where applicable. |
| Refund / reversal | Preserve the original transaction and controlled adjustment history. |
| Settlement batch | Connect approved transactions to vendor statements, invoice matching and payment status. |
Connect employee identity, NFC access, subsidy rules, transaction control and reporting through one operating workflow.
Discuss Meal Benefit Program →