Nexra
Start in the sandbox
All connectors
QuickBooks Desktop logo

QuickBooks Desktop

Accounting, billing & payments

Keep QuickBooks Desktop in step with your orders, invoices and payments without re-keying, with the right person approving what changes.

9 ways to read.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
QuickBooks Desktop with Nexra

Connected, approved, proven.

The things teams do most with QuickBooks Desktop, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • List bill paymentsbill_payments.listRead

Example flow

  1. QuickBooks Desktop · List bill paymentsbill_payments.listDone
  2. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches QuickBooks Desktop.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to QuickBooks Desktop
  • QuickBooks Desktop's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Reads QuickBooks Desktop invoices, payments, credit notes, journal entries, deposits, sales orders, customers and items through the Nexra relay and the QuickBooks Web Connector.

Intuit API docs
Source actions
9
Data types
9

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

bill payments1
  • List bill paymentsSourceIncremental

    Payments to vendors by cheque (BillPaymentCheckQueryRq).

credit notes1
  • List credit notesSourceIncremental

    Customer credit memos (CreditMemoQueryRq).

customers1
  • List customersSourceIncremental

    Customers (CustomerQueryRq), active and inactive.

deposits1
  • List bank depositsSourceIncremental

    Bank deposits (DepositQueryRq).

invoices1
  • List invoicesSourceIncremental

    Invoices (InvoiceQueryRq), headers only.

items1
  • List itemsSourceIncremental

    Items of every type (ItemQueryRq): service, inventory, non-inventory and others.

journal entries1
  • List journal entriesSourceIncremental

    General journal entries with their lines (JournalEntryQueryRq).

payments1
  • List customer paymentsSourceIncremental

    Customer payments received (ReceivePaymentQueryRq).

sales orders1
  • List sales ordersSourceIncremental

    Sales orders (SalesOrderQueryRq), headers only.

Access and limits

Authentication
Signed in on your server through the QuickBooks Web Connector; nothing is stored in Nexra
Plans and access
QuickBooks Desktop Pro, Premier or Enterprise (2019 or later) with the QuickBooks Web Connector. The company file must be open on the QuickBooks computer, or QuickBooks set to allow access when no user is signed in.
Test environment
Use a copy of your company file for Test mode.
Rate limits
One request at a time per company file; each read waits for the Web Connector's next run (at most a minute).
Pagination
Opaque cursors from the relay agent (QuickBooks iterators within a fixed time window).
Provider events
QuickBooks Desktop has no outbound events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Needs a paired Nexra on-premise relay agent that is online; requests fail fast with a clear message while it is offline.
  • The relay agent only reaches the systems, paths and methods its administrator allows in its local configuration file.
  • Read only: Nexra builds qbXML query requests only and asks QuickBooks for read-only access, so it cannot add, change or delete QuickBooks data. Writes are not implemented.
  • Each read waits for the QuickBooks Web Connector to call the relay (scheduled at most once a minute), so a read can take up to about 100 seconds.
  • Vendor payments cover cheque bill payments; credit card bill payments are not read.
  • Needs on-site validation with a real QuickBooks Desktop company file: field names follow the qbXML 13.0 reference, and paging across calls repeats a fixed time window.

Developer reference

  1. Create the Intuit credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose QuickBooks Desktop, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Intuit docsAPI referenceIntuit docsAuthentication

Machine-readable detail: GET /api/public/connect/connectors/quickbooks-desktop and the Connections API.