7 Common Controller Pitfalls (and How to Climb Out of Each)

You're past the honeymoon. Six to eighteen months in seat, the CFO has stopped praising you for "stabilizing the close." The board deck cycles through without commentary. Your name comes up in succession conversations, but always with a "but." And the things that got you the seat (heroics, late nights, holding the calculation in your head) are exactly the things keeping you from the next one.

Here's what I see when I look at controllers who plateau. It isn't laziness. It isn't lack of technical skill. It's seven specific traps. Each one is a habit that worked at the senior accountant level and quietly fails at the controller level. Each one has a number attached. Each one has a 30 to 90 day fix that doesn't require a new system, a bigger team, or a CFO who finally listens.

Read these honestly. Score yourself at the end. Pick one. Block the calendar. Go.

Pitfall 1: Firefighting the Close Instead of Redesigning It

Symptom: Same journal entry adjustments month after month. Same 12-day close. Same 11pm Slack messages on day eight. You know exactly which accounts will break because they break every time, and you've built a little ritual around catching them.

The number: APQC pegs median mid-market month-end close at 6.4 days. Yours is twelve. Each extra day costs you roughly $15K in finance team hours, plus a rolling tax on FP&A who can't reforecast on stale data. Over a year you're burning $90K and a forecast cycle.

Why it happens: Firefighting feels productive. You catch the broken AR cutoff, you fix it, the close lands, you get thanked. The structural problem (that AR cutoff is broken every month) never gets named because you keep solving the symptom on day six.

The fix (30-60 days): Pick the top three recurring late items from your last three closes. Not five. Three. For each one, push the cutoff into pre-close week. Sales ops sends final commission data on the 28th, not the 4th. AR runs the cash apply on the last business day, not day three. Inventory takes its physical count two days early. You'll fight for these dates exactly twice. After the second close lands two days faster, nobody fights you anymore.

If you cannot list your top three recurring late items off the top of your head, you don't have a close problem. You have a close-tracking problem, which is pitfall seven.

Pitfall 2: Under-Documenting Accruals

Symptom: Only you know why the bonus accrual is what it is. The deferred rent calc lives in a tab labeled "JE-23 v4 FINAL_actual." When auditors ask how you sized the warranty reserve, you start the answer with "well, historically..."

The number: One undocumented accrual costs four to eight audit hours when the audit team has to reconstruct it. At blended mid-market audit rates that's $1,200 to $2,400 per accrual in fees. A typical mid-market controller has 15 to 25 material accruals. Do the math: an undocumented accrual policy is a $20K to $60K annual line item you're paying with nothing to show for it.

Why it happens: You did the calculation in your head three years ago. It worked. You've been adjusting it ever since. Writing it down feels like extra work for a problem nobody is currently asking about.

The fix (30 days): Every accrual, before the JE posts, gets a one-page memo. Four sections: what it covers, how it's calculated (formula and source data), who reviewed it, when it gets revisited. One page, not five. A junior accountant should be able to read it and reproduce the JE. Save them in a single folder with a clean naming convention. Do this for new accruals starting next close. Backfill the existing ones at one per week.

The ROI shows up in two places: audit fees drop, and you stop being the only person who can answer accrual questions. The second one is what gets you promoted.

Pitfall 3: Skipping Audit Prep Until October

Symptom: Q4 is hell. Your audit team treats your PBC list as adversarial negotiation. Things you did in February come back as questions in November and you've forgotten the context. Year-end stretches to mid-March and somebody on your team quits in February.

The number: Late audit prep adds 30 to 50 percent to audit fees. At mid-market, that's $40K to $120K of avoidable spend. It also costs you about three weeks of CFO patience, which is harder to put a dollar value on but easier to feel.

Why it happens: Audit prep feels optional in March. The close is monthly, the audit is annual, and the close keeps winning the calendar fight. By the time it's not optional, you've lost the prep window.

The fix (60-90 days): Monthly mini-PBC. Eight to ten items refreshed every close instead of all 200 in fall. The roll-forwards, the supporting schedules, the major estimate documentation: these get touched every month while the data is fresh. Keep a simple log with item name, last refresh date, owner, audit area. Show the CFO at quarter-end. By October, your PBC list is 80 percent ready and the auditors think you're a wizard.

Build the list once with your audit partner. They'll tell you which 10 items they ask about every year. Those are the ones you refresh monthly. The rest stays seasonal.

Pitfall 4: Over-Relying on Excel Reconciliations

Symptom: A 14-tab workbook nobody else can open without breaking the formulas. Reconciliations that take three hours because the macro nobody documented stopped working in 2024. A cash recon held together by a VLOOKUP that points to a file path with your old laptop's username in it.

The number: Manual recons take three to five times longer than tooled ones. The IMA puts the average cost of one fat-finger error at around $7K in restated numbers, plus the sunk cost of the redo. The real cost isn't the time, though. It's that your top recons are concentrated in one head (yours), and that's a control weakness an auditor will eventually find.

Why it happens: The Excel works. It's been working. Your boss didn't approve a recon tool, so you built a better Excel. Each new edge case adds another tab. You're now maintaining a small software product with no version control and no test coverage.

The fix (60-90 days): Move your top five recons into a recon tool. Cash, AR, AP, intercompany, deferred revenue. Even a basic tool. The vendor doesn't matter as much as getting them out of Excel. You don't need to migrate everything. Just the recons that touch material balances and the ones that take you the most time. Build the business case on hours saved plus control improvement, not on Excel hate.

If your CFO won't approve a tool, get the cash recon out of Excel anyway using your ERP's native recon module. Most ERPs have one. Most controllers don't use it.

