Use case · Documents and finance
Bills typed into QuickBooks Desktop from PDFs — by a bot, not a clerk
The document half is the same as any invoice flow: IntelliDocs returns the fields, a workflow validates them. The last mile is different because QuickBooks Desktop is a Windows application: an RPA bot opens Enter Bills, picks the vendor, fills the lines and account codes, attaches the PDF and saves — on a free Bot Runner installed next to QuickBooks, unattended, with every action logged.
- Who it is for
- Accounting firms and companies still on QuickBooks Desktop (Pro, Premier, Enterprise) who receive supplier bills as PDFs and key them in by hand — often an outsourced bookkeeper working inside a remote desktop.
- Systems involved
- Outlook / Gmail / shared folderIntelliDocsQuickBooks Desktop (Studio bot)Teams / email approvalExcel 365 log
How the run goes
5 steps · logged per run
- Trigger01
PDF arrives
Email, scanner folder or portal download
- Document02
IntelliDocs extracts
Vendor, date, lines, GL hints
- Agent03
Validate and code
Vendor list, account mapping, duplicates
- Bot04
Enter bill in QuickBooks Desktop
Free Bot Runner on the QB machine
- Person05
Review exceptions
Unknown vendor, unclear account
How it runs, step by step
- 1
Invoices arrive by email or land in a scanner folder. Each one starts a run; the file is sent to an IntelliDocs stream that returns vendor, dates, line items and totals.
- 2
The workflow checks the vendor against the QuickBooks vendor list (exported nightly by the bot into a table), proposes an expense account from the vendor's history, and recomputes totals. Unknown vendors or ambiguous coding go to the bookkeeper as a task with the PDF attached.
- 3
A Studio bot runs on the Windows machine where QuickBooks Desktop is installed — the firm's server or a client's VM. It opens the company file, navigates to Enter Bills, types the vendor, date, reference and lines, attaches the PDF and saves. Each field entry is a deterministic step with a screenshot in the run log; nothing is "figured out" by a model on screen.
- 4
If QuickBooks shows a dialog the bot doesn't expect — a vendor name prompt, a closed-period warning — the bot stops that item, captures the screen and routes it to a person; the queue continues with the next bill.
- 5
A daily summary lists bills entered per company file, with run links and the bookkeeper's exceptions.
Limits — what this does not do
- Multi-user mode and company-file locks have to be planned: the bot needs a QuickBooks user and a window when the file is not exclusively open elsewhere.
- QuickBooks Desktop upgrades can change screens; the bot is retested after each (it is a deterministic bot, so changes are found on the first run, not silently).
- This is a bot use case, so it needs the RPA module in the plan; the SaaS variant uses the QuickBooks Online API instead.
Questions about this process
The SDK works but needs a developer, a certificate and a QBXML integration maintained per version; most firms we meet have neither. The bot uses the same screens the bookkeeper uses and is maintained by the same person who built it in Studio.
In multi-user mode with its own user, yes, subject to the same locks any user hits. Many firms run the bot overnight on the server.
Yes; the screens differ slightly per edition and are handled in the bot's configuration.
Related use cases
Build this on your systems in a guided sandbox.
Tell us the process; after a 30-minute call the sandbox is ready from 24 hours, and we build the first run with your team.