What does the first 30 days look like for a new Treasurer owning meals?

Week 1: read the policy clause and the prior-quarter exception log. Week 2: shadow one submission end-to-end with the controller. Week 3: own the weekly exception review and propose one cap or category change. Week 4: present a single-slide DPO on card, FX slippage, advance recovery rate baseline to the team and lock the next quarterly review date.

Should the Treasurer approve every meals submission?

No. The Treasurer's approval should be the exception, not the rule. Set automated rules so 80%+ of meals submissions auto-approve at the line manager level; the Treasurer reviews the exception list weekly.

What's the right cap for meals?

Anchor the cap at the 75th percentile of the prior-year median by city tier — high enough to cover a typical traveler, low enough that the top 25% requires a justification. Refresh quarterly against actuals.

How do I align meals with the GL?

Map every meals category to one GL account in the policy appendix. Avoid sub-categories that don't have a GL counterpart — they accumulate into "Other" and ruin variance reporting.

What is an expense policy?

An expense policy is a written set of rules defining which work-related expenses a company will reimburse, the limits per category, the receipt and approval requirements, and the country-specific compliance addenda. It is the contract between the employee and finance.

Who owns the expense policy?

The CFO owns the document, with sign-off from the General Counsel for legal language and the People / HR lead for the employee-facing clauses. Local controllers own the country addenda. Sales-ops, IT and Travel are consulted but do not approve.

How long should an expense policy be?

Eight to twelve pages for the master policy, plus a one-page addendum per country. Anything longer goes unread; anything shorter cannot cover client meals, travel, cards, exceptions and country compliance with the required specificity.

How is an expense policy enforced?

Encode the rules in your expense platform (policy-as-code), surface the relevant clause inline at submission, audit 100% of items above $1,000 and statistically below, and publish a monthly violation-rate dashboard. Enforcement that lives only on PDF is not enforced.

How often should an expense policy be reviewed?

Once a year as a hard minimum, plus an out-of-cycle update whenever the IRS, HMRC, SAT, DIAN or Receita Federal changes a relevant deduction rule, mileage rate or per-diem table.

Meals for Treasurer

If you are a Treasurer owning meals as a slice of the expense policy, this page is the playbook. Meals split three ways: traveler meal, working meal with team, client entertainment. Each band needs its own cap and approval rule. Through the Treasurer lens: Float, FX policy, advance settlement, card-program payment terms.

What Treasurers actually need from Meals

Treasurer owns the outcome, not the rule. Meals flares up when caps are wrong, when categories don't match the GL, or when the audit-trail is incomplete. The first job is to make meals stop showing up on the Treasurer's desk: define the rule once, set automated enforcement at submission, and reserve human review for exceptions only. The KPI to anchor against: DPO on card, FX slippage, advance recovery rate.

Meals caps and rules that survive an audit

Meals split three ways: traveler meal, working meal with team, client entertainment. Each band needs its own cap and approval rule. The four rules below are the audit-pass minimum: Traveler meal cap by city · Working meal cap per attendee · Client entertainment pre-approval · Alcohol policy.

KPIs the Treasurer should track on Meals

Track DPO on card, FX slippage, advance recovery rate broken out by meals. Three sub-metrics matter: % of submissions auto-approved (target ≥80%), median cycle time from incurred to reimbursed (target ≤7 days), and exception count per 100 submissions (target ≤8). When the auto-approval rate falls below 80%, the cap is wrong; when cycle time stretches past 7 days, the SLA tooling is missing; when exceptions explode, a category is misnamed in the policy.

Workflow the Treasurer can defend in front of legal

Submission → automated rule check → manager approval (skip if under threshold) → posting to GL → reimbursement. The Treasurer's defensive posture: every step has a timestamp, every override has a written reason, every category maps 1:1 to a GL account. Meals adds two specific protections: a cap visible to the employee at submission time (so the violation is voluntary, not surprise) and a quarterly review of cap accuracy against actual median spend (so the policy doesn't ossify).

Quarterly review checklist for the Treasurer

Every quarter the Treasurer should walk a 7-item checklist on meals. (1) Pull the prior-quarter DPO on card, FX slippage, advance recovery rate and compare to the prior four quarters — flag any deviation > 15%. (2) Re-anchor the cap at the new 75th percentile and propose a revision if the delta is > 5%. (3) Audit the exception log for repeat offenders (same employee, same category, more than 3 exceptions) and route to manager 1:1. (4) Spot-check 10 random submissions for meals to confirm the rule fires correctly in the platform. (5) Re-confirm the GL mapping with accounting — onboarding new vendors often introduces ungoverned categories. (6) Update the policy version + date in the wiki and push a one-line changelog to the all-hands channel. (7) Brief the next-quarter focus to legal so they have early warning of any clause revisions in flight.

