Audit Support Services: Adding Capacity for an Audit While Your Team Leads

What Audit Support Services Cover

Audit support services cover four work streams for the company being audited: the request list, reconciliations, supporting schedules, and auditor questions during fieldwork. That reader distinction matters, because search results for this term mix two different buyers. One is a company whose financial statements are under audit. The other is a CPA firm sending its own audit fieldwork outside. This is about the first one.

The auditor writes the list. Your company prepares it.

• The request list. The auditor issues an itemized ask for documents, schedules, reconciliations, contracts, board minutes, system reports and sample populations. It’s commonly called the PBC list, short for prepared-by-client. PBC list support, then, means capacity against a list the auditor wrote and your company owns. Much of that work is ownership and tracking rather than accounting. A named preparer and a named reviewer per line, one authoritative version, a status per line, and a log of what went to the auditor and when. Teams lose more days to version confusion and unanswered lines than to the accounting itself.
• Reconciliations. Cash and credit cards, intercompany, accounts receivable and accounts payable aging tied to the general ledger, payroll clearing accounts, accrual support, prepaid amortization, deferred revenue, and fixed assets. The deliverable isn’t a spreadsheet. It’s a balance that ties to the trial balance, with the difference explained and documented well enough that someone else could repeat it.
• Supporting schedules. Lead schedules by account, rollforwards for the balances that move, tie-outs from each schedule back to the trial balance, and the populations the auditor samples from. Rollforwards are where outside capacity usually earns its place, because they’re mechanical, they’re documented, and they don’t need institutional memory once the source reports are identified.
• Auditor questions during fieldwork. This is the stream companies under-scope most often. Once fieldwork starts, selections, document pulls, variance explanations and follow-up questions arrive continuously, and they land on whoever built the underlying schedule. Scope against the opening list alone and the second wave has no owner.

What audit support isn’t: the audit, an opinion, a sign-off, or an independent review of your records. The independent auditor performs the audit. Audit support prepares what the auditor asks for.

It also isn’t your auditor’s own staff, and that’s a rule rather than a preference. In the AICPA Code of Professional Conduct, the Nonattest Services subtopic at ET sec. 1.295 sits under the Independence Rule at ET sec. 1.200.001 and governs what an audit firm may do for a company it audits. A 2021 AICPA interpretation, Staff Augmentation Arrangements at ET sec. 1.275.007, permits a brief, non-recurring loan of a firm’s own staff to an attest client only under narrow conditions, and the Journal of Accountancy walked through those conditions in 2022. Read practically, extra hands come from somewhere other than your auditor.

If what you need is the readiness work itself, our audit readiness checklist walks that ground line by line. This piece answers the adjacent question. Who prepares it, and how the work gets split.

When an Audit Outgrows Your Finance Team

An audit outgrows your finance team when the audit calendar and the close calendar overlap and the same people own both. That’s a structural condition, not a performance problem. A controller who runs a clean monthly close can still be unable to absorb a request list on top of it. The close doesn’t pause for fieldwork.

Six triggers create the overlap.

• A first audit. A lender, a capital provider, a board or a grant funder has asked you to ready audited numbers, which means getting the books, the reconciliations and the reporting into shape for someone outside to examine.
• A recurring annual audit that got bigger. A new revenue stream, an acquisition, new locations or states, or a new system all add lines to the list.
• A calendar collision. For a December year end, fieldwork sits in the same weeks as year-end close, 1099s, W-2s, property tax filings, insurance renewal and budget season.
• A vacancy or a leave during fieldwork. The work doesn’t wait for the seat to be filled.
• Records that need a cleanup before anyone outside the company looks at them.
• A mid-year system change. The audit then spans two systems, two sets of reports and sometimes two chart-of-accounts versions, and every rollforward has to bridge the cutover.

The signals are easy to read. Request-list lines with no named owner. Reconciliations being prepared for the first time for the audit instead of monthly. The close slipping in the month fieldwork started. One person owning more than half the list. A prior-year audit that ended with a long list of adjusting entries. Prior-year workpapers nobody can locate. Any two of those together is your answer.

Hiring is usually the wrong lever for a dated peak. The U.S. Bureau of Labor Statistics Occupational Outlook Handbook for accountants and auditors, last modified August 27, 2026, projects 5 percent employment growth in the occupation from 2025 to 2035, faster than the average for all occupations, with about 115,300 openings a year over the decade. Most of those openings come from workers transferring to other occupations or leaving the labor force. Read operationally, that’s a market where openings are driven mainly by turnover, and it’s the market you enter when you post a role to cover a dated peak. The peak has a date. A search doesn’t.

Getting outside help preparing for an audit is permitted and ordinary, which is worth saying plainly, because the independence rules that bind your auditor get misread as binding you. Outside audit support is how a lot of lean teams absorb the peak without adding a permanent seat.

