Expense Policy Checker

Expense Review Evidence

{{ summary.flaggedRows }} row(s) flagged {{ formatMoney(summary.overLimitAmount) }} over policy {{ summary.missingReceipts }} missing receipt(s) {{ summary.missingFieldRows }} evidence gap(s) {{ summary.duplicateRows }} duplicate watch {{ summary.blockedRows }} blocked category row(s)

Currency symbol:

Enter the symbol or code used for this review, e.g. $, RM, or EUR.

Receipt required over:

Use 0 to require receipts for every positive expense row.

Review required over:

Enter the amount that should trigger manager or finance review.

Meal cap:

Use the per-claim meal limit from the policy being checked.

Lodging cap:

Use the per-claim lodging or hotel limit from the review policy.

Mileage rate:

Enter the reimbursable rate per mile or km, matching the distance units in rows.

{{ currencySymbolDisplay }} per mile/km

Blocked categories:

Separate blocked categories with commas or new lines, e.g. Alcohol or Personal gifts.

Category limits:

One cap per line as category, amount, e.g. Taxi, 80.

Expense rows:

CSV header is optional; accepted columns include date, category, amount, receipt, distance, merchant, currency, notes.

{{ error }}

Notes required over:

Set 0 to skip notes review; positive amounts flag blank notes above the limit.

Mileage tolerance:

Use 0 for exact mileage math, or a small percent for rounding differences.

Blank receipt means:

Use Missing for strict review, or Unknown to separate blanks from explicit no.

Duplicate review window:

Set 0 to skip; otherwise enter a 1-60 day window.

days

Near-threshold watch:

Set 0 to skip; enter 1-25 to flag rows within that percent below a limit.

Display rounding:

Choose the displayed currency increment: cents, nickel, tenth, or whole unit.

Row	Date	Category	Claimed	Policy basis	Receipt	Flags	Copy
{{ row.rowNumber }}	{{ row.dateDisplay }}	{{ row.categoryDisplay }}	{{ row.amountDisplay }}	{{ row.policyBasis }}	{{ row.receiptDisplay }}	{{ row.severityLabel }} {{ row.flagText }}

Check	Rows	Severity	Evidence	Next step	Copy
{{ row.check }}	{{ row.rows }}	{{ row.severityLabel }}	{{ row.evidence }}	{{ row.nextStep }}

Category	Rows	Claimed	Flagged	Over policy	Copy
{{ row.category }}	{{ row.count }}	{{ row.totalDisplay }}	{{ row.flaggedCount }}	{{ row.overDisplay }}

Rule	Setting	Evidence	Copy
{{ row.rule }}	{{ row.setting }}	{{ row.evidence }}

No positive expense amounts available for the spend mix.

Export to PDF Fullscreen

Include query parameters

Embed:

Customize embed code

Include query parameters

Wrap embed in collapsible toggle

Collapse panel by default

Hide card frame (bare iframe)

Loading behavior

Width

Height

Aspect ratio (width : height)

Max height (optional)

Collapsible heading

Collapsible description (optional)

Allow fullscreen

Referrer policy

Sandbox tokens

Expense policy review compares a claimed business cost with the reimbursement rules an organization has already chosen. The same receipt can be acceptable for one employer and flagged by another because the meal cap, receipt threshold, mileage rate, currency rule, or blocked category list is different. A useful review therefore needs both the expense details and the exact policy limits used for that review.

Most expense reports fail for ordinary reasons: a missing date, unclear category, amount above a meal or hotel cap, receipt evidence missing above the required threshold, or a mileage claim that does not match distance times rate. Those problems are easier to fix before submission than after payroll, finance, or a manager has already rejected the claim.

Expense rows flowing through entered policy limits and rule checks into review flags, totals, and evidence records.

Good expense review separates evidence from approval. A flag can mean the row needs a receipt, a corrected amount, a business-purpose note, a currency check, or an exception rationale. It does not automatically mean the employee should be paid or denied. Final reimbursement still depends on the employer policy, the manager's authority, tax treatment, and any local employment or accounting rules that apply.

