You’re a Manager, Not an Accountant

By Ty Sutherland

Nobody handed you a management role so you could spend your afternoons updating formulas and chasing receipts. But at some point, someone asks where the budget went, and suddenly you’re responsible for knowing the answer. That’s a fair expectation. The trap is thinking the answer requires a complex spreadsheet system that eats hours you don’t have.

Tracking team costs well doesn’t mean tracking everything obsessively. It means knowing the numbers that actually matter, having a simple way to stay current, and being able to explain your spending in plain language when someone asks. That’s it. Everything beyond that is overhead.

Understand the Costs You’re Actually Responsible For

Before you build any system, get clear on what’s actually in scope. Most managers are accountable for a narrower slice of costs than they assume. Start by asking your finance contact or your manager exactly which budget lines sit under your control.

Common cost categories for team managers include:

• Headcount costs: Salaries, contractor fees, and any overtime. These are usually the biggest line item and are often managed at the HR or payroll level, but you may need to track contractor invoices directly.
• Tools and software: Subscriptions, licenses, and one-off software purchases your team uses.
• Training and development: Course fees, conference registrations, books, certifications.
• Equipment and supplies: Laptops, peripherals, office supplies, anything physical.
• Travel and expenses: Flights, hotels, client dinners, mileage claims.
• Project-specific costs: External vendors, agencies, freelancers brought in for a specific piece of work.

Not every manager owns all of these. Some sit with procurement or finance. Know your actual scope so you’re not tracking things that aren’t yours to manage.

The Minimum Viable Budget System

Here’s the honest truth: for most team managers, a single shared document with a few tabs is enough. You don’t need a project management platform with budget modules. You don’t need to learn financial forecasting software. You need something you’ll actually look at weekly.

A workable minimum system has three components:

1. A running spend log

One place where every cost gets recorded when it happens. Date, what it was, amount, category, who requested it. One row per item. This doesn’t need to be beautiful. It needs to exist and be current. If you update it when something happens rather than trying to reconstruct it at month end, it stays manageable.

2. A budget summary

A separate view that shows your total allocated budget by category, what you’ve spent so far, and what’s left. This is the view you look at before approving a new expense and the one you share when someone asks how you’re tracking. Five rows and three columns is enough. Budget. Spent. Remaining.

3. A committed costs section

Money you’ve approved but that hasn’t been invoiced or paid yet. This is the piece most managers miss, and it’s why budgets blow out unexpectedly. If you’ve said yes to a contractor starting next month or approved a conference registration that hasn’t been charged yet, that money is already gone even though it doesn’t show in your actuals. Track it separately so your “remaining” figure is honest.

Set a Weekly Rhythm, Not a Monthly Panic

Budget surprises almost always come from neglect, not from bad luck. The fix is a short weekly habit rather than a stressful monthly review.

Once a week, spend ten minutes on three questions:

• Did anything get spent or approved this week that I haven’t recorded yet?
• Is anything coming up in the next two weeks that I need to budget for?
• Am I on track against my budget summary, or do I need to flag something early?

Ten minutes. That’s the entire system maintenance. If you do it weekly, month-end reviews become a formality rather than an emergency. If you skip it for a month, you’ll spend two hours trying to reconstruct what happened instead.

Tie this habit to something that already exists. Do it at the end of your weekly team meeting. Do it every Friday morning before you check email. Attach it to a routine so it doesn’t require willpower to remember.

The Right Way to Handle Approvals

One of the biggest sources of budget blowouts is an unclear approval process. When team members aren’t sure what they can spend without asking, one of two things happens: they ask for everything and slow down, or they buy things and ask forgiveness later. Neither is what you want.

Set a clear, simple rule. Something like: anything under $100 you can proceed with and log it; anything over $100 needs my approval before you commit. Adjust the number for your context, but make it explicit and consistent. The goal is to remove ambiguity, not to control every decision.

When someone brings you an approval request, ask three questions before you say yes:

