From bookkeeping
Contains verified opening-balance JE construction logic, summary-vs-detailed entry strategy decision framework (2-year threshold), and bank statement transaction-type routing tables that produce more precise answers than reasoning from general training alone. Backlog assessment, catch-up period boundaries, monthly summary JEs, OBE cleanup, hybrid multi-year reconstruction, fiscal year alignment, tax-filing readiness gates. Consult when books are months or years behind, reconstructing GL from statements, or asking "should I use summary JEs or enter each transaction."
How this skill is triggered — by the user, by Claude, or both
Slash command
/bookkeeping:catchup-bookkeepingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Operational skill for planning and executing multi-period bookkeeping reconstruction.
Operational skill for planning and executing multi-period bookkeeping reconstruction. Covers the full lifecycle from backlog assessment through transaction entry to period validation, with decision logic for choosing between summary and detailed approaches.
Gather before starting any catch-up work:
Bank and Financial Statements — All checking, savings, money market statements; credit card statements; loan statements with amortization schedules; brokerage/investment account statements
Income Documentation — Invoices issued, payment receipts, 1099s received for prior years, sales reports or POS summaries
Expense Documentation — Bills, receipts, and vendor invoices; payroll records and pay stubs; prior tax filings (if any exist); contracts, leases, and agreements
Priority: Bank and credit card statements are the minimum viable source set. If nothing else is available, statements alone can reconstruct cash-basis books.
Before entering transactions, determine what already exists:
This assessment determines the catch-up period boundaries and whether you are starting from zero or filling gaps in partial records.
The catch-up period runs from the first month with missing records through the current period. Key decisions:
Work oldest-to-newest within the catch-up period. Each fiscal year should balance independently before moving to the next.
The single most important decision in catch-up bookkeeping: summary or detailed.
One journal entry per month aggregates all activity into category totals.
Choose when: Catch-up period exceeds 2 years, source documentation is limited to bank statements only, the goal is tax-filing readiness (not audit), or budget is constrained.
How it works: For each month, total deposits by income category and withdrawals by expense category from bank statements. Create a single journal entry dated the last day of the month with one line per category and the bank account as the offset.
Trade-offs: Faster execution (minutes per month vs. hours). Higher audit risk — no transaction-level detail. Acceptable for cash-basis tax returns. Not suitable if the client may face IRS examination on specific transactions.
Enter individual transactions from statements as native accounting entries (deposit entries, expense entries, transfer entries, check payments).
Choose when: Catch-up period is under 2 years, audit preparation is required, tax planning requires transaction-level granularity, or the client needs detailed P&L reporting by period.
How it works: Classify each bank/credit card line item by transaction type (deposit, withdrawal, transfer, check, fee). Enter each as the appropriate entry type with correct account coding.
Trade-offs: Slower but produces a complete audit trail. Each transaction is individually reconcilable. Required for accrual-basis reporting or if payroll detail matters.
For multi-year backlogs, combine both approaches:
This gives tax-ready books for filing years while minimizing effort on statute-expired periods.
Before entering any transactions, establish the account structure. A catch-up COA needs at minimum:
Balance Sheet — Operating Checking, Savings (per actual bank accounts), Undeposited Funds, Accounts Receivable, Fixed Assets with Accumulated Depreciation, Security Deposits, Accounts Payable, Company Credit Card (per actual card), Notes Payable, Owner's Equity, Owner's Draw, Opening Balance Equity
Income — Sales Revenue, Service Revenue, Interest Income, Other Income
COGS — Cost of Goods Sold (expand if the business has distinct cost categories)
Expenses — Advertising, Bank Fees, Insurance, Office Supplies, Professional Services, Rent, Utilities, Payroll Expenses, Travel, Meals, Miscellaneous
Create only accounts that will actually receive postings. Add accounts as needed during transaction entry rather than building an exhaustive structure upfront. Duplicate account names are silently skipped if the account already exists in the system.
Invoke accounting-foundation:chart-of-accounts for numbering conventions, Form 1120 tax-line mapping, and C-corp equity account design.
Opening balances record account values as of the day before the catch-up period starts. They establish the balance sheet starting point so that catch-up transactions flow correctly.
Create a single journal entry dated one day before the catch-up start date:
Normal balance direction by account type: Asset, Expense, and COGS accounts have normal debit balances. Liability, Equity, and Revenue accounts have normal credit balances. Positive balances follow the normal direction; negative balances reverse it.
After entering opening balances, the Opening Balance Equity account should hold the net difference. As the catch-up progresses:
For months using the summary approach:
When categorizing statement transactions for summaries:
After each monthly summary JE, verify:
For months using the detailed approach:
Each bank statement line maps to an accounting entry type:
When the expense category is unknown, route to Miscellaneous. When the income category is unknown, route to Other Income. Flag these for client review. It is better to enter the transaction with a placeholder category than to skip it — skipped transactions break reconciliation.
Process credit card statements the same way as bank statements but with the credit card account as the source. Each charge becomes an expense against the credit card; payments from checking become transfers from the bank to the credit card account.
After entering all transactions for a given month, reconcile that month before proceeding to the next.
Per-month reconciliation sequence:
Multi-account reconciliation: Reconcile each bank and credit card account independently. A month is not complete until all accounts for that month are reconciled.
Invoke bookkeeping:reconciliation for the full reconciliation workflow and variance resolution procedures.
Before marking any catch-up period as complete:
A catch-up period is ready for tax filing when:
Once the catch-up is current:
Invoke bookkeeping:transaction-processing for day-to-day entry patterns after catch-up is complete.
Read these for implementation detail and workflow patterns:
references/catchup-planning.md — Assessment and planning phase: source document gathering, company file state evaluation, catch-up period definition, COA setup for catch-up, opening balance journal entry construction. Read for the full account structure template and opening balance creation logic.references/catchup-transaction-entry.md — Transaction entry phase: monthly summary JE creation, bank statement classification by transaction type, deposit/expense/transfer entry patterns. Read for the detailed workflow of each transaction type and the summary-vs-detailed decision framework.For platform-specific catch-up execution:
qbo-integration:qbo-bookkeeping for QBO-specific catch-up workflows, bank feed import, and multi-year reconstruction within QBOFor foundational knowledge used during catch-up:
accounting-foundation:chart-of-accounts for COA design, numbering conventions, and Form 1120 tax-line mapping when building the catch-up account structureFor related bookkeeping workflows:
bookkeeping:reconciliation for per-period bank reconciliation procedures and variance resolutionbookkeeping:transaction-processing for standard entry patterns used after catch-up is completetax-prep:form-1120-prep — Catch-up often directly precedes delinquent-year return preparationtax-prep:tax-planning — Completed catch-up provides historical data for tax projectionfinancial-planning:budgeting-forecasting — Reconstructed historical periods feed budget baselinesnpx claudepluginhub aeyeops/aeo-basis-plugin-marketplace --plugin bookkeeping<!-- AUTO-GENERATED by export-plugins.py — DO NOT EDIT -->
Records Japanese journal entries (shiwake), imports transactions from CSV/receipts/invoices via CLI, manages ledger with init/search/update/delete. For bookkeeping workflows.
Guides complete monthly financial reconciliation: reviews/categorizes/verifies transactions, reconciles invoices, checks documents, prepares taxes. For month-end bookkeeping.