A Melio sync incident is rarely solved by pressing Sync now repeatedly. A bill may be outside the connected product's eligibility, a vendor may have been matched incorrectly, a funding method may point to the wrong ledger account, or an action may not synchronize in the direction the operator expects. Payment collection and vendor delivery can also fail independently of the accounting connection. Troubleshooting begins with one object, one product, and one documented expected result.
Current Melio documentation distinguishes QuickBooks Online, QuickBooks Desktop, and Xero. QuickBooks Online and Xero each have plan limits, field-direction tables, initial vendor matching, and different timing or workflow rules. Desktop depends on a Windows company file and Web Connector configuration. Vendor-credit behavior also varies: current guidance describes different capabilities for QuickBooks Online, Desktop, and Xero and further limits application by Melio subscription.
Create an evidence packet before repair: Melio organization and payment IDs, accounting company, vendor and bill identifiers, timestamps, plan, product, sync status, error text, funding source, delivery method, bank activity, screenshots, and last known correct record. Decide which system owns the specific change. Then correct only the proven condition and verify adjacent bills, payments, vendor balances, and financial statements.
Key decisions at a glance
- Write a product- and plan-specific sync contract instead of treating QuickBooks Online, QuickBooks Desktop, and Xero as interchangeable.
- Review initial vendor matching carefully because current Melio guidance says skipped suggested links may not be available later.
- Follow field and action direction tables when deciding where to correct a bill, vendor, payment, void, or credit.
- Classify collection failures, delivery failures, duplicates, overpayments, refunds, and sync gaps before choosing a recovery action.
- Close only after Melio status, vendor outcome, accounting entries, funding account, bank evidence, and exception records agree.
Write a product-specific Melio sync contract before troubleshooting
For QuickBooks Online, record the connected company, Melio plan, last successful sync, authorization owner, payment-method mapping, and supported fields. Current Melio guidance says Core, Boost, and Unlimited receive unlimited synchronization, while Go is limited to the first ten payments across directions and payables or receivables. The current field table shows many AP vendor and bill fields moving both ways, but payments generally post from Melio to QuickBooks Online and several fields or actions do not sync.
For Xero, document the organization, plan, connection owner, and precise AP or AR workflow. Current Melio guidance says AP bills and vendor information have two-way behavior with field-level exceptions, while AR invoices originate in Xero and paid status can return after a Melio payment request is paid. The current data page says automatic sync occurs hourly and warns that marking an externally paid bill as paid in Melio can create a duplicate entry in Xero.
Keep QuickBooks Desktop separate. It uses a Windows company file and Web Connector, and current troubleshooting guidance requires the correct file, supported Desktop version, running connector, enabled Auto-Run, and specific connector timing. A QBO or Xero remedy should not be applied to Desktop merely because all three appear under accounting sync. Record the exact product in every incident and runbook title.
- Document plan, accounting product, company, entity, connection owner, last success, schedule, and manual-sync path.
- Maintain a field-and-action direction register for vendors, bills, payments, credits, attachments, classes, and locations.
- Identify the authoritative system and permitted correction path for each object and lifecycle state.
- Revalidate the contract after plan, product, chart, bank, authentication, or Melio documentation changes.
Control initial matching, payment mappings, and reconciliation evidence
Treat first connection as a data conversion. Current QBO and Xero guidance says Melio scans existing vendors, proposes similar matches, and warns that skipped suggested vendors cannot be linked later. Review full names, contacts, accounting IDs, open bills, history, tax status, and delivery details before confirming. Export the decision set, assign a reviewer, and stop if the proposed match joins different legal entities or payment relationships.
Link each Melio funding method to the correct QuickBooks Online bank or credit-card account. Melio's current help page explains that an unlinked method can post to a MelioChecks account and lead to duplicate-looking bank entries. Before merging or renaming accounts, identify every affected payment and obtain accounting approval; the missing-payment guide explicitly warns that a QuickBooks account merge cannot be undone and may require transaction-by-transaction correction when multiple accounts are involved.
Reconcile one payment end to end. Connect the source bill, vendor ID, bill ID, scheduler, approval, payment ID, funding method, deduction date, Melio status, delivery method, trace or check evidence, accounting bill-payment entry, ledger account, bank debit, vendor confirmation, and period. Timing differences may be valid, but a remaining clearing or bank difference needs an owner, explanation, expected resolution, and reviewer.
- Capture initial vendor-match candidates, decisions, reviewers, and unresolved exceptions before completing connection.
- Map each funding method to the correct ledger account and verify the first posted payment in that account.
- Use durable vendor, bill, payment, check, and trace identifiers instead of names alone during reconciliation.
- Do not merge, delete, or recreate records until the authoritative object and downstream effects are proven.
Classify failed, duplicate, overpaid, refunded, and missing payments
Separate collection failure from delivery failure. Current Melio guidance lists payer-side causes such as insufficient funds, card limits, authorization, or frozen accounts and receiver-side causes such as closed accounts, invalid routing or account numbers, or refusal. Preserve the failure reason and status before changing anything. Correct the funding source or vendor delivery information through the supported path, then verify whether the original payment is retried, refunded, canceled, or still pending.
For a failed ACH delivery, current Melio guidance offers a supported retry or, when eligible, a full refund. The retry flow states that funds are not debited again, while refund availability and timing depend on the payment. Do not schedule a second new payment simply because the vendor has not received the first. Confirm the original status, settlement, refund state, and bank activity so recovery does not produce a second disbursement.
Classify duplicates by cause: the same invoice paid twice, a bill recreated after sync, an external payment marked in the wrong system, an unlinked QBO funding account, or a legitimate recurring reference. Current Melio guidance treats delivered overpayments as a vendor-recovery matter, while Xero guidance warns where to mark outside payments. Compare documents, identifiers, amounts, dates, states, and bank results before deleting or reversing anything.
- Preserve the original error, status timeline, payment ID, bank evidence, vendor communication, and accounting entries.
- Use the supported retry, refund, cancellation, void, or vendor-recovery route for the exact payment state.
- Prove whether a proposed action can debit cash or create another accounting payment before executing it.
- After recovery, verify the vendor balance, bill status, funding account, bank statement, and exception register.
Close the period with targeted recovery and product-aware evidence
Run a month-end Melio checklist with a defined cutoff. Record the last successful synchronization; review unmatched vendors, missing bills, unsynced or failed payments, pending vendor details, refunds, duplicates, overpayments, credits, and scheduled items; and reconcile AP control totals, vendor balances, bank accounts, credit cards, and any clearing accounts. Review date and period differences rather than forcing totals to agree with unsupported journals.
Handle vendor credits according to the connected product and plan. Current Melio guidance says credits originate in accounting software; QuickBooks Online supports viewing and, on eligible higher plans, applying credits in Melio; QuickBooks Desktop changes remain managed in Desktop; and Xero credits do not sync. A refunded payment with applied credit may require restoring the credit in QBO and refreshing the sync. Record the exact product, credit state, and approved accounting treatment.
Turn each incident into a controlled improvement. Preserve the original and corrected states, approval, action, resulting Melio and accounting records, bank evidence, and reviewer. Update mapping registers, vendor-match procedures, funding-account checks, plan-limit monitoring, and training based on the proven cause. Test future changes with representative data and a rollback plan rather than using broad disconnect, resync, or record recreation as a default response.
- Age every unresolved exception by financial-statement effect, cash risk, vendor impact, owner, and target date.
- Keep QBO, Xero, and Desktop recovery procedures separate and cite the current product-specific Melio guidance.
- Back up reports, mappings, error evidence, and configuration state before irreversible accounting changes.
- Obtain independent close review that connects Melio status to ledger balances and external bank evidence.
Vendor documentation and ALLMSP resources
- Melio: Connect and sync QuickBooks Online
- Melio: What data syncs with QuickBooks Online
- Melio: QuickBooks Online automatic or manual sync
- Melio: Link a payment method to QuickBooks Online
- Melio: Find missing bill payments in QuickBooks Online
- Melio: Missing QuickBooks bills
- Melio: What data syncs with Xero
- Melio: Does Melio sync to Xero
- Melio: QuickBooks Desktop connection troubleshooting
- Melio: Handle unsuccessful payments
- Melio: Resolve failed ACH delivery
- Melio: Duplicate or overpaid invoice recovery
- Melio: Apply vendor credits
- ALLMSP Melio Software Support category
- ALLMSP Software Support services
- ALLMSP Cloud Computing and Migrations
- ALLMSP Managed IT services
- ALLMSP CPA and Financial Firms IT
- Contact ALLMSP
Frequently Asked Questions
Does Melio sync the same way with QuickBooks Online and Xero?
No. Both products have documented field and workflow directions, but their timing, field coverage, AP and AR behavior, and exceptions differ. QuickBooks Desktop has a separate Web Connector architecture. Record the exact accounting product and use its current Melio documentation for every correction.
What is the current Melio sync limit on the Go plan?
Current Melio QBO and Xero guidance says Go can synchronize the first ten payments across both directions and across payables or receivables. After the limit, additional Melio payments and pending accounting bills may stop syncing. Verify current subscription terms before relying on continued synchronization.
Why is initial vendor matching important in Melio?
Current QBO and Xero guidance says Melio proposes matches for similar existing vendors and warns that skipped suggested links cannot be created later. Review legal identity, accounting ID, contact data, open bills, history, and delivery relationship before confirming or skipping each match.
Which system should be authoritative for Melio sync corrections?
The business must document authority by object and lifecycle state using the product's supported directions. Make vendor, bill, payment, credit, or void changes in the designated system and verify propagation. Do not edit both sides simultaneously merely because the same field is visible in each.
How can an unlinked Melio payment method affect QuickBooks Online?
Melio guidance says an unlinked funding method can post payments to a MelioChecks account and create duplicate-looking bank entries. Link the method to the correct QBO bank or card account, identify affected payments, and obtain accounting approval before any irreversible account merge.
Should a failed Melio ACH delivery be paid again as a new payment?
Not until the original is resolved. Current Melio guidance provides a supported retry that does not debit the payer again and, when eligible, a full refund path. Confirm original status, settlement, bank activity, delivery details, and refund state before creating any new disbursement.
How should Melio collection and delivery failures be separated?
Collection failures involve the payer's bank or card, such as funds, limits, authorization, or account status. Delivery failures involve the vendor endpoint, such as invalid or closed banking details. Assign the correct owner, preserve the failure evidence, and use the supported recovery for that stage.
What should happen after an invoice is paid twice through Melio?
First prove that two payments actually settled. Preserve both IDs, bank evidence, bill and vendor history, and accounting entries. For a delivered overpayment, current Melio guidance describes requesting repayment from the vendor. Correct the ledger under accounting approval without deleting the evidence trail.
Do vendor credits behave identically across Melio integrations?
No. Current guidance says credits originate in accounting software. QuickBooks Online, QuickBooks Desktop, and Xero have different visibility and action behavior, and applying credits in Melio depends on subscription. Verify the connected product, plan, credit state, and refund consequences before acting.
What closes a Melio sync incident at month-end?
Closure requires agreement among the Melio object and status, vendor outcome, accounting bill and payment entries, funding account, bank or card evidence, credits or refunds, and the exception log. Retain the before state, approved correction, after state, and independent reviewer evidence.