When a controller, accounting or specialist seat is empty or a deadline outgrows the team, indinero can match a professional to the role, so you skip a lengthy hiring cycle. If you’re still working out which seat your company needs permanently, what a controller, comptroller and CFO each own sorts the roles out before you write a job description.

Where Audit Support Fits

Audit support fits wherever your own team directs the work and simply needs more hands or one missing skill. If you want a finance function run for you rather than supported, that’s a different model, and what finance as a service covers explains it. Ongoing strategic finance leadership sits with indinero’s CFO services, and an ongoing outsourced controller layer that already absorbs audit prep inside the engagement is its own arrangement rather than added capacity. The test is who directs the work.

How to Scope Audit Support Around the Request List

Scope audit support against the auditor’s actual request list, line by line, with a named preparer and a named reviewer on every line. Scoping by a block of hours or a general promise of help is the failure mode, because it leaves the handoffs undefined and sends the auditor documents nobody inside the company reviewed. Good audit support for finance teams is scoped against the list.

1. Start from the real list. Pull last year’s request list and the auditor’s current-year list. For a first audit, ask the auditor for the list before you scope anything. The list is the specification. Prior-year adjusting entries and unresolved items belong in the same pile, because they predict this year’s hard lines.
2. Classify every line into four buckets. Only our team can do this, for anything carrying management’s own judgment or assertion: estimates, reserves, impairment conclusions, policy decisions, related-party disclosure, going-concern input and the representation letter. Either could, but we’re faster, for lines that depend on contract history, customer context or a conversation with a department head outside finance. Mechanical and documented, for reconciliations, rollforwards, tie-outs, schedule building, document pulls, population extracts and formatting. That third bucket is the scope. Not ready, for lines that need correcting before they can be prepared at all, which is a separate scope item from audit prep and the reason catch-up bookkeeping sometimes has to come first.
3. Put a preparer and a reviewer on every line. The outside professional prepares. Your controller reviews and approves before anything reaches the auditor. Keep that review step even when it feels like friction. It’s what keeps your company owning its own numbers.
4. Name one internal contact for the auditor. Every submission goes through that person. A single channel prevents duplicate answers, conflicting file versions and unapproved documents landing in the audit file, and the auditor always knows who to ask. The outside professional can join fieldwork calls with your contact present, which beats relaying questions, and your contact stays the channel of record.
5. Scope the second wave on purpose. Agree in writing, before fieldwork, who takes selections and follow-up requests. Default them to whoever built the underlying schedule, since that person already has the source reports open.
6. Define artifacts, not effort. A reconciliation file per account, a rollforward per moving balance, a tie-out to the trial balance for each, a submission log, and a request-list tracker with owner, reviewer and status per line. Artifacts are checkable. Effort isn’t.
7. Scope the access, read-only where it works. Name the systems, the permission level and who approves access up front, because the same list becomes the revocation list at handback. Our note on security in an outsourced accounting engagement covers what to ask for.

The first bucket is where independence actually bites. Management has to accept responsibility for the results of any nonattest service, and designate a person with suitable skill, knowledge or experience to oversee the work, determine its scope, supervise it and evaluate the results. Those are the AICPA’s general requirements at ET sec. 1.295.040, explained in a Journal of Accountancy walkthrough from 2016, with the companion rule at ET sec. 1.295.030 holding that the auditor can’t assume management responsibilities.

Companies that file with the SEC sit under tighter constraints, in SEC Regulation S-X Rule 2-01 and PCAOB Rule 3520. None of it changes who owns the numbers. Your own auditor is the only right source for your own facts, so ask them before you engage anyone.

An indinero controller can take on reconciliations, payables and audit schedules inside your process, while your team keeps its priorities.

A worked example helps, and the company in it is fictional. Northline Fabrication doesn’t exist, and these counts are illustrative rather than a benchmark. Northline has a December year end and receives a 120-line request list. The in-house team keeps 72 lines, 60 percent, because most of them carry management judgment or sit with the two people who hold the contract and customer history. The outside professional takes 48 lines, 40 percent, and roughly three quarters of those are reconciliations, rollforwards and tie-outs. During fieldwork another 45 follow-up requests arrive, and because the routing rule was agreed in advance, about 60 percent of them go to the outside professional as document pulls against schedules that professional already built. The controller reviews and submits all 165 items through one channel.

How to Hand Audit Work Back to Your Team

Hand audit work back as a defined deliverable: final schedules, reconciliation notes, open items, and the access list to revoke. Agree what the handback contains before the engagement starts, not after the opinion is issued. The work product isn’t only the schedules you submitted. It’s the schedules plus everything your team needs to rebuild them next year without the same outside help.

