This glossary covers all entities supported in the QuickBooks integration. Use this as a reference when mapping fields, configuring sync rules, or troubleshooting records.
1. Account
What it is: An Account represents a category in your Chart of Accounts (COA) used to classify every financial transaction in QuickBooks. It is the backbone of your entire accounting structure.
Account Types:
|
Account Type |
Sub-types |
Purpose |
|---|---|---|
|
Asset |
Bank, Accounts Receivable, Other Current Asset, Fixed Asset |
Things you own |
|
Liability |
Accounts Payable, Credit Card, Other Current Liability, Long-term Liability |
Things you owe |
|
Equity |
Owner's Equity, Retained Earnings |
Net worth of the business |
|
Income |
Sales, Other Income |
Revenue earned |
|
Expense |
Cost of Goods Sold, Operating Expense, Other Expense |
Money spent |
Key Fields: Name, Account Type, Account Sub-type, Account Code (Number), Currency, Description, Parent Account (for sub-accounts), Active/Inactive status.
How it's used in integration: Every transaction line — Invoice, Bill, Journal Entry, Payment — must be mapped to an Account. During integration setup, your external system's categories are mapped to QuickBooks Accounts.
Things to note:
-
Accounts cannot be deleted if transactions exist against them — they are marked Inactive
-
Sub-accounts allow hierarchical reporting (e.g., Travel > Airfare, Travel > Hotel)
-
The Account Number field is optional but recommended for large Charts of Accounts
-
Accounts Receivable and Accounts Payable types are reserved for Customer and Vendor transactions respectively
2. Customer
What it is: A Customer is a person, company, or organization that purchases goods or services from your business. All sales transactions in QuickBooks must be linked to a Customer.
Key Fields: Name, Display Name, Email, Phone, Billing Address, Shipping Address, Payment Terms, Currency, Tax Code, Opening Balance, Active/Inactive status.
How it's used in integration: Customers are synced from your CRM, e-commerce platform, or billing system into QuickBooks. Every Invoice, Payment, Credit Memo, and Sales Receipt must reference a Customer record.
Things to note:
-
QuickBooks supports Sub-customers to represent jobs or projects under a parent Customer (e.g., ABC Corp > Project Apollo)
-
Duplicate detection is typically done by Name or Email
-
A Customer cannot be deleted if transactions exist — it is marked Inactive instead
-
In QuickBooks Online, Customers and Vendors can share the same contact but must be created as separate records
3. Vendor
What it is: A Vendor is a person, company, or contractor that you purchase goods or services from. All purchase transactions in QuickBooks must be linked to a Vendor.
Key Fields: Name, Display Name, Email, Phone, Billing Address, Payment Terms, Currency, Tax ID, Account Number, Opening Balance, 1099 Flag, Active/Inactive status.
How it's used in integration: Vendors are synced from procurement systems, ERP platforms, or supplier portals. Every Bill, Bill Payment, Purchase Order, and Vendor Credit must reference a Vendor record.
Things to note:
-
Employees paid through payroll are not created as Vendors
-
US-based Vendors eligible for 1099 reporting have a dedicated flag that must be set correctly
-
A Vendor cannot be deleted if transactions exist — it is marked Inactive instead
-
The Account Number field stores your company's reference number with the Vendor (e.g., your supplier account ID)
4. Product / Item
What it is: A Product or Item (called Item in QuickBooks) represents a good or service that your business buys or sells. Items appear as line entries on Invoices, Bills, Purchase Orders, and Estimates.
Item Types:
|
Item Type |
Description |
Used On |
|---|---|---|
|
Inventory |
Physical goods tracked by quantity and value |
Invoices, Bills, POs |
|
Non-Inventory |
Physical goods not tracked by quantity |
Invoices, Bills |
|
Service |
Labor or services rendered |
Invoices, Bills |
|
Bundle |
A group of items sold together as a package |
Invoices only |
Key Fields: Name, SKU, Item Type, Description, Sales Price, Cost, Income Account, Expense/COGS Account, Inventory Asset Account (for Inventory type), Tax Code, Quantity on Hand, Active/Inactive status.
How it's used in integration: Items are synced from your product catalog, inventory management system, or e-commerce platform. When an Invoice or Bill is created, each line item references a Product/Item record which drives the account posting automatically.
Things to note:
-
Each Item must be mapped to at least one Account — an Income Account for sales and an Expense Account for purchases
-
Inventory Items additionally require an Inventory Asset Account and a starting Quantity on Hand
-
Bundles do not track individual component inventory in QBO
-
Item names must be unique in QuickBooks
-
Deleting an Item is not allowed if it has been used on transactions — it is marked Inactive
5. Invoice
What it is: An Invoice is a formal request for payment sent to a Customer for goods or services delivered. It is the primary Accounts Receivable (AR) transaction in QuickBooks.
Key Fields: Invoice Number, Customer, Invoice Date, Due Date, Line Items (Item/Account, Description, Quantity, Rate, Amount), Discount, Tax, Total Amount, Amount Due, Status (Draft, Open, Paid, Void).
Invoice Lifecycle:
|
Status |
Meaning |
|---|---|
|
Draft |
Created but not yet sent to the customer |
|
Open |
Sent to customer, payment pending |
|
Partially Paid |
One or more payments applied, balance remaining |
|
Paid |
Fully paid, zero balance |
|
Void |
Cancelled — reverses the accounting entry but record is retained |
How it's used in integration: Invoices are generated from orders in your e-commerce, billing, or ERP system and pushed into QuickBooks. Payments received against those Invoices are then applied to reduce the open balance.
Things to note:
-
An Invoice increases Accounts Receivable on creation
-
Each line item must reference either a Product/Item or a direct Account
-
Partial payments are fully supported — the Invoice stays Open until the balance is zero
-
Voiding an Invoice reverses the AR impact but does not delete the record
-
Invoice Numbers must be unique — integration should handle de-duplication or use QuickBooks auto-numbering
6. Journal Entry
What it is: A Journal Entry (JE) is a manual accounting record that directly debits and credits General Ledger accounts. It is used for adjustments, accruals, corrections, and transactions that do not fit any standard QuickBooks form.
Key Fields: Journal Date, Reference Number, Currency, Lines — each line contains: Account, Debit Amount, Credit Amount, Description, Name (Customer/Vendor/Employee), Class, Department.
Common Use Cases:
|
Use Case |
Example |
|---|---|
|
Accruals |
Recognizing revenue or expense before cash moves |
|
Depreciation |
Monthly depreciation of fixed assets |
|
Inter-company transfers |
Moving funds between entities |
|
Opening balances |
Posting historical balances during migration |
|
Corrections |
Fixing a mis-posted transaction |
|
Bulk imports |
Posting summarized data from external systems |
How it's used in integration: Journal Entries are used when transactions from external systems do not map cleanly to QuickBooks native forms, or when summary-level postings are needed (e.g., daily sales totals from a POS system posted as a single JE).
Things to note:
-
Total Debits must always equal Total Credits — the entry will not save otherwise
-
Journal Entries bypass the AR and AP sub-ledgers — do not use them for customer or vendor transactions if you need aging reports or reconciliation
-
A Name (Customer/Vendor) can optionally be attached to a JE line for reporting purposes but it does not create a transaction in the sub-ledger
-
Journal Entries are difficult to reverse once downstream transactions are posted against them — use with caution
7. Payment
What it is: A Payment (Customer Payment) records money received from a Customer and applies it against one or more open Invoices. It is the transaction that closes or reduces the Accounts Receivable balance.
Key Fields: Customer, Payment Date, Payment Method (Cash, Check, Credit Card, ACH, Bank Transfer), Reference / Check Number, Deposit To Account, Amount Received, Applied-to Invoices (Invoice Number + Amount Applied).
Payment Application Scenarios:
|
Scenario |
How QuickBooks Handles It |
|---|---|
|
Full payment against one Invoice |
Invoice marked as Paid, AR reduced fully |
|
Partial payment against one Invoice |
Invoice stays Open with remaining balance |
|
Payment split across multiple Invoices |
Each Invoice reduced by its applied amount |
|
Overpayment |
Excess sits as a Customer Credit for future use |
|
Unapplied payment |
Sits as a credit on the Customer record until manually applied |
How it's used in integration: Payments are synced from payment gateways, bank feeds, or POS systems. The integration matches the Payment to the correct open Invoice using Invoice Number, Amount, or Customer reference.
Payment Gateway Integration via Cloud Maven's Payment App: Customers can sync payments directly into QuickBooks using Cloud Maven's Payment App, powered by the Payment Guru platform. It integrates with 30+ payment gateways — including ACH, credit card, and secondary gateways — reducing processing costs and increasing payment flexibility.
Supported gateway types include:
|
Gateway Type |
Examples |
|---|---|
|
ACH / Bank Transfer |
Direct bank debits, eChecks |
|
Credit Card |
Visa, Mastercard, Amex, Discover |
|
Secondary Gateways |
30+ additional gateway integrations via Payment Guru |
Things to note:
-
A Payment must be deposited to a specific Bank or Undeposited Funds account in QuickBooks
-
Using the Undeposited Funds account is recommended when batching multiple payments into a single bank deposit
-
Payments cannot be applied to Invoices belonging to a different Customer
-
Deleting a Payment reopens the Invoice it was applied to
-
Payment Method does not affect accounting — it is for reporting and reconciliation purposes only
8. Sales Receipt
What it is: A Sales Receipt records a completed sale when payment is received at the time of purchase. Unlike an Invoice, it does not create an open Accounts Receivable balance because the payment is recorded immediately.
Key Fields: Customer, Sales Receipt Date, Sales Receipt Number, Payment Method, Deposit To Account, Billing Email, Line Items (Item/Account, Description, Quantity, Rate, Amount), Discount, Tax, Total Amount, Class.
How it's used in integration: Sales Receipts are synced from e-commerce platforms, point-of-sale systems, payment gateways, or other billing systems when a customer has already paid. The integration creates the receipt in QuickBooks, records the payment, and posts the funds to the selected Bank or Undeposited Funds account.
Things to note:
-
A Sales Receipt should be used for completed or prepaid sales; use an Invoice when payment is expected later
-
A Customer reference is required when the sale must be associated with a specific QuickBooks Customer
-
The Payment Method identifies how the customer paid, while the Deposit To Account identifies where the funds are recorded
-
Use the Undeposited Funds account when payments will be grouped into a later bank deposit
-
Each line item must reference a Product/Item or a direct Account, with the appropriate quantity, rate, and amount
-
Sales Receipt numbers should be unique to prevent duplicate records during synchronization