🎙️ Session: 07 10:48 CDT - Notes by Gemini

Executive Summary

The meeting on July 7, 2026, focused on resolving critical synchronization conflicts between HubSpot and QuickBooks to finalize June’s financial records. Key issues included duplicate customer records and erroneous payment entries causing invoices to appear incorrectly paid in HubSpot. Participants successfully consolidated duplicate company and contact records in QuickBooks (e.g., Jeff Kramer, Grecian Delights) and removed invalid payment entries from HubSpot that lacked corresponding QuickBooks records. The team confirmed QuickBooks Online as the primary book of record and outlined a future strategy for data reconciliation, including establishing a “look-back” date for data cleanup and defining clear sync parameters. Weekly HubSpot meetings will continue as standard check-ins, with dedicated breakout sessions for specialized financial topics.

Architectural Frameworks & Core Principles

• Primary Book of Record: QuickBooks Online is established as the primary book of record for all financial reconciliation, influencing how HubSpot data should be managed.
• Targeted Troubleshooting: Sync failures are best resolved by identifying and fixing specific individual customer records rather than attempting broad, simultaneous database analysis.
• Data Consolidation Strategy: Duplicate company and contact records should be merged in QuickBooks to resolve mapping, association, and synchronization conflicts with HubSpot.
• Payment & Invoice Interdependency: Invoice statuses are directly updated by their associated payments; therefore, to correct an invoice status, the corresponding payment must be updated (e.g., deleted or disassociated).
• Manual Entry Management: Manual entries in QuickBooks must have a corresponding, consistently managed record or a clear exclusion rule in HubSpot to prevent synchronization conflicts.
• Fiscal Period Integrity: HubSpot should ideally be restricted from attempting to push updates to finalized (closed) fiscal periods in QuickBooks to prevent “circular” sync errors.

Flight Plan Action Items

• [Carley Endersbe] Merge Customer Records: Consolidate duplicate profiles by merging individual contact records into their primary company entity in QuickBooks Online (e.g., completed for Jeff Kramer and Peter/Grecian Delights).
• [Kevin Dockman] Resolve Sync Errors: Develop a comprehensive strategy to address recurring synchronization failures and legacy invoice status discrepancies between HubSpot and QuickBooks Online.
• [Carley Endersbe] Clean Sync Records: Review the remaining failing synchronization records in HubSpot to determine if they are legacy issues or ongoing errors requiring further investigation.
• [Carley Endersbe] Resend Invoices: Resend invoice links to clients for identified unpaid invoices (e.g., invoice 1417) where erroneous payments have been removed.
• [Kevin Dockman] Reconcile Data: Compile a list of customers, invoices, and payments that require reconciliation to establish a clean sync “look-back” date and define necessary sync parameters. This includes supplying the reconciliation list and an action plan for task allocation.

Key Structural Sections of the Discussion

Meeting Objectives and Urgency

• Kevin Dockman initiated the meeting, addressing personal technical difficulties before transitioning to the primary agenda.
• Jessica Colley outlined meeting goals: finalizing contact records and troubleshooting synchronization between HubSpot and QuickBooks.
• Emphasis was placed on the urgency of resolving issues to close June financial records, as current failures cause unsynced invoices and duplicate payments, falsely marking unpaid invoices as paid in HubSpot.

Sync Strategy and Approach

• The team discussed the current state of synchronization, with Carley Endersbe noting improved system communication but persistent duplicate payment errors attributed to legacy customer data.
• Kevin Dockman proposed a “seesaw” methodology: identifying failing syncs by backtracking from specific legacy customer records, correcting them, and establishing clear configurations.

Troubleshooting Jeff Kramer Sync Failures

• Carley Endersbe investigated a persistent monthly sync error for “Jeff Kramer,” which was identified as having multiple associated company entries.
• Decision: The team decided to merge redundant company records in QuickBooks, using the primary domain as the reference point to consolidate data and resolve the conflict.
• Outcome: Following the merge, the “failing” status for Jeff Kramer was cleared immediately upon rerunning the sync.

San Mateo County District Invoicing Review & Historical Data

• The team examined “San Mateo County Community College District” records that were failing to sync despite appearing correct.
• Discussion included issues with “waiting for payment” statuses on older quotes due to process changes and payments associated with closed fiscal periods.
• Kevin Dockman noted rigid statuses for paid or canceled invoices, suggesting they cannot be changed directly after a certain point.
• Jessica Colley emphasized QuickBooks as the “book of record” for reconciliation and reporting, with HubSpot acting as a payment collection tool.

Fiscal Periods and Time Zone Synchronization

• The team discussed potential causes for sync errors, including QuickBooks settings for closing books (e.g., Q2 ending April 1st) and the QBO API’s inability to modify data in closed periods.
• Kevin Dockman hypothesized that time zone discrepancies (e.g., Eastern vs. HubSpot’s settings) could also trigger “circular” sync errors if payment dates are off by a day.

Grecian Delights Contact Consolidation

• Jessica Colley raised concerns about recurring sync issues involving “Grecian Delights” and a contact named “Peter.” Kevin Dockman identified these as separate customer entities in QuickBooks.
• Decision: Carley Endersbe executed a merge of Peter’s contact records in QuickBooks into the primary “Grecian Delights” profile, moving Peter’s transactions to unify customer history.

Analysis of Payment Discrepancies and Identifying Invalid Records

• After consolidating Grecian Delights records, conflicting payment data was discovered, including an open invoice (for $20,000) not reflected in HubSpot as unpaid and erroneous “fake” payments.
• The team identified invalid payment records in HubSpot (e.g., those with a CRM source rather than a valid integration source) that did not represent actual cash received.
• Kevin Dockman advised that erroneous payments deleted from QuickBooks should also be removed from HubSpot to prevent the system from attempting to sync invalid data.

HubSpot Payment Deletion Strategy

• Kevin Dockman explained that online HubSpot-recorded payments cannot be deleted but can be refunded or disassociated. However, payments processed through an API (like from QuickBooks) or manually recorded can be deleted.
• Jessica Colley confirmed that deleting an identified erroneous payment (with an API source) worked, and the change was reflected in the associated deal.

Resolving Invoice 1417 and Manual Payment Errors

• The team investigated payments for invoices 1296 and 1417. It was discovered that a manual $10,000 payment for invoice 1417 was erroneously applied and caused sync issues.
• Action: Jessica Colley and Carley Endersbe decided to unmatch the manual payment from invoice 1417 in QuickBooks and simultaneously delete the payment from HubSpot to prevent conflicting sync attempts.
• Outcome: Following the deletion, invoice 1417 correctly displayed as “open” in HubSpot. Kevin Dockman emphasized that deleting or disassociating a linked payment is the most efficient way to update an invoice status.

Future Planning and Reconciliation Strategy

• Kevin Dockman plans to compile a list of affected customers, invoices, and payments to establish a “look-back” date and define the necessary scope for reconciling data.
• The goal is to transition from troubleshooting to finance-specific projects, ensuring a clean sync from an agreed-upon date forward.

Meeting Cadence and Communication

• Decision: Weekly HubSpot meetings were confirmed as the standard check-in cadence.
• Breakout sessions were designated for specialized project-based topics like commissions and revenue, allowing for focused discussions.