QuickBooks Custom Automations: A Control Checklist for Accounting Firms

QuickBooks custom automations can reduce recurring work, but an accounting firm should begin with one low-risk client workflow and a documented reviewer. Run the automation beside the existing process, compare every material output, inspect exceptions and audit evidence, and expand only when a named owner accepts the results.

Why QuickBooks custom automations matter now

In a product update published 2026-09-15, Intuit described automations that users create in plain language and run on a schedule. Available examples include invoice reminders, business health checks, books cleanup, revenue-to-cash tracking, and profit and loss analysis. Intuit also says users can see whether each automation is running, paused, or in error and can inspect its audit log.

The operational question for a firm is therefore specific: which recurring task can be standardized without allowing an incorrect period, incomplete population, or unusual client transaction to pass unnoticed? That question is more useful than switching on several templates at once. A narrow pilot produces evidence that a partner can review before the firm changes its standard procedure.

Intuit's help documentation, updated 2026-08-24, says a Primary Admin or Company Admin creates, edits, or deletes an automation. It also documents live previews, run history, failure notifications, approval for outward-facing actions, and activity recorded in the QuickBooks Audit Log. Those features provide evidence, but the firm still needs to define what constitutes an acceptable result.

Choose one workflow and establish a baseline

Start with a read-only output whose expected result is already familiar. A weekly profit and loss summary, an overdue-invoice list, or a month-end exception report is easier to test than a workflow that communicates with customers. Avoid a first pilot that posts entries, changes master data, or relies on an unresolved accounting judgment.

Select one client with stable records and enough activity to reveal exceptions. Preserve the current manual procedure for two close cycles. Record the normal preparation time, the report filters, the accounting basis, the reporting period, the source accounts, the reviewer, and every recurring adjustment. This baseline lets the firm compare like with like.

Write the automation instruction as a miniature procedure. For example: prepare an accrual-basis profit and loss summary for the prior calendar month, compare each account with the prior month, flag changes above both $2,500 and 10%, and draft an internal summary for review. Specify both a dollar and percentage threshold so a small account does not create noise while a large account does not hide a meaningful dollar change.

Run the automated and existing procedures from the same locked reporting period. Reconcile revenue, total expenses, and net income before assessing commentary. If the totals differ, stop and identify the filter, timing, classification, or source-population difference. Firms that need a consistent reporting foundation can use the approach in shared chart of accounts mapping before comparing automated outputs across clients.

Accounting controls for a safe pilot

Source data: document the company file, reporting basis, period, included accounts, customer or vendor population, and any excluded classes or locations. Save the source report used by the existing procedure. The workflow owner confirms that both methods use the same cutoff and population.

Calculation: define every deterministic calculation outside the prose instruction. A variance should use current-period amount minus comparison-period amount. A percentage variance should use an approved denominator and a documented rule for zero or negative comparison values. Recalculate a sample independently and reconcile control totals to QuickBooks.

Review: assign someone other than the preparer to inspect the live preview, exceptions, failure notices, recipients, and Audit Log. The reviewer compares material totals with the baseline, investigates unmatched items, and records whether each difference is expected, corrected, or escalated. Outward-facing drafts receive a separate recipient and wording check before approval.

Decision: name the partner, controller, or workflow owner who can approve expansion. The decision record should state the clients covered, permitted task, schedule, thresholds, reviewer, evidence-retention location, and conditions that pause the automation. Access changes, repeated failures, unexplained differences, and changes to the underlying report should trigger a new test.

This structure complements an established audit-ready close control. FinBoard can help teams compare recurring financial outputs and review multi-entity reporting in one place. See how FinBoard supports controlled financial reporting.

Rollout limits and common mistakes

Custom automations do not remove accounting judgment. An accurate report can still support a poor conclusion if the period, basis, population, or materiality threshold is wrong. Audit-log evidence shows what ran and when; it does not prove that the instruction reflected the client's accounting policy.

A common mistake is treating a polished narrative as evidence that the underlying totals are complete. Reconcile the numbers first. Another is testing only a quiet client, then assuming the same instruction works for clients with classes, locations, multicurrency activity, unusual revenue recognition, or inconsistent charts of accounts. Expand by workflow pattern and client complexity, with a fresh baseline for each material variation.

Do not count draft preparation as completed communication. Intuit says outward-facing actions wait for approval, so the firm's procedure should identify the individual who checks the recipient, attachments, amount, reporting period, tone, and confidential information. A missed approval queue also needs an owner and an aging threshold.

Measure results over complete cycles. Track preparation minutes, review minutes, exceptions detected, false positives, failed runs, late approvals, and corrected outputs. Time saved is useful only when the error rate and review burden remain acceptable. Pause the workflow when unexplained differences exceed the firm's threshold or when the evidence needed for review is unavailable.

Frequently Asked Questions

What are QuickBooks custom automations?

QuickBooks custom automations are scheduled workflows created through Intuit Intelligence from a plain-language instruction. They can generate reports, draft reminders, summarize data, and record activity for later review.

Who can create a QuickBooks custom automation?

Intuit says a Primary Admin or Company Admin can create, edit, or delete a custom automation. Accounting firms should also assign a named workflow owner and reviewer in their internal control register.

Do custom automations send messages without approval?

Intuit states that outward-facing actions wait for review and approval. The reviewer should still confirm the recipient, amount, period, source data, and wording before approving a draft.

How should an accounting firm pilot custom automations?

Start with one low-risk, read-only workflow for one client and run it in parallel with the existing process for two close cycles. Compare the output, document exceptions, and expand only after the reviewer accepts the evidence.