QuickBooks holds AI-categorized bank transactions for review before they are posted

The task

A business that links its bank account to QuickBooks Online receives a steady flow of imported transactions. Before any of them reaches the books, someone has to assign a category from the chart of accounts and often a customer or supplier, a class or a location as well. Handled one transaction at a time, this is slow and repetitive bookkeeping work.

What they did

Intuit's help article lays out how the feature works. As each transaction lands in the bank feed, the Accounting AI looks at how the business categorized similar transactions in the past and checks the company's own posting criteria. Only when that history supports one clear category, plus a confident payee, class or location where the books normally record one, is the transaction marked Ready to post. In a Transaction posting policy the user chooses which extra fields are required, enters an amount above which a transaction always waits for a person, sets a date so that older history is ignored, and can write posting notes in plain language. Colored review signals on each field show how strongly past data backs a suggestion, and a Policy reviews tab records every check that passed or failed with the reason. The feature belongs to the Essentials, Plus and Advanced plans on the new AI-powered banking page.

Where the approval sits

The AI does not post anything by itself. On the Pending tab the user opens the ready transactions, looks at category, payee or customer and amount, edits any field, unticks items to come back to later and only then selects Post. A transaction that fails any check stays in the bank feed for the usual manual review. According to the article, the AI also never makes a bank rule post a transaction automatically.

Worth knowing

The source is Intuit's own help documentation for its product, so it explains how the feature is meant to work and reports no results from real businesses. A whole batch can be posted with one click, so the review is only as careful as the person doing it. The feature depends on existing categorization history and is not part of every plan. This entry describes a product feature and does not replace professional advice from an accountant.

More in this category

• Back office and documents

  A blogger tests Paperless-ngx 3.0 suggestions and accepts each by hand

  A tech blogger connected Paperless-ngx 3.0 to a language model and tried its Suggest button, which proposes tags, a document type, a correspondent, and a title. Nothing changes until a person accepts a suggestion.

  Read the entry
• Back office and documents

  A Paperless-ngx archive holds paperless-gpt suggestions for review

  A hosting provider describes paperless-gpt, a service that proposes titles, tags, correspondents, document types, and dates for scanned documents in Paperless-ngx. Documents with the review tag wait in a screen where a person approves each change.

  Read the entry
• Back office and documents

  A sole proprietor books receipts with Claude Code and approves each

  A one-person business built a Claude Code skill that reads receipts from its Fiken inbox and proposes an account for each one from past bookings. The owner confirms every proposal before anything is booked.

  Read the entry