Each claim looked fine. The split did not.
What looked normal
Three expense claims. Each under the limit. Each approved. On paper, policy worked.
Then someone added them up:
-
Meal total — 9,600
-
Approval needed above — 5,000
-
Submitted as — 3,200 + 3,200 + 3,200
One dinner. Three claims. The split kept each line under the limit.
Why people should care
Limits only work if one spend stays as one claim.
When people break a large spend into many small ones, each claim looks fine. Approvers never see the full amount. That is how policy gets skipped without a hard “reject.”
Seven checks that catch split expenses
These tests join merchant, employee, date, amount, and payment type— data most expense systems already hold.
-
Same merchant, same day, multiple claims under the limit
Several claims to one merchant on one day, each under the approval cap.
Business impact: Finds the classic dinner split in one glance.
-
Same employee, several claims that add up to one large spend
Claims close in time that together cross the limit the single lines avoided.
Business impact: Rebuilds the full spend approvers never saw.
-
Claims just under the approval or receipt threshold
Amounts clustered just below the line that needs a receipt or extra approval.
Business impact: Spots gaming of the threshold.
-
Split across card and out-of-pocket for the same event
Part on the corporate card, part claimed as cash for the same meal or trip.
Business impact: Catches double paths for one spend.
-
Same attendees / same restaurant, billed more than once
Matching people, place, or time across more than one claim.
Business impact: Flags repeat billing of the same event.
-
Peer spike: far more sub-limit claims than others in the same role
One employee files many just-under-limit claims vs peers.
Business impact: Prioritizes people who live under the cap.
-
Pattern over time: always just under the limit
A long run of claims that sit just below policy thresholds.
Business impact: Shows habit, not a one-off mistake.
Why reviews miss this
One claim at a time
Is this amount under the limit? Is there a receipt? Each line can pass while the full spend is hidden.
Claims added together
Same person, same day, same merchant— do several small claims hide one large spend?
Policy looks at each claim. Risk looks at the total.
How foretale.ai helps
foretale.ai checks expense claims across merchant, employee, date, and amount— same-day splits, under-limit clusters, card plus out-of-pocket doubles, repeat events, peer spikes, and long-run threshold patterns—with clear evidence for every finding.
Controllers and auditors review the full spend—not one small claim at a time.
How often do “small” expenses add up to a big one?
Most companies do not know—until they join claims by person, merchant, and day. Continuous AI checks can surface splits before the next reimbursement run.
Request a demo