Integrations
QuickBooks Integration
Bills, expenses and vendors created in QuickBooks from the documents, without the typing.
What moves
What flows between QuickBooks and PTAS AI
Documents and master data come in. Bills, vendors, attachments and status go out. QuickBooks stays the ledger; the typing stops.
QuickBooks Online
The documents
Your coding rules
PTAS AI
Bills created, not typed
One Bill or Purchase per document, lines coded, the PDF linked, written only after approval.
Payment status back in the queue
BillPayment and Bill changes arrive by webhook, so FinSuite knows what was paid without anyone checking.
A trail on both sides
The QuickBooks transaction Id sits on the invoice record in FinSuite; the invoice image sits on the Bill.
QuickBooks is a planning example here, not a packaged connector. Whether your file is QuickBooks Online or Desktop, which objects we write and who approves what are confirmed during assessment.
How FinSuite posts to a ledgerIntegration methods
How QuickBooks can be connected
Four ways in, and QuickBooks Online makes the first choice easy. Desktop is a different conversation.
Native
What QuickBooks does itself
QuickBooks Online has its own receipt and bill capture for simple cases. It does not run your approval rules or match a bill to a purchase order. We do not list an app on the QuickBooks app store, and nothing on this page is a packaged connector.
API
QuickBooks Online Accounting API
REST over HTTPS, authorised by your QuickBooks admin through OAuth 2.0. Vendor, Bill, Purchase, PurchaseOrder, BillPayment and Attachable are the objects we read and write. This is what we would propose for almost every QuickBooks Online company.
File
QuickBooks Desktop
Desktop takes transactions through the QuickBooks Desktop SDK (qbXML over the Web Connector) or IIF import files. We treat both as file integration: batches on a schedule and a reconciliation report, rather than a live link.
Custom
Several company files, or several systems
Groups with four or five company files, or a QuickBooks that is one of three systems in the flow, usually need orchestration on top of the API: one queue, one approval policy, one authorisation per company file.
Our default for QuickBooks Online is API integration: the Accounting API for reads and writes, and Intuit webhooks for change notifications on Bill, Vendor and BillPayment, so payment status reaches FinSuite without polling. Intuit withdrew QuickBooks Online from India in 2023, so the companies we see on it are usually the overseas entities of an Indian group, or businesses run from the US, UK, Canada or Australia with tax handled by that edition. Rate limits apply per company file and the sync is sized to stay inside them.
Field mapping
Where each finance object lands in QuickBooks Online
The mapping is agreed before build and kept per company file. This is the starting point we bring to the assessment.
The entry, on both sides · Illustrative example
Field mapping is yours to define. Entries are validated against it before they reach the ERP, not rejected by it afterwards.
Security of the connection
What protects the link to your company file
Four controls, each one visible to your admin. None of them depends on trusting us.
OAuth 2.0, granted by your admin
Your QuickBooks admin authorises the connection on Intuit's consent screen and can revoke it there. We hold no QuickBooks password. Tokens are stored encrypted and refreshed on Intuit's schedule.
Accounting scope and nothing else
The app asks for the accounting scope only: no payments scope, no payroll. The scope is reviewed at assessment against what the workflow needs.
Signed webhooks, verified
Every webhook from Intuit carries a signature computed with the verifier token. We check it before a payload is trusted. Unsigned or mismatched calls are dropped and logged.
Writes you can audit
Each Bill or Vendor we create records who approved it, which document it came from and the Id QuickBooks returned. A sandbox company first; production after you have seen the entries.
FAQ
Questions QuickBooks teams ask
Do you work with QuickBooks Desktop, or only Online?
Both, but differently. QuickBooks Online has the REST API and webhooks, so the link can be live. Desktop talks through the Desktop SDK and the Web Connector, or takes IIF files, and we plan it as a scheduled batch with a reconciliation report. If you are on Desktop Enterprise for inventory, tell us early; the batch is designed around the stock postings.
Will bills show up in QuickBooks before they are approved?
No. A Bill is a posted transaction in QuickBooks Online the moment it is created; there is no draft state. FinSuite holds the document until approval, then writes it. If you would rather approve inside QuickBooks Online Advanced using its workflow feature, we create the Bill first and leave approval there. One place approves, never both.
We have four company files. Does that need four integrations?
One integration, four authorisations. Each company file is authorised separately by its admin, and each has its own vendor list and chart of accounts, so the mapping is kept per file. The queue is shared, with the company as a dimension, so one team can work all four.
Is this an app on the QuickBooks app store?
No. The connection is registered as an app on a developer account and authorised privately for your company file. We do not claim a marketplace listing or a partnership with Intuit, and we would rather build it to your file than ship something generic.
Keep reading
Related integrations
Zoho Integration
The other mid-market suite we plan around, with Indian GST built into the ledger.
Read more →Tally Integration
Where the Indian entity of a QuickBooks group usually keeps its books.
Read more →FinSuite Integrations
The four integration methods and how FinSuite posts into any ledger.
Read more →All integrations
ERPs, accounting suites, the REST API and webhooks in one list.
Read more →Next step
Bring a month of bills and your chart of accounts
An assessment starts with your real documents and a sandbox company file. Nothing touches production until you have seen the entries.