What to Audit in a Client's Financial Stack During Week One

In week one, a financial-stack audit is not a software-selection exercise. It is a fast, evidence-based way to determine whether the client can produce information that management can safely use for cash, payroll, resource allocation, hiring, and operating decisions.

For a fractional CFO, the risk is not simply that the ledger is untidy. The risk is accepting responsibility for a financial narrative before understanding how the numbers are created, changed, reconciled, and delivered. A polished dashboard cannot compensate for an unreconciled bank account, an invoice that was never issued, a payroll file controlled by a former employee, or a revenue report that means something different to sales and finance.

The first-week objective is narrower and more useful: identify the systems that matter, follow the critical data paths, confirm who owns each handoff, and surface the few conditions that require an immediate decision. The output should be a prioritized findings list with evidence, an owner, and a next action—not a vague maturity score or a recommendation to replace every tool.

Start with decisions, not applications

Before requesting credentials or exporting reports, ask what management must decide in the next 30 days. The answer tells you which parts of the stack deserve the earliest attention.

Typical questions include:

• How much usable cash is available today, and what is likely to happen before the next payroll?
• Which invoices are expected to convert to cash, and which are disputed, late, or not yet billable?
• Are payroll taxes, debt payments, rent, and other non-discretionary obligations visible on a calendar?
• How long does the close take, and which balances remain uncertain when leadership sees the results?
• Can the company explain revenue, gross margin, headcount, and customer performance using definitions that the leadership team shares?
• Who can move money, change vendor banking, run payroll, approve journal entries, or alter reporting logic?

These questions keep the audit anchored to operational decisions. A list of applications alone is inventory. A mapped chain from source data to a management decision is an audit.

Build a one-page system map

Create a simple working map before you evaluate individual tools. For each critical area, record the system of record, connected systems, primary owner, backup owner, frequency, and most recent successful reconciliation or review.

Area	System of record	Key handoff	Accountable owner	Evidence to request
Cash	Bank or treasury portal	Bank feed or manual import to ledger	Finance owner	Latest balances and reconciliations
Revenue	Billing, ERP, CRM, or commerce system	Invoice, credit, and collection flow	Accounting / sales operations	AR aging and recent invoices
Payables	AP tool, ERP, or bank bill-pay system	Approval and payment batch	AP / operations	AP aging and approval list
Payroll	Payroll provider	Journal entry and tax calendar	People / payroll owner	Pay calendar and last payroll register
General ledger	Accounting or ERP system	Close checklist and reporting exports	Controller / bookkeeper	Trial balance and close status
Reporting	Spreadsheet, BI tool, or ERP reports	Manual transformations and review	Finance leader	Latest management package

Do not assume one system has one owner. In smaller companies, an outside bookkeeper may own the ledger, an operations manager may own vendor setup, and a CEO may hold the bank token. The map should show the real operating model, including external parties and personal accounts where access is still tied to an individual.

Audit cash first

Cash is usually the first financial output that can create an immediate operating consequence. Confirm what “cash available” means before relying on any reported number. It may exclude pending wires, restricted balances, payment-processor reserves, uncleared checks, debt-service sweeps, or intercompany transfers.

Cash checklist

• List every operating, payroll, savings, merchant, and treasury account.
• Confirm the latest balance date and time for each account.
• Compare the latest reconciled ledger balance with the bank balance and identify timing items.
• Identify payment platforms, merchant reserves, lockboxes, and wallets that hold material cash.
• Review the payroll calendar, debt schedule, tax deposits, rent, insurance, and major vendor due dates.
• Ask who can initiate a payment, approve it, release it, and change bank instructions.
• Confirm whether management has a short-horizon cash view and what assumptions it uses.

The key test is traceability. A finance owner should be able to explain the difference between the cash number on the bank site, the cash number in the ledger, and the cash number being used for a decision. If those numbers are different, the difference is not necessarily an error; it is a fact that needs a clear explanation and owner.

Follow revenue from activity to cash

Revenue errors often begin outside the accounting system. A CRM opportunity may be marked closed before a signed order exists. A service milestone may be complete operationally but not invoiced. A customer may receive a credit in the billing system that does not reach the ledger promptly. The audit should follow the path rather than simply reviewing a revenue report.

Start with a small sample of recent transactions: one new customer, one renewal, one credit or refund, and one large or overdue invoice. For each, trace the sequence from commercial event through contract or order, invoicing, cash collection, revenue recognition where applicable, and management reporting. Note every manual upload, spreadsheet transformation, and handoff between teams.