Pitfall 5: Not Partnering with FP&A

Symptom: You hand over the trial balance on day six and disappear. FP&A reforecasts without context, doesn't know about the one-time true-up you booked, gets surprised by the legal accrual. Leadership distrusts both numbers because they don't reconcile and nobody can explain why.

The number: Deloitte's finance benchmark data shows companies where controllership and FP&A meet weekly close their forecast variance by roughly three percentage points. At a $50M revenue company, that's $1.5M of forecasting accuracy. The CFO notices.

Why it happens: You're an accountant. They're modelers. The relationship feels like throwing a finished thing over a wall. Also: weekly meetings sound like a lot.

The fix (30 days): A 30-minute weekly sync with the FP&A lead. Fixed agenda: accruals you booked this week, surprises you saw in the actuals, things they should pressure-test in the model. That's it. No PowerPoint. No status update. Just three topics. The first two meetings will feel awkward. The third one, FP&A will start bringing things back to you. By month two, your forecast accuracy improves and your CFO starts mentioning you and the FP&A lead in the same sentences.

The point isn't to do FP&A's job. It's to give them context they can't get from the GL. That context is your competitive advantage as a controller and you've been giving it away in fragments instead of trading on it.

Pitfall 6: Becoming the "No" Voice Without Offering a Path

Symptom: Every business partner email starts with "we can't do that because GAAP." Sales asks for a deal structure, you say no. Marketing asks to capitalize a campaign, you say no. The CRO has stopped including you in deal reviews because the answer is always the same and they've found ways around you.

The number: Russell Reynolds finance leadership data shows controllers rated "blockers" by their CFO are about twice as likely to be passed over for VP roles. The CFO doesn't say it that way. They say things like "great in seat" or "very technically sound." Those are kiss-of-death phrases when they're not paired with "and a strong business partner."

Why it happens: The technical answer is often genuinely no. The deal structure does have a rev rec problem. The campaign cost isn't capitalizable. You're protecting the company. The pitfall isn't the no — it's stopping at the no.

The fix (30 days): Rule of two. Every "no" comes with two alternatives that achieve 80 percent of what the partner wanted. Sales wants to recognize revenue on signing? Two alternatives: net it across the contract term but front-load services rev, or restructure the contract with two performance obligations. Marketing wants to capitalize the campaign? Two alternatives: identify the portion that's a reusable asset, or expense it but defer matching revenue treatment.

This takes 10 extra minutes per email. It also takes some technical depth, which you have. What it does, week by week, is reposition you from blocker to partner. Six months in, you're in the deal review again. Twelve months in, the CRO requests you on the strategic accounts.

If you can't think of two alternatives, that's a signal you need to dig deeper or pull in tax/external counsel. "I'll come back tomorrow with two paths" is still better than "no."

Pitfall 7: Under-Investing in Close Management Tooling

Symptom: You track the close in a Google Sheet. Status updates live in Slack DMs. The audit trail of who did what when lives in your head and your sent folder. When somebody on the team is out, the close stalls because nobody else knows the current state.

The number: Ventana Research data on close maturity shows teams without close management software run two to three days longer and lose around 20 percent of close hours to status-chasing. For a typical mid-market finance team, that's roughly $80K to $120K a year in pure status overhead, before you count the close days you can't compress without visibility.

Why it happens: Close tools cost money. Your CFO sees them as a nice-to-have. The Google Sheet is free and "good enough." Also, building the business case feels like extra work you don't have time for, which is a great example of the same trap eating itself.

The fix (60-90 days): Build the business case for a close tool. Payback typically lands at four to seven months in finance hours saved, not counting audit fee reduction or close compression. Frame it three ways: hours saved (concrete, easy to model), control improvement (audit fees and SOX coverage), and risk reduction (key-person dependency on you specifically).

Don't pitch the most expensive option. Pitch the one with the cleanest implementation path and a six-month payback. Get a pilot on the cash recon and one accrual area. Show the CFO the time savings after one full close. Expand from there. The product names matter less than the discipline of getting your close out of a sheet and into something with role-based access, audit trail, and dependency tracking.

If the CFO still says no, move the close tracker to a project management tool you already pay for. Even a free Trello board with columns for "open / in review / signed off" beats a status-DM culture.

Self-Diagnostic: Where Are You Bleeding?

Score yourself 0 to 2 on each pitfall. Zero means clean. One means you have the habit but it's contained. Two means it's actively hurting you.

Total 0-3: You're fine. Pick the highest single score and fix it next quarter. Total 4-7: Typical mid-tenure controller. Pick two pitfalls. One operational (1, 4, or 7), one relational (5 or 6). Fix one per quarter. Total 8 or higher: Stop reading. Stop optimizing. Pick the single highest score, block your calendar this week, and start the 30-day fix Monday. Anything else is rearranging deck chairs.

What Promoted Controllers Actually Do

The controllers who get the VP Finance call aren't the ones who never hit these traps. Everybody hits them. The promoted ones name the trap out loud, in their own one-on-ones, before their CFO has to. Then they fix one per quarter. Four traps a year. Two years from now you've systematically moved through all seven and your CFO has watched you do it.

That's the move. Not heroics. Not a new framework. Not waiting for the next system implementation to fix everything. Pick the pitfall with the highest score. Block the calendar. Start Monday. Tell your CFO what you're doing and why. Show them the number after 60 days.

The finance org that respects you is the one that watches you turn a habit into a system. Do that seven times and you're not a controller anymore.

Learn More

• Controller Job Description Template
• Month-End Close Checklist for Controllers
• How Controllers Partner with FP&A
• Audit Prep Calendar for Controllers