One Claim, Five People: Why Per-Head Expense Limits Fail on Group Claims

The Control That Quietly Stops Working

Almost every expense policy contains per-head limits. A meal cap per person. An entertainment limit per attendee. A hospitality threshold above which approval is required.

These limits are enforced by comparing the claim amount against the cap. For an individual claim this works perfectly — a S$45 lunch against a S$50 cap passes; a S$80 lunch fails.

Then someone takes their team out.

Five people. S$225 total. Against a S$50 per-head cap, the system sees a claim that is 350% over limit. It is in fact S$45 per person — entirely compliant.

Finance now faces a choice, and neither option is good.

Block it, and a compliant claim is rejected. The claimant escalates, an exception is granted manually, and everyone learns the control produces false positives.

Disable the check for that category, and per-head limits stop existing for meals and entertainment — precisely the categories where discretionary overspending is easiest and hardest to spot.

In practice most organisations end up at the second option, arrived at gradually rather than decided. The cap remains in the written policy. It is simply no longer enforced by anything.

Why This Is Harder Than It Looks

The obvious response is “add an attendee field”. That is the right direction, but the problem has more layers than a single field resolves.

The payer is not the beneficiary

One person pays. Five people benefit. The reimbursement goes to the payer, but the cost belongs to the attendees.

This creates an immediate accounting divergence. As one finance team described their process: the claim is one expense report, the responsibility centre and product code are split across several products, but it is paid out to just one person.

Payment and allocation have to diverge — one payee, several cost objects. Many expense systems assume they are the same thing.

Attendees span cost centres

If all five people sat in one department, allocation would be trivial. They rarely do.

A team dinner might include three people from Sales, one from Marketing and one from Product. Charging the entire amount to the claimant’s cost centre overstates that department’s spend and understates the others’. Departmental cost reporting becomes systematically wrong — and because it is wrong consistently in the same direction, it looks stable rather than broken.

Some attendees are external

Client dinners include people who are not employees. This is also where tax treatment diverges most sharply — IRAS and HMRC both apply different rules to client entertainment than to staff welfare. External attendees usually cannot be allocated anywhere and often attract different policy treatment, since client entertainment typically has its own limits and approval requirements. Systems that only accept internal employees as attendees force people to under-report headcount, which corrupts the per-head calculation they were trying to enable.

The same event can be claimed twice

If two attendees both submit — one for the meal, one for the taxi, or worse, both for the meal because both were charged a portion — standard duplicate detection may miss it. The receipts differ, the amounts differ, the claimants differ.

Similarly, an employee who attends a group dinner may also claim their standard per diem for that day, effectively being reimbursed twice for the same meal. Without attendee data linking the group claim to the individual, nothing catches it. This is a variant of the broader problem covered in detecting duplicate employee expense claims, but group events make it materially harder.

Approval routing gets ambiguous

If a claim spans three cost centres, whose approval is required? The claimant’s manager alone is insufficient — they are approving spend against budgets they do not own. Requiring all three creates a slow multi-party approval for a routine team lunch.

What Goes Wrong Downstream

Per-head control is lost where it matters most. Meals and entertainment are the highest-frequency discretionary categories. Turning off the cap here removes control from the area with the most claims and the most judgement.

Accurate cost attribution is a core management accounting principle, and one the IMA treats as foundational to segment reporting.

Departmental budgets are wrong. Costs land on whoever paid rather than who benefited. Departments with senior staff who habitually pick up the bill look expensive; departments whose people are always guests look efficient. Neither is true.

Approval thresholds are triggered incorrectly. A S$225 group meal may cross an approval threshold designed for individual spend, routing routine claims to senior approvers. Volume rises, scrutiny falls.

Manual review absorbs finance time. Because automated validation cannot handle these claims, they are reviewed by hand — the finance team asking how many people attended, working out per-head value, and deciding allocation manually. This is one of the largest remaining sources of manual effort in otherwise automated expense processes.

The ACFE consistently ranks expense reimbursement among the more common occupational fraud schemes, and group claims are where per-head scrutiny is weakest.

Tax and audit exposure. In many jurisdictions entertainment and staff welfare carry different tax treatment, and deductibility can depend on attendee composition. Claims without attendee records may not support that treatment under audit.