The most useful output is a defensible review record. It should show which rows were checked, which rule caused each flag, how much was over a configured cap, and what follow-up would make the expense easier to support.

Technical Details:

Expense substantiation usually turns on a few concrete facts: the amount, date, place or description, business purpose, and supporting evidence such as a receipt when required. Employers often add their own controls on top of those records, including category caps, meal and lodging limits, mileage rates, approval thresholds, ineligible expense types, and duplicate checks.

The checker uses user-entered policy limits only. It does not carry built-in company rules, tax rates, per diem tables, or government mileage rates. That matters because reimbursement policies vary by employer, jurisdiction, trip purpose, and employee role. The review is only as current as the limits entered for the report being checked.

Rule Core

Each row is parsed into date, category, amount, receipt state, distance, merchant, currency, and notes where those fields are present. The review then applies strict greater-than checks for caps and thresholds, plus optional watch rules for duplicates and just-below-limit amounts.

\begin{array}{lcl} Expected mileage amount & = & distance \times entered mileage rate \\ Allowed comparison amount & = & expected mileage amount \times (1 + \frac{tolerance percent}{100}) \\ Mileage row flags & when & claimed amount > allowed comparison amount \end{array}

Expense policy checker rule boundaries
Check	Boundary used	Review result
Required fields	Missing date, missing category, or amount that cannot be parsed	Row is marked for review because the claim cannot be evaluated cleanly.
Category cap	Claimed amount is greater than an exact matched category limit	Row shows the matched cap and the amount over that cap.
Meal or lodging cap	Category text looks like a meal or lodging category and amount is greater than the entered cap	Row is marked `Over limit` with the cap as the policy basis.
Mileage	Category text looks like mileage, distance is present, and claimed amount is greater than distance times rate plus tolerance	Row is marked over the mileage allowance. Missing distance creates a review flag instead.
Receipt threshold	Amount is greater than `Receipt required over` and receipt evidence is missing or unclear	Row is marked for missing receipt evidence. An amount exactly equal to the threshold is not above it.
Review threshold	Amount is greater than `Review required over`	Row is marked for approval review even when no cap is exceeded.
Blocked category	Normalized category matches the entered blocked category list	Row receives the strongest blocked-category severity.
Duplicate watch	Same normalized category, same amount rounded to cents, and dates within the entered day window	Rows are marked as potential duplicates for human confirmation.
Near-threshold watch	Amount is below a limit but at or above the selected percent window below that limit	Row receives an informational flag, useful for split-claim or cutoff review.

Input parsing and evidence handling rules
Area	How it is handled	Why it matters
Expense rows	CSV-style rows may include a header. Accepted header meanings include date, category, amount, receipt, distance, merchant, currency, and notes.	Reports pasted from different systems can still map to the same review fields.
Money values	Currency symbols are stripped for numeric parsing. Commas are handled as thousands separators, or as decimals when no period is present.	Rows can be compared numerically, while currency mismatches still receive a separate review cue.
Receipt text	Values such as yes, true, provided, attached, or receipt count as provided. No, false, missing, none, and not provided count as missing. Other text is unknown.	Receipt flags are based on evidence state, not just whether the cell contains any text.
Blank receipt cells	The advanced setting can treat blanks as missing, unknown, or provided.	Different teams handle blank receipt fields differently during early pre-checks.
Display rounding	Displayed money and exports can round to 0.01, 0.05, 0.10, or 1.00.	The review math keeps numeric precision before display formatting.

Severity labels are review cues, not final decisions. Clear means no configured rule flagged the row. Info marks neutral context such as a refund or near-threshold amount. Review, Over limit, and Blocked identify rows that need evidence, exception handling, correction, or policy review before reimbursement is settled.

Everyday Use & Decision Guide:

Start with the current policy, not last month's remembered limits. Set Currency symbol, Receipt required over, Review required over, Meal cap, Lodging cap, and Mileage rate from the policy that applies to the expenses in front of you. Then paste the report rows into Expense rows and keep each row as one claim line.

