Clean books start with
intentional mappings.
Turn a POS catalog into an accounting structure you can trust—without treating menu categories like a chart of accounts.
Turn a POS catalog into an accounting structure you can trust—without treating menu categories like a chart of accounts.
Connect your sources to begin the audit.
Every stage is inspectable and reversible until the final confirmation.
Credentials never enter browser storage. They stay in server environment variables or an encrypted local vault.
Read items, variations, categories, SKUs, prices and tax flags using the Catalog API.
Read accounts, products/services and classes. Write only after a reviewed plan and explicit confirmation.
http://localhost:3000/api/qbo/callbackAccounts describe financial reporting. Classes describe the operating segment.
| Account name | Financial group | QBO type | Status |
|---|
Suggested rules are editable. Deferred sales stay flagged for recognition rather than being treated as ordinary revenue.
This creates missing records only. It does not post sales, journal entries, or deferred-revenue recognition.
Existing accounts are skipped by name.
Availability depends on your QBO plan and settings.
Mapped Square variations become QBO products/services.
Every item needs an income or liability destination.
Account and item creation is difficult to undo cleanly in QBO. Test this flow against an Intuit sandbox first.