30 Claude Prompts for QuickBooks

You are a bookkeeper who reconciles bank accounts in QuickBooks every month. <context> My QuickBooks reconciliation for this account will not zero out and I need a structured way to find the difference before I force it closed. </context> <inputs> - Account being reconciled: [ACCOUNT NAME] - Statement ending balance: [AMOUNT] - QuickBooks balance per reconciliation screen: [AMOUNT] - Difference amount: [AMOUNT] - Recent changes made to already-reconciled transactions, if known: [DESCRIBE OR WRITE UNKNOWN] </inputs> <task> Give me an ordered checklist of the most common causes for a reconciliation difference of this size and how to check for each one in QuickBooks, starting with the most likely cause first. </task> <constraints> Order by likelihood given the difference amount and any known changes. Do not suggest forcing an adjustment entry until every diagnostic step has been listed. Keep each step to one or two sentences. </constraints> <format> A numbered checklist, most likely cause first, each with a one-line instruction for how to verify it in QuickBooks. </format>

You are a bookkeeper reporting monthly reconciliation status to a business owner client. <context> I just finished reconciling all bank and credit card accounts for the month and need to send the client a short summary they will actually read. </context> <inputs> - Accounts reconciled: [LIST ACCOUNT NAMES] - Month: [MONTH AND YEAR] - Any outstanding items: [DESCRIBE, E.G. UNCLEARED CHECK, DUPLICATE CHARGE] - Anything the client needs to do: [ACTION NEEDED OR NONE] </inputs> <task> Write a short client-facing email summarising that reconciliation is complete, noting any outstanding items in plain language, and stating clearly what, if anything, the client needs to do. </task> <constraints> Under 150 words. No accounting jargon like uncleared or outstanding without a plain explanation next to it. If there is nothing for the client to do, say so directly instead of leaving it ambiguous. </constraints> <format> A ready-to-send email with subject line and body. </format>

You are a bookkeeper handling a client whose payment processor deposits money in batches that do not match daily sales. <context> Sales recorded in QuickBooks each day do not match the lump-sum deposits from the payment processor because of a settlement lag and fees, and I need to reconcile them cleanly. </context> <inputs> - Payment processor: [PROCESSOR NAME, E.G. SQUARE, STRIPE] - Typical deposit lag: [NUMBER OF DAYS] - Fee structure: [PERCENT PLUS FLAT FEE OR DESCRIBE] - Sample data: [PASTE A FEW DAYS OF SALES AND A DEPOSIT AMOUNT] </inputs> <task> Explain the QuickBooks workflow to match processor deposits to sales using a clearing account, including where fees should be recorded, so the bank feed matches without forcing entries. </task> <constraints> Assume the reader already uses QuickBooks Online daily but has never set up a clearing account. Keep the explanation concrete with the sample numbers given, not abstract. </constraints> <format> A short explanation of the clearing account concept, then a numbered setup and matching procedure using the sample data. </format>

You are a bookkeeper who just found a duplicate transaction while reconciling a QuickBooks account. <context> I found what looks like the same transaction entered twice, once through a bank feed match and once through a manual bill payment, and I need to confirm the right way to remove it without breaking anything already reconciled. </context> <inputs> - Transaction description: [DESCRIPTION] - Amount: [AMOUNT] - Date of each entry: [DATE 1] and [DATE 2] - Whether either entry is already marked reconciled: [YES OR NO, AND WHICH ONE] - Related bill or invoice, if any: [BILL OR INVOICE NUMBER OR NONE] </inputs> <task> Give me the correct QuickBooks steps to identify which entry is the duplicate and remove or void it safely, accounting for whether it is already reconciled. </task> <constraints> If one entry is already reconciled, explain the extra caution needed and the impact on the reconciliation report. Do not recommend deleting a reconciled transaction without flagging the consequence first. </constraints> <format> A short numbered procedure with a warning callout if a reconciled transaction is involved. </format>

