How Zola Cut Its Month-End Close From 25 Days to 12 With Automated Expense Management
The Challenge
Zola's lean finance team relied on a manual expense management stack of spreadsheets and manually tracked corporate credit cards. Spend visibility was unreliable — transaction coding required manual intervention, receipts arrived late, and the reporting process was fragmented. The VP Controller described the team as wearing "multiple hats" and relying on systems to automate the work that headcount could not cover. Month-end close ran for 20–25 days, consuming a disproportionate share of the finance team's bandwidth on a repeating cycle. Out-of-policy and fraudulent spending incidents occurred without the controls to prevent them at point of purchase. Training employees on the previous expense system required 15-minute one-on-one sessions for each new user.
The Solution
Ramp replaced the spreadsheet-and-card system with an all-in-one platform providing virtual card management, automated spend controls, and real-time transaction coding. Slack integration delivered immediate transaction alerts, reducing late receipt submissions. Automated coding rules eliminated manual categorisation for the majority of transactions. The platform's accounting software integration streamlined reconciliation, and an intuitive interface reduced employee onboarding from 15-minute training sessions to self-serve adoption.
The Outcome
Zola cut its month-end close from 20–25 days to 12–13 days — roughly halving the cycle. Automated coding and reporting saved 6 hours per month, and expense report processing saved a further 3 hours, totalling 9 hours of finance team capacity reclaimed per month. Spend controls reduced out-of-policy and fraudulent transactions. Employee onboarding to the expense system became self-serve, eliminating the training overhead the finance team previously absorbed for each new user.
Strategic Takeaway
Zola's case is a compact illustration of what manual expense infrastructure costs a lean finance team: not just the hours spent processing reports, but the close cycle that stretches to 25 days because spend data arrives unreliably. A 12-day close is not just faster — it means the business has reliable financial data nearly two weeks earlier each month, which compounds into better cash management and faster decisions. For a consumer-facing business with variable and seasonal spend, that visibility matters. The self-serve adoption result is also notable: when finance teams choose tools that require individual training sessions, they become support desks for their own tooling. Intuitive design is not a convenience — it is a capacity multiplier for small teams.
- Month-end close length is a proxy for data quality. A 25-day close means the business is running on month-old financial data for most of each period — compressing it to 12 days is a decision-making improvement, not just an efficiency gain.
- Lean finance teams cannot afford tools that require training. Self-serve adoption compounds: every hour saved on onboarding a new user is an hour the finance team keeps for strategic work.
- Spend controls at point of purchase are more effective than policy enforcement after the fact. Automated limits catch out-of-policy spend before it occurs, not during a close cycle review.
See how Ramp can help your business address similar challenges.
Affiliate link — we may earn a commission at no cost to you.