Multi-Entity Reconciliation For Bookkeepers: 4-Entity Close Workflow

Your client has 4 entities: 2 LLCs, an S-corp, and a personal account. Each closes on a different day. The books need to close on the last day of the month, and the inter-entity transfers are killing your reconciliation.

Multi-entity reconciliation is the #2 pain point for bookkeepers, right after bank feed failures. This page covers the per-entity cycle dates, the inter-entity transfer flag, the per-entity period-end split, and the 4-entity close workflow.

Multi-entity clients have different cycle dates, different cutoff dates, and transfers between entities. The recon cutoff tool’s per-entity period-end split handles each entity independently. The inter-entity transfer flag eliminates the double-counting that happens when transfers are recorded as income or expense.

The 4-entity close takes 2-3x longer than a single-entity close. The recon cutoff tool’s per-entity handling compresses it back to 1.5x. The remaining 50% extra time is the inter-entity transfer matching, which is judgment work that doesn’t compress the same way.

For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For month-end close, see the month-end close guide. For client onboarding, see the client onboarding guide.

The 4-Entity Client

The 4-entity client is the most common multi-entity pattern: 2 LLCs (operating companies), 1 S-corp (the owner), and 1 personal account. Each entity has its own bank account, its own cycle date, and its own bank feed.

What most guides miss about this workflow is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input).

Choosing between tools based on UI alone misses the actual quality lever.

The books close on the last day of the month, calendar-month close. The bank cycles are anchored to the day the account was opened, so they don’t match the calendar month. The recon cutoff tool’s per-entity period-end split handles the gap.

The Per-Entity Cycle Dates

Each entity has its own cycle date. For example, LLC1 might close on the 7th, LLC2 on the 14th, S-corp on the 21st, and personal on the 3rd. The bookkeeper needs to know each cycle date to do the per-entity period-end split.

The cycle date is in the bank statement header. The recon cutoff tool’s archive feature stores the cycle date for each entity, so the bookkeeper doesn’t have to look it up every month.

The Inter-Entity Transfer Problem

Inter-entity transfers are the biggest reconciliation problem for multi-entity clients. When the owner moves $10,000 from their personal account to LLC1, the bank shows it as a transfer. The accounting system often records it as “Owner Contribution” (income on the LLC side) or “Owner Draw” (expense on the personal side).

Both are right for tax purposes, but the bank statement sees it as a transfer. The bookkeeper needs to mark transfers as “Transfer” in the Category column, not as income or expense, to avoid double-counting.

How to Identify Inter-Entity Transfers

Inter-entity transfers are transactions where the payee name matches another entity in the client’s books, or the memo includes “transfer” or “from [entity name].” The recon cutoff tool’s inter-entity flag identifies these automatically when the entity mapping is set at upload time.

The entity mapping is a one-time setup. The bookkeeper lists each entity and its bank account, then the tool flags every transaction that matches another entity in the list.

The Tax Treatment

Inter-entity transfers are not taxable events. The owner contribution from personal to LLC is recorded as equity, not income. The owner draw from LLC to personal is recorded as equity, not expense. The recon cutoff tool’s per-entity handling keeps the inter-entity transfer out of the income/expense totals.

Multi-Entity Reconciliation for Bookkeepers: 4-Entity Close Workflow

Turn any PDF statement into a clean sheet

Skip the typos and the hours of copying. Our converter handles any bank statement format and outputs Excel, CSV, or QBO for QuickBooks. No file retention, free to try.

Convert your statement

The Per-Entity Period-End Split

The per-entity period-end split is the recon cutoff tool’s main feature for multi-entity clients. The tool reads each entity’s statement, finds the calendar-month boundary, and splits the transactions: pre-cutoff for the current period, post-cutoff marked OUTSTANDING.

The split is per-entity, not per-bank. A 4-entity client with 1 bank (e.g., Mercury) and 4 accounts gets 4 separate period-end splits. A 4-entity client with 4 banks (e.g., Chase, Mercury, BofA, Wells) also gets 4 separate period-end splits, one per entity.