You are a bookkeeping operations lead standardising the month-end close process across client files. <context> I want a repeatable reconciliation checklist my team follows for every client every month, covering all account types, not just the bank feed. </context> <inputs> - Account types typically reconciled: [LIST, E.G. CHECKING, SAVINGS, CREDIT CARD, LOAN] - Team size: [NUMBER OF BOOKKEEPERS] - Current pain points: [DESCRIBE, E.G. MISSED CREDIT CARD RECONCILIATIONS] - Deadline for close: [DAY OF MONTH] </inputs> <task> Create a month-end reconciliation checklist covering every account type listed, in the order they should be reconciled, with a note on what commonly gets missed for each. </task> <constraints> Address the stated pain points directly rather than giving a generic checklist. Keep each line item actionable, not a vague reminder like check the account. </constraints> <format> A checklist grouped by account type, each item phrased as an action, plus a short note at the end on how to track completion across the team. </format>

You are a bookkeeper who explains QuickBooks reports to business owners who are not trained in accounting. <context> I exported this month's Profit and Loss from QuickBooks and need to turn it into a plain-language summary for a client who glazes over at financial statements. </context> <inputs> - Report period: [MONTH AND YEAR] - Total revenue: [AMOUNT] - Total expenses: [AMOUNT] - Net income: [AMOUNT] - Top three expense categories with amounts: [LIST] - Comparison to prior month, if available: [AMOUNT OR NOT AVAILABLE] </inputs> <task> Write a short plain-language summary of this Profit and Loss that a non-finance business owner can read in under a minute and understand where their money went. </task> <constraints> No accounting terms like variance or margin without explaining them in plain words first. Lead with the number the owner cares about most, which is net income. Under 200 words. </constraints> <format> Three short paragraphs: The headline number, Where the money went, What changed from last month. </format>

You are a controller reviewing client Balance Sheets before they go out for a monthly close package. <context> I need a second set of eyes on this Balance Sheet to catch anything that looks off before I send the close package to the client. </context> <inputs> - Balance Sheet data: [PASTE ACCOUNT NAMES AND BALANCES] - Prior period balances for comparison: [PASTE OR STATE NOT AVAILABLE] - Business type: [BUSINESS TYPE] - Known one-time events this period: [DESCRIBE OR NONE] </inputs> <task> Review the Balance Sheet for anything unusual, such as a negative balance in an account that should not go negative, an account that has not moved in a suspiciously long time, or a swing too large to explain by the known one-time events. </task> <constraints> Only flag genuine anomalies, not normal fluctuations for a [BUSINESS TYPE]. For each flag, state what specifically looks wrong and what you would ask the bookkeeper to confirm. </constraints> <format> A table: Account, What looks unusual, Question to ask, Priority (high, medium, low). </format>

You are a fractional controller preparing monthly financial updates for a small company's leadership team. <context> I need to turn a raw QuickBooks Profit and Loss and Balance Sheet export into a short update for a leadership meeting where most attendees are not finance people. </context> <inputs> - Company stage: [STAGE, E.G. PRE-REVENUE, GROWTH, MATURE] - Key metrics from the reports: [REVENUE, GROSS MARGIN, CASH BALANCE, RUNWAY IF KNOWN] - Notable events this period: [LIST, E.G. NEW HIRE, LOST A CUSTOMER] - Audience: [WHO IS IN THE MEETING] </inputs> <task> Write a one-page financial update summarising the key metrics, connecting them to the notable events, and stating whether the trend is a reason for concern or confidence. </task> <constraints> Lead with the single most important takeaway in one sentence. Avoid hedging language, state a clear read on the numbers. Keep it to one page. </constraints> <format> Headline sentence, then three short sections: Numbers, What drove them, What to watch next month. </format>

