Sales invoices, credit notes, purchase orders and sales receipts — all posted automatically from your ERP, IMS or eCommerce platform. Bidirectional sync keeps QBO and your operational systems aligned. Class and Location tracking applied at posting so your reporting stays intact without manual intervention.
QuickBooks Online distinguishes between transaction types in ways that matter operationally. Invoices, sales receipts, credit notes and purchase orders each have their own QBO model, their own workflow and their own place in your chart of accounts. Supply Lens handles each correctly.
Invoices, sales receipts, credit notes and purchase orders all flow from wherever transactions originate — eCommerce, ERP or IMS — and land in QBO correctly formatted, classified and matched.
QBO's API is well-documented and the OAuth flow is stable. The complexity is in using the right transaction type, applying Class and Location consistently, and keeping customer and vendor records aligned across systems.
QBO makes an important distinction between an Invoice (money owed, payment pending) and a Sales Receipt (payment received at the time of sale). Shopify DTC orders that are paid at checkout should create Sales Receipts, not Invoices — otherwise QBO's accounts receivable fills with transactions that have already been paid and need manual settlement. Supply Lens applies the correct transaction type based on the order's payment status and the configured rule for each source channel, so paid orders and on-terms orders each land in QBO in the right form from the start.
Class tracking in QBO is only useful if it is applied consistently and correctly at the point of every transaction. A batch of manually entered transactions with missing Class assignments corrupts the entire segment report. Supply Lens derives Class and Location values from the source order data — the channel, warehouse, customer type or any rule you define — and applies them automatically to every invoice, sales receipt, credit note and purchase order at the moment of creation. There is no manual editing of QBO transactions to add Class values after the fact.
QBO customer records accumulate quickly when every order creates a new entry without checking for an existing match. Supply Lens resolves the QBO customer before creating any transaction — matching by email address, company name, account reference or any combination you define. Guest checkout orders are handled with a configurable strategy: match to an existing account, create a named record, or route to a single generic guest customer. The customer resolution logic runs before every transaction, so duplicates do not accumulate regardless of order volume.
In QBO, a credit note is most useful when it is linked to the specific invoice it relates to — this keeps the customer's balance accurate, makes reconciliation straightforward and keeps the audit trail clean. Supply Lens matches every credit note to the original invoice reference from the source system before posting to QBO, linking the two transactions correctly. Where the return is partial, the credit note covers only the returned lines and the original invoice balance is reduced accordingly, leaving the unreturned portion correctly outstanding.
The scope call usually takes 30 minutes. The main configuration work is account code mapping, Class and Location rules, and agreeing the transaction type logic per source channel.
Ongoing support includes account code updates, Class rule changes and QBO API version compatibility maintenance.
Invoices, sales receipts, credit notes and purchase orders — all four transaction types automated. 30-day trial available.