← All insights
Full-Stack Finance Case Study Oct 2025 · 2 min read

Payroll and Compliance Cleanup for a Multi-State US SMB

By the CFOLogic team

Financial Operations

A growing US services SMB ran payroll across several states with filings handled ad hoc — late penalties, vendor double-payments, and a permanent 'the books are a bit behind' state.

5th

business day — books closed, every month

On time

payroll, filings, and vendor payments

WHAT WE DID

Took over bookkeeping, AR/AP, payroll, and compliance as one accountable function

Set up approval controls that stopped duplicate payments and surprise fees

Reconciled bank, cards, and ledger monthly with a doer–reviewer–QA structure

WHAT CHANGED

Penalties and vendor escalations stopped

The monthly report became short, clear, and trusted

The founder got evenings back

STACK Gusto QuickBooks Online Ramp

The situation

A growing US services SMB ran payroll across several states with filings handled ad hoc. Late penalties, vendor double-payments and a permanent sense that the books were a bit behind had become normal.

Multi-state payroll is where administrative debt compounds fastest. Each state adds its own registration, filing calendar and rules, and the work is both unavoidable and invisible — nobody is thanked for filing on time, and the penalty for missing arrives weeks later as a letter.

Double-payments point at something more structural than carelessness. They happen when no single approval gate sits between an invoice arriving and money leaving, which means the control is somebody's memory of whether it was already paid.

What we did

Took over bookkeeping, AR/AP, payroll and compliance as one accountable function. Splitting these across providers is how gaps form. Each party performs its own scope correctly and the space between scopes is where the filings get missed.

Set up approval controls that stopped duplicate payments and surprise fees. A control is not a policy; it is a step in the process that cannot be skipped without someone noticing.

Reconciled bank, cards and ledger monthly with a doer–reviewer–QA structure. Cards are the account most often reconciled last and least, and they are where small unexplained charges accumulate into a number nobody can account for.

What changed

The books now close by the fifth business day, every month, and payroll, filings and vendor payments run on time.

Penalties and vendor escalations stopped. The monthly report became short, clear and trusted. And the founder got their evenings back.

The middle outcome deserves emphasis. A report becomes trusted when it stops changing after the fact — the value is not that it is shorter but that nobody is waiting for the corrected version.

What this means for multi-state SMBs

Compliance work has no upside and unbounded downside, which is exactly why it drifts. It is never the most valuable thing to do on a given day, and it is occasionally the most expensive thing to have not done.

The structural fix is accountability rather than effort. When bookkeeping, payroll and filings sit with one accountable function, missed work is visible to someone whose job it is to see it. When they are split, everyone's scope is complete and the outcome is still wrong.

A fixed close date is the simplest health indicator available. Books that close on the fifth business day every month are books where the underlying process works. Books that close when they close are telling you something, and it is rarely only about the books.

Full-Stack Finance Published Oct 2025 · CFOLogic Insights
The newsletter

Actionable insights like this, once a month.