You are a bookkeeper who tracks budget performance for clients using QuickBooks reports. <context> I have this month's actual Profit and Loss from QuickBooks and the client's budget for the same categories, and I need a variance summary that highlights what needs attention. </context> <inputs> - Budget by category: [PASTE CATEGORY, BUDGETED AMOUNT] - Actuals by category from QuickBooks: [PASTE CATEGORY, ACTUAL AMOUNT] - Threshold for flagging a variance: [PERCENT, E.G. 10 PERCENT] - Business context for the period: [ANYTHING RELEVANT, E.G. RAN A PROMOTION] </inputs> <task> Calculate the variance for each category, flag any that exceed the stated threshold, and give a likely plain-language explanation for the largest variances given the business context. </task> <constraints> Show the variance as both a dollar amount and a percent. Do not explain every category, only the ones over the threshold. Do not guess at a cause with no supporting context, say the cause is unclear instead. </constraints> <format> A table: Category, Budget, Actual, Variance dollars, Variance percent, Flagged (yes or no), then a short paragraph on the top two variances. </format>

You are a bookkeeper explaining cash position to a client who is confused why they show a profit but have no cash. <context> The client's QuickBooks Profit and Loss shows a profit for the month but their bank balance dropped, and I need to explain the disconnect using their actual numbers. </context> <inputs> - Net income for the period: [AMOUNT] - Change in bank balance for the same period: [AMOUNT, INCREASE OR DECREASE] - Large non-cash or timing items: [LIST, E.G. LOAN PAYMENT PRINCIPAL, LARGE RECEIVABLE, OWNER DRAW] - Client's main question: [WHAT THEY ASKED] </inputs> <task> Explain in plain language why profit and cash movement differ this period, using the specific items listed, and answer the client's stated question directly. </task> <constraints> Do not use the phrase working capital without defining it in one plain sentence first. Tie every dollar mentioned back to one of the listed items, do not introduce unlisted causes. </constraints> <format> A short answer to the client's question first, then a simple breakdown showing how net income reconciles to the cash change. </format>

You are a small business owner managing accounts receivable through QuickBooks invoicing. <context> An invoice I sent through QuickBooks is now overdue and I want to send a reminder that is firm but keeps the client relationship intact. </context> <inputs> - Invoice number: [INVOICE NUMBER] - Amount due: [AMOUNT] - Days overdue: [NUMBER OF DAYS] - Original due date: [DATE] - Relationship with client: [ONE-OFF OR ONGOING] - Prior reminders sent: [NONE, ONE, OR MORE] </inputs> <task> Write an email reminding the client the invoice is overdue, stating the amount and days overdue clearly, and asking for either payment or a response by a specific date. </task> <constraints> Match the tone to the relationship type, warmer for [ONGOING] clients, more direct for [ONE-OFF] ones. If this is not the first reminder, acknowledge that briefly without sounding annoyed. Under 120 words. </constraints> <format> A ready-to-send email with subject line and body, plus a one-line note on when to escalate if there is no response. </format>

You are a freelance consultant preparing an invoice in QuickBooks for a client who has asked for more detail in the past. <context> I need to write clear line item descriptions for this month's invoice so the client understands exactly what they are paying for without needing a follow-up call. </context> <inputs> - Work performed this period: [LIST TASKS OR DELIVERABLES] - Billing method: [HOURLY OR FLAT FEE OR RETAINER] - Hours or units per task, if applicable: [LIST] - Client's past confusion or questions: [DESCRIBE OR NONE] </inputs> <task> Write one clear line item description per task that would go directly into a QuickBooks invoice, specific enough that the client understands the value without needing to ask what it means. </task> <constraints> Each description under 15 words. Use outcome language where possible instead of vague activity language like worked on project. Do not combine unrelated tasks into one line. </constraints> <format> A simple list, one line item description per task, ready to paste into QuickBooks. </format>

You are a small business consultant helping a client formalise how they handle late payments. <context> This client has no written late payment policy and keeps having awkward conversations case by case, so I need to draft policy language they can put directly on their QuickBooks invoice template. </context> <inputs> - Industry: [INDUSTRY] - Typical invoice size: [AMOUNT RANGE] - Current informal practice: [DESCRIBE WHAT THEY DO NOW] - Desired grace period before a late fee applies: [NUMBER OF DAYS] - Desired late fee structure: [FLAT FEE OR PERCENT PER MONTH] </inputs> <task> Write short, clear late payment terms this client can add to their QuickBooks invoice template footer, and separately explain how to configure the equivalent late fee automation in QuickBooks Online. </task> <constraints> Keep the invoice terms to two or three sentences, written to be read, not legal boilerplate. Note that late fee enforceability can vary by state, marked as [STATE], and suggest confirming with an advisor rather than asserting it is fine. </constraints> <format> Two parts: Invoice footer text, then numbered QuickBooks configuration steps. </format>

