Table of Contents
Toweringmedia QuickBooks Connector User Guide
Related overview
For a shopper-friendly overview of features and setup, see the Magento 2 QuickBooks Online Connector User Guide on the storefront. This wiki page remains the full technical documentation.
Extension context
This is a Toweringmedia Magento 2 extension guide for the current admin extension catalog.
Product page
- Toweringmedia QuickBooks Connector (SKU
tm-quickBooks-connector)
Overview
This connector links Magento 2 with QuickBooks so that order, customer, and accounting records can be kept in step. It provides a queued sync with configurable direction, field mapping, sync rules, and a conflict review screen for records that changed on both sides.
What this extension does
- Queued synchronisation between Magento and QuickBooks.
- Configurable sync direction and conflict resolution policy.
- Field mapping between Magento and QuickBooks records.
- Sync rules to control which records are eligible.
- Conflict review screen for records changed in both systems.
- Sync operation logs.
Requirements
- Magento 2.4.x (Open Source or Adobe Commerce).
- PHP: >=8.1 <8.5 (as declared by the published package).
- A current Toweringmedia license and Composer credentials for
https://composer.toweringmedia.com/. - A QuickBooks account with API access and an Intuit developer app for credentials.
- Composer resolves
toweringmedia/module-baseautomatically.
Installation
Install and validate in a staging environment before production rollout.
cd /path/to/magento composer require toweringmedia/module-quickbooks-connector bin/magento module:enable Toweringmedia_QuickbooksConnector bin/magento setup:upgrade bin/magento setup:di:compile bin/magento setup:static-content:deploy -f bin/magento cache:flush
Currently published versions at the time of writing:
toweringmedia/module-quickbooks-connector— 0.5.2
Toweringmedia packages are served from the licensed Composer repository https://composer.toweringmedia.com/. If Composer reports that the package could not be found, your credentials are missing or the license does not cover this package yet. Retrieve your keys from My Account on toweringmedia.com, or contact support@toweringmedia.com.
General installation notes that apply to every Toweringmedia extension are in the installation guide.
Package naming note
The storefront product and CMS guide refer to the QuickBooks Online Connector, but the Composer package is toweringmedia/module-quickbooks-connector (no -online segment). The install command above uses the real package name.
Configuration
- Stores > Configuration > Towering Media > QuickBooks Connector (config section
toweringmedia_quickbooks_connector). - Groups include
generalwith connector type, profile scope mode, global sync direction, and default conflict policy. - Admin screens: System > QuickBooks Connector > Configuration, Pending Sync Queue, Sync Operation Logs, Conflict Review, Field Mapping, Sync Rules.
Basic usage and what to expect
- Set the connector type and sync direction first, then complete the QuickBooks authorization.
- Review Field Mapping before enabling any sync so records land on the correct QuickBooks fields.
- Use Pending Sync Queue and Sync Operation Logs to confirm records are moving, and Conflict Review for records that changed on both sides.
Notes and limitations
- This package is currently published at a pre-1.0 version. Confirm the feature set for your QuickBooks edition (Online vs Desktop) with support@toweringmedia.com before relying on it for production accounting.
Validation checklist
bin/magento module:statusshows the module(s) as enabled.- Extension configuration saves without errors in Admin.
- The admin screens listed above are reachable and load without error.
- Expected storefront/admin behavior is present after a cache flush.
- No critical PHP/JS errors appear in
var/log/during the primary test flow.
Troubleshooting
- Composer cannot find the package: confirm the
https://composer.toweringmedia.com/repository and your credentials are present inauth.json, and that your license covers this package. - Feature not visible: verify module status, flush cache, and redeploy static content.
- Admin setting not applying: clear cache and confirm the config scope (default / website / store view).
- Unexpected behavior: retest with only the required related modules enabled.
