The candidate pool is narrower than it looks

Document intake, data entry, routing, and status tracking require real attention to detail — a mistake in a client file or a missed notification has consequences. But the work itself is repetitive and offers little variety or growth path. That combination filters out a lot of otherwise-capable candidates before you ever post the job: people who want detail-oriented work usually want it attached to a career trajectory, and this role often isn't one.

The tooling learning curve narrows it further

Add QuickBooks Online or Xero, a practice management system, and firm-specific intake conventions, and the effective candidate pool shrinks again. You're not hiring for "administrative skills" in the abstract — you're hiring for administrative skills plus a specific software stack plus accounting-adjacent judgment, and that combination is genuinely scarce.

You're competing with better-paying, less-repetitive work

The same detail-oriented, organized candidate who could do this job well can often earn comparable or better pay in less repetitive roles elsewhere — office management, operations coordination, even other professional services firms with more varied admin work. Accounting firms aren't offering a worse job on paper, but they're offering a more repetitive one, and that shows up directly in tenure.

Short average tenure in these roles isn't a hiring execution problem. It's what happens when a repetitive, high-stakes role meets a candidate pool that has better options.

The reframe

If the role is structurally hard to fill and structurally short-tenure, the fix isn't a better job posting or a higher signing bonus — it's removing the parts of the role that make it repetitive and low-growth in the first place. The SOP-driven pieces (intake, routing, notifications, status updates) are exactly the parts that don't need a person doing the same steps every time. What's left is work that's actually worth hiring for: judgment calls, exceptions, client relationships.

Related: Billable hours vs. admin overhead: what's actually eating your margin →