Skip to main content
← Blog/Integration Guides

QuickBooks Desktop Web Connector Setup for EDI

Set up SignalEDI with QuickBooks Desktop 2024 through the QuickBooks Web Connector, verify the read-only handshake, and test EDI records safely.
CR

Christopher Rosecrans

· · 7 min read

Quick answer

QuickBooks Desktop Web Connector Setup for EDI

Set up SignalEDI with QuickBooks Desktop 2024 through the QuickBooks Web Connector, verify the read-only handshake, and test EDI records safely.

QuickBooks Desktop Web Connector setup for SignalEDI

SignalEDI connects to QuickBooks Desktop through Intuit's QuickBooks Web Connector. There is no separate SignalEDI Windows program to install. The Web Connector polls SignalEDI over HTTPS, carries qbXML requests into the company file that is open in QuickBooks Desktop, and returns a status for each request.

This guide covers the self-serve setup, a privacy-minimized read test, a controlled write test, and the recovery steps an operator should know before using the connection with production documents.

Compatibility and plan requirements

  • QuickBooks Desktop 2024: Pro Plus 2024, Premier Plus 2024, or Enterprise 24.0
  • A Windows version currently supported by Intuit for QuickBooks Desktop
  • QuickBooks Web Connector installed and updated
  • A SignalEDI Growth or Enterprise plan
  • QuickBooks administrator access for the first company-file authorization

SignalEDI's marketplace review environment uses QuickBooks Desktop Enterprise 24.0, QuickBooks Web Connector 34.0.10010.76, and qbXML 16.0 on Windows 11. Intuit now maintains the 2024 / 24.0 platform through continuous updates, so accept the in-product maintenance releases when prompted.

What the connector exchanges

The Desktop connector currently prepares these qbXML writes from eligible SignalEDI EDI records:

  • 810 invoice to a QuickBooks invoice
  • 850 purchase order to a bill in buyer mode or a sales order in supplier mode
  • 835 remittance to a received payment

An optional read-only inventory check queries active inventory items. SignalEDI stores only the resulting item count and snapshot time in the connector status; it does not store item names in the connection configuration.

Connect to QuickBooks Desktop

1. Provision the connection

Sign in to SignalEDI and open Signal Setup → ERP connectors → QuickBooks Desktop. Select Provision connection. SignalEDI displays a Web Connector username and a one-time password. Copy the password before leaving the page; only its hash is retained by SignalEDI.

2. Download the Web Connector profile

Select Download .qwc file. The profile points to SignalEDI's production HTTPS endpoint and identifies the SignalEDI application to the Web Connector.

3. Import and authorize the profile

Open the intended QuickBooks Desktop company as its administrator. In QuickBooks Desktop, go to File → App Management → Update Web Services, then select Add an Application in the Web Connector. Choose the downloaded SignalEDI .qwc file, approve the application for the open company, and enter the one-time Web Connector password.

4. Run the first update

Select the SignalEDI row in the Web Connector and run Update Selected. The first poll performs a read-only company query. A successful run ends with OK in the Web Connector, and all three setup steps show complete in SignalEDI. Auto-Run can then be enabled for the preferred interval; the downloaded profile defaults to 30 minutes.

Verify the required Desktop-to-SignalEDI read

In the QuickBooks Desktop status card, turn on Inventory read, then run the Web Connector again. The next successful poll shows the active item count and snapshot date in SignalEDI. Turn the read off at any time; the core EDI write flow does not depend on it.

Use a sample company for marketplace or onboarding tests. Do not record the one-time password, company-file path, account numbers, or real customer data in screenshots or support logs.

Run a controlled write test

Prepare one synthetic 850 or 810 in a non-production QuickBooks sample company, using customer, vendor, account, and item references that already exist in that company. Confirm the document is eligible for Desktop delivery in SignalEDI, then run Update Selected.

Verify both sides before testing another document:

  1. QuickBooks Desktop contains the expected bill, sales order, or invoice.
  2. SignalEDI shows the matching queue result, timestamp, request correlation, and QuickBooks transaction correlation.
  3. Replaying the same SignalEDI record does not create a second QuickBooks transaction.

Creating an accounting record changes the open QuickBooks company. Perform the write only in an approved sample company until mappings and references have been reviewed.

Recovery and safe disconnect

  • QuickBooks is offline: Open the intended company, then run Update Selected again. SignalEDI keeps queued work for a later poll.
  • Web Connector rejects a reference: Correct the missing customer, vendor, account, or item in the sample company before retrying. Review the reconciliation warning so an uncertain result is not duplicated.
  • Wrong company is open: Stop. The connector binds to the first authorized company and fails closed if a different company file polls.
  • Password is lost or expired: Select Rotate credentials in SignalEDI, save the newly shown one-time password in the Web Connector, and run the update again.
  • The connection should stop: Select Disconnect in SignalEDI. Existing tickets and credentials fail closed. Remove the SignalEDI application from the Web Connector if the local profile is no longer needed.

Support and policy links

For help, email support@signaledi.com. Never send a Web Connector password or an unredacted QWCLog.txt file by email.

Same EDI mandate. Different connect path.

Partner 850/856/810 requirements do not relax for Desktop. QuickBooks Online starts OAuth from the public mandate; QuickBooks Desktop opens the in-app Web Connector card.

Apps, Connect, and trial

Connect to QuickBooks Online through the public OAuth mandate, or open the matching in-app Connect card for QuickBooks Online or QuickBooks Desktop. The free trial and published pricing are one click away.

850, 855, 856, and 810 land as QuickBooks drafts

Retailer X12 stays reviewable. Finance approves the accounting write — automation handles translation, not silent posting.

QuickBooks does not speak X12 natively — post JSON, ship compliant EDI

An 850 purchase order arrives as X12, becomes a reviewable QuickBooks sales-order draft, and your 810 invoice goes back out as compliant X12. Developers work in JSON; SignalEDI owns the segment translation.

850 → QuickBooks sales-order draft

Inbound 850 parsed to JSON your code can review before creating the draft — no BEG/PO1 segment parsing.

POST /v1/documents/parse
{
  "partner": "walmart",
  "transactionSet": "850",
  "target": "quickbooks-sales-order-draft",
  "payload": {
    "poNumber": "PO-88142",
    "lines": [{ "sku": "WIDGET-01", "qty": 120 }]
  }
}
// → 200 { "draftId": "qbo-draft_9f3k",
//         "status": "awaiting-review" }

JSON → 810 invoice out

Post invoice JSON; SignalEDI validates the PO three-way match and emits compliant X12 810 to the partner.

POST /v1/documents/emit
{
  "partner": "walmart",
  "transactionSet": "810",
  "source": { "draftId": "qbo-draft_9f3k" },
  "invoice": {
    "poNumber": "PO-88142",
    "total": 14280.00
  }
}
// → 202 { "x12": "accepted",
//         "ack": "997 pending" }

Flat pricing for QuickBooks-first teams

No standard setup fee and no per-document toll. Start on the 30-day trial, then pick the tier that matches volume.

QuickBooks Desktop EDI

Evaluate the Web Connector flow

Growth and Enterprise include the Desktop connector, a visible queue, read-only verification, and guarded recovery when QuickBooks cannot confirm a result.

© 2026 SignalEDI Inc. All rights reserved.