Reviewed October 17, 2026. The current guides describe build 1.19.48. See Release notes for the difference between the tested preview and the public store release.
| Environment | What has been checked | Availability / limits |
|---|---|---|
| Chrome on macOS | Installed workflows and settings in earlier desktop builds; latest source covered by 177 automated regression tests | Public store release is older; check the installed version |
| Edge on macOS | Installed desktop workflows, payment navigation, settings and backups | Testing does not establish an Edge Add-ons publication |
| Safari on macOS | Signed 1.19.48 build 50: bill, receipt and vendor remittance, native printing, Quick Create and 13-field settings retention | Submitted to Apple review; store-delivered installation and update checks follow availability. Refresh QBO after import |
| Windows browsers | Selected behavior has automated coverage | Installed UI and Ctrl-key variants are not fully qualified |
| iOS Safari | Unsigned simulator Release wrapper builds | Installed iOS UI and signed distribution remain unverified |
QuickBooks Online requirements
The extension is scoped to qbo.intuit.com and sandbox.qbo.intuit.com. It does not enhance QuickBooks Desktop. It uses the controls and data your QBO account can already access; it does not grant extra company permissions.
Features appear where they belong
- Print Remit needs a saved bill with applied payments.
- Print Receipt needs a supported saved bill payment.
- Vendor Remittance appears on a supported vendor detail page.
- Quick Create and related workflow controls require Workflow Polish. Quick Create also needs at least one non-blank action.
- Creator filters and aliases require a supported table with creator information.
- Report controls depend on supported report-builder row and header structures.
Printing and changes to QBO
Print layout varies by browser. Safari’s multi-page bill remit can omit repeated column headings on later pages. Review the generated output before saving or sharing it.
QBO can change its interface, and company layouts differ. Older or newly introduced forms are not all covered. If a required native control becomes difficult to use, disable the extension and refresh QBO, then report the page and version.