Why Per-Entity, Not Per-Bank

Per-entity is the right level of split because the books close per-entity. The LLC’s books close on the last day of the month, regardless of which bank holds the LLC’s account. The recon cutoff tool’s per-entity split aligns with the books.

Per-bank would be wrong because a single entity might have accounts at multiple banks (e.g., Chase for operations, Mercury for treasury). Per-bank would split the entity’s transactions across multiple files, which is harder to reconcile.

The 4-Entity Close Workflow

The 4-entity close runs in 8 steps. The recon cutoff tool compresses the conversion step but the review and adjust steps still take longer than a single-entity close.

Step 1: Collect All 4 Statements

Each entity has its own bank statement. The collection request goes out on the 1st of the month for all 4 entities. The recon cutoff tool’s archive feature tracks which statements have arrived.

Step 2: Convert All 4 Statements

The recon cutoff tool’s batch upload handles all 4 statements in one go. The conversion is 30 seconds per statement. The per-entity period-end split is automatic, with each entity’s transactions split at the calendar-month boundary.

Step 3: Import to QBO or Xero

Each entity has its own file in QBO or Xero. The 4 converted files import to the 4 entity files. The recon cutoff tool’s per-entity handling ensures each file goes to the right entity.

Step 4: Reconcile Each Entity

Reconciliation runs per-entity. The recon cutoff tool’s reconciliation worksheet shows which transactions match and which don’t. The inter-entity transfers are flagged automatically.

Step 5: Review the Inter-Entity Transfers

The review step looks at every flagged inter-entity transfer. The bookkeeper confirms the transfer is inter-entity, not a real income/expense. The recon cutoff tool’s inter-entity flag makes this review targeted at the flagged transactions, not the full transaction list.

Step 6: Adjust Per Entity

Adjustments are recorded per-entity. The recon cutoff tool’s per-entity handling ensures the journal entries go to the right entity. Inter-entity transfers are recorded as equity, not income/expense.

Step 7: Deliver Per Entity

Delivery is per-entity. The client might want a single report that consolidates all 4 entities, or 4 separate reports. The recon cutoff tool’s per-period export handles both formats. For the full deliverable workflow, see the deliverable format guide.

Step 8: Archive Per Entity

Archiving is per-entity. Each entity gets its own folder with the original PDF, the converted file, the reconciliation worksheet, and the client deliverable. The recon cutoff tool’s archive feature creates the per-entity folders automatically.

The Common Mistakes

3 mistakes bookkeepers make on multi-entity clients.

Treating transfers as income or expense. The double-counting problem. The fix: the recon cutoff tool’s inter-entity flag marks transfers as “Transfer” in the Category column.

Per-bank split instead of per-entity. The per-bank split scatters each entity’s transactions across multiple files. The fix: the recon cutoff tool’s per-entity split aligns with the books.

Skipping the inter-entity review. The review is what catches the misclassified transfers. Skipping it is the most common cause of audit issues for multi-entity clients.

The Time Difference

A 4-entity close takes 2-3x longer than a single-entity close. The recon cutoff tool’s per-entity handling compresses the conversion step but the review and adjust steps still take longer. The total time for a 4-entity close is 6-8 hours with the tool, 12-16 hours without.

The 6-8 hours saves 6-8 hours per month for a 4-entity client. Multiplied by 12 months, that’s 72-96 hours per year saved. For bookkeepers with multiple multi-entity clients, the time savings compound.

For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For month-end close, see the month-end close guide . For client onboarding, see the client onboarding guide . The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.

The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.

This topic is part of the bookkeeper-resource cluster on this site. The consolidated hub, covering onboarding, monthly close, year-end, client deliverables, and multi-entity workflows, lives in the complete bookkeeper workflow guide.

For related reading on the broader clusters, the covers credit-card-side mechanics, and the covers bank-account-side mechanics. The expanded bank statement anatomy is a useful primer.

More on the broader cluster

For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.

Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored.

Decision framework for this topic

Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.

When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.

For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.

Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.

For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.

The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.