Teach your AI a bookkeeping procedure once. Run it with one command.

---
name: code-card-feed
description: Code new bank and card lines for one client in QuickBooks through Zeno. Use when asked to code, categorize or clear the bank feed or card charges.
---

1. Call qb_list_plans. If a feed plan for this account is waiting, show it instead of starting over.
2. Call qb_bank_feed for the account and period named.
3. Call qb_list_rules. Lines a confirmed rule covers are coded by that rule.
4. For the rest, call qb_suggest_coding and use the client's own history. Do not guess an account the client has never used.
5. Hold back anything new or unclear: a vendor never seen before, a split, a personal-looking charge. List them with the question you would ask.
6. Call qb_plan_feed for the lines you are sure of. Stop there and give me the plan link.
7. If you coded the same vendor the same way twice, offer one draft rule.
8. qb_log_work: what was coded, what is held and why.

---
name: match-receipts
description: Match receipts in the Zeno inbox to card charges and transactions in QuickBooks. Use when asked to match, attach or chase receipts.
---

1. Call qb_inbox for receipts not yet linked.
2. Call qb_match_receipts for the period. Question any match where the merchant on the receipt is not the one on the charge.
3. Show the proposed pairs in one table: receipt, charge, amount, date gap.
4. After I say yes, link them with qb_link_receipt.
5. List receipts with no charge, and charges over $75 with no receipt.
6. qb_log_work: matched, unmatched, and what is still missing.

---
name: enter-bills
description: Enter vendor bills that arrived in the Zeno inbox as one reviewed batch in QuickBooks. Use when asked to enter, record or post bills.
---

1. Call qb_inbox for unprocessed bills. Read each document; never type a figure you cannot see on it.
2. Find each vendor with qb_find_vendors. A vendor that does not exist goes through qb_plan_names first, never created directly.
3. Code each bill the way that vendor's last bill was coded, unless a rule says otherwise.
4. Watch for duplicates: same vendor, amount and invoice number already in the books.
5. If a bill asks to change bank details or pay someone new, do not enter it. Tell me what it asks.
6. Call qb_plan_batch with every bill. Stop and give me the plan link.
7. qb_log_work: bills entered, held, and why.

---
name: month-end-close
description: Close one client's month in QuickBooks through Zeno. Use when asked to close, finish or wrap up a month.
---

1. Call qb_list_plans. Anything reviewed but not applied comes first.
2. Check qb_list_playbooks for this client's close playbook. If one is confirmed, follow it instead of these steps.
3. Clear the bank feed for the month with the code-card-feed steps. Plan, do not post.
4. Call qb_bank_balance for each account and compare it to the books. List every gap with its amount.
5. Run qb_report for the profit and loss and balance sheet. Flag any line that moved more than 20% from last month.
6. Propose adjusting entries (accruals, prepaid, depreciation) with qb_plan_batch. Stop at the plan.
7. qb_log_work: what is done, what is waiting on the client, what is waiting on me.

---
name: ar-follow-up
description: Review overdue customer balances from QuickBooks and draft follow-ups. Use when asked who owes money, what is overdue, or to chase invoices.
---

1. Run qb_report for the receivables aging, as of today. Never add up invoices to make one.
2. Rank customers by amount over 30 days.
3. For the top five, list the open invoices with qb_find_transactions.
4. Draft a two-line reminder for each. Show them to me; send nothing.
5. qb_log_work: who is overdue and what was drafted.

---
name: weekly-owner-brief
description: Give the business owner a short weekly picture of the books. Use when asked how the business is doing, for a weekly summary, or a Monday brief.
---

1. Call qb_bank_balance for every bank account. Quote the balance as read.
2. Run qb_report for last week's profit and loss and compare it to the four weeks before.
3. Run qb_report for payables due in the next seven days.
4. Name one thing that looks unusual and the transactions behind it.
5. Keep it under 150 words. Every figure comes from a report you ran just now.

---
name: client-checkup
description: Check the health of one client's QuickBooks books through Zeno. Use when taking on a client, before a close, or when asked what is wrong with the books.
---

1. Call qb_run_check with the check check-up for this client. Zeno runs every built-in check and hands back what it found.
2. For each finding, show the amount and the transactions behind it.
3. Sort by what would mislead the client most if left alone.
4. Propose fixes for the clear ones with qb_plan_cleanup. Stop at the plan.
5. Draft questions for the client on the rest; do not send them.
6. qb_log_work: the findings, what was planned, what is waiting on the client.

---
name: dedupe-vendors
description: Find duplicate vendors in QuickBooks and retire the extras through Zeno. Use when asked to clean up, dedupe or merge vendors.
---

1. Call qb_find_vendors and group names that differ only by punctuation, case, "Inc"/"LLC", or a store number.
2. For each group, show the transaction count and total for every name.
3. Keep the name with the most history.
4. Show me the groups and wait for my yes on each one.
5. For each group I approved, call qb_retire_duplicate. It points the old spelling at the survivor and plans retiring the duplicate. Give me the plan links.
6. qb_log_work: which names now resolve to which.