How Should Group Claims Actually Work?

1. Make attendees a structured, mandatory field

For every category where per-head limits apply, attendees must be captured as structured data — not free text in a description.

Each attendee record should carry name, internal or external status, and for internal attendees their cost centre — broadly the level of detail HMRC VAT record-keeping rules expect for entertainment claims. Internal attendees should be selected from the employee directory so cost centre is derived automatically rather than typed.

This single change enables everything that follows. Without it, none of the remaining steps are possible.

2. Validate per-head, not per-claim

With attendee count available, the validation changes from:

claim amount ≤ per-person cap

to:

claim amount ÷ attendee count ≤ per-person cap

A workable structure:

The control is restored rather than relaxed. A five-person dinner at S$45 each passes. The same dinner at S$120 each fails, correctly — and that is exactly the claim the disabled control was letting through.

3. Allocate by attendee, split the accounting

Reimbursement stays single-payee. Allocation follows attendees.

For a S$225 dinner with three Sales, one Marketing and one Product attendee:

One payment, three accounting lines. Departmental reporting now reflects who actually consumed the cost. This is the same split-allocation mechanic used in cost centre expense coding automation, applied to attendee-driven rather than location-driven splits.

Where per-head splitting is inappropriate — a client dinner hosted by one department, for example — allocation should be overridable with a reason, defaulting to attendee split.

4. Route approval by materiality, not by every affected cost centre

Requiring approval from every cost centre owner is technically correct and practically unworkable for routine claims.

A pragmatic rule:

• Claimant’s manager approves in all cases
• Additional cost centre owners are notified but not required to approve below a per-centre threshold
• Above the threshold, affected cost centre owners must approve their portion
• Client entertainment always routes to the applicable entertainment approver regardless of value

This keeps routine claims fast while preserving control where amounts are material. Configuring these paths through approval workflow automation allows the thresholds to be tuned by finance as claim patterns become clearer.

5. Use attendee data for duplicate detection

Once attendees are captured, event-level duplicate detection becomes possible:

• Two claims with same date, same merchant, overlapping attendees — likely duplicate
• An attendee on a group meal also claiming per diem for that meal — double reimbursement
• The same event claimed by two attendees with different receipt components — requires review

These checks are impossible without attendee data and straightforward with it.

How Does Peakflo Handle Group Expense Claims?

Peakflo’s expense and travel management treats multi-attendee claims as a first-class case rather than an exception.

Structured attendee capture

Attendees are selected from the employee directory with cost centres derived automatically, and external attendees recorded separately with the appropriate policy treatment applied.

Per-head policy validation

Limits are evaluated against computed per-head value rather than claim total, so group claims are validated correctly instead of being blocked or exempted. Finance configures which categories use per-head basis.

Automatic split allocation

Claims split across cost centres by attendee composition, producing one payment to the claimant and correctly apportioned accounting entries, with override and reason capture where a different basis applies.

Receipt data extraction

OCR-based receipt capture extracts merchant, date, amount and tax so the claim is populated from the receipt, leaving the claimant to add only attendees.

Event-aware duplicate detection

Duplicate checks run across attendees, dates and merchants rather than receipts alone, catching same-event double claims and per diem overlaps that receipt-level matching misses.

Policy exception audit trail

Where a claim exceeds per-head limits and is approved anyway, the exception, its justification and the approver are recorded — giving finance a reviewable exception population rather than a disabled control.

Our Verdict: Is This Worth Fixing?

Fix this if:

• Your policy contains per-head limits that are not enforced on group claims
• Team meals, client entertainment or shared transport are common
• Finance manually reviews group claims to work out per-head value
• Departmental cost reporting is known to be distorted by who paid
• You cannot currently tell whether a per diem overlaps a group meal claim
• Entertainment carries different tax treatment requiring attendee substantiation

Lower priority if:

• Group claims are rare — a handful a month is manageable manually
• Your policy uses total-value caps only, with no per-head basis, in which case standard validation already works
• Everyone sits in one cost centre, removing the allocation problem entirely
• You use corporate cards for all group spend with a separate reconciliation process — though note the per-head validation and attendee substantiation questions still apply, they just surface at card statement reconciliation instead

