When this skill is activated, always start your first response with the 🧢 emoji.

Bookkeeping Automation

Bookkeeping is the systematic recording and organizing of all financial transactions for a business. Done well, it produces a reliable single source of truth for every dollar in and out, enabling confident decision-making, clean audits, and accurate tax filings. Automation shifts the work from data entry to exception handling - the machine reconciles the routine, the human resolves the unusual.

This skill covers the design and automation of core bookkeeping workflows: chart of accounts architecture, bank and credit card reconciliation, accounts payable and receivable pipelines, month-end close checklists, recurring journal entries, and expense management. It applies equally to spreadsheet-based setups, QuickBooks, Xero, NetSuite, and custom-built finance tooling.

When to use this skill

Trigger this skill when the user:

• Asks how to design or restructure a chart of accounts
• Needs to automate or streamline bank reconciliation
• Wants to build or improve an accounts payable (AP) workflow
• Wants to build or improve an accounts receivable (AR) and collections process
• Asks about month-end or year-end close procedures
• Needs to create or automate recurring journal entries or accruals
• Wants to implement an expense management and reimbursement system
• Asks about the difference between accrual and cash basis accounting

Do NOT trigger this skill for:

• Tax strategy, tax planning, or tax filing preparation (use a tax-specialist skill)
• Financial modeling, forecasting, or FP&A (bookkeeping records history; FP&A projects forward)

Key principles

1. Double-entry is non-negotiable - Every transaction touches at least two accounts: a debit and a credit of equal value. This self-balancing property is what makes accounting auditable. Never design a system that records only one side.

2. Classify at the source - The cheapest time to categorize a transaction is when it first enters the system. Reclassifying entries later is expensive and error-prone. Design intake workflows (AP approval, expense submission, bank feed rules) to capture the correct account, department, and project code upfront.

3. Reconciliation is the heartbeat - Reconcile bank and credit card accounts at minimum monthly, ideally weekly. Unreconciled books drift from reality. Reconciliation is what transforms a transaction log into trustworthy financials.

4. Separate duties - The person who approves a payment should not be the same person who processes it. The person who records a journal entry should not be the only person who reviews it. Segregation of duties prevents both fraud and honest error.

5. Automate the routine, review the exception - Use bank feed rules, recurring transaction templates, and scheduled journal entries for predictable items. Reserve human attention for variance investigation, approval workflows, and anything over a materiality threshold.

Core concepts

Double-entry bookkeeping

Every financial event is recorded as a pair of equal and opposite entries. Debits increase asset and expense accounts; credits increase liability, equity, and revenue accounts. The fundamental equation always holds:

Assets = Liabilities + Equity

A simple example - paying a $500 vendor invoice:

Debit:  Accounts Payable   $500   (reduce liability)
Credit: Cash/Bank           $500   (reduce asset)

Chart of accounts structure

The chart of accounts (COA) is the master list of every account used to classify transactions. A well-structured COA uses a numeric scheme that groups by type:

Keep the COA as flat as possible. Sub-accounts add granularity but also complexity. Add a new account only when reporting genuinely requires it - not speculatively.

Accrual vs. cash basis

Most growing businesses should use accrual. Cash basis can mask real obligations (e.g., a large unpaid bill not showing up as an expense yet).

Reconciliation

Reconciliation is the process of comparing two sets of records to ensure they agree. Types:

• Bank reconciliation - Match the general ledger cash account to the bank statement. Identify timing differences (outstanding checks, deposits-in-transit) and errors.
• Credit card reconciliation - Match the credit card GL account to the card statement.
• AR aging reconciliation - Ensure the AR subledger total matches the AR control account.
• AP aging reconciliation - Ensure the AP subledger total matches the AP control account.
• Balance sheet reconciliation - Every BS account should have a schedule supporting its balance (e.g., fixed asset roll-forward, prepaid amortization schedule).

Common tasks

Design a chart of accounts

1. Start with the standard numeric ranges above. Reserve gaps (e.g., 1100-1199 for cash, 1200-1299 for AR) so related accounts cluster together.
2. Map every real transaction type to an account. If a transaction cannot be mapped, add an account - but never use a catch-all "Miscellaneous" account for regular activity.
3. Define a naming convention and enforce it: [Type] - [Detail], e.g., 6200 - Software Subscriptions, 6210 - Software Subscriptions - Engineering.
4. Create departments or classes at the reporting layer, not by multiplying accounts. Use one 6100 - Payroll account with a department tag, not separate payroll accounts per team.
5. Review quarterly: retire unused accounts, merge near-duplicates, add only what reporting genuinely requires.

Automate bank reconciliation

Manual process baseline:

1. Export bank statement (CSV or OFX)
2. Import into accounting system or spreadsheet
3. Match each bank line to a GL entry by date, amount, and description
4. Flag unmatched items on either side
5. Investigate and resolve exceptions
6. Sign off when difference = 0

Automation levers:

• Bank feed rules - In QuickBooks/Xero, create rules that auto-categorize recurring transactions by payee name or description pattern (e.g., "STRIPE" -> Revenue).
• Fuzzy matching scripts - For custom setups, match bank lines to GL entries by amount tolerance and date window (±1 day, ±$0.01).
• Auto-import OFX/CSV - Schedule a daily import so the feed is never more than 24 hours stale.
• Exception queues - Surface only the unmatched items for human review. The matched 90% should require zero human time.

Key reconciliation formula:

Bank Statement E