An employee takes lunch and a drink from a workplace cabinet. The employer funds part of the purchase; the employee pays the rest. Finance needs to know which source paid for each part and what should happen if an item is refunded.
Before choosing a monthly allowance, agree what the employee is entitled to spend and how any personal payment is handled. Record the employer contribution separately from the employee’s payment.
In this guide
Start with a funding policy that can be applied to a purchase
Write down who qualifies, which products and locations are included, and when the contribution becomes available. Decide whether unused entitlement carries forward, expires or requires a separate review. Keep an employee’s own payment distinct from the employer’s contribution, even if both appear on the same screen.
Product eligibility matters as much as the amount. An unrestricted snack allowance should not be described as a locally qualified meal benefit without checking the actual arrangement. Country rules, employee contributions and the agreed payment route belong in the policy, not in assumptions made by the checkout design.
A shared application does not make the employment or tax treatment identical across jurisdictions.
Track allowance and settlement separately
Separate at least three questions: how much the employee may spend, how much of that entitlement has been committed to a purchase, and how much the operator has been paid. They can temporarily have different answers.
Agree the allocation before testing mixed baskets
A correction to a mixed purchase needs a clear allocation between the employer contribution and the employee’s payment. Agree how the original allocation will be recorded and corrected.
Was the removed item fully employer-funded? Did the contribution apply to eligible items in a defined order? Was it a percentage, a per-purchase cap or a daily rule? Depending on that policy, the employer adjustment and personal refund can differ. Preserve the original allocation so the correction can be explained.
| Decision | Question to settle | Record to retain |
|---|---|---|
| Eligible amount | Which products may receive the contribution? | Original basket and policy version |
| Funding order | Is employer funding applied first, proportionally or by another agreed rule? | Allocation to each funding source |
| Insufficient funds | What happens if the personal payment cannot complete? | Unresolved amount and responsible party |
| Correction | Which original item and funding allocation are being corrected? | Original reference and linked adjustment |
| Period boundary | Which statement receives a late adjustment? | Purchase date, adjustment date and export version |
This table is a specification prompt. It is not a universal accounting rule or a list of confirmed payment integrations.
Keep payment outcomes distinct from allowance changes
Restoring an employer allowance does not prove that an employee’s payment has been refunded. Each system needs its own outcome and reference.
Stripe’s refund documentation illustrates the distinction between cancelling an incomplete payment and refunding a completed one. It also describes refunds that can remain pending. These are examples from that provider’s contract; they do not establish Stripe support in MoiPass or the behaviour of a cabinet’s payment provider.
Ask the selected provider which states are final, how they can be retrieved and what evidence support staff can share with an employee. Avoid promising an immediate bank refund simply because the application has accepted a refund request.
Protect the funding records when events repeat
A repeated transaction notification should not create another company deduction. A retry after a connection failure should also be traceable to the original action. Request evidence for these cases during integration testing.
Stripe’s idempotency reference is one documented example of controlling retries through an operation key. The cabinet and budget services need their own agreed behaviour; copying a header name from another API is not evidence that they provide the same guarantee.
Authorisation must also be specific to the employee, company and transaction. OWASP’s object-level authorisation guidance explains why access to a record cannot be granted merely because the caller knows its identifier. Apply that question to refunds and exports as well as purchases.
Give finance a statement it can explain
Ask for a sample statement that shows opening entitlement, additions, completed use, adjustments and closing entitlement. Display unsettled or disputed transactions separately. Then compare operator sales, employer contributions and actual payment outcomes using shared references.
Decide who signs off the period and how a corrected export is identified. An overwritten spreadsheet makes it difficult to explain why the number sent to payroll changed.
MoiPass provides an employee allowance and cabinet application; the exact funding and payment arrangement is agreed for each deployment. The operator solution explains that scope. For a demonstration, share one mixed-basket and refund example with the company policy and cabinet model, and we can work through what needs to be confirmed.