What the public information establishes
A named integration option
Blackstone’s developer page names QuickBooks among integration options. Its equipment and invoicing pages also reference accounting connections. Those references do not identify one universal connector or prove support for every edition.
What remains to confirm
Get the connector name, supported Online or Desktop product, setup route, and the exact records it changes. Payment acceptance, invoice records, fees, and bank reconciliation are different requirements. Do not assume all are included.
Which QuickBooks payment workflow do you use?
Online or Desktop
Start with the exact QuickBooks product and version. Do not assume that an integration announced for QuickBooks supports both Online and Desktop.
Invoice payments or accounting records
Taking a payment from an invoice and synchronizing a payment already collected are different tasks. Identify which task you need before assessing the connector.
What records need to reconcile?
Gross payments, fees, and deposits
For a sample invoice, identify the payment amount, processing charge, and net bank deposit. Ask which entries the connector creates and which must still be matched manually.
Refunds and duplicate entries
Ask how refunds, partial payments, and an existing bank feed are handled. The setup should avoid recording the same payment twice.
What should be tested before rollout?
Your actual invoice flow
Use an approved test process for an invoice, payment, partial payment if needed, and refund. Compare the result with the gateway and bank feed workflow.
Availability and cost
Confirm the released connector, supported product, setup owner, and recurring charges in writing. Blackstone’s announcement does not establish support for every QuickBooks workflow.