Revenue and receivables checklist

• Identify the source used for booked revenue, invoicing, and recognized revenue; these may be different.
• Reconcile the accounts-receivable aging to the general ledger at the latest available date.
• Review the ten largest open invoices, their expected payment dates, and their collection owner.
• Identify recurring billing failures, unbilled work, disputed invoices, credits, and customer deposits.
• Ask how sales, operations, and accounting are notified when a contract changes.
• Confirm whether revenue and gross-margin reports use the same customer, offering, and period definitions across functions.
• Document material manual journals or spreadsheet uploads that affect revenue.

You are not trying to complete an audit of every transaction in week one. You are looking for points where the company could make a confident-looking decision with incomplete or inconsistent information.

Test the payables and purchasing path

Payables are more than an AP aging. They include signed commitments, purchase orders, contractor obligations, recurring software renewals, inventory, commissions, and payments that employees expect but have not yet submitted for processing. A ledger may look current while a significant payment batch waits outside it.

Request the latest AP aging, a vendor list, upcoming payment run, purchasing or commitment report if one exists, and the calendar of recurring obligations. Then ask operations what has been committed but not received or entered. If the company has no formal purchasing process, identify the practical one: email approvals, chat messages, CEO instructions, or a card held by an employee.

Payables and purchasing checklist

• Reconcile AP aging totals to the general ledger.
• Identify the largest overdue vendor balances and any disputed invoices.
• Review payment terms, early-payment discounts, and late-payment risks.
• List recurring obligations and their renewal or cancellation dates.
• Identify open purchase orders, contractual commitments, and planned inventory or contractor spend.
• Confirm the approval threshold for new vendors, purchase commitments, and payment releases.
• Test whether a vendor bank-detail change requires independent verification.

This review frequently produces a useful immediate action: create a forward-looking commitments list that cash planning can use before the process itself is redesigned.

Examine the close, not only the ledger

The general ledger is the accounting record, but its operational reliability depends on the close process. Ask for the most recent close checklist, close calendar, trial balance, balance-sheet reconciliations, and the latest management reporting package. Review the sequence: when transactions stop, when reconciliations occur, who reviews them, and when leadership receives numbers.

Look for unresolved balances that repeat month after month, journal entries posted after reporting, payroll or inventory entries that are delayed, and management reports assembled before the books are complete. A short close is not automatically a strong close. A longer close may be appropriate if the team is transparent about what remains open and when it will be resolved.

Close and ledger checklist

• Determine the last fully closed month and the date it was finalized.
• Obtain the close checklist and identify tasks without an owner or review step.
• Review reconciliations for cash, receivables, payables, payroll liabilities, debt, inventory, and intercompany balances where relevant.
• Identify recurring manual journal entries and the support for each.
• Compare the latest trial balance to the management report for the same period.
• Ask which balances are estimated, provisional, or routinely adjusted after close.
• Confirm whether the chart of accounts supports the decisions leadership expects to make.

Treat unexplained recurring adjustments as an operating signal. They may point to weak upstream data, unclear ownership, inadequate documentation, or an accounting policy question that needs qualified review.

Review payroll, people data, and statutory calendars

Payroll affects cash, employee trust, withholding obligations, and the accuracy of labor reporting. Review the payroll provider, pay calendar, payroll approval process, employee and contractor roster, and the process for syncing payroll expense and liabilities to the ledger.

The audit should also reveal where people information changes. A hire date, termination, compensation change, commission plan, or contractor conversion can affect payroll, cash planning, benefits, and reporting. If those changes are communicated informally, quantify the operational exposure without assigning blame.

Payroll checklist

• Confirm pay dates, funding dates, tax-deposit cadence, and the last completed payroll.
• Identify payroll administrators, approvers, and former employees with access.
• Reconcile the latest payroll register to payroll entries in the ledger.
• Review the process for new hires, terminations, pay changes, bonuses, and commissions.
• Identify benefits, retirement, and employer-tax obligations that are paid outside the main payroll run.
• Confirm who monitors notices from taxing agencies or the payroll provider.

If payroll administration, tax notices, or employment classifications raise specialized questions, document the issue and involve the appropriate payroll, tax, HR, or legal adviser. The week-one review is meant to surface those questions early, not to provide specialized advice outside the CFO role.

Make reporting definitions visible

