When should expenses be cut off for the monthly close?

Most teams set a cut-off of close + 3 to 5 business days for receipt submission, with anything later accrued. The exact day matters less than holding it consistently so the close is predictable.

How do I stop the close slipping when someone is out?

Codify the checklist and its owners so any qualified person can run it, and automate receipt-matching and accruals so the close does not depend on one person's memory of the steps.

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.

Monthly Close Checklist

The monthly close is where an expense program is graded: every transaction must be matched, coded and either reimbursed or accrued before the books lock. A monthly close checklist turns that scramble into a repeatable routine, so the close lands on the same business day each month instead of slipping when one person is out. This page lays out the checklist a finance team runs for expenses specifically — the matching, the accruals, the category review and the controls that keep the close fast and defensible.

Receipt matching: the first close-checklist task

The monthly close checklist starts with matching every card transaction to a receipt and a business purpose. Anything unmatched by the close cut-off is the day's biggest risk: it cannot be coded confidently and may be personal spend hiding in the corporate account. Run the unmatched report mid-month, not on close day, so cardholders have time to attach receipts before the deadline. A close-checklist target worth holding is a 95%+ match rate by cut-off, with the remainder routed to the accrual step rather than left to block the whole close.

Accruals for unreceipted spend

Card spend without a matched receipt at month-end does not get ignored — it gets accrued. The close checklist should accrue each unmatched transaction at its spend amount, book it to the best-estimate category, and flip it to actual expense the following month once the receipt lands. This keeps the period's expense complete and prevents the see-saw where one month looks artificially low and the next artificially high. Document the accrual policy in the expense policy itself so the treatment is consistent and an auditor can follow it without asking.

Category and coding review

Before the books lock, the close checklist includes a sweep for misclassified spend. Pull the largest transactions and any category that moved sharply versus prior months, and confirm the GL coding is right — a SaaS renewal miscoded as travel distorts every downstream report. This review is also where policy drift surfaces: a spike in a category usually means either a real business change or a control that has gone slack. Logging what you find feeds the next policy revision, closing the loop between the monthly close and the policy that governs it.

Exception log and sign-off

The final close-checklist task is reconciling the exception log: every out-of-policy item that was approved anyway, with who approved it and why. A clean exception log is what lets the controller sign off on the close with confidence and what an external auditor reviews first. Hold the exception rate as a KPI across months; a rising rate is the earliest signal that the policy's limits no longer match reality. Sign-off should be a named, dated act so the close has a clear owner and a clear finish line each month.

Turning the checklist into a faster, repeatable close

A monthly close checklist only pays off when it shortens the cycle, not when it documents how slow the cycle already is. Time-box each task and record how long it actually took, then attack the longest item first — usually chasing missing receipts or recoding miscategorised spend. Both vanish when categorisation and documentation happen at submission rather than at close, so push that discipline upstream into the spend-control rules. Assign every line of the checklist a named owner and a hard due time relative to close-day, not a vague day-of-week. Automate the mechanical steps — bank-feed matching, accruals, intercompany eliminations — so humans spend their hours on judgement, not data entry. A close that runs the same way every month becomes a metric you can improve, and a finance team that trusts its own numbers.

FAQ

When should expenses be cut off for the monthly close?: Most teams set a cut-off of close + 3 to 5 business days for receipt submission, with anything later accrued. The exact day matters less than holding it consistently so the close is predictable.
How do I stop the close slipping when someone is out?: Codify the checklist and its owners so any qualified person can run it, and automate receipt-matching and accruals so the close does not depend on one person's memory of the steps.

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.