• Do I have the budget headroom for this right now?
• Is this the right time in the quarter or project cycle to spend it?
• Is this the best use of available funds compared to other things I know are coming?

If you can answer yes to all three, approve it. If you’re unsure on any of them, take a day to check before committing. Saying “let me confirm I have the budget and I’ll get back to you by tomorrow” is a completely reasonable response.

How to Talk About Budget With Your Own Manager

Most managers dread budget conversations with their boss because they feel like an interrogation. They’re usually not. Your manager mostly wants to know two things: are you going to overspend, and do you know what’s going on?

If you’ve maintained your simple system, you can answer both questions easily. Come to any budget discussion with:

• Your current spend versus budget by category
• Any committed costs not yet showing in actuals
• A brief note on anything unusual or worth flagging

If you’re going to come in under budget, say so early. This is valuable information for your organisation and it builds trust. If you’re going to overspend, say so early too. A manager who flags a budget issue in advance and explains why is far easier to work with than one who delivers a surprise at month end. Early warning gives everyone time to react. Surprises don’t.

Never walk into a budget review without having looked at your numbers first. Even a five-minute glance the morning of the meeting is enough to avoid looking like you don’t know what’s going on.

Contractor and Vendor Costs Deserve Special Attention

Permanent headcount costs are usually handled through payroll and don’t require much day-to-day tracking on your part. Contractor and vendor costs are different. They can vary month to month, they often involve invoices arriving at unpredictable times, and they’re easy to lose track of across a quarter.

For any ongoing contractor or vendor relationship, keep a simple record of:

• The agreed rate or monthly fee
• The expected duration or end date of the engagement
• The total committed cost across the full engagement
• Invoices received and paid to date

This means you always know your total exposure on a contract, not just what you’ve paid so far. It also means you can spot if invoices stop arriving or if a contractor’s hours are drifting higher than agreed.

When you bring on a new contractor or vendor, add them to this record before work starts. Not after the first invoice arrives.

What to Do When You’re Heading Toward Overspend

It happens. A project runs longer than expected, an unplanned hire comes up, equipment fails and needs replacing. The question isn’t whether you’ll ever face a budget pressure — it’s what you do when you see it coming.

The moment you think you might overspend, do three things:

• Quantify it. How much are you likely to be over, and in which category? An approximate number is fine at this stage. “I think we’re heading for about $4,000 over in contractor costs” is enough to start a conversation.
• Identify your options. Can you pull back in another category? Can you delay a planned spend into the next quarter? Can you make a case for additional budget? Come with options, not just a problem.
• Flag it early. Tell your manager before it’s a certainty, not after. Bring your quantification and your options at the same time. This is what being on top of your budget actually looks like in practice.

Trying to solve a budget problem quietly without flagging it is almost always a mistake. It limits your options and it removes your manager’s ability to help. Transparency early is nearly always the right call.

Keep It Simple Enough to Actually Use

The best budget tracking system is one you maintain consistently. That means it has to be simple enough that you don’t put it off. If your system requires thirty minutes to update, you’ll update it monthly. If it requires ten minutes, you’ll update it weekly. If it requires five minutes, you’ll update it as things happen.

Resist the urge to make it comprehensive. You don’t need colour coding, pivot tables, or automatic category totals. You need current numbers and a clear picture of where you stand. A simple document that’s up to date beats a sophisticated system that hasn’t been touched in three weeks.

When someone asks how the team budget is tracking, you want to be able to pull up one view and give a clear, confident answer in under a minute. That’s the whole goal. Not perfection. Not financial analysis. Just a clear, current picture that lets you lead your team without budget surprises getting in the way.

Budget Tracking Is a Leadership Skill

Managers who stay on top of their budgets without obsessing over them are easier to work with, more trusted by their own managers, and better able to advocate for their teams. When you know exactly where you stand financially, you can say yes to opportunities faster, push back on requests with confidence, and make the case for resources when your team needs them.

That’s not accounting. That’s leadership. And it doesn’t require becoming a spreadsheet manager to pull it off.