Edge cases Treasurers see most often

For meals: split-cost across cost centers, retroactive client-tag changes, vendor invoice arriving 60 days after the trip, currency-conversion disputes, and the perennial "I forgot the receipt." Each gets its own paragraph in the policy with a default decision so the Treasurer doesn't adjudicate the same case twice. The default is the policy; the deviation is the audit risk.

FAQ

What does the first 30 days look like for a new Treasurer owning meals?: Week 1: read the policy clause and the prior-quarter exception log. Week 2: shadow one submission end-to-end with the controller. Week 3: own the weekly exception review and propose one cap or category change. Week 4: present a single-slide DPO on card, FX slippage, advance recovery rate baseline to the team and lock the next quarterly review date.
Should the Treasurer approve every meals submission?: No. The Treasurer's approval should be the exception, not the rule. Set automated rules so 80%+ of meals submissions auto-approve at the line manager level; the Treasurer reviews the exception list weekly.
What's the right cap for meals?: Anchor the cap at the 75th percentile of the prior-year median by city tier — high enough to cover a typical traveler, low enough that the top 25% requires a justification. Refresh quarterly against actuals.
How do I align meals with the GL?: Map every meals category to one GL account in the policy appendix. Avoid sub-categories that don't have a GL counterpart — they accumulate into "Other" and ruin variance reporting.

Why this expense-policy library exists

Every page on this site is built from the same opinionated framework: an explicit per-category cap, a named approver chain, a documented exception path, and a review cadence anchored to the controller's close calendar. We publish the framework openly so finance leaders, controllers, and operations teams can adopt it without a vendor lock-in or a six-figure consulting engagement. The expense-policy generator turns the framework into a finished document in three languages, with country-specific tax compliance baked in from the first draft.

Behind every URL is a typed registry — landing pages, glossary entries, calculators, country pillars, and learning hubs are all generated from the same data layer that powers the policy generator itself. That means the per-diem rate you see in the calculator, the GSA-aligned mileage benchmark in the rates table, and the threshold language in the generated PDF are all sourced from one canonical place and refreshed on the same cadence. There is no drift between what we write here and what the generator produces.

Trust signals are non-negotiable: every editorial page lists the reviewer, the review date, and the underlying source — IRS publication, HMRC manual, SAT criterio, Receita Federal IN, or peer-reviewed research. When a regulator updates a per-diem schedule, the change propagates to the calculator, the country pillar, the glossary entry, and the policy template in the same release. That is the bar we hold ourselves to, and the reason controllers across the US, UK, Mexico, Brazil, and the broader LATAM region rely on this library when they re-issue their expense policy each fiscal year.

The editorial program is organized into four parallel surfaces. The industry vertical (SaaS, FinTech, Manufacturing, Retail, Hospitality, Agency, Healthcare, Nonprofit) gives every reader a starting template tuned to the cost categories, regulators, and audit findings that dominate their sector. The country pillar (United States, United Kingdom, Mexico, Brazil, Colombia, Argentina, Chile, Peru, Spain, and Portugal) layers on the local tax-compliance overlay — CFDI, NF-e, DIAN, AFIP, SII, IRS Form 8027, HMRC P11D — so the generated policy is enforceable in every jurisdiction where you operate. The persona track (CFO, controller, finance manager, head of operations, founder) reframes the same building blocks around the buyer's specific quarterly priorities. Finally, the calculator suite (per-diem, mileage, VAT-recovery, T&E benchmark, carbon, tax-id validator) gives finance teams the specific numerical inputs they need to set thresholds, justify caps, and back-test the policy against actual spend before it ships.

Cross-linking between these surfaces is deliberate, not accidental. A SaaS reader landing on the industry page is one click from the country overlay that matches their primary entity, the calculator that backs the per-diem cap they are about to commit to in writing, and the glossary entry that defines whatever IRS or SAT term they have not seen before. We measure the ratio of internal links per page weekly and refuse to publish a new landing without at least four anchors into the topical hubs. That single discipline is why a CFO can land on any page in this library and reach the policy generator in under three clicks — no matter which surface their search engine routed them through.