You are a bookkeeper managing collections for a client with several overdue invoices in QuickBooks. <context> This client has a handful of overdue invoices in QuickBooks and I need to decide which ones to chase first given limited time this week. </context> <inputs> - Overdue invoices: [LIST: CLIENT NAME, AMOUNT, DAYS OVERDUE] - Client payment history notes: [ANY NOTES ON WHICH CLIENTS PAY LATE VS NEVER] - Relationship importance: [WHICH CLIENTS ARE HIGH PRIORITY TO KEEP HAPPY] - Time available this week: [HOURS OR NUMBER OF CALLS] </inputs> <task> Rank the overdue invoices in the order they should be pursued this week, balancing amount at risk, days overdue, payment history, and relationship importance, and suggest the right contact method for each. </task> <constraints> Explain the reasoning for the top three rankings, not just the order. Do not recommend an aggressive collections approach for a client marked as high relationship importance unless they are far overdue. </constraints> <format> A ranked table: Rank, Client, Amount, Days overdue, Suggested contact method, then a short paragraph explaining the top three. </format>

You are a bookkeeper helping resolve a client dispute over an invoice amount. <context> A customer is disputing the amount on an invoice I issued through QuickBooks and I need to check the numbers and prepare a clear response. </context> <inputs> - Invoice number: [INVOICE NUMBER] - Invoiced amount: [AMOUNT] - Customer's claimed correct amount: [AMOUNT] - Line items on the invoice: [PASTE LINE ITEMS AND AMOUNTS] - Customer's stated reason for the dispute: [REASON] </inputs> <task> Compare the invoice line items against the customer's stated reason, identify whether the dispute has merit, and draft a response that either corrects the invoice or explains why the original amount stands. </task> <constraints> Base the conclusion only on the line items and reason given, do not assume facts not stated. If the dispute has partial merit, say so specifically rather than picking one side entirely. </constraints> <format> A short internal analysis first, then a separate customer-facing response ready to send. </format>

You are an accountant who sets up new QuickBooks files for small businesses. <context> I am setting up QuickBooks for a new client and need a starting chart of accounts tailored to their industry instead of the generic default list. </context> <inputs> - Business type: [BUSINESS TYPE] - Entity structure: [LLC, S CORP, SOLE PROP, PARTNERSHIP] - Revenue streams: [LIST, E.G. SERVICE FEES, PRODUCT SALES] - Major expense categories expected: [LIST] - Whether they need job costing or class tracking: [YES OR NO] </inputs> <task> Propose a chart of accounts organised by account type, income, cost of goods sold, expenses, assets, liabilities, and equity, specific to this business rather than a generic template. </task> <constraints> Only include accounts this business would realistically use, do not pad the list with unused categories. If job costing is needed, note which expense accounts should be tagged for it. </constraints> <format> Grouped list by account type, each account with a one-line note on what it captures. </format>

You are a bookkeeper cleaning up a QuickBooks file that has accumulated too many accounts over the years. <context> This client's chart of accounts has grown to a size that makes reports hard to read and I need to consolidate it without losing any needed detail. </context> <inputs> - Current account list: [PASTE FULL LIST OF ACCOUNT NAMES] - Business type: [BUSINESS TYPE] - Reports the client actually uses: [LIST, E.G. MONTHLY P AND L] - Anything that must stay separate for tax reasons: [LIST OR NONE KNOWN] </inputs> <task> Recommend which accounts should be merged into a parent account or a broader category, which should stay separate, and the QuickBooks steps to merge accounts safely without losing historical data. </task> <constraints> Do not recommend merging any account flagged as needed for tax reasons. Explain the merge steps clearly since merging accounts in QuickBooks is irreversible. </constraints> <format> A table: Current account, Recommendation (merge into X, or keep), Reason. End with the general merge procedure as a numbered list. </format>

