Contact
StandardQuickBooksRefId__ctextPrimary_Billing_Contact__ccheckbox
Architecture · Object Schema
Every object in QBO by Tally, on one tree.
The data model behind the sync — generated straight from the managed package metadata. Salesforce CRM on top, QuickBooks mirrors beneath it, transaction documents in the middle with their line items hanging off master-detail spines, reference books at the base — and the plumbing kept deliberately link-free at the bottom. Expand any object to see every field it ships with.
32objects
614fields
7master-detail spines
36lookups
4self-hierarchies
2platform events
master-detail — owns its children, roll-upslookup — arrow points at the referenced objectconversion pathhover an object to isolate its relationships
01Salesforce Core— standard CRM objects, extended but never mangled
Account
StandardOpportunity Line Item
StandardQuickBooks_Taxable__ccheckbox
fires ActionOnOLI__e
Product
StandardQuickBooksRefId__ctextQBO_Sync_Status__ctext · formulaLast_Synced__cdatetime
02Identity Mirrors— who QuickBooks thinks you're doing business with
QBO Payment Option
CustomQuickbooks_Card_Id__ctextAccount_Number__cencryptedTokenization_Status__cpicklist
card + ACH vault
QBO Customer
CustomQuickBooksRefId__cext idSyncToken__ctextDisplay_Name__ctext
⟲ Parent_Customer__cbill-with-parent
Vendor
CustomId__cext idBalance__cnumberVendor1099__ccheckbox
full QBO vendor mirror
03Transaction Documents— the four papers money moves on
QBO Estimate
CustomQBO_RefId__ctextSubTotal__cΣ roll-upStatus__cpicklist
⇄ converts to Invoice__cParent_Object + Id pointer
QBO Invoice
CustomInvoice_Id__ctextSubTotal__cΣ roll-upAmount_Paid__ccurrencyPayment_Status__ctext
⟲ Parent_Invoice__c12-field recurring engine
QBO Sales Receipt
CustomQBO_Ref_Id__ctextSub_Total__cΣ roll-upPayment_Method__ctext
sale + payment in one
QBO Purchase Order
CustomQuickBook_RefId__cext idStatus__cpicklistTotal_Amount__cnumber
money going out, not in
04Line Items & Money— master-detail children; delete the parent and these go with it
QBO Estimate Item
CustomAmount__ccurrency · formulaRate__ccurrencyQuantity__cnumber
QBO Invoice Item
CustomQBO_Line_Id__cext idAmount__ccurrency · formula
QBO Payment
CustomAmount__ccurrencyStatus__cpicklist
QBO Sales Receipt Item
CustomAmount__ccurrency · formulaQuantity__cnumber
PO Line Item
CustomType__cpicklistAmount__cnumber
05Reference Books— QuickBooks lists cached locally, so pickers never wait on a callout
QBO Account
CustomAccountType__cpicklist
⟲ ParentRef__cchart of accounts
QBO Class
CustomFullyQualifiedName__ctext
⟲ Parent_Class__c
QBO Tax Code
CustomTotal_Tax_Value__cΣ roll-up
QBO Tax Rate
CustomTax_Value__cnumber
Payment Method
CustomId__cext id
Cash · Check · Credit Card
QBO Custom Field
CustomEntity__cmultipicklist
Custom Fields API defs
Custom Field Value
CustomValue__ctextLabel__ctext · formula
⚙︎ Plumbing — zero hard links, by design— auth, config, observability and async signals never hold a foreign key 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
SettingThe switchboard: endpoints + every feature toggle (product sync, sales receipts, custom fields…).
Configuration
MetadataPackage-shipped defaults: client id/secret, auth + callback URLs. (v1 __mdt kept but deprecated.)
Customer Sync Settings
SettingOne checkbox per attribute — field-by-field control over what syncs on a customer.
Trigger Switch
SettingOne checkbox per trigger — the kill-switch for automation.
QBO Log
CustomCorrelation id, direction, payloads, stack trace, duration — record ids stored as text so logging can never block a transaction.
Action On OLI
EventFired when opportunity products change; decouples CRM edits from sync work.
Populate Invoice Products
EventStreams product lines onto a draft invoice asynchronously.
Why it's shaped this way
Six deliberate decisions
None of this structure is accidental — each pattern answers a specific constraint of syncing two systems that both think they own the data.
01
Mirror, don't mangle
Every QuickBooks entity gets its own __c mirror object instead of being crammed into Account or Opportunity. Standard CRM objects stay clean (Account gets zero packaged fields), and each mirror carries a QuickBooksRefId__c external id plus SyncToken__c — the pair that makes every sync an idempotent upsert instead of a duplicate factory.
02
Master-detail where money rolls up
All five line-item objects, payments, and tax rates hang on master-detail. That's what buys the SubTotal__c roll-up summaries (the total is computed by the platform, never drift-prone Apex math) and cascade delete — an orphaned invoice line is structurally impossible.
03
Lookups where records outlive each other
Documents reference customers, tax codes, and products through plain lookups. Deactivating a QBO class or deleting a product must never take three years of invoices down with it — so ownership is reserved for lines, and reference is kept loose everywhere else.
04
The generic parent pointer
Every document carries a Parent_Object__c + Parent_Record_Id__ctext pair instead of a polymorphic lookup. That's what lets an invoice be spawned from an Opportunity, a Work Order, or any custom object — in any subscriber org — without the package declaring a hard dependency on objects that may not exist there.
05
Hierarchies mirror QuickBooks' own trees
QuickBooks nests things: sub-customers billed with parents, sub-classes, sub-accounts in the chart of accounts. Each mirror gets a self-lookup (Parent_Customer__c, Parent_Class__c, ParentRef__c) so the tree survives the trip — and Parent_Invoice__c chains recurring invoices to their template the same way.
06
Plumbing stays link-free
Tokens, config, logs, and events hold no foreign keys at all. Log__c stores related ids as text so a failed sync can be logged even when the record it references is gone; custom settings and metadata sit outside the transaction graph entirely; platform events decouple CRM edits from callout work. The plumbing can never deadlock the money.
Ready to unify QuickBooks and Salesforce?
Unify your QuickBooks experience directly from your Opportunities in Salesforce.