Wave integration not syncing: Practical Guide, Risks, Checks and Best Practices

Start with the exact symptom and accounting scope

Write down what the user expected to happen, what actually happened, the affected entity or file, the date range, the user role, and the last time the workflow worked correctly. In Wave, the same visible symptom can come from different layers. For example, payroll may be correct while a connected service or report filter is wrong, or the accounting record may be correct while the screen is showing a stale state. For a useful cross-check, compare this step with Wave payroll not processing: Practical Guide, Risks, Checks and Best Practices and Wave invoice marked paid incorrectly: Practical Guide, Risks, Checks and Best Practices; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Capture evidence before trying fixes. Useful items include source trial balance, aged receivables, aged payables, and inventory valuation. If you post a question publicly, redact bank account numbers, tax IDs, payroll details, customer data, API secrets, passwords and multi-factor codes. A precise, safe problem statement produces better answers than a long description with no reproducible steps. For a useful cross-check, compare this step with Wave duplicate income transaction: Practical Guide, Risks, Checks and Best Practices and Wave customer payment pending: Practical Guide, Risks, Checks and Best Practices; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Likely causes to rule in or out

For this topic, the most useful fault domains are data mapping, opening balances, tax configuration, historical completeness and rollback safety. Common causes include unsupported fields, different chart-of-account structures, date or decimal-format mismatches, duplicate customer or supplier records. Do not assume the first plausible cause is the correct one. Instead, compare the symptom with a known-good record or user, then change one variable at a time. That makes the result attributable and protects the audit trail. For a useful cross-check, compare this step with Wave bank transactions not importing: Practical Guide, Risks, Checks and Best Practices and Wave duplicate bank transactions: Practical Guide, Risks, Checks and Best Practices; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

• Unsupported fields
• Different chart-of-account structures
• Date or decimal-format mismatches
• Duplicate customer or supplier records
• Partial historical imports
• Tax-code mapping differences
• Inventory opening quantities that do not agree
• Currency or fiscal-period differences

Where the page involves reconciliation, review the accounting consequence before applying a technical workaround. A shortcut that restores access but creates lost history or duplicated opening entries is not a successful fix. The operational and accounting outcomes both have to be correct. For a useful cross-check, compare this step with Wave payment not showing: Practical Guide, Risks, Checks and Best Practices and Wave reconciliation status incorrect: Practical Guide, Risks, Checks and Best Practices; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Controlled diagnostic workflow

1. Step 1: Take a recoverable source backup. Record the result before continuing.
2. Step 2: Freeze the migration cut-off date. Record the result before continuing.
3. Step 3: Export control totals before moving data. Record the result before continuing.
4. Step 4: Map accounts and tax codes explicitly. Record the result before continuing.
5. Step 5: Test a small representative import first. Record the result before continuing.
6. Step 6: Reconcile opening balances after import. Record the result before continuing.
7. Step 7: Compare aged receivables and payables. Record the result before continuing.

Move through the sequence in order. If an early step proves the cause, stop and verify before doing more. If nothing changes, preserve the evidence and continue. This is especially important with financial systems because bulk retries, historical edits, forced matches, mass imports and permission changes can create a second problem that hides the first. For a useful cross-check, compare this step with Wave invoice not sending: Practical Guide, Risks, Checks and Best Practices and Wave bank reconciliation not matching: Practical Guide, Risks, Checks and Best Practices; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

When a test changes the accounting result, compare the outcome with the control evidence you saved earlier. For Wave, that may mean a trial balance, reconciliation report, invoice balance, payroll liability, inventory valuation, payment settlement or migration control total depending on the workflow. For a useful cross-check, compare this step with Wave app not syncing and Wave Accounting Integrations And Api Connections: Integration Checklist for Finance Teams; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Brand-specific checks in Wave

Wave users should identify the exact product surface involved. This article may apply differently across Wave Accounting, Wave Invoicing, Wave Payments. Confirm the organization, edition, region and user role before following a fix. Product names may look similar while permissions, bank connectivity, import tools, tax workflows and support channels differ. For a useful cross-check, compare this step with Wave receipt scan problem: Causes, Diagnostic Workflow, Safe Fixes and Prevention and Wave receipt scan problem; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Within Wave, also consider whether the issue intersects with bank connections, transaction categorization, invoices, or payments. Those adjacent workflows can change the evidence you need and the safest recovery path. If the problem is vendor-controlled—identity verification, subscription state, hosted outage, payroll filing service, payment processor hold, or account ownership—use the official support channel rather than trying to bypass the control. For a useful cross-check, compare this step with Wave expense missing and Wave bank balance mismatch; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Protect data, controls and audit history