Add Category limits for caps that do not come from the meal, lodging, or mileage shortcuts. Put ineligible spend types in Blocked categories rather than setting their cap to zero, because blocked categories carry a stronger warning and read more clearly in the evidence tables.

Open Advanced when the review needs a stricter evidence standard. Notes required over is useful when business-purpose text is expected above a chosen amount. Duplicate review window helps find same-category same-amount rows close together. Near-threshold watch is useful when finance wants to see claims just below a receipt, approval, or cap threshold.

Expense Flags is the first place to review row-by-row policy basis, receipt status, severity, and flag text.
Evidence Trail summarizes missing fields, receipts, caps, blocked categories, approval thresholds, duplicate watch, near-threshold watch, and currency consistency.
Category Totals shows claimed spend, flagged rows, and over-policy totals by category.
Policy Summary records the entered limits and how many rows each rule affected.
Policy Spend Mix visualizes claimed spend by category and can export chart images or chart CSV.
JSON is useful when the review record needs to move into another system or ticket.

A row with no policy flags is not the same as an approved reimbursement. It only means the entered limits did not catch an issue. Check whether the policy itself is complete, whether the category wording mapped correctly, and whether confidential notes or receipts need separate handling before the claim moves forward.

Use the result as a pre-check, audit aid, or finance follow-up record. It is a poor fit for deciding tax deductibility, replacing manager approval, reading receipts with optical character recognition, converting currencies, or applying company rules that were never entered.

Step-by-Step Guide:

Work from policy setup to pasted rows, then read the evidence tables before using the summary number.

Set Currency symbol. Rows with a different detected money symbol or currency column value can appear in Evidence Trail under currency consistency.
Enter Receipt required over, Review required over, Meal cap, Lodging cap, and Mileage rate. The top summary later shows total claimed, flagged rows, over-policy amount, missing receipts, evidence gaps, duplicate watch rows, and blocked-category rows.
List ineligible categories in Blocked categories. Separate values with commas, semicolons, or new lines.
Enter one category cap per line in Category limits, such as Taxi, 80. Fix any validation message that says a category limit amount could not be parsed.
Paste rows into Expense rows. A header is optional, and recognized aliases can map date, category, amount, receipt, distance, merchant, currency, and notes.
Open Advanced if blank receipts, notes, duplicate matching, near-threshold review, mileage tolerance, or display rounding should differ from the defaults.
Read Expense Flags first. Confirm that each row's Policy basis, Receipt, and Flags match the policy you intended to test.
Use Evidence Trail, Category Totals, Policy Summary, Policy Spend Mix, and JSON for follow-up records, management review, or export.

Interpreting Results:

Read the row flags before the total. Total claimed tells you the size of the report, while Flagged rows, Over policy, Missing receipts, and Evidence gaps tell you where follow-up is needed.

The strongest trust check is whether Policy Summary reflects the policy you meant to apply. A wrong receipt threshold, meal cap, blocked category spelling, or mileage rate can make a clean report look ready when the setup was incomplete.

How to interpret expense policy checker results
Result cue	What it means	What to verify
`No policy flags from configured rules`	The entered rules did not flag that row.	Confirm the policy setup is complete and the row category was entered clearly.
`Review`	The row needs supporting evidence, approval review, distance evidence, currency review, or complete required fields.	Read `Evidence Trail` for the follow-up action tied to the check.
`Over limit`	The row exceeded a configured cap or mileage allowance.	Check `Policy basis` and the `Over policy` total before asking for correction or exception notes.
`Blocked`	The category matched an unsupported category entered for this review.	Confirm the category spelling and the policy's exception path.
`Info`	The row has context worth noting, such as a refund or near-threshold amount.	Decide whether that context needs follow-up under the review process.

Do not read a clean result as proof of compliance. It means no configured check found a problem in the pasted rows. The corrective step is to compare the output with the source policy, receipt records, and approval process before reimbursement decisions are made.

Worked Examples:

Meal claim over the cap:

With Meal cap set to $35.00, the row 2026-04-01, Meals, 42.50, no, , Client lunch appears in Expense Flags with a meal-cap policy basis. The row is Over limit by $7.50. It does not trigger the receipt rule when Receipt required over is $75.00, because $42.50 is below that receipt threshold.

