Bookkeeping Practice Ops Official

Reads uncategorized transactions and suggests an account with a confidence level, flagging low-confidence items for a client query. Suggestions only.

1. 01Select transactions to categorize from the Uncategorized Transactions table. If {{transactionId}} is provided, work only that row. Otherwise take rows with Status New, filtered to {{client}} if given, up to {{maxToProcess}} (default 20). For each, read the description, amount, and date, and look up the client's basis and rules.Output: The transactions selected with their key details, ready to categorize.
2. 02For each transaction, suggest the closest account from the chart of accounts using the categorization rules. Set Suggested Category and a Confidence of High, Medium, or Low. If confidence is Low or the item could be personal or unusual, set Status to Client Query and write a short, specific Client Question; otherwise set Status to Suggested. Never post to the ledger and never fabricate an account that is not in the chart of accounts.Output: Confirmation of the rows updated, then a short readable summary using headings and bullet points: how many suggested at each confidence level and how many flagged for a client query. Never output JSON or raw data.

Generates the standard monthly close checklist for a client and period into the Monthly Close Tasks table.

1. 01Determine which clients and period to set up. If {{client}} is given, use that client; otherwise use all Active clients from the Clients table. Use {{period}} if given, otherwise the most recent closed month. Read each client's entity type and basis, and the close process in the knowledge base.Output: The clients and period to set up, with any client-type variations noted.
2. 02For each client, create the standard close tasks as rows in the Monthly Close Tasks table for the period, each with Task, Status Not Started, a sensible Due Date, and Owner blank for assignment. Skip tasks already present for that client and period so you do not duplicate. Do not mark anything done and do not post to the ledger.Output: Confirmation of the tasks created per client, then a short readable summary using headings and bullet points: clients set up and tasks created for the period. Never output JSON or raw data.

Drafts batched, client-friendly questions for transactions flagged as needing a client query. Draft only.

1. 01Read transactions in the Uncategorized Transactions table with Status Client Query, filtered to {{client}} if given, up to {{maxToProcess}} (default 30). Group them by client.Output: The flagged transactions grouped by client, with their date, amount, and description.
2. 02For each client, draft one brief, friendly message per the query etiquette that lists each transaction with its date, amount, and vendor and asks the specific question, offering the most likely category as a yes or no. Save the drafted question back to each transaction's Client Question field. Do not send anything.Output: Confirmation of the rows updated, then a short readable summary using headings and bullet points: clients with pending questions and how many items each. Include the drafted message per client in readable prose. Never output JSON or raw data.

Reviews close tasks marked ready for review and drafts a reviewer note, flagging discrepancies for a human. Never adjusts the books.

1. 01Read close tasks from the Monthly Close Tasks table with Status Ready for Review, filtered to {{client}} and {{period}} if given. Focus on reconciliation and review tasks. Use the review and sign-off checklist in the knowledge base.Output: The tasks ready for review, with what the checklist says to verify for each.
2. 02For each, draft a reviewer note covering what was checked, anything that looks inconsistent or unusual, and open questions. Write the note to the task's Notes. If something needs correction, set Status to Blocked with a clear reason for a human; otherwise leave it Ready for Review for a human to sign off. Never adjust the books or mark a task Done.Output: Confirmation of the tasks updated, then a short readable summary using headings and bullet points: reviewed, cleared to sign off, and blocked with reasons. Never output JSON or raw data.

Reads clients and close tasks and produces a per-client close-status digest with blockers and open client queries.

1. 01Read the Clients and Monthly Close Tasks tables, and the Uncategorized Transactions table for open client queries. For each active client, work out close progress for the current period: tasks done, in progress, blocked, and ready for review, plus how many transactions are awaiting a client answer.Output: Per-client progress with counts by status and open client queries, and the overall bottlenecks.
2. 02Write a concise close-status digest for the owner, leading with clients at risk of a late close and the biggest blockers. Optionally record period totals in the Close Metrics table.Output: A readable digest using headings and bullet points: clients at risk first, then a per-client status line, blockers, and open client queries. Lead with the headline. Never output JSON or raw rows.