Contact
StandardQuickBooksRefId__ctextPrimary_Billing_Contact__ccheckbox
Every object in the packageon one tree
The data model behind Tally for QuickBooks, generated from the managed package metadata. Salesforce objects on top, QuickBooks mirrors beneath them, documents and their line items in the middle, reference lists below and the plumbing at the bottom.
- objects
- 32
- fields
- 624
- master-detail links
- 7
- lookups
- 40
- self-hierarchies
- 4
- platform events
- 2
The treewith every field
Each card shows the fields that matter most. Open one to see every field it ships with, their types and what they point at.
master-detail: owns its children, roll-upslookup: arrow points at the referenced objectconversion pathHover an object to isolate its relationships.Open any object to see every field it ships with.
01Salesforce CoreStandard CRM objects, extended with a few packaged fields
Account
StandardOpportunity Line Item
StandardQuickBooks_Taxable__ccheckbox
Product
StandardQuickBooksRefId__ctextQBO_Sync_Status__ctext · formulaLast_Synced__cdatetime
- Points to
- Vendor
02Identity MirrorsCustomers, vendors and saved payment methods, kept in sync with QuickBooks
QBO Payment Option
CustomQuickbooks_Card_Id__ctextAccount_Number__cencryptedTokenization_Status__cpicklist
saved cards and bank accounts
- Points to
- Contact, Account
QBO Customer
CustomQuickBooksRefId__cext idSyncToken__ctextDisplay_Name__ctext
self-lookup: Parent_Customer__cbill-with-parent
- Points to
- Account
Vendor
CustomId__cext idBalance__cnumberVendor1099__ccheckbox
full QBO vendor mirror
03Transaction DocumentsEstimates, invoices, sales receipts and purchase orders
QBO Estimate
CustomQBO_RefId__ctextSubTotal__cΣ roll-upStatus__cpicklist
converts to Invoice__cparent object + record id
- Points to
- QBO Customer
- Owns
- QBO Estimate Item
- Converts
- QBO Invoice
QBO Invoice
CustomInvoice_Id__ctextSubTotal__cΣ roll-upAmount_Paid__ccurrencyPayment_Status__ctext
self-lookup: Parent_Invoice__crecurring schedule fields
- Points to
- Account, Contact, QBO Customer, QBO Payment Option
- Owns
- QBO Invoice Item, QBO Payment
- Converts
- QBO Estimate
QBO Sales Receipt
CustomQBO_Ref_Id__ctextSub_Total__cΣ roll-upPayment_Method__ctext
sale + payment in one
- Points to
- QBO Customer
- Owns
- QBO Sales Receipt Item
QBO Purchase Order
CustomQuickBook_RefId__cext idStatus__cpicklistTotal_Amount__cnumber
money going out, not in
- Points to
- QBO Customer, Vendor
- Owns
- PO Line Item
04Line Items & MoneyMaster-detail children: delete the parent and they go with it
QBO Estimate Item
CustomAmount__ccurrency · formulaRate__ccurrencyQuantity__cnumber
- Points to
- QBO Estimate
QBO Invoice Item
CustomQBO_Line_Id__cext idAmount__ccurrency · formula
- Points to
- QBO Invoice
QBO Payment
CustomAmount__ccurrencyStatus__cpicklist
- Points to
- QBO Invoice
QBO Sales Receipt Item
CustomAmount__ccurrency · formulaQuantity__cnumber
- Points to
- QBO Sales Receipt
PO Line Item
CustomType__cpicklistAmount__cnumber
- Points to
- QBO Purchase Order
05Reference BooksQuickBooks lists synced into Salesforce
QBO Account
CustomAccountType__cpicklist
self-lookup: ParentRef__cchart of accounts
QBO Class
CustomFullyQualifiedName__ctext
self-lookup: Parent_Class__c
QBO Tax Code
CustomTotal_Tax_Value__cΣ roll-up
- Owns
- QBO Tax Rate
QBO Tax Rate
CustomTax_Value__cnumber
- Points to
- QBO Tax Code
Payment Method
CustomId__cext id
Cash · Check · Credit Card
QBO Custom Field
CustomEntity__cmultipicklist
Custom Fields API definitions
- Owns
- Custom Field Value
Custom Field Value
CustomValue__ctextLabel__ctext · formula
- Points to
- QBO Custom Field
06Plumbing, with no hard linksAuth, configuration, logs and events hold no foreign keys that could lock, cascade or block a transaction.
QBO API Token
CustomOAuth access + refresh tokens, realm id, and a mirror of QBO company preferences.
Configurations
SettingEndpoints, defaults and feature switches: product sync direction, sales receipt sync, the Custom Fields API, card and ACH options.
Configuration
MetadataPackage-shipped defaults: client id and secret, auth, token and callback URLs.
Customer Sync Settings
SettingOne checkbox per attribute — field-by-field control over what syncs on a customer.
Trigger Switch
SettingOne row per trigger, by name, with an IsActive box: turn a trigger off without a deploy.
QBO Log
CustomCorrelation id, direction, payloads, stack trace and duration. Record ids are stored as text, so a log can be written even when its record is gone.
Action On OLI
EventA platform event that carries an opportunity id and the action that triggered it.
Populate Invoice Products
EventThe invoice and purchase order product tables subscribe to it: product lines published here appear on the open form.
Six decisionsbehind the shape
Each pattern answers a constraint of keeping two systems in sync when both of them think they own the data.
01
Mirror QuickBooks, leave CRM objects alone
Each QuickBooks entity gets its own __c object instead of being packed into Account or Opportunity. Account ships with no packaged fields. Each mirror stores the QuickBooks id of its record, and several also keep the SyncToken__c version stamp QuickBooks requires on every update.
02
Master-detail where money rolls up
Four line-item objects, payments, tax rates and custom field values hang on master-detail. The subtotals on invoices, estimates and sales receipts are roll-up summaries the platform computes, and deleting a document deletes its lines with it.
03
Lookups where records outlive each other
Documents reference customers, tax codes and products through lookups. Retiring a class or deleting a product does not take the invoices that used it along with it. Ownership is kept for lines only.
04
A parent pointer that works on any object
Invoices, estimates, sales receipts and purchase orders store the parent object name and record id as text (for example Parent_Object__c and Parent_Record_ID__c) instead of a hard lookup. That is what lets a document start from an opportunity, a work order or a custom object without the package depending on objects your org may not have.
05
QuickBooks' own trees survive the trip
QuickBooks nests sub-customers, sub-classes and sub-accounts. Their mirrors carry a self-lookup (Parent_Customer__c, Parent_Class__c, ParentRef__c), and Parent_Invoice__c links each recurring invoice to the invoice it was generated from.
06
Plumbing holds no foreign keys
Tokens, configuration, logs and events carry no lookups. Log__c stores record ids as text, so a failed sync can still be logged after its record is gone. Custom settings and metadata sit outside the data model entirely.