The short answer
A sound outsourced accounting engagement defines who prepares, reviews, approves, and owns each recurring responsibility. It separates transition or cleanup from recurring work, names the reports and timing expected, preserves company authority over payments and access, and explains how additional requests will be approved. Fees then follow the volume, book condition, structure, systems, deadlines, complexity, coordination, and level of professional review involved.
Key takeaways
- For each process, name who prepares, reviews and approves the work, when it is due, the records to keep and what falls outside the scope.
- Separate initial assessment, cleanup, and implementation from the recurring monthly responsibilities.
- Keep payment release, banking authority, access approval, accounting judgments, and business decisions with company management.
- Assess fees using volume, book condition, entities, systems, timing, complexity, coordination, and professional review.
- Put competing proposals into the same format before comparing their fees.
“Outsourced accounting” can describe very different arrangements. One proposal may cover selected transaction work and the monthly close. Another may add controller review, management reporting, meetings, forecasting, or business-tax coordination. Those differences need to be visible before the fees can be compared.
Begin with the work already being performed, the capability of the internal team, and the information management needs each month. A capable bookkeeper may continue to manage daily records while an outside team assumes selected close, review, or reporting responsibilities. The guide to bookkeeper, controller, and outsourced accounting roles explains the staffing models. The Business Accounting & Tax relationship shows how recurring accounting and year-round business-tax coordination can be scoped together.
Put every recurring responsibility in writing
A responsibility matrix is a written list of who does what. Use the topics below to build one for the engagement: name the people or positions involved, record the agreed timing, and align the assignments with the engagement letter. Add or remove responsibilities as the business requires.
Responsibilities to agree before work begins. Open a topic below for details.
Source records and transaction coding
- Company responsibilities
- Accounting and operating staff supply complete source information and explain exceptions.
- Provider responsibilities, if included
- Record or review the assigned activity using approved coding rules.
- Who reviews
- Named accounting reviewer.
- Company approval or control
- Management approves policies and unusual treatment.
- Timing
- Agreed cutoff and processing calendar.
- Records to keep
- Source records, coding support, and exception log.
- Scope limits and additional requests
- Missing history, new activity, and cleanup follow the change process.
Vendor setup and payment-detail changes
- Company responsibilities
- The business owner initiates the request through an approved channel.
- Provider responsibilities, if included
- Document or route the request when assigned.
- Who reviews
- Internal reviewer independent of the request.
- Company approval or control
- An authorized company representative approves the change.
- Timing
- Before the first affected payment.
- Records to keep
- Request, verification, and approval record.
- Scope limits and additional requests
- Investigation or recovery work is addressed separately.
Payment preparation and release
- Company responsibilities
- The company confirms the obligation, amount, and business approval.
- Provider responsibilities, if included
- Assemble payment information or a payment file when assigned.
- Who reviews
- Designated internal reviewer.
- Company approval or control
- An authorized company representative releases funds and retains banking authority.
- Timing
- Scheduled cycle with defined exceptions.
- Records to keep
- Invoice, approval trail, payment batch, and release record.
- Scope limits and additional requests
- Urgent and off-cycle requests follow the agreed escalation path.
Monthly close and reconciliations
- Company responsibilities
- Account owners provide schedules, contracts, estimates, and responses to open questions.
- Provider responsibilities, if included
- Prepare assigned reconciliations and entries and maintain the close checklist.
- Who reviews
- Controller-level or other named reviewer.
- Company approval or control
- Management approves material judgments and significant nonroutine entries.
- Timing
- Agreed close calendar.
- Records to keep
- Reconciliations, schedules, review evidence, and open-item log.
- Scope limits and additional requests
- Backlog cleanup and unsupported opening balances belong in transition or an approved change.
Management reporting
- Company responsibilities
- Operating leaders provide agreed measures, explanations, and assumptions.
- Provider responsibilities, if included
- Prepare the specified statements, schedules, comparisons, and commentary.
- Who reviews
- Named reviewer checks consistency with the completed close.
- Company approval or control
- Management confirms operating information and owns the resulting decisions.
- Timing
- Agreed circulation and meeting dates.
- Records to keep
- Final package, variance support, open-item disclosure, and action log.
- Scope limits and additional requests
- Special third-party or transaction requests receive separate scope treatment.
Planning and advisory
- Company responsibilities
- Management supplies the questions and owns the operating assumptions.
- Provider responsibilities, if included
- Update agreed forecasts, prepare scenarios, or analyze performance.
- Who reviews
- Senior advisory role named in the scope.
- Company approval or control
- Management approves assumptions, selects actions, and remains accountable for results.
- Timing
- Recurring cadence plus approved event-driven work.
- Records to keep
- Assumption log, versioned analysis, and decision record.
- Scope limits and additional requests
- Daily executive authority and implementation ownership remain with the company.
Tax and external coordination
- Company responsibilities
- Management supplies complete facts and authorizes the communication.
- Provider responsibilities, if included
- Prepare agreed schedules or coordinate information within the defined scope.
- Who reviews
- Reviewer appropriate to the assigned work.
- Company approval or control
- Management approves elections, representations, and filings as applicable.
- Timing
- Agreed tax or external-request calendar.
- Records to keep
- Supporting schedules, authorizations, request log, and confirmations.
- Scope limits and additional requests
- Tax preparation, legal work, and audit or attest services require their own defined scope.
The written assignments show how the teams will work together. A provider may supplement the existing team or assume selected responsibilities. The matrix makes clear who prepares, who reviews, and which approvals remain with the company.
Build the recurring scope by layer
Transaction and record support
The scope may assign transaction coding, invoicing support, payable processing, payroll entries, or record organization. It should also name the source information the company must supply, the cutoff for that information, the exception process, and the person who resolves missing or unclear support.
Monthly close and reconciliations
A recurring month-end close process should identify the accounts and schedules included, who prepares and reviews each item, and how unresolved matters are reported. The engagement scope should state which parts of that process each party performs.
Management reporting and controller review
The proposal should name the financial statements, schedules, comparisons, and meeting cadence included. The guide to a monthly management reporting package explains how reports can connect results to cash, outlook, and follow-up. Controller review may cover reconciliations, unusual transactions, reporting consistency, and discussion with management.
Planning, advisory, and tax coordination
Forecasts, scenarios, decision analysis, and business-tax coordination require their own responsibilities, inputs, and review. The comparison of controller support and fractional CFO advisory helps distinguish the accounting foundation from forward-looking decision support. The engagement letter should state which capabilities are included and how event-driven requests will be handled.
Keep approvals, authority, and accountability with management
Company management remains responsible for its records and information, accounting policies and judgments, financial statements, controls, approvals, representations, and business decisions. The scope should identify the people authorized to approve vendors, changes to payment information, payments, transfers, payroll, system access, and significant journal entries.
Payment work deserves particular precision. A provider may enter an approved invoice, prepare a payment schedule, or assemble a payment file when that work is assigned. An authorized company representative should review the required support and release the funds. The company retains banking authority and the ability to approve or revoke access.
The FBI recommends verifying changes in account numbers or payment procedures with the requester using independently obtained contact information. The FTC’s vendor-security guidance also supports limiting access to what a vendor needs and using multi-factor authentication. The accounts-payable controls guide covers the workflow in greater detail.
Give transition work its own scope
Recurring service begins from an agreed starting point. Unreconciled accounts, missing schedules, prior-period corrections, unreliable opening balances, integration problems, and undocumented workarounds can require a distinct transition before the monthly process reaches its intended cadence.
Transition phase
Define the periods, accounts, systems, and processes to be assessed; the known problems and assumptions; access setup and procedure documentation; completion criteria; and the person who accepts the work. The proposal should also explain how newly discovered matters will be described and approved.
For the practical sequence from records and access to the first close, see how to plan a move to outsourced accounting.
Recurring phase
Define the standing responsibility matrix, monthly cutoffs, close and reporting dates, management inputs, review cadence, and process for additional requests. If open transition items remain, record them along with their expected effect on the recurring process. The proposal should explain the fee treatment for each phase and for approved changes.
Connect the fee to the work
Consider two companies with comparable revenue. Company A has a defined internal process and relatively straightforward structure. Company B has more entities, systems, cleanup, specialized accounting, deadlines, and stakeholders. Their revenue is similar, while the work differs materially.
Two companies with similar revenue can need different levels of accounting support. Open a topic below for details.
Transaction volume
- Company A
- Stable monthly activity, a modest number of accounts, and an internal bookkeeper handling daily records.
- Company B
- Seasonal volume, more accounts and data feeds, and recurring transaction exceptions.
- What the proposals should clarify
- The activity assumptions, assigned processing, and events that trigger a scope review.
Structure and systems
- Company A
- One entity using a primary accounting system with a small number of connected applications.
- Company B
- Several entities or locations, multiple applications, intercompany activity, and inventory or project information.
- What the proposals should clarify
- Included entities, systems, reporting dimensions, integrations, reconciliations, and consolidations.
Starting condition
- Company A
- Books are current and material accounts have supporting reconciliations.
- Company B
- Historical accounts need support, reconciliations are incomplete, and process documentation is limited.
- What the proposals should clarify
- A separate transition phase, starting assumptions, completion criteria, and approval of discoveries.
Timing and frequency
- Company A
- A stable monthly close, a defined report package, and one management review.
- Company B
- Earlier stakeholder deadlines, seasonal peaks, several reports, and more frequent coordination.
- What the proposals should clarify
- Cutoffs, dependencies, reporting dates, meeting cadence, and treatment of time-sensitive requests.
Professional judgment
- Company A
- Activity and estimates are recurring and well documented.
- Company B
- Unusual transactions, estimates, debt, specialized accounting, or reporting judgments arise regularly.
- What the proposals should clarify
- The subject areas included and the preparation, research, consultation, and senior review expected.
People and coordination
- Company A
- The owner, bookkeeper, and provider form the main working group.
- Company B
- Several business owners, departments, locations, advisers, or external stakeholders contribute information.
- What the proposals should clarify
- Participants, handoffs, meeting responsibilities, issue ownership, and the escalation path.
Company A’s proposal may concentrate on recurring close and review. Company B’s proposal needs to address a larger transition, more data sources and reconciliations, tighter coordination, and more senior involvement. Those facts explain the difference in work before a fee is considered.
Put competing proposals into the same format
Translate each proposal into the same responsibility matrix and assign every row one of five statuses:
- included in recurring service;
- included in transition;
- retained by the company;
- conditional or separately approved; or
- excluded.
For each row, record the preparer, reviewer, approver, timing, evidence, assumptions, and fee treatment. Then resolve broad labels. “Monthly close” may cover selected entries in one proposal and a full set of assigned balance-sheet reconciliations in another. “Management reporting” may mean standard financial statements, or it may also include comparisons, cash information, commentary, and a management meeting.
Compare the fees after the open and conditional rows have been resolved. A lower total may reflect narrower work, fewer deliverables, a different starting assumption, or less senior review. A broader proposal may contain responsibilities the company already performs effectively. Comparing the same responsibilities makes those differences easier to see.
Review the scope as the business changes
Review the scope when the company adds or removes an entity or location, changes systems, materially changes volume, changes internal accounting staff, accelerates the close, adds recurring reports or meetings, introduces specialized accounting, or develops a pattern of requests outside the original calendar.
A scheduled scope review can also give both parties a regular point to confirm responsibilities, access, deliverables, timing, assumptions, and fee treatment. Document agreed changes so the responsibility matrix and the engagement letter continue to describe the same operating model.
Questions to resolve before signing
- Which responsibilities are assigned to the provider, and which remain with company personnel?
- Who prepares, reviews, approves, and owns each process?
- Which accounts, schedules, reports, meetings, entities, and systems are included?
- What information must the company provide, and by what cutoff?
- Where does payment preparation end and company authorization begin?
- What belongs in transition, and how will newly discovered work be approved?
- Which volume, timing, and complexity assumptions support the fee?
- How are additional requests authorized, and which events trigger a scope review?
Define the scope around the actual work
Client Accounting Services can complement an existing team or assume defined responsibilities across accounting operations, the monthly close, controller oversight, reporting, and selected advisory work. The written scope should make the monthly outcome, company inputs, provider work, approval points, and escalation path clear.
When the current responsibilities, systems, and problem areas remain unclear, an Accounting Operations Assessment can establish the facts before a recurring scope is written.
Frequently asked questions
How can a company compare two outsourced accounting proposals?
Put both proposals into the same responsibility matrix. Separate recurring work, transition work, company-owned responsibilities, conditional work, and exclusions. Record the deliverables, timing, required inputs, review level, assumptions, and fee treatment for each row before comparing the fees.
What should happen when transition work uncovers more cleanup?
The transition scope should state its starting assumptions, completion criteria, and approval process for newly discovered work. When additional cleanup is identified, the company and provider can document the affected accounts or periods, decide who will perform the work, and approve the timing and fee treatment before proceeding.
When should an outsourced accounting scope be reviewed?
Review the scope when entities, locations, systems, transaction volume, staffing, deadlines, reporting requirements, or specialized accounting needs change. Recurring requests outside the written scope are another signal. The review should address responsibilities, deliverables, assumptions, access, timing, and fee treatment together.