That last case is worth flagging. Moving group spend onto corporate cards does not solve the problem; it relocates it. The attendee data is still required for policy validation, allocation and tax substantiation — it is simply collected at reconciliation rather than at claim.

Conclusion

Group expense claims are not an edge case. Team meals, client dinners and shared transport are among the most common expense types in most organisations, and they are the ones where per-head policy limits silently stop working.

The failure is subtle because nothing visibly breaks. The policy document still specifies a cap. Claims still get approved. Reports still balance. What has quietly disappeared is enforcement — in the exact categories where discretion is widest and overspending is easiest.

The remedy is unusually cheap for the control it restores. Capture attendees as structured data, validate against computed per-head value rather than claim total, and allocate by attendee rather than by payer. One additional field at claim time restores a control that most organisations believe they already have, corrects departmental cost reporting, and makes a whole class of duplicate reimbursement detectable for the first time.

Related reading: detecting duplicate employee expense claims, real-time budget validation on expense requests, and why travel requests get re-approved from scratch.

Want to see per-head validation and attendee-based allocation on your own policy? Request a demo.

Frequently Asked Questions

What is a group expense claim?

A group expense claim is a single reimbursement claim submitted by one employee covering costs incurred on behalf of several people — a team meal, client dinner, shared transport, or group booking. One person pays and is reimbursed, but the underlying expense belongs to multiple attendees and often to multiple cost centres, which is what breaks both policy validation and cost allocation.

Why do per-head expense limits fail on group claims?

Per-head limits are enforced by comparing the claim amount against a per-person cap. When one claim covers five people, the total legitimately exceeds the single-person cap, so the check either blocks a compliant claim or is switched off entirely. Without an attendee count the system cannot compute actual per-head value, so the control becomes meaningless precisely where overspending is easiest to hide.

How should group expense claims be allocated across cost centres?

Allocation should follow the attendees, not the payer. If five people from three departments attend a team dinner, the cost should split across those three cost centres in proportion to attendance rather than landing entirely on the claimant’s department. Reimbursement is still paid to one person, but the accounting entry is split, keeping departmental cost reporting accurate.

Should attendees be a mandatory field on expense claims?

For any category where per-head limits apply — meals, entertainment, client hosting — attendee capture should be mandatory. Without it, per-head validation cannot run, cost allocation defaults to the claimant, and duplicate claims where two attendees both submit for the same event become undetectable. Attendee capture is the single data point that makes group claim controls possible.

How do you detect duplicate claims on a group expense?

Duplicate detection on group expenses requires matching on the event rather than only the receipt. When attendees, date, merchant and amount are captured, the system can identify when a second person claims for an event already reimbursed to someone else, or when an attendee on a group meal also submits an individual per diem for the same meal on the same day.

What is the difference between splitting a claim and allocating it?

Splitting divides a single claim into multiple accounting lines, typically across cost centres, projects or categories, while still paying one claimant. Allocating determines the rule by which that split is calculated — by attendee headcount, department proportion, project code or fixed percentage. Splitting is the mechanism; allocation is the policy that drives it.

How should external attendees be handled on client entertainment claims?

External attendees should be recorded with name and organisation but no cost centre, since they cannot be allocated internally. Client entertainment typically carries its own per-head limit and approval path, and in many jurisdictions a different tax treatment, so the presence of external attendees should switch the claim into that category automatically rather than relying on the claimant to select it.

Does per-head validation work when attendee numbers are estimated?

It works, but the estimate should be flagged. Some events — large functions, open-invite gatherings — genuinely cannot produce an exact attendee list. For these, allow an attendee count with supporting documentation such as a registration list or booking confirmation, and route them through a separate approval path rather than treating an estimated headcount as equivalent to a named list.

Should group claims be approved by every affected cost centre owner?

Not for routine amounts. Requiring approval from every affected cost centre makes a team lunch slower than a capital purchase. A practical design has the claimant’s manager approve in all cases, other cost centre owners notified below a per-centre threshold, and their explicit approval required only above it. This keeps control proportionate to materiality.

How does this affect per diem policies?

Group claims and per diems interact badly if not linked. An employee attending a company-paid group dinner should not also draw the meal component of their per diem for that day. Once attendee data is captured, this overlap can be detected and the per diem automatically reduced. Without it, the double reimbursement is invisible and, in most organisations, routine.