How to hire a bookkeeper (job description, interview questions, screening workflow)

A bookkeeper sees more of your business than almost anyone you hire, before you've verified anything about them. They see what the owner actually draws, what the team actually gets paid, which invoices you're quietly stalling on, and where the business really stands versus how you describe it to a lender. A charming interview and a resume that name-drops QuickBooks tell you almost nothing about whether someone can be trusted with that, or whether they can actually close a set of books instead of just entering what's put in front of them. This guide screens for the two things that matter here: real bookkeeping judgment, not software familiarity, and the discretion to handle what they'll see.

What a bookkeeper actually does at a small business

At a company large enough to have a finance department, a bookkeeper is one link in a chain. A controller reviews their work, a payroll specialist runs payroll, an AP clerk handles vendor invoices, and an outside auditor checks all of it once a year. Errors get caught by someone else before they matter.

At a business with a couple locations and a handful of people, there's no chain. The bookkeeper is the entire back office short of filing taxes. They record every transaction, reconcile every account, run payroll for the crew, and hand the owner a P&L that's the closest thing to ground truth the business has. Nobody reviews their work before it becomes the number the owner makes decisions on. If they miss something, it doesn't get caught downstream. It just becomes wrong, and the owner finds out three months later when the CPA asks a question nobody can answer.

That's what makes this hire different from most others on a small team. It looks like a data-entry role from the outside, and a chunk of the daily work is data entry. But it's really a trust role: someone with real, structured judgment about where the money is actually going, who can also be handed sensitive information, payroll numbers, owner draws, margins, and keep it exactly where it belongs.

The core responsibilities, in practice:

• Recording and categorizing every transaction across every account, not just the easy ones
• Reconciling bank and credit card accounts every month, and tracking down discrepancies until they're actually explained
• Processing payroll for the team, including overtime, tips, or multi-location wage rules where they apply
• Managing accounts payable and receivable: paying vendors on time, chasing late invoices, catching duplicate or incorrect charges
• Producing a monthly P&L and balance sheet the owner can actually read and use to make a decision
• Flagging cash flow problems early, since there's no CFO watching runway behind them
• Handling sensitive financial data, the owner's and the team's, with real discretion
• Working directly with the outside CPA or tax preparer at year end, and whenever they need something pulled from the books

If you want the deeper breakdown of where a bookkeeper's job ends and an accountant's or controller's begins, our guide to hiring a bookkeeper covers that distinction in more depth. This page assumes you already know you need a bookkeeper and gets you straight to the posting, the interview questions, and the screening workflow.

Job description you can post today

Copy this, then adjust the specifics (your software, your hours, your pay) to match your business.

Bookkeeper
[Company name] is looking for a bookkeeper to keep our books accurate and current, so we always know where the business actually stands. You'll own transaction recording, reconciliations, and payroll for the team, and be the detail person we count on to catch what would otherwise slip through.

What you'll do
Record and categorize transactions across all accounts and keep the books current, not just caught up once a quarter. Reconcile bank and credit card accounts every month and track down every discrepancy until it's explained. Process payroll accurately and on schedule, including any overtime, tips, or multi-location wage rules that apply to our team. Manage accounts payable and receivable: pay vendors on time, chase down late invoices, and flag anything that looks off. Prepare a monthly P&L and balance sheet we can actually read and use to make decisions. Handle sensitive financial information, ours and our team's, with real discretion. Work directly with our outside CPA or tax preparer at year end and whenever they need something from the books.

What we're looking for
Real, hands-on experience with [QuickBooks / Xero, name your platform], not just familiarity. A track record of owning a monthly close and reconciliation process end to end, not just entering transactions someone else reviews. Comfort working with sensitive financial data and a clear sense of what stays confidential. Strong attention to detail and a system for catching your own mistakes before they compound.

Schedule
[Insert hours, e.g. part-time 20 hours/week or full-time Monday-Friday, in-office or remote]