Before a high-impact change, create a recoverable backup or export where the product supports it, save period-end control reports, and note who is making the change. Avoid deleting history merely to make a balance agree. If correction requires a journal, adjustment, reclassification, credit, refund or opening-balance change, make the accounting reason explicit and involve a qualified accountant when the treatment is uncertain. For a useful cross-check, compare this step with Wave alternatives 2026: Decision Guide for Accounting Teams in 2026 and Wave accounting free vs paid: Workflow, Cost, Controls and Migration Comparison; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

The main risks for this issue include lost history, duplicated opening entries, misclassified tax, broken audit trails, incorrect customer or supplier balances. A technically successful workaround that introduces one of those risks should be treated as temporary at best. Preserve original files, imported source data and before/after reports so that another authorized person can reconstruct what changed. For a useful cross-check, compare this step with Wave Payroll Financial Reporting: Control-Total Validation for Finance Teams and Wave Payments Financial Reporting: Report Review Checklist for Finance Teams; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

How to verify the fix

Repeat the original workflow with the smallest safe test. Then confirm that trial balance agrees to the source at cut-over; opening receivables and payables reconcile; and tax balances are explainable. Review the audit trail or change history where available. If the issue involved an integration, bank feed, payment gateway, import or automated process, also verify that the same record was not created twice. For a useful cross-check, compare this step with Wave Payments Data Imports: Pre-Import Checklist for Finance Teams and Wave Invoicing User Permissions And Security: Least-Privilege Audit for Finance Teams; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Verification should use the same date range and accounting basis as the original symptom. A report that looks right under different filters is not proof. Save the final evidence, document the cause and fix, and make the result easy for the next bookkeeper, accountant or administrator to understand. For a useful cross-check, compare this step with Wave Invoicing Period-End Accounting: Common Close Mistakes for Finance Teams and Wave Invoicing Invoices And Payments: Payment-Matching Mistakes for Finance Teams; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Prevention and operating controls

After resolution, turn the lesson into a repeatable control. Good prevention for this issue includes use a written field map, keep source data read-only after cut-over, reconcile control totals before inviting users, and document excluded objects. Assign an owner and a review frequency instead of relying on memory. Small controls are especially valuable when multiple users, entities, integrations or external accountants touch the same books. For a useful cross-check, compare this step with Wave payroll year end issue and Wave missing bank transactions: Causes, Diagnostic Workflow, Safe Fixes and Prevention; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Use the control to catch exceptions early, not to create unnecessary work. A short weekly or month-end check that highlights only missing, duplicated, unmatched, failed or out-of-scope items is more useful than a broad checklist that nobody completes. Keep official vendor links and internal troubleshooting notes beside the control so future incidents start with evidence rather than guesswork. For a useful cross-check, compare this step with Wave employee payment problem: Causes, Diagnostic Workflow, Safe Fixes and Prevention and Wave contractor payment issue; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

2017–2026 operating context for this workflow

This ten-year table is an editorial operating timeline, not a market-size or search-volume dataset. It shows why modern accounting-software troubleshooting increasingly needs to consider cloud identity, connected apps, automated matching, compliance workflows and audit evidence together rather than treating every symptom as a single-screen software error. For a useful cross-check, compare this step with Wave bank transactions not importing and Wave help hub; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

Build a related knowledge path instead of reading one page in isolation

A strong investigation often crosses several related topics. Start with the closest symptom, then move outward to the connected accounting workflow. If your issue touches data mapping, opening balances, tax configuration, historical completeness and rollback safety, use the related pages linked throughout this article to compare symptoms, controls and evidence rather than repeating the same test in different forms. For a useful cross-check, compare this step with Wave blog and accounting software comparisons; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

For finance teams, the most useful internal links are the ones that explain the next decision. A page about a bank-feed gap should lead naturally to reconciliation and duplicate checks; a migration article should lead to opening balances, import mapping and post-migration validation; a permissions article should connect to login, role and integration authorization. That is why links here are embedded in the explanatory paragraphs rather than collected only in a footer. For a useful cross-check, compare this step with latest accounting questions and accounting software guides; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.

If you still cannot isolate the cause, create a concise incident note with the exact symptom, safe evidence, what changed, what you tested, and the result. Then use the official vendor channel for vendor-controlled issues or ask the AccountingQnA community a focused question that another user can reproduce. For a useful cross-check, compare this step with Wave integration not syncing: Practical Guide, Risks, Checks and Best Practices and Wave app not syncing: Practical Guide, Risks, Checks and Best Practices; the relationship between those workflows often reveals whether the symptom is isolated or part of a wider accounting-data pattern.