QuickBooks Online Advanced workflows put imported transactions up for approval

QuickBooks Online Advanced users who automate approvals are noticing a shift in where new transactions wait. Anything created outside the software, whether by a connected app, an import, batch entry, receipt capture, or spreadsheet sync, now moves itself into pending approval. Nobody has to send it there. Accepted guidance from Intuit confirms the behavior and lays out how to put the feature to work for a team rather than against it.

The feature is not new, but its reach keeps growing. Workflows in this tier can nudge a customer about an open invoice or walk a bill through sign-off. The questions users raise tend to cluster in the same spots: which template to start from, why a condition field is missing, and why an imported transaction sits untouched.

The job workflows are built for

Workflows exist to automate the routine chasing: reviewing invoices, collecting payments, approving transactions. You set the conditions. When they are met, QuickBooks sends the reminder, to your team or to your customer. The setup can start from a template or from scratch. Built-in options cover the documents teams chase most: invoices, bills, estimates, purchase orders, and bill payments. More than sixty templates ship with the feature.

Templates carry most of the setup

Setup starts in Settings. Open Manage workflows, then Templates, and pick a starting point. Keep the default name or type your own. Then set two things: actions, which tell QuickBooks what to do, and conditions, which tell it when. You can save the workflow as a draft, or save and turn it on in one step.

One quirk trips people early. Action and condition labels vary from template to template, so the same idea can read differently depending on what you picked. The option to add another condition appears only in the trigger step, and not in every template. We read that as a template limit rather than a malfunction.

Do multi-condition approvals fit a growing team?

For bills, invoices, estimates, and purchase orders, multi-condition workflows add a checkpoint. When someone without admin rights creates one of these, QuickBooks tests it against your conditions and releases it only after approval. You can name one approver or several, and set the order in which they sign off. The search box on the Templates tab finds the approval variants by name. Extra conditions attach to the trigger step, again only where the template allows.

Imports no longer slip past approval

Here is the change worth flagging. Transactions created through third-party apps, batch entry, imports, receipt capture, or spreadsheet sync once needed a manual push toward approval. Current behavior sends them straight to pending approval on arrival. Conditions can also key off a transaction’s source, so an entry from an app can be treated differently from one keyed directly in QuickBooks.

The trap sits after submission

One limit deserves the most attention. Change a transaction in the third-party app after it has gone up for approval, and QuickBooks will not start a new approval cycle. The original approval keeps its place. An approver can therefore sign off on figures that no longer match what the app holds. The accepted guidance offers no reset. The protective habit is dull but effective: approvers verify amounts on screen before approving, and edits made after submission get a fresh manual look.

Can a queue be cleared in bulk?

Approvers can clear several transactions at once instead of one at a time. That matters for teams that import heavily. An overnight sync can leave many items waiting, and single approvals would turn the morning into clerical work. Bulk approval keeps the queue moving.

The short version

Workflows belong to the Advanced tier of QuickBooks Online, and the order of setup stays consistent: template first, then actions and conditions, then approvers. If a transaction seems stuck after an import or an app sync, check pending approval before anything else. Treat post-submission edits with care, because the approval attached to the earlier version is the one that stands.