You are a bookkeeper migrating a client from a legacy accounting system into QuickBooks Online. <context> I am migrating this client from their old system into QuickBooks and need to map their existing account list to QuickBooks equivalents. </context> <inputs> - Old system account list: [PASTE ACCOUNT NAMES AND TYPES] - Old system name: [SOFTWARE NAME] - Business type: [BUSINESS TYPE] - Anything the client explicitly wants renamed or restructured: [DESCRIBE OR NONE] </inputs> <task> Map each old account to a QuickBooks account name and type, flagging anything that does not have a clean one-to-one match and needs a judgment call. </task> <constraints> Use standard QuickBooks account type categories, do not invent nonstandard types. For anything without a clean match, propose the closest option and explain the tradeoff rather than skipping it. </constraints> <format> A table: Old account name, Old type, Proposed QuickBooks account, QuickBooks type, Note if a judgment call was needed. </format>

You are a bookkeeper setting up more granular expense tracking for a growing client. <context> This client wants to see expenses broken out by department or location and I need to restructure part of their chart of accounts to support that in QuickBooks. </context> <inputs> - Departments or locations to track: [LIST] - Parent expense accounts that need breaking out: [LIST ACCOUNT NAMES] - Whether QuickBooks class tracking is already enabled: [YES OR NO] - Reporting the client wants at the end: [DESCRIBE, E.G. P AND L BY LOCATION] </inputs> <task> Recommend whether to use sub-accounts or QuickBooks class and location tracking to achieve the departmental breakdown the client wants, and explain the setup steps for the recommended approach. </task> <constraints> Explain the tradeoff between sub-accounts and class tracking in plain terms before recommending one. Base the recommendation on the specific reporting goal stated, not a generic preference. </constraints> <format> A short comparison paragraph, a clear recommendation, then numbered setup steps. </format>

You are a bookkeeping firm owner standardising how your team names and organises accounts across client files. <context> Different bookkeepers on my team name accounts inconsistently across client files and I need a naming convention document everyone will follow. </context> <inputs> - Team size: [NUMBER OF BOOKKEEPERS] - Common inconsistencies observed: [LIST EXAMPLES, E.G. SOFTWARE VS SOFTWARE EXPENSES] - Client industries served: [LIST] - QuickBooks versions used: [ONLINE, DESKTOP, OR BOTH] </inputs> <task> Write a naming convention guide covering capitalisation, abbreviation rules, how to name sub-accounts, and how to handle industry-specific accounts, using the observed inconsistencies as examples of what to fix. </task> <constraints> Keep rules simple enough that a new hire can follow them without memorising a long document. Use the specific examples given to show the wrong way and the right way side by side. </constraints> <format> A short rules list, each rule with a wrong example and a right example. </format>

You are a bookkeeper implementing internal controls for a client who currently pays bills with no approval step. <context> This client's bills go straight from received to paid with no one else reviewing them, and the owner wants a lightweight approval step added without slowing payments down too much. </context> <inputs> - Number of people who should approve: [NUMBER] - Typical bill volume per month: [NUMBER OF BILLS] - Bill dollar threshold requiring approval: [AMOUNT] - QuickBooks plan level: [SIMPLE START, ESSENTIALS, PLUS, ADVANCED] - Current process: [DESCRIBE BRIEFLY] </inputs> <task> Design a bill approval workflow that fits inside QuickBooks Online's available features for the stated plan level, specifying who approves what and at which dollar threshold. </task> <constraints> Do not recommend a feature that requires a higher QuickBooks plan than the one stated without flagging the upgrade clearly. Keep the workflow realistic for the stated bill volume, do not require approval on every single bill if volume is high. </constraints> <format> A short workflow diagram described in numbered steps, followed by a one-line note on any plan upgrade needed. </format>

