Creatio to QuickBooks Online — SmartTracks Training
Your Creatio–QuickBooks Online SmartTracks, Explained
This training program walks Berkowitz Pollack Brant's teams through the Creatio-to-QuickBooks Online integration — how it works day to day, how to read its status, and how to configure and support it.
Before this integration, Berkowitz Pollack Brant's sales and account teams worked in Creatio while accounting worked in QuickBooks Online — two systems, no automatic connection. Every order, estimate, invoice, credit memo, payment, and deposit had to be re-keyed by hand. InterWeave's SmartTracks Solution closes that gap: records created in Creatio now flow automatically into QuickBooks Online, and confirmation status flows back. This document is the companion training to Master Support Document IW-BPB-MSD-2026-01, which remains the technical source of truth for Berkowitz's configuration, scope, and SLAs.
Training is organized into two tracks. The End User Track is for Berkowitz's sales and account teams who create and manage records day to day. The Admin & IT Track is for the team members responsible for monitoring, configuration, and QuickBooks Online alignment. Most people only need one track — a few sections are shared by both.
Working in Creatio
For Berkowitz staff who create and manage Accounts, Orders, Estimates, and Invoices in Creatio and need to understand how that data lands in QuickBooks Online.
- Module 01 — Platform Orientation
- Module 02 — Daily Workflows in Creatio
- Module 03 — Reading Sync Status & Self-Service Fixes
- Module 07 — Support Escalation & Change Requests
Configuring & Supporting the Integration
For Berkowitz's IT and finance systems administrators responsible for configuration, monitoring, and QuickBooks Online hierarchy alignment.
- Module 01 — Platform Orientation
- Module 04 — Object & Field Mapping Reference
- Module 05 — Connection, Error Management & Credentials
- Module 06 — Customer Hierarchy & Location Tagging
- Module 07 — Support Escalation & Change Requests
Seven Modules, Two Tracks
Work through the modules assigned to your track in order. Module 01 and Module 07 are shared by everyone.
Platform Orientation
What the Creatio–QuickBooks Online SmartTracks Solution does for Berkowitz, the five-layer platform stack (AI SmartAgents → FlowCopilot → SmartFlows → SmartIntegration → Connector Ecosystem), and a plain-language walkthrough of the data flow from Creatio into QuickBooks Online.
VIEW FULL LESSON →Daily Workflows in Creatio
How Accounts, Orders, Estimates, and Invoices flow into QuickBooks Online as Customers, Estimates, and Invoices. What fields sync automatically, what stays editable in Creatio only, and a full walkthrough from new Order to posted Invoice.
VIEW FULL LESSON →Reading Sync Status & Self-Service Fixes
The three sync status states, the two most common sync failures Berkowitz sees (duplicate customer names, missing SKU or required fields), and what to try before opening a support ticket.
VIEW FULL LESSON →Object & Field Mapping Reference
The complete reference for how Creatio objects map to QuickBooks Online entities in Berkowitz's configuration — Customers, Estimates, Invoices, Credit Memos, Payments, and Deposits. See the Quick Reference table below.
VIEW FULL LESSON →Connection, Error Management & Credentials
How to reconnect QuickBooks Online when authorization lapses, interpret the most common error codes Berkowitz sees, and follow secure practice for managing integration credentials.
VIEW FULL LESSON →Customer Hierarchy & Location Tagging
How Berkowitz's two-to-three-level customer hierarchy maps into QuickBooks Online's two-level limit, the composite naming convention, and how department/location tagging works on deposits.
VIEW FULL LESSON →Support Escalation & Change Requests
When to use this Academy's resources, when to open a ticket with the InterWeave Help Center, and when to escalate directly to Berkowitz's InterWeave account team. How Master Support Document IW-BPB-MSD-2026-01 governs what's in scope and what requires a change request.
VIEW FULL LESSON →Module Detail
The complete content for each module. Work through your track in order — Module 01 and Module 07 first and last, everything else in between.
- Explain what problem the SmartTracks Solution solves for Berkowitz Pollack Brant
- Name the five layers of the InterWeave Automation Platform stack, in order
- Trace the path a single record takes from Creatio into QuickBooks Online
- Know where to find Berkowitz's Master Support Document and what it governs
1.1 Why This Integration Exists
Before this integration, Berkowitz Pollack Brant's sales and account teams worked in Creatio while accounting worked in QuickBooks Online, with no automatic connection between the two. Sales orders, invoices, credit memos, payments, and deposits all had to be re-entered manually on the finance side — a slow, error-prone process.
The SmartTracks Solution eliminates that re-entry: records created in Creatio flow automatically into QuickBooks Online on a schedule, and sync status flows back into Creatio so everyone can see what posted.
1.2 The Five-Layer Platform Stack
Everything InterWeave builds sits on the same five-layer stack. Berkowitz's Solution uses all five, even though most people will only ever interact with the top one or two layers.
| Layer | What it does for Berkowitz |
|---|---|
| AI SmartAgents | Monitors the integration and flags unusual patterns (e.g. repeated duplicate-name errors) |
| FlowCopilot | The configuration assistant InterWeave uses to build and adjust Berkowitz's flows |
| SmartFlows | The actual configured workflows running for Berkowitz — e.g. "Order to Estimate," "Estimate to Invoice," "Payment to QuickBooks" |
| SmartIntegration | The core engine that maps Creatio fields to QuickBooks Online entities |
| Connector Ecosystem | The underlying connectors and APIs that talk to Creatio and QuickBooks Online directly |
1.3 The Data Journey: From Order to Posted Invoice
- A team member creates or updates an Account and an Order in Creatio, with the customer hierarchy and SKU-coded products in place.
- The Order reaches the "Completed" stage and a team member generates an Estimate from it.
- The Estimate is converted to an Invoice; the invoice date is stamped once the invoice reaches its final approval stage.
- The relevant SmartFlow picks up the record on its schedule and SmartIntegration maps Creatio fields to QuickBooks Online entities (Customer, Estimate, Invoice, Credit Memo, Payment, or Deposit).
- The record posts to QuickBooks Online; confirmation status flows back to Creatio as a sync status badge.
1.4 Where to Find Documentation
This Academy training program is the place to learn how the Solution works. For Berkowitz's exact technical configuration, scope, and support terms, the source of truth is Master Support Document IW-BPB-MSD-2026-01. The InterWeave Help Center covers general platform troubleshooting that isn't specific to Berkowitz.
- SmartTracks
- InterWeave's pre-configured CRM-to-accounting integration program Berkowitz is on
- SmartFlow
- A single configured automation, e.g. "Estimate to Invoice"
- USR Object
- An InterWeave/Creatio-generated record (e.g. USR Credit Memo, USR Invoice Payment) with no native Creatio equivalent
- Master Support Document
- IW-BPB-MSD-2026-01 — the single source of truth for Berkowitz's exact configuration and scope
- Name the five layers of the InterWeave platform stack, in order.
- True or false: editing a record directly in QuickBooks Online will automatically update Creatio.
- Which document is the source of truth for Berkowitz's exact technical configuration?
- Identify which Creatio objects sync, and what they become in QuickBooks Online
- List the required fields a record needs before it will sync cleanly
- Know which fields stay editable in Creatio only, post-sync
- Walk through creating an order correctly, end to end, including the Estimate → Invoice step
2.1 What Syncs and What It Becomes
| In Creatio | Becomes in QuickBooks Online |
|---|---|
| Account (Customer, with Parent/Child hierarchy) | Customer |
| Order | Estimate, then Invoice (linked to the Estimate) |
| Products (matched by SKU code) | Items |
| USR Credit Memo | Credit Memo (standalone, or applied to specific invoices) |
| USR Payment | Payment Received (linked to one or more invoices) |
| Payment Adjustment (type "Payment AR") | Bank Deposit |
Berkowitz's confirmed workflow is order-to-estimate, followed by an invoice linked to that estimate — not a direct order-to-invoice flow. This was a deliberate decision to match the firm's accounting process and is final going into production.
2.2 Required Fields Checklist
- Customer/Account name following the composite naming convention (see Module 06) so it is unique in QuickBooks
- SKU code on every order line item — products are matched by SKU, not by name or category
- Billing/parent account assignment for hierarchy accounts
- The "ready for invoice" flag set once the order reaches its invoice-approval stage
2.3 Sync-Locked Fields (Avoid Editing After Sync)
- QuickBooks Online customer ID once a Customer record has synced
- Invoice number — Creatio's invoice number is forced into QuickBooks Online to keep sequencing controlled from Creatio
- Invoice date, once stamped at final approval stage
2.4 A Day in the Life: Order to Posted Invoice
- Create the Account with the correct hierarchy level and a unique composite name.
- Create the Order and add line items, confirming every product has a SKU code.
- Move the Order to "Completed" — this enables the button to generate the Estimate.
- Click to create the Estimate from the Order; review for accuracy.
- Convert the Estimate to an Invoice when the order reaches its final approval stage — the invoice date is stamped automatically at this point.
- The relevant SmartFlow posts the Estimate and Invoice to QuickBooks Online; Creatio shows a synced status badge once confirmed.
- SKU code
- The unique product identifier used for matching — required because product names differ between Creatio's category hierarchy and QuickBooks
- Ready for invoice flag
- A checkbox on the Order that tells the SmartFlow the order is approved and ready to convert
- Composite name
- A customer name combining the account name and a code (e.g. name-code) to guarantee uniqueness in QuickBooks
- What does a Creatio Order become once it fully syncs to QuickBooks Online?
- Why are products matched by SKU instead of by name?
- What's the first required field to check if a new customer record won't sync?
- Recognize the three sync status states and what each one means
- Diagnose the two most common sync failures Berkowitz sees, without IT help
- Know when to fix it yourself versus when to escalate
3.1 Sync Status Indicators
| Status | Meaning |
|---|---|
| Synced | Record successfully posted to QuickBooks Online — no action needed |
| Pending | Record is queued, waiting for the next scheduled sync run |
| Error | Record failed to sync and needs attention |
3.2 Common Error #1 — Duplicate Customer Name
Symptom: Error status referencing an existing Customer match, or a child account silently overwriting another with the same name.
Cause: QuickBooks Online only accepts unique names as its customer key. Parent/child/grandparent accounts in Creatio that share a name will conflict.
Self-fix: Confirm the account uses the composite naming convention (Module 06). If it already does and still conflicts, escalate — this may indicate a genuine duplicate account in Creatio that needs cleanup.
3.3 Common Error #2 — Missing SKU or Required Field
Symptom: Record shows Error status almost immediately after creation.
Cause: A required field from Module 02 was left blank — most often the SKU code on a line item, or the billing/hierarchy assignment.
Self-fix: Open the record, fill in the missing field, save, and allow the next scheduled sync to retry.
3.4 When to Escalate
Escalate to Admin & IT (Module 07) if an error persists after a self-fix attempt, if the error code is unrecognized, or if it references an account-type or connection issue rather than a missing field — those require Admin & IT access to QuickBooks Online configuration.
- Sync status badge
- The visual indicator (Synced / Pending / Error) shown on a Creatio record
- Customer match
- QuickBooks Online's check for an existing Customer with the same name
- What are the three sync status states?
- A new customer record shows Error referencing an existing match — what's the likely cause?
- Should you create a brand-new Account in Creatio to work around a suspected duplicate? Why or why not?
- Use the full AR object mapping as a working reference
- Understand how USR objects model relationships QuickBooks Online requires but Creatio doesn't natively have
- Know the safe process for extending a mapping without breaking existing flows
4.1 AR Object Mapping, in Depth
- Account (Customer) → QuickBooks Online Customer, flattened to a two-level parent/child hierarchy (QuickBooks Online supports a maximum of two levels; grandparent-level data is excluded from sync)
- Order → Estimate → Invoice (linked one-to-one; the invoice date is set only once the order reaches its invoice-approval stage)
- Products → Items, matched on SKU code rather than name or category hierarchy
- USR Credit Memo → Credit Memo, either standalone (for refunds with no invoice link) or applied to specific invoices via the child object Credit Memo applied to invoices, supporting multiple invoices credited from a single memo
- USR Payment → Payment Received, linked to one or more invoices via the intermediary object USR Invoice Payment, which holds references to both the invoice ID and payment ID (a many-to-many relationship: one payment can cover multiple invoices, and one invoice can receive multiple payments)
- Payment Adjustment (filtered by payment type "Payment AR") → Bank Deposit, broken out as multi-line deposits with invoice numbers in the description and tagged with the operational department reference
4.2 Why USR Objects Exist
QuickBooks Online requires explicit linkage objects — for example, a payment-to-invoice relationship, or a credit-memo-to-invoice relationship — that Creatio doesn't model natively. InterWeave's configuration adds USR-prefixed custom objects and fields (USR Credit Memo, USR Invoice Payment, USR Number, USR Total, USR Amount) specifically to carry that relationship data cleanly into QuickBooks Online.
4.3 Extending a Mapping Safely
- Confirm the new field or object isn't already covered — check IW-BPB-MSD-2026-01 first.
- Document the proposed mapping, including any account-type or department tagging it should carry.
- Submit as a change request (Module 07).
- Test in a sandbox/test order with a single record before relying on it in production.
- USR Object
- An InterWeave/Creatio custom object with no native Creatio equivalent, used to carry relationship data
- USR Invoice Payment
- The intermediary object linking one payment to one or more invoices
- Credit Memo applied to invoices
- The child object linking one credit memo to one or more specific invoices
- Why does QuickBooks Online only support two levels of customer hierarchy, and what does Berkowitz do about the third level?
- What object links a single payment to multiple invoices?
- What's the first step before extending a live mapping?
- Reconnect the QuickBooks Online authorization when it lapses
- Interpret the most common error codes Berkowitz sees
- Follow secure practice for managing integration credentials
5.1 Reconnecting QuickBooks Online
- Confirm the existing QuickBooks Online authorization has been lost (a full reconnect requires credentials and, depending on security settings, MFA on a live call).
- Coordinate with the QuickBooks Online account admin to deactivate, then reactivate, the integration user.
- Ensure the reauthorization email reaches the correct person promptly — these links can expire.
- Schedule a follow-up retest within one to two days of reactivation to confirm the connection and resume integration testing/syncing.
5.2 Common Error Codes Reference
| Error | Likely Meaning |
|---|---|
| Incorrect Type of Account | A mapped account (e.g. deposit or asset account) is the wrong QuickBooks account type — e.g. an expense account used where an asset account is required |
| Duplicate Customer / Name Conflict | A matching Customer name already exists — see composite naming, Module 06 |
| Missing Required Field | SKU, billing assignment, or another required field (Module 02) wasn't populated |
| Terms Mismatch | Payment Terms in QuickBooks Online don't case-sensitively match Creatio's term list — terms must be aligned manually |
| Doc Number Not Populated | QuickBooks Online's deposit doc-number field is empty/unavailable via the API, which can lead to duplicate deposits if not tracked by an alternate transaction ID |
| Caching Unavailable (Multi-Line Payments) | QuickBooks Online's payment-line caching isn't available; the integration falls back to an incremental multi-line method, which is reliable but should be monitored |
5.3 Managing Connection Credentials
Passwords used for the Creatio/QuickBooks Online integration must avoid XML reserved characters — specifically the ampersand (&) and quotation marks ("") — which can break the integration's authentication flow. Complexity should still be maintained using other special characters such as $ and #. Use a single password for both integration and user access where possible, and update it in every location (company profile and flow configuration) whenever it changes.
- Reauthorization
- The process of re-granting QuickBooks Online API access after a lapsed or revoked connection
- Connection profile
- Berkowitz's saved Creatio/QuickBooks Online authentication settings
- Transaction ID workaround
- A custom Creatio field storing the QuickBooks Online transaction ID, used to prevent duplicate deposits when the native doc-number field is unavailable
- What two characters should never appear in an integration password?
- How long after reactivating the QuickBooks Online connection should you retest?
- Why can duplicate deposits occur in QuickBooks Online?
- Understand how Berkowitz's multi-level customer hierarchy maps into QuickBooks Online
- Apply the composite naming convention correctly
- Know how department/location tagging works on deposits
6.1 Hierarchy Depth: Two to Three Levels
Berkowitz's accounts in Creatio typically run two to three levels deep: child, parent, and sometimes grandparent. Orders and invoices are always assigned at the lowest (child) level; credits may split between the lowest and parent levels. QuickBooks Online supports a maximum of two hierarchy levels, so the integration flattens Berkowitz's structure — grandparent-level data is excluded from sync since transactions are rarely posted there.
6.2 Composite Naming Convention
QuickBooks Online only accepts unique names as its customer key. Where Creatio has multiple child accounts with identical names under different parents — which QuickBooks Online would otherwise reject or silently overwrite — accounts must use a composite name combining the customer name with a unique code (e.g. name-code or code-name). This preserves readability while guaranteeing uniqueness.
6.3 Location & Department Tagging on Deposits
Accurate financial reporting requires every deposit to carry an operational location/department tag. In QuickBooks Online, this is stored in the Department Reference / Full Name field. Berkowitz's configuration copies the same department-tagging logic already used on invoices over to deposits, so the "operational" tag is applied consistently across both.
6.4 Adding a New Hierarchy Level, Customer, or Department Value
- Confirm the new value doesn't already exist under a different name or spelling.
- If it's a new department/location value, create it directly in QuickBooks Online first.
- Update the relevant Creatio field or picklist feeding that value.
- Submit a change request (Module 07) to include the new value in the live SmartFlow.
- Test with a single record before broader use.
- Composite name
- A customer name combining the account name and a unique code to satisfy QuickBooks' unique-name requirement
- Department Reference / Full Name
- The QuickBooks Online field used to carry the operational location/department tag
- Flattening
- Reducing Berkowitz's three-level Creatio hierarchy to the two levels QuickBooks Online supports
- How many hierarchy levels does QuickBooks Online support, and what happens to the level above that in Berkowitz's data?
- Why does Berkowitz use composite customer names instead of plain names?
- Where should a brand-new department/location value be created first?
- Know the three support tiers and when to use each
- Tell the difference between a support ticket and a change request
- Understand what's in scope under IW-BPB-MSD-2026-01
7.1 The Three Support Tiers
- InterWeave Academy — revisit these modules or check Documentation/User Guides for general platform questions.
- InterWeave Help Center — searchable articles and a support ticket queue for non-Berkowitz-specific issues.
- Berkowitz Account Team — direct escalation for configuration-specific, scope, or unresolved Tier 1/2 issues.
7.2 Support Ticket vs. Change Request
A support ticket is for something that should already be working but isn't — a sync error, a duplicate-name conflict, an unexpected behavior in an existing flow. A change request is for something new — a new field mapping, a new credit memo type, a new department value, or a new object to sync.
- Example — ticket: A customer record that has synced fine for months suddenly throws a duplicate-name error.
- Example — change request: Berkowitz wants to add a brand-new credit memo type, or sync a new Creatio object that isn't currently part of the integration.
7.3 What's In Scope vs. Out of Scope
IW-BPB-MSD-2026-01 defines exactly what Berkowitz's Solution covers — the objects, fields, and mappings documented in Modules 04 and 06 are in scope for standard support. New QuickBooks Online modules, new Creatio objects, or structural changes to the hierarchy/naming model are out of scope for support and require a change request.
- Support ticket
- A request to fix something that should already be working
- Change request
- A request for new functionality or configuration
- In scope
- Covered under Berkowitz's current Master Support Document
- A sync that's worked fine for weeks suddenly throws an error — ticket or change request?
- Berkowitz wants to sync a brand-new object that isn't currently integrated — ticket or change request?
- Which document defines what's in scope for Berkowitz's support?
Object & Field Mapping Quick Reference
The core mappings active in Berkowitz's environment. Full detail lives in IW-BPB-MSD-2026-01.
| Creatio Object | QuickBooks Online Entity | Notes | |
|---|---|---|---|
| Account / Contact | → | Customer | Composite name required for uniqueness; flattened to 2 hierarchy levels |
| Order | → | Estimate | Generated once Order reaches "Completed" stage |
| Order / Estimate | → | Invoice | Linked to Estimate; invoice date set at final approval stage |
| Products (by SKU) | → | Items | Matched on SKU code, not name or category |
| USR Credit Memo | → | Credit Memo | Standalone or applied to invoices via "Credit Memo applied to invoices" |
| USR Payment / USR Invoice Payment | → | Payment Received | Many-to-many invoice linkage via intermediary object |
| Payment Adjustment (Payment AR) | → | Bank Deposit | Multi-line; tagged with operational department reference |
| n/a | → | Department Reference / Full Name | QuickBooks Online location/department tag, mirrored from invoice mapping |
Frequently Asked Questions
Answers to the questions Berkowitz's teams ask most often during onboarding.
Get Help When You're Stuck
Three resources, in the order most people need them.
InterWeave Academy
Revisit these modules anytime, plus the broader Creatio and QuickBooks Online documentation and user guides on the platform.
academy.interweave.biz →InterWeave Help Center
Searchable support articles and troubleshooting guides for common sync issues, plus a direct line to the support team.
help.interweave.biz →Berkowitz Account Team
For configuration changes, scope questions, or anything outside self-service: your InterWeave engagement team, per IW-BPB-MSD-2026-01.
Contact account team →Scope reminder. This training document covers how to use and support Berkowitz's Creatio ↔ QuickBooks Online integration as it moves toward production. Configuration changes outside the scope of IW-BPB-MSD-2026-01 — new objects, new entities, or structural changes to the hierarchy/naming model — should go through your InterWeave account team as a change request, not a support ticket.