Set it up once.
Every build after runs itself.

Yes. Vata Assembly reads your items, accounts and vendors, and creates new transactions. It has no ability to edit, void or delete anything that already exists — across every place it talks to Intuit, the only permitted verbs are GET and POST.

Up to four documents: an inventory adjustment consuming the components, a journal entry for the conversion cost, a purchase recording the finished receipt, and a clearing journal entry. Each is searched for before it's posted and re-read after, so a retry can't create a second one.

Separately, and only when you approve it, a shortage can be funded by creating a purchase order, a vendor bill or a new item. Those take an administrator or a typed confirmation of their own — they don't ride along on the build's approvals.

We won't give you a number we can't stand behind — it depends entirely on how clean your item list is. What we can tell you is the shape: four steps to a committed import, then linking, then one manual build per assembly you want automated.

The linking step is usually where the time goes. Exact-name matches bind automatically, but only for companies at or under 500 active items — that is a hard limit in this release, not a batch size. Above it, every link is made by hand. Everything else is a decision only you can make either way.

The build stops. The screen names how many parts are short and which ones, and offers to cost the order — stating in the same breath that nothing is ordered or posted until you confirm.

If you've authorised the nightly lane to fund shortfalls, it can create the vendor bill itself, but it only proceeds to build if that bill is independently verified by reading it back from QuickBooks with its purchase-order linkage intact. An unverified or unknown result stops the assembly.

Three approvals across two roles: an Approver signs the preflight, an Accountant signs the conversion source, and an Approver signs the posting. By default the requester, the operator and every approver must be different people.

A one-person shop can register as single-operator, which lets one principal sign all three. That mode is also what the unattended lane runs under — worth knowing before you enable it, because separation of duties and unattended operation are genuinely in tension.

Yes. This release posts to live QuickBooks Online companies, through Intuit's public OAuth 2.0 and Accounting API. Every screen tells you which company you're connected to, so there's no doubt about where a build is going.

We'd still recommend running your first assembly against a sandbox company. Be aware of what does and doesn't travel: your assemblies, recipes and history come with you, but item links and build precedent are bound to the QuickBooks company they were made in. Linking, and the one manual build per assembly, are done once per company you connect.

It stops and tells you. If a request is sent and the answer never arrives, the result is recorded as accepted-unknown and opened as an exception for reconciliation. It is never re-posted on the assumption it failed — that's how duplicate accounting gets made.

It also won't claim a matching QuickBooks record as its own unless it already holds a durable local marker proving it authorised that post. A transaction someone else created stays someone else's.

A stopped assembly costs you nothing, because nothing was built — it becomes its own row in the run history with a named class, and the count of assemblies needing attention is the first thing on the automation screen. There are no emails and no alerts in this release; you find out when someone opens the app.

For something posted that you'd rather undo: Vata Assembly can't reverse it, and won't pretend to. The evidence record deep-links to each transaction it created in QuickBooks Online, and you void or adjust them there — which keeps the correction in your books, under your accountant's control, where an auditor expects to find it.

Pricing publishes with general availability. Early access isn't charged, and any company in it gets the number in writing before anything is billed — we're not going to surprise you with an invoice for a product you helped shake down.

UTF-8 CSV and XLSX, up to 25 MB and 50,000 rows per file. Items, revisions, component lines and build requests, each with a template you can download in the app. Legacy .xls, .xlsb and .xlsm are refused, and any file containing formulas is rejected rather than evaluated.

Your column mappings are saved as a reusable profile, so the second import of the same file shape is a pick rather than a re-map.