Reporting breaks down when each function uses a plausible but different definition. Sales may call a signed order revenue, operations may use delivered work, and accounting may use invoiced or recognized revenue. None of those views is inherently wrong; the issue is whether the report says what it measures and whether decision-makers know the difference.

Request the most recent board, investor, or leadership package. For each key metric, identify the source, calculation, refresh frequency, owner, and known limitation. Then reconcile a small selection of headline metrics to their sources. This is more valuable than reviewing every chart.

Reporting checklist

• List the metrics used in leadership meetings and the decisions each is intended to support.
• Record the precise definition for revenue, gross margin, cash, backlog, churn, headcount, and contribution margin where used.
• Identify spreadsheet-only calculations and manual data exports.
• Verify whether a reviewer checks the report before distribution.
• Reconcile selected metrics to source systems and note timing differences.
• Flag reports that lack a stated period, source, owner, or definition.

The goal is a shared vocabulary. A report can remain simple and still be decision-ready when its definitions, sources, and limitations are clear.

Review access and change controls pragmatically

You do not need to conduct a technical security assessment to identify operational access risks. Ask for a list of administrators and users with sensitive permissions in banking, accounting, payroll, billing, and payment systems. Look for shared credentials, former employees, unreviewed external access, and one person who can create a vendor and release a payment without an independent check.

Access and change-control checklist

• List administrators for bank, ledger, billing, payroll, AP, and reporting systems.
• Identify shared logins, personal email addresses, and former employees or contractors with access.
• Confirm whether multi-factor authentication is enabled for sensitive systems.
• Map who can create vendors, change bank details, approve bills, release payments, and post journals.
• Review the approval evidence retained for material payments and accounting adjustments.
• Document the immediate access removals or permission changes that require an owner.

Do not overstate the conclusion. A week-one finance review can identify access and approval exposures, but it is not a cybersecurity certification or an internal-control opinion.

Use a five-day sequence

The audit is more effective when requests and conversations have an order. The following sequence keeps the work focused while giving operational owners enough time to produce evidence.

Day 1: Frame decisions and secure access

Meet with the CEO and finance owner to establish the decisions that matter most in the next month. Confirm system owners, request read-only access where appropriate, and collect the latest cash position, trial balance, AR aging, AP aging, payroll calendar, and management package. Start the one-page system map.

Day 2: Establish cash and commitments

Reconcile the reported cash position to bank evidence and ledger balances. Map payroll, debt, tax, rent, major vendor, and committed-spend dates. Review the near-term collections list with the person responsible for each material invoice.

Day 3: Trace revenue, payables, and close

Walk a small sample of revenue and expense transactions through their systems and handoffs. Review the close calendar, reconciliations, recurring entries, and reporting preparation. Document exceptions with evidence rather than assumptions.

Day 4: Review reporting, access, and ownership

Test key management metrics back to their sources. Review administrator access and payment/change authorities. Identify tasks that depend on one person, external party, or undocumented spreadsheet.

Day 5: Prioritize and align

Deliver a concise findings discussion. Separate items into immediate actions, stabilization work, and improvement opportunities. For every item, name the evidence, business consequence, owner, next action, and target date. Confirm which issues require a specialist.

Turn observations into a useful output

Avoid a color-coded score that suggests accuracy beyond the evidence available. Instead, document findings in a format management can act on:

Priority	Finding	Evidence	Business consequence	Owner	Next action
Immediate	Cash position excludes processor reserve	Bank and processor balances do not reconcile to reported cash	Liquidity decision may be overstated	Finance owner	Add reserve to daily cash view
Stabilize	AR aging lacks collection dates	Aging has no owner or expected receipt field	Cash forecast is less reliable	Sales operations	Add collection owner and expected date
Improve	KPI calculations exist only in one spreadsheet	No documented source or review	Leadership may compare inconsistent periods	Finance leader	Define source, logic, and reviewer

This structure makes the week-one audit useful even when the client’s systems are imperfect. It creates a shared fact base, identifies the few issues that should change behavior now, and gives the fractional CFO a defensible sequence for the next phase of work.

What not to do in week one

Do not promise a system replacement before understanding the process around it. Do not rebuild reports before confirming the definitions management needs. Do not turn every gap into an emergency. And do not imply an audit, assurance, legal, tax, or security conclusion that the scope and evidence do not support.

Week one is successful when leadership has a clearer view of the finance operating chain, knows which information can be used confidently today, and agrees on the next few actions that improve reliability. That is a practical foundation for better decisions long after the initial review is complete.