You wrote a Controller job description. Most of it is standard: month-end close, financial reporting, GAAP, audit prep, managing a small team.
Then there's one line near the bottom. Something like: “experience implementing or managing our ERP (NetSuite, Dynamics, or similar).”
That line looks like a nice-to-have. It's the most important sentence in the whole document, and it quietly changes what you're actually searching for.
Why that one word matters
A Controller who runs a clean close is one kind of hire. A Controller who can own an ERP, configure the modules, lead a migration, get every department onto the new system, is a different kind of hire. The two skill sets live in different people far more often than they overlap.
When “ERP” shows up in a Controller JD, it usually means one of two things. Either you're mid-implementation and need someone who can drive it, or your books and systems are tangled enough that reporting and the platform can't be separated anymore. Both cases need the systems side as much as the accounting side.
Treat that word as a footnote and you'll hire a strong Controller who freezes the moment they're asked to own the system. The close stays clean. The implementation stalls.
What most recruiters do
They read the title, “Controller,” and run a standard Controller search. The ERP line becomes a checkbox: does the resume say NetSuite somewhere? If yes, move to the shortlist.
The problem is that “NetSuite” on a resume covers two very different people. One configured the inventory and purchasing modules for a manufacturer and led the data migration. The other ran reports in a system someone else built. Both write “NetSuite.” Only one gets you through go-live.
“The word ERP in a Controller JD is a systems hire wearing a finance title.”
What to do about it instead
Decide which side of the role is really driving the hire. If the business case is the system, you need someone who thinks like a finance person and happens to know the platform cold. If the books come first and the ERP is secondary, say so, and don't over-index on systems experience you won't use.
Then test the ERP claim in conversation, not on paper. Ask the candidate to walk through a real implementation they led: which modules, what the timeline was, what broke during migration, how they handled the cutover. Someone who has done it answers in specifics. Someone who has used the system reaches for generalities.
That combination, a finance leader who can genuinely own the system, is a specific and thin search. It rewards a recruiter who understands both halves. It punishes one who treats it as a normal Controller hire with a keyword attached.
The one-line test
Before you post the role, read your own JD and find the ERP line. Then ask yourself one question: do I need someone who keeps the books clean, or someone who can also own the system that produces them? If it's the second, you're running a harder search than the title suggests, and it's worth treating it that way from day one.
About ICA
I'm April Ben-Sabat, founder of Inner Circle Agency. I built my career in finance, accounting, HR leadership, and industrial operations before starting ICA. ICA recruits for the roles I used to hold, so our team evaluates candidates the way a board would, because that operational experience is baked into how we work.
ICA is boutique by design. We take on a small number of searches at a time so every client gets senior-level attention. We specialize in Director-to-C-Suite placements across finance, ERP, and operations for mid-market companies in the US.
If you're hiring for a role where the wrong person costs you a year of momentum, let's talk.
Frequently asked questions
What does “ERP experience” mean on a Controller resume?
It can mean two very different things: someone who configured and implemented the system, or someone who simply used it for reporting. Both list the platform by name. The difference only surfaces when you ask them to walk through a real implementation in detail.
Should a Controller own the ERP implementation?
Only if they have specific implementation experience. A Controller who is already running close, audit, and reporting is stretched. Adding a full system rollout on top usually means either the books suffer or the implementation does. The companies that get it right hire for that combination deliberately, or bring in a dedicated implementation lead.
How do you hire a Controller with real NetSuite experience?
Screen for the implementation, not the keyword. Ask which modules they configured, what the data migration involved, and what they would do differently. Specific, detailed answers signal someone who led the work. Vague answers signal someone who used a system others built.
Why is a Controller with ERP experience hard to find?
The finance side and the systems side rarely live in the same person, and the ones who have both are usually employed and not job-hunting. It's a thin, specific search that a generalist recruiter tends to treat like a standard Controller hire.