1. Schedules, findable and final. Every schedule in a named, versioned location inside your own storage, with an index, and with the final version matching exactly what the auditor received. A file-naming convention agreed on day one costs nothing and saves a week next year.
2. Reconciliation notes that record method, not just output. Where the data came from, which report, which parameters and date ranges, which filters, what judgment was applied, and which exceptions recur and why. Written so next year’s preparer can repeat the work instead of reverse-engineering a spreadsheet.
3. Open items as of the handoff. Anything unresolved, with the auditor’s current position, what’s still outstanding and who the auditor last spoke to about it. Nothing should surface after the engagement that was known during it.
4. The access list to revoke. Every system, login, shared drive, email alias and auditor portal account. Revoke on a named date, confirm it in writing and keep the documentation, because provisioning and deprovisioning user access is itself a control an auditor may test next year.
5. The tracker and submission log in final state. Next year’s planning should start from the real record of what was asked, what was prepared and what took longest, not from memory.

Your team reviews and owns each item before the outside professional steps away. That last review is the whole point of the arrangement. Your company keeps control over priorities and day-to-day management the entire time, and the knowledge stays in-house when the work ends.

The best handback output is a shorter list next year. Any reconciliation or rollforward that got built for the audit and didn’t previously exist monthly is a candidate to become a standing close step. Convert even a handful of them and the next request list shrinks structurally, which is the quiet argument for running a disciplined month-end close checklist in the first place.

How Indinero’s On-Demand Finance Support Works

Indinero matches a finance professional to a defined role inside your existing process, and your team keeps directing the work. The service is access to experienced finance professionals who support specific projects, initiatives or operational needs without requiring a fully outsourced finance function. For an audit, the initiative is the audit and the project is the request list.

It runs in four steps. Define the role, aligning on your current priorities and what the role has to cover. Match a professional who integrates into your existing workflows and systems. Support the work. Scale up or down as the need changes.

Indinero provides CFOs, controllers, accounting professionals and finance specialists, and the mix depends on the need and the scope of the engagement. For an audit that usually means controller-level and accounting hands on reconciliations, supporting schedules and the request list, with your controller still reviewing and submitting. CFO-level support is available for a defined initiative, while ongoing strategic finance leadership is a separate engagement rather than part of audit capacity.

Indinero’s professionals work within your existing systems and processes, so your team doesn’t change how it operates to get help.

Two things worth stating plainly. Indinero supports audit preparation, and your independent auditor performs the audit. And timing depends on the role and scope, which is why the scoping conversation comes before any commitment about who takes which lines. The firm behind the role matters when it’s working inside your general ledger during fieldwork. Continuous operations since 2009. Stable ownership. SOC 2 compliant (2026).

That’s what audit support services look like when your own team stays in charge. An audit doesn’t have to be the month your close slips. If the request list is bigger than the hands you have, indinero’s on-demand finance support is built for exactly that gap, and the next step is a short conversation about which lines you’d hand over and which ones stay with your team. Talk to an expert about the split before fieldwork starts.

Frequently asked questions

These are the questions owners and finance leaders ask most often when an audit is on the calendar and the team is already full. Short answers below.

Does audit support replace the independent auditor?

No, audit support doesn’t replace the independent auditor, who performs the audit and forms the opinion on your financial statements. Indinero adds capacity on your company’s side of the engagement, covering the request list, reconciliations and the supporting schedules the auditor asks for. The two roles stay separate by design, so your controller still reviews and submits everything before it reaches the auditor.

Who should prepare the PBC list, the in-house team or outside help?

Preparing the PBC list is your company’s responsibility either way, and the practical answer is to split it by who holds the knowledge. Your in-house team keeps the lines that need management judgment and institutional context, including estimates, reserves, policy decisions and anything touching contract or customer history. Outside help takes the schedule-building and reconciliation volume, and your team reviews everything before it goes to the auditor.

Can the firm that audits us also prepare our schedules?

Generally no, because your audit firm can’t assume management responsibilities for a company it audits. The AICPA’s nonattest-services rules at ET section 1.295 limit what an audit firm may do for its own attest client, and its staff-augmentation interpretation permits only a brief, non-recurring arrangement under narrow conditions. Public companies sit under stricter PCAOB and SEC rules, so put your own company’s question to your own auditor.

Who should answer the auditor’s questions during fieldwork?

One named internal contact should route the auditor’s questions, and management answers anything that requires judgment or a representation. A single channel prevents duplicate answers, conflicting file versions and unapproved documents landing in the audit file, and the auditor always knows who to ask. An indinero professional can produce support and reconcile detail behind that contact, and can join fieldwork calls, but never speaks for management.

What should we have ready before audit support begins?

Before audit support begins, have the prior-year request list, your trial balance and close status, completed reconciliations, and the open items you know about. Add a defined scope, so everyone knows which lines outside help takes and which ones stay with your team, plus decisions on system access and who approves it. For a first audit with no prior list, ask your auditor for the current-year list before scoping anything.

Is audit support worth it for a recurring annual audit?

Audit support can be worth it for a recurring annual audit, which is a known, repeatable surge on a team that closes the month. Each cycle leaves reusable schedules, reconciliation notes and a submission log behind, so your in-house team carries more of the list next time. The value is capacity and documentation, not a cleaner opinion or a shorter audit, and any reconciliation built for the audit is a candidate to become a standing close step.