Mileage claim near the allowance:

A mileage row with distance of 120 and Mileage rate of $0.65 has an expected amount of $78.00. With Mileage tolerance at 5%, the allowed comparison amount is $81.90. A claimed amount of $81.00 stays below the mileage flag, while $82.00 appears in Expense Flags as a mileage overage.

Receipt threshold boundary:

When Receipt required over is $75.00 and blank receipts mean missing, a $75.00 taxi row without receipt evidence is not above the threshold. A $75.01 taxi row with the same missing receipt status is flagged in Evidence Trail under Receipt threshold. That one-cent difference matters because the checker uses a strict greater-than comparison.

Possible duplicate rows:

If Duplicate review window is set to 3 days, two Parking rows for $30.00 dated April 3 and April 5 are compared as possible duplicates. The flag does not prove double reimbursement. It means the same normalized category and same cent-rounded amount appeared close enough together to need confirmation.

Troubleshooting an invalid amount:

A row such as 2026-04-08, Taxi, eighty, yes creates a validation message because the amount cannot be parsed. In Expense Flags, the amount displays as invalid and the row is marked for review. Replacing eighty with 80 lets the category cap, receipt threshold, and review threshold checks run normally.

Responsible Use Note:

Expense reimbursement can affect payroll, tax records, employment obligations, and audit evidence. Use the checker to organize rule-based review evidence, not to decide legal compliance, tax deductibility, employee discipline, or final approval authority. When a claim is disputed, regulated, unusually large, or tied to local labor rules, confirm the handling with the appropriate finance, HR, tax, or legal reviewer.

FAQ:

Does a clear row mean the expense is approved?

No. A clear row only means no entered rule flagged it. Manager approval, business-purpose review, receipt inspection, payroll handling, tax treatment, and exception authority remain separate business decisions.

Which expense row headers are accepted?

A header is optional. Recognized meanings include date, category, amount, receipt, distance, merchant, currency, and notes, with common aliases such as expense date, expense type, claim amount, receipt provided, miles, vendor, and business purpose.

Why did a meal, hotel, or mileage row get a special cap?

The checker looks for category words that resemble meals, dining, food, lunch, dinner, breakfast, restaurant, hotel, lodging, accommodation, stay, mileage, miles, kilometers, personal car, or vehicle. If a category is unusual, add an exact Category limits line to make the policy basis clearer.

Why is a currency row marked for review?

The selected Currency symbol is a display and consistency setting, not an exchange-rate converter. If a row contains a different leading money symbol or a different currency column value, the checker marks it for currency review so conversion can be handled elsewhere.

What should I do when validation messages appear?

Fix the named input first. Common causes are no expense rows, an amount that cannot be parsed, or a category limit line whose amount is not numeric. After correction, recheck Expense Flags and Policy Summary.

Are pasted expense rows sent to a policy review service?

No server-side policy review is used by this checker. The parsing, flags, summaries, chart data, and JSON output are generated in the browser from the values you enter. Normal page assets still load as part of opening the site, and shared URLs or exported files should be handled as sensitive records.

Glossary:

Accountable plan: An employer reimbursement arrangement where employees must account for business expenses with timely records and supporting evidence.
Receipt threshold: The amount above which missing or unclear receipt evidence creates a review flag.
Category cap: A maximum entered for a specific expense category, such as taxi, parking, meals, lodging, or office supplies.
Blocked category: An expense type entered as unsupported for the review, such as alcohol or personal gifts.
Near-threshold watch: An optional informational flag for amounts just below a configured cap, receipt threshold, approval threshold, notes threshold, or mileage allowance.
Evidence Trail: The result table that summarizes which review checks found missing evidence, over-limit rows, blocked categories, duplicate candidates, or currency issues.

References:

Internal Revenue Service, Publication 463 (2025), Travel, Gift, and Car Expenses: https://www.irs.gov/publications/p463
U.S. General Services Administration, Per diem rates, last updated April 13, 2026: https://www.gsa.gov/travel/plan-book/per-diem-rates