When a QuickBooks or Sage integration is not syncing, the cause may be the integration app, an authorization or permission change, a recent update, or the accounting software itself. A careful check can help narrow down the issue without creating duplicate transactions or disrupting other records.
Start by documenting what stopped, when it began, and the last successful sync. Avoid repeated reconnect attempts or manual edits to affected transactions until you understand what has and has not been processed.
Start by defining the problem
Before changing settings, identify the integration and the records involved. Note whether the connection is a third-party app, a built-in feature, or a bank feed. These can have different settings and support paths, so do not assume that guidance for one type applies to another.
- Which records are affected, such as invoices, payments, bills, or journal entries?
- Is data failing to move into the accounting software, out of it, or in both directions?
- Is the issue limited to one user, workstation, company file, or connected application?
- When did syncing last work, and what was the last record that completed successfully?
Keep a short timeline with the time the problem was noticed, the last successful sync, and any error wording. This gives your internal support team or vendor something specific to investigate.
Check connection status and error details
Review the integration’s status inside the app or service that manages the connection. Look for a paused, expired, disconnected, or attention-needed state. Also check the accounting software for notices that may explain a service interruption or a sign-in requirement.
Record the complete error message and when it appeared. If the error includes a reference or request identifier, preserve that too. Do not include passwords, authentication codes, or client financial details in ordinary support messages.
If you use QuickBooks Online and the app relies on an authorization connection, its authorization guidance can help explain why an app may need access renewed. Follow the app provider’s instructions for your particular connection rather than changing permissions at random.
Review permissions and the account that connected the app
A sync can fail if the app no longer has the access it needs, or if the user who originally connected it has lost access or changed roles. Check which account authorized the integration and whether that user still has the appropriate role in both systems.
Ask an administrator to confirm that the connection is still approved and that the required permissions have not been removed. In a financial firm, keep access limited to what the integration needs. Do not grant broader access simply to see whether it fixes the error.
Before disconnecting an app, check the integration provider’s recovery instructions. Disconnecting may require authorization again, and the provider can explain how that affects pending records or the sync history. Reconnecting without checking can make it harder to determine which transactions were already processed.
Compare the failure with recent changes
Think about what changed near the time syncing stopped. Check for updates to QuickBooks, Sage, the integration app, the operating system, or network security settings. Also note changes to user roles, passwords, multi-factor authentication, or the account that manages the connection.
Do not roll back software, disable security controls, or install an update based only on timing. Ask the integration provider to confirm compatibility with the current versions and any recent release. Sage advises checking whether a program can link with a third-party product; its third-party compatibility guidance is a useful starting point. For a specific update, consult the vendor’s release information, such as the Sage release notes.
Check for delayed, missing, or duplicated records
Before trying to run the sync again, compare the integration’s queue or activity history with the accounting software. Identify the last successful record and review the items that were pending afterward. Where available, note each affected record’s date, type, amount, and reference identifier, while keeping sensitive client information out of general support tickets.
Look for signs that a transaction reached one system but did not appear in the other. Check for duplicates before retrying a batch or manually entering missing items. If you cannot tell whether an item has already been processed, pause that record and ask the integration provider how to proceed.
Keep a record of the checks you performed and any settings changed. This creates a clearer handoff for support and helps your firm document the steps taken without relying on memory.
Choose the right support contact
Contact the integration provider when the app reports an error, its queue is stuck, its connection status is unclear, or you need instructions for reconnecting safely. Provide the app name, affected direction of sync, error text, timestamps, last successful sync, and relevant version information.
Contact QuickBooks or Sage when the accounting software itself shows an error, a sign-in or company-file problem, or a feature-specific issue that persists without the integration. If you are unsure which system is responsible, start with the integration provider and ask whether the error points to its service or the accounting platform.
Your internal IT support team can help review access, network or workstation changes, update timing, and the support handoff. For firms managing several technology providers, a documented vendor management process can clarify who owns each part of the connection. If the issue involves remote troubleshooting, review practices for secure remote access before granting access to systems or records.
For support, share only what the recipient needs to investigate. Do not send passwords, authentication codes, or unnecessary client records. Use an approved secure channel if the provider needs a file or other sensitive material.
Frequently asked questions
Why did the integration suddenly stop syncing?
Common areas to check include the app connection, user permissions, a software or operating-system update, and changes to the network or account used to authorize access. The error details and timeline can help identify which area to investigate first.
Could a QuickBooks or Sage update have broken the connection?
An update may affect compatibility, but timing alone does not prove that it caused the failure. Note what changed and ask the integration provider to confirm compatibility before changing versions or settings.
Should I disconnect and reconnect the app?
Not as an initial troubleshooting step. First review the app’s instructions, authorization status, and pending records. Reconnect only when the provider’s guidance explains how to do so without losing track of transactions already processed.
What should I send when I contact support?
Include the integration name, affected records and sync direction, error wording, relevant timestamps, last successful sync, and recent changes. Do not send passwords, authentication codes, or unnecessary client financial information.
Restore the connection carefully
A measured QuickBooks or Sage integration troubleshooting process starts with the scope and timeline, then checks connection status, permissions, recent changes, and transaction history. If the cause is unclear, preserve the evidence and involve the provider or accounting-software support team before attempting a reset.
Zevonix lists support for QuickBooks and Sage as part of its technology services for financial firms. If you need help assessing a sync issue, contact Zevonix at (904) 658-0777.