[Insert pay, per your company's policy and any applicable state salary transparency requirements]

12 interview questions, and what a good answer sounds like

1. Walk me through your month-end close, start to finish, at the last place you did it solo.

You're checking for a real sequence, not a list of tasks. A strong answer moves in order: reconcile the bank and credit card accounts, review outstanding AP and AR, check payroll clearing accounts, run the P&L and compare it against last month for anything that looks off, then close the period. A candidate who describes the close as "entering everything and sending it to the accountant" hasn't owned one. That's the gap this question is built to catch.

2. Tell me about a reconciliation that didn't balance and took real digging to fix.

Listen for a specific example with a real cause: traced a discrepancy to a duplicate entry, an amount entered wrong, a transaction that hit the bank but never made it into the ledger. "I just kept looking until it matched" is a weak answer with no method behind it. A candidate who can name the actual detective work is telling you they'll catch the next one too, not just this one.

3. What's a feature in QuickBooks or Xero you had to learn the hard way, not just one you use casually?

This separates software familiarity from real fluency. A strong answer names something specific and ties it to a real problem: setting up class tracking to separate revenue across two locations, or building a bank rule so recurring transactions stop getting double-counted. "I use it for invoicing and reconciling, basically the normal stuff" is the answer of someone who's used the software, not mastered it.

4. This role sees the owner's draws, what the team gets paid, and margins before almost anyone else. Tell me about a time you had to keep something confidential, even when someone pushed you on it.

Discretion isn't optional here, and it's hard to coach after a bad hire is already inside your books. A strong answer names a specific instance and the boundary they held. A candidate who can't produce an example, or who volunteers specific numbers from a past employer to make the point, has just shown you exactly how they'll handle yours.

5. Tell me about a time an owner or manager pushed back on how you categorized or handled something. What did you do?

You want someone who holds their ground professionally when they're right, and can explain why in plain language rather than accounting jargon. A weak answer caves immediately regardless of the facts, or gets defensive and makes it personal. Either one is a problem in a role where the owner will disagree with them again.

6. Say you inherited books that hadn't been reconciled in three months. Where do you actually start?

This comes up constantly at small businesses bringing on their first real bookkeeper, or replacing one who let things slide. A strong answer triages: reconcile the bank accounts first to establish a clean baseline, work backward transaction by transaction from there, and flag anything that needs the owner's input before proceeding rather than guessing. "I'd probably just start fresh going forward" is a red flag. It leaves whatever's wrong in the old numbers exactly where it is, including anything that already fed a tax filing.

7. Walk me through how you'd process payroll for an hourly crew, including overtime.

For a business running a crew or shift workers, this is core to the job, not a side task. A strong answer describes verifying hours before running payroll, applying overtime rules correctly, and catching a timesheet that looks off before it becomes a wrong paycheck. "I just run it through the software" without describing any verification step tells you they'll trust the input blindly, which is exactly where payroll errors come from.

8. Tell me about a mistake you made in the books and how it got caught.

Every bookkeeper who's done real work has made a real mistake. A strong answer owns it specifically, describes how it was caught, whether by them or someone else, and names something that changed afterward, a new check step, a different process. A candidate who claims they've never made one, or immediately shifts blame elsewhere, is either inexperienced or not being honest with you, and neither is what you want in this hire.

9. An invoice comes in from the same vendor twice, three weeks apart. What's your process for catching that before it gets paid?

Listen for an actual system: checking vendor payment history or invoice numbers before approving payment, not just "I'd probably notice." A candidate with real AP experience will describe a habit, not a hope. This is a small, concrete question, and the concreteness is the point.

10. If I asked you to hold a vendor invoice out of this month's books and record it next month instead, so the numbers look stronger for a loan application, what would you say?

This is an integrity test dressed up as a scenario, and it's a realistic one. A strong answer holds the line without turning it into a lecture: something like "I can't do that, because it makes the numbers wrong for the bank, and if it surfaces later that's a real problem for both of us. Here's what I can do instead." A candidate who agrees, or hedges instead of naming the problem directly, is telling you exactly how they'll handle the next request like this one, and there's always a next one.

11. What's your system for keeping track of payroll tax deadlines and other recurring filings, so nothing slips?

You want a concrete system, not a personality trait. A strong answer names something specific: calendar reminders set at the start of the quarter, relying on the payroll software's built-in filing calendar plus a manual double-check, a running checklist reviewed monthly. "I just know when things are due" is not a system, and a missed payroll tax deadline costs real money in penalties.

12. What's the difference between someone who's good at QuickBooks and someone who's actually a good bookkeeper?

This is the question that gets at everything the others are circling. A strong answer names judgment: understanding why an entry is made, not just how to make it, noticing when a number doesn't look right, knowing when something needs to go to the owner instead of being decided alone, and holding the line on confidentiality. A candidate who struggles here, or reduces the answer to "knowing the software really well," has just told you which one they actually are.

A scorecard you can score candidates against

Twelve questions only help if everyone interviewing is listening for the same thing. Score every candidate on the same six signals instead of comparing gut feelings about who sounded most confident.

How to screen bookkeeper candidates without losing a week to it

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, so you can build a workflow that matches how much trust this specific hire carries.

Unlike a role where the biggest risk is a disappointing hire you notice within a week, a bad bookkeeper hire is a risk you might not discover for months, once the numbers you've been making decisions on turn out to be wrong. That changes how much verification is worth doing before someone gets real access to your accounts. A workflow that fits a small business:

• Resume review, weighted toward scope over polish. Look past job titles for detail on transaction volume, whether they owned the full close or assisted with pieces of it, and which software they actually used day to day. Resume screening software surfaces the candidates whose experience actually matches your scope, so you're not reading every application yourself.
• A one-way video interview before you schedule a call. Ask 2-3 of the scenario questions above on video. The month-end close walkthrough and the discretion question both work well this way, so you can hear how someone actually explains their process before you commit live time. A one-way video interview shows you communication and judgment in a way a resume never will.
• A skill-based accounting assessment before the live interview, not after. A resume can claim QuickBooks fluency. A structured work sample, a reconciliation with intentional discrepancies, a journal entry to check for errors, actually tests it. Our skill-based accounting assessment is built around exactly that kind of evidence, scored the same way for every candidate.
• A reference check that asks specifically about accuracy and discretion, not just "would you rehire them." Ask a past manager directly whether the books stayed clean under this person and whether they could be trusted with sensitive information. Given what this hire will see, this step earns its time before an offer, not after.
• A short paid trial task for finalists, on your actual books if you're comfortable with that, or a close simulation if you're not. This is where the earlier signals get confirmed against the real thing instead of a sample.

AI surfaces the evidence, resume matches, video responses, assessment scores, side by side, so you're not piecing it together from memory. It doesn't decide who gets the job. You review it and make the call, especially on a hire where the cost of trusting the wrong person shows up in your books, not just your calendar.

3 questions from the skills check we'd actually run for this role

A skills check for a bookkeeper only means something if it tests the actual work, not trivia about accounting terms. These three are adapted from Truffle's skill-based accounting assessment, scaled down to the kind of numbers you'd actually see running a small business's books. Try them yourself before you decide what "qualified" means for your opening.

The point isn't these three questions specifically. It's that a structured skills check like this surfaces real bookkeeping judgment, which is a far harder signal to fake than a resume line about years of QuickBooks experience. Truffle's AI scores and surfaces the results against the bar you set. You still make the call on who clears it.

Common hiring mistakes for this role

Testing for software speed instead of bookkeeping judgment. A candidate who can fly through data entry in QuickBooks isn't the same as one who catches a miscategorized expense or notices a number that doesn't look right. If your only test is how fast someone can enter ten transactions, you're screening for the wrong skill. Test whether they understand why an entry is made, not just how quickly they can make it.

Handing over bank logins and payroll access before verifying anything. It's tempting to get a new hire set up and productive on day one, but this is one of the few roles where "productive" means real access to your money and your team's pay information. Verify the skill and check a reference before you hand over that access, not after.

Skipping the work sample and deciding on interview charm alone. A confident, personable interview tells you almost nothing about whether someone can actually find a reconciliation error or catch a duplicate invoice. Those are the job. A short work sample, even 30 to 45 minutes, tells you more than an hour of pleasant conversation ever will.

Not writing down the real scope before you post the role. "Bookkeeper" covers everything from basic transaction entry to a full-charge role that owns payroll and month-end close. Post a vague title without naming the actual scope, and you'll get a pool that doesn't match what you need, and you won't find out until the person is a few weeks in and the work isn't landing at the level you assumed.

Rushing past the reference check because you're short-staffed. This is one of the roles where a reference check earns its time, specifically asking a past manager whether the books stayed accurate under this person and whether they could be trusted with sensitive information. Skipping it to fill the seat faster is exactly how a business ends up finding a problem three months in, when the numbers stop adding up.