Reconciliation and close · 6 minute read

Month-End Close Checklist for Small Business Owners

Closing the books each month does not have to feel like a scramble. This checklist walks through what to gather, what to review, and how to sign off with confidence.

Published 2026-08-03 · Last reviewed 2026-08-03

The short version

A clean close is mostly about gathering the right source activity, not chasing perfection.
Approval-first workflows keep the owner in control of what actually lands in the books.
Closing a period explicitly is what turns a working draft into a reportable history.

What month-end close actually means

Close is the moment when you stop adding new activity to a period and turn it into a finished picture. Before close, the books are a workspace where drafts are reviewed and adjusted. After close, the period is treated as a record you can report on and hand to outside reviewers.

For small businesses, close is usually monthly because that is how often most owners look at their numbers. A monthly close keeps surprises from piling up, gives your CPA clean periods to work from, and makes tax preparation less hectic later.

Close is not a tax filing, and it is not a financial statement audit. It is simply the owner saying, "This period is finished."

Workspace phase: collecting activity and reviewing drafts.
Close phase: posting approved entries and locking the period.
Report phase: producing exports and a downloadable CPA package.

Step 1: Gather the source activity for the period

Start by listing what should feed the period. The big buckets are usually bank activity, payment processor activity, payroll activity, and any invoices or bills you track by hand.

Mercury is the direct bank connection in Fionas. PDF and CSV statement uploads cover other U.S. banks. Stripe and Whop provide revenue and payout context, while Plane provides payroll activity to review.

Write down what is connected and what still needs a manual upload. That list becomes your "is the source complete" check before you do anything else.

Bank activity: direct connection where available, otherwise PDF or CSV.
Payment processors: revenue, payouts, and any fees shown in the processor report.
Payroll: gross pay, taxes withheld, and net pay per period.
Manual items: invoices issued, bills received, owner contributions or distributions.

Step 2: Reconcile bank, payment, and payroll context

Reconciliation is the process of matching the activity you have gathered to the entries you expect in the books. For a bank, that means comparing the statement balance to the sum of the entries you have drafted. For a payment processor, it means checking that payouts and fees line up with what your processor reported.

Approval-first software like Fionas can prepare source-linked drafts from the gathered activity, but those drafts are proposals, not finished matches. Reconciliation is what aligns each draft against its source line; the owner still has to review and approve before anything becomes a recorded entry.

Payroll adds a third stream. Confirm that each payroll run appears once, that the gross and net amounts are sensible, and that the period assignment matches how your CPA prefers payroll to be mapped (for example, accrued versus paid). Document the choice you make so the mapping stays consistent from month to month.

Compare statement ending balance to the sum of posted and drafted entries.
Match processor payouts to deposits and review processor fees as separate lines.
Confirm each payroll run sits in the correct month.
Flag anything unusual rather than forcing a match.

Step 3: Review drafts and exceptions

Once you have drafts, your job is to review them. Read the description, check the amount, look at the source link, and decide whether the entry belongs in the period. Some drafts will be obvious. Others will need a question answered or a category chosen.

Exceptions are the lines that do not fit a clean pattern. A refund larger than the original sale, a duplicate deposit, a payroll adjustment, a fee you do not recognize. Put exceptions in a short list and resolve them one at a time instead of guessing.

Approval-first workflows are designed for this step. Nothing posts until you say so, which means review is where the real decisions happen.

Skim every draft, even the small ones.
Use the source link to confirm what the line actually was.
Keep an exception list and resolve items before closing.
Resist the urge to post anything you cannot explain.

Step 4: Approve and post

Posting is the action that moves an entry from a draft into the books. In an approval-first system, posting happens only when the owner takes a deliberate step. That separation is the point: it keeps a human decision in the loop for every change to the record.

A practical routine is to approve in batches of similar items, then handle exceptions individually. This keeps the review efficient without skipping the entries that need attention.

Remember that the software never moves money and never replaces a CPA. Posting is a bookkeeping step, not a banking step or a tax step.

Related reading: Draft vs. posted entries

Step 5: Close the period explicitly

Closing is its own action. The owner explicitly marks a ready period as closed, which signals that no further changes are expected. Without that step, the period stays in a working state and reports can shift under you.

Make closing a habit. A short note in the file saying what was closed, when, and by whom is enough. If your software supports an audit history, that record becomes part of the period's documentation.

If you discover a problem after close, do not panic. Note the issue, decide whether to adjust in the current period or the next, and document the decision.

Close only after drafts are reviewed and exceptions are resolved.
Record the close date and the person responsible.
Treat the closed period as the starting point for the next month.

Step 6: Produce reports and a CPA package

Once the period is closed, generate the exports you need. Every Fionas plan provides CSV, JSON, and a downloadable CPA-package export. Ask your CPA which format fits their review process before you send anything.

Send the package to your CPA with a short note describing the period, any unusual items, and what you would like them to focus on. The clearer the handoff, the less back-and-forth later.

Fionas is not a CPA, accountant, bank, lender, or advisor. The CPA package supports your reviewer's work, but it does not replace professional advice.

Common close mistakes and a calm disclaimer

The most common mistake is closing a period that still has unresolved exceptions. The second is posting drafts without reading them. The third is treating a CSV export as a substitute for a conversation with your CPA.

Build in a small buffer of time after the period ends. A close done in a rush is the close that needs to be redone.

Fionas does not provide tax, legal, financial, or investment advice, and nothing here should be read as such. Use this checklist as a starting structure and adapt it to your business, your reviewers, and your jurisdiction.

Do not close with open exceptions.
Do not post drafts you have not read.
Do not skip the CPA conversation.
Leave room in the calendar for a careful close.

See how Fionas structures a close

Fionas prepares source-linked drafts and waits for owner approval before posting. See which plan fits your monthly close routine.

View pricing

Related guides

All articles