Is this policy ready for CO statutory audit?

Yes — every Medellín reimbursement requires the local electronic-invoice reference (DIAN electronic invoice + CUFE), the audit trail captures approver + timestamp, and exception logs are reviewable for a 5-year retention window required by CO regulators.

Do these caps work for a Series-A Retail team?

Series-A teams typically scale the lodging cap down 15-20% from this baseline (USD 115 for Medellín) and remove the regional-manager budget category. The other controls stay; the per-day per-diem in Retail is more about discipline than dollars.

What changes if we add a Medellín office?

Office presence flips lodging spend to <30% of total — the cost center shifts to client-meeting transport and on-site working meals. Recalibrate caps and add an office-perk addendum (snacks, Friday meals, gym).

Where do I get Medellín per-diem benchmarks updated?

Our State of Expense report tracks Medellín per-diem quarterly using anonymized card data. The benchmarks above are pulled from the latest snapshot (Q1 2026); subscribe via /state-of-expense-2025 to receive the next refresh.

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.

Expense Policy — Retail, Medellín

A expense policy for retail chains based in Medellín (Colombia) needs to fold three things together: the CO fiscal regime (DIAN electronic invoice + CUFE), the Medellín cost-of-living (140 USD lodging tier), and the controls that make retail chains auditable. This template ships with all three in place — clone, edit two caps, attach to onboarding.

Why Medellín Retail needs its own policy

Retail expense policy is shop-visit centric: store-tour budget, regional manager travel, and store-level petty-cash reform. The biggest leakage is uncategorized petty-cash that bypasses the corporate-card program entirely. Medellín's tech-hub re-rating drove El Poblado lodging up 35% since 2023 — Laureles is the smart-money substitute at 25% less. The Metro plus EnCicla cover most CBD travel, lowering ground-transport spend vs Bogotá.

Medellín cost-of-living anchors

Per-diem benchmark Medellín: lodging USD 110-160, meals USD 30, ground transport USD 14. Anchor neighborhoods: El Poblado · Laureles · Envigado · Sabaneta. Use these tiers to cap lodging by neighborhood rather than a flat city number — saves 12-18% per traveler-night without breaking employee experience.

Retail-specific controls

Top categories: store-tour, regional travel, signage/visual merchandising. The four controls below transplant cleanly into a 5-page policy: Store-tour daily budget; Petty-cash cap per store per month; Visit checklist tied to expense; Regional-manager monthly cap.

CO fiscal mechanics

DIAN electronic invoice + CUFE. Every reimbursement in Medellín must reference an electronic document; receipts without an electronic counterpart are not deductible and must be flagged at submission. The policy treats this as a hard reject — not a manager-discretion item.

Approval workflow

Two-tier approval: line-manager up to USD 500, director above. Auto-escalation at 48h, hard reject at 7 days unmoved. Retail adds a third control: client-code or project-tag must accompany every billable submission, validated against the active SOW list. Medellín ground-transport limit set at the city tier; lodging-tier override requires director plus a written reason logged to the audit trail.

Medellín Retail KPIs to track

Five KPIs surface whether the Medellín Retail policy is operating as designed. (1) % of Medellín submissions with a valid CO e-doc reference — target 98%+, alert below 95%. (2) Median submission-to-reimbursement cycle time — target 7 days for Retail, alert above 12. (3) Exception rate per traveler-month — target <2.0, alert above 4. (4) Lodging-tier override rate — target <8% in Medellín, alert above 15% (signals the cap is below market). (5) Project-tag completeness on billable spend — target 100% (no tag = not rebillable), alert below 95%. Pull these monthly into a one-pager that goes to the Retail business lead and the controller; the cadence forces the conversation that drives the next refresh.

Rollout in 30 days

Week 1: clone this template, set the two Medellín-specific caps (lodging + ground), and route to legal for a one-page redline. Week 2: pilot with five travelers in the Retail team, capture three real receipts to validate the fiscal-doc check works. Week 3: launch to the full Medellín team with a single Slack/email and a 90-second Loom. Week 4: pull the first KPI snapshot — % of submissions with valid e-doc, % with project-tag, median cycle time. The first month's KPIs become the baseline you measure annual progress against.

FAQ

Is this policy ready for CO statutory audit?: Yes — every Medellín reimbursement requires the local electronic-invoice reference (DIAN electronic invoice + CUFE), the audit trail captures approver + timestamp, and exception logs are reviewable for a 5-year retention window required by CO regulators.
Do these caps work for a Series-A Retail team?: Series-A teams typically scale the lodging cap down 15-20% from this baseline (USD 115 for Medellín) and remove the regional-manager budget category. The other controls stay; the per-day per-diem in Retail is more about discipline than dollars.
What changes if we add a Medellín office?: Office presence flips lodging spend to <30% of total — the cost center shifts to client-meeting transport and on-site working meals. Recalibrate caps and add an office-perk addendum (snacks, Friday meals, gym).
Where do I get Medellín per-diem benchmarks updated?: Our State of Expense report tracks Medellín per-diem quarterly using anonymized card data. The benchmarks above are pulled from the latest snapshot (Q1 2026); subscribe via /state-of-expense-2025 to receive the next refresh.

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.