You are a small business owner managing cash flow through QuickBooks bill tracking. <context> I want to ask a vendor to extend my payment terms because my cash flow is tighter than usual this quarter, and I need to word this without sounding like the business is in trouble. </context> <inputs> - Vendor name: [VENDOR NAME] - Current terms: [CURRENT TERMS, E.G. NET 15] - Requested terms: [REQUESTED TERMS, E.G. NET 45] - Length of relationship with vendor: [YEARS OR MONTHS] - Payment history with this vendor: [ON TIME OR OCCASIONALLY LATE] </inputs> <task> Write an email requesting extended payment terms from this vendor, framing it as a business planning decision rather than a cash shortage, and referencing the payment history to support the request. </task> <constraints> Do not use language that suggests financial distress. Keep it under 130 words. Offer something in return if reasonable, such as a longer commitment or larger order volume, marked as [OFFER IF ANY]. </constraints> <format> A ready-to-send email with subject line and body. </format>

You are a bookkeeper doing a vendor statement reconciliation for accounts payable accuracy. <context> A vendor sent a statement showing a different balance than what QuickBooks shows as owed to them, and I need to find the discrepancy. </context> <inputs> - Vendor name: [VENDOR NAME] - Balance per vendor statement: [AMOUNT] - Balance per QuickBooks accounts payable: [AMOUNT] - Bills and payments on the QuickBooks side: [PASTE LIST WITH DATES AND AMOUNTS] - Bills and payments on the vendor statement: [PASTE LIST WITH DATES AND AMOUNTS] </inputs> <task> Compare the two lists line by line, identify which bills or payments are missing or mismatched between the two records, and state the likely cause of the overall discrepancy. </task> <constraints> Show the matching and non-matching items clearly rather than just stating a conclusion. Do not assume a payment was received by the vendor unless it appears on their statement. </constraints> <format> A table: Item, On QuickBooks, On vendor statement, Match status. End with a one-sentence conclusion on the likely cause. </format>

You are a bookkeeper setting up recurring transaction rules for a client with predictable monthly bills. <context> This client has several bills that repeat every month at the same or similar amount, and I want to set up QuickBooks recurring transactions so they are not entered manually each time. </context> <inputs> - Recurring bills: [LIST VENDOR, TYPICAL AMOUNT, DUE DATE] - Which ones vary slightly each month versus are fixed: [NOTE WHICH ARE FIXED VS VARIABLE] - Payment method for each: [LIST, E.G. AUTO-DRAFT, CHECK, ACH] </inputs> <task> Recommend which of these bills are good candidates for QuickBooks recurring transaction templates versus which should stay manual because the amount varies, and explain the setup for the good candidates. </task> <constraints> Only recommend automation for genuinely fixed-amount bills. For variable amount bills, suggest a reminder-based approach instead of full automation, so nothing gets paid at the wrong amount. </constraints> <format> A table: Vendor, Fixed or variable, Recommended approach, then numbered setup steps for the fixed ones. </format>

You are a bookkeeper reviewing an accounts payable aging report before a client meeting. <context> The accounts payable aging report in QuickBooks shows bills as older than they should be, or shows a bill as unpaid that the client says was already paid, and I need to find the cause before the meeting. </context> <inputs> - Vendor and bill in question: [VENDOR, BILL NUMBER, AMOUNT] - What the aging report shows: [DESCRIBE, E.G. SHOWS 90 DAYS OVERDUE] - What the client says actually happened: [DESCRIBE, E.G. PAID BY CHECK LAST MONTH] - Any related payment transaction found: [DESCRIBE OR STATE NONE FOUND] </inputs> <task> Work through the most likely reasons a bill would still show as open on the aging report despite the client's claim, and give the specific QuickBooks check to confirm each one. </task> <constraints> Order the possible causes from most to least likely given the details provided. If a related payment was found but not linked to the bill, treat that as the top suspect. </constraints> <format> A numbered list of possible causes, most likely first, each with the QuickBooks screen or report to check. </format>