How to Connect Wise to QuickBooks for Automatic Reconciliation

Set up Wise and QuickBooks to make reconciliation more predictable#

Connect Wise to QuickBooks Online in two separate ways: use the QuickBooks bank feed to import Wise currency transactions, and connect from Wise if you want unpaid supplier bills and payment status linked. Map each currency account and review downloaded transactions before relying on the books.

A small studio may receive client payments, pay overseas suppliers and convert currencies through the same Wise account. The connection can reduce entry work, but the bookkeeper still needs to distinguish sales, supplier payments, fees and transfers.

This guide covers the Wise and QuickBooks Online connection, including access, currency mapping, first import, supplier bill payments and exception handling. Product availability depends on the actual region and subscription; check the current screens before authorizing changes.

A downloaded transaction is a statement item to review. Matching it links to an existing accounting entry; adding it creates a new one. Formal account reconciliation is the separate check against the statement’s opening and closing balances. A feed import or an automatic bill-paid flag alone does not complete that reconciliation.

For a two-person creative studio, assign one setup owner and one accounting reviewer. The same person may cover both roles, but record when a setting changed and which transactions were checked. A currency or start-date mistake can duplicate activity even when the connection appears healthy.

Use the setup matrix, currency map and limited sample review to document the bank-feed and bill-payment paths. Preserve the existing ledger before importing more history.

Document the last reconciled statement date and the first transaction date you intend to import. Those boundaries give you a practical check when reconnecting or using a manual file later.

What do we know and what must you verify before trusting this integration?#

Use current Wise and Intuit documentation to distinguish supported features from settings that must be checked in your own account.

Confirm the business profile, QuickBooks company, region, plan, home currency and active currency accounts before authorizing a connection. Do not treat a familiar product name as proof that the selected account or feature is correct.

Keep a short setup matrix with the documented scope, the account-specific setting, the verification result and its owner.

Record the bank-feed path and the bill-payment path separately. Each has its own authorization and review checks, so a successful connection on one side does not prove the other is working.

Label remaining questions: earliest available feed history, refresh delay, currencies supported by your subscription and how refunds, fees and conversions appear. Resolve them from documentation or a limited review sample.

Assign an owner for account configuration, accounting decisions and support follow-up before importing or paying anything. Maintain an exception record with status and next action.

A connection marked successful is the start of verification: confirm the selected currency, import period and resulting ledger entries.

If a studio sees a missing transaction after setup, it can compare the dated Wise statement with QuickBooks’s imported date range and the existing register. That establishes whether the issue is a missing feed item, an unreviewed item or an accounting entry already present.

What should you prepare before you start the connection?#

Prepare access, currency accounts, import boundaries and an accounting reviewer before the first connection. Keep account credentials and payment authority separate from a shared mapping sheet.

Turn the setup matrix into a preflight checklist. Review existing feed connections, manual imports, opening balances and the last reconciliation so the new connection does not cover an already imported period without a duplicate check.

1. Confirm authorized access. Select the intended Wise business profile and QuickBooks company; keep individual access and recovery details current.
2. Check currencies before connecting. Verify the subscription supports the required feature. Intuit warns that enabling multicurrency cannot be undone; decide with the accounting owner and confirm home currency first.
3. Define the import period. Retain the last reconciled statement and register export, then choose a start date and record any expected overlap.
4. Create the mapping sheet. Map each Wise balance to its currency-specific ledger account, with separate treatment for fees, supplier payments and transfers.
5. Assign review and support owners. Record where to route authorization, feed and accounting questions, and who approves corrections.
6. Choose traceable samples. Use historical legitimate activity, an approved demonstration environment or a genuine small supplier payment that is already due and authorized. Do not create fake bills or force live payment failures.

Step 1 - Confirm Access, Currency Settings and Owners#

Use your authorized Wise Business profile and the correct QuickBooks Online company, with permissions appropriate to connection setup and review.

Avoid shared credentials. Verify the current admin and recovery process, then assign a person who can approve accounting corrections without granting every operator payment authority.

1. Confirm the company and profile. Compare their displayed identities with the mapping sheet before approving either connection.
2. Confirm permissions without disrupting work. Review approved roles and documented recovery; do not remove production access solely to test it.
3. Approve the currency setup. Record home currency and required foreign-currency accounts before enabling irreversible multicurrency.
4. Record the handover. Name who owns each connection and who reviews accounting outcomes; use supported ownership transfer when staffing changes.
5. Set escalation triggers. A stale feed, wrong account, duplicate or unexplained bill status gets an owner and a dated support case.

If a colleague leaves, transfer supported app ownership and revoke the obsolete access through the relevant Wise or QuickBooks workflow. Confirm which connections remain active; do not remove unrelated feeds or delete posted records as part of an access change.

Step 2 - Connect the Bank Feed and Map Wise Currency Accounts#

Connect from QuickBooks for the bank feed, selecting the correct Wise regional option and mapping each selected currency balance to the intended QuickBooks account.

In QuickBooks, open Accounting → Bank transactions → Link account, search for Wise and choose the option for the registered business address. Wise currently documents EU → Wise (European Union), US/Canada → Wise (US), UK → Wise (UK), and other regions → Wise (UK). Follow the current account prompts if labels change.

1. Choose the correct region. Follow the documented regional Wise option for your registered business address. If a region choice fails, confirm it rather than repeatedly creating new account links.
2. Authorize the intended balances. Select the Wise business profile and currencies, then the date from which QuickBooks should pull activity.
3. Map each balance. Use the intended account in the correct currency and retain the mapping reference. The account label alone does not establish currency correctness.
4. Check existing records. Compare opening balance, last reconciliation, manual imports and any active rules that might create entries.
5. Review the first items. Use a small selection spanning receipts, payments, fees and a transfer where present. Verify amount, sign, date and currency, then match existing records or add only genuinely new activity.
6. Keep an exception table. Record source reference, feed account, register reference, owner and next action. Recheck affected samples after any mapping change.

After the Wise authorization, review the business profile, balances and start date before confirming. Use the existing correctly denominated ledger account where appropriate; do not create a second account for the same balance accidentally. Refresh and inspect the first imported items before expanding review.

Worked receipt, fee and transfer checks#

Illustrative GBP example: a client invoice of £1,000 is fully collected, and the provider retains a £10 fee, leaving £990 in the Wise balance. Record the £1,000 client payment and £10 fee in the appropriate receipt/deposit workflow, then match the £990 statement item to that net result. The client is paid in full; the missing £10 is not automatically another amount to chase. If Wise instead shows a £1,000 credit and a separate £10 debit, match those two actual statement lines without also creating a £990 receipt.

If you then move £600 from Wise to your own GBP bank account with no fee in this illustrative transfer, the Wise balance falls from £990 to £390 and the bank balance rises by £600. It is a transfer between owned accounts, not another £600 of client revenue or a supplier expense. Match both sides to the same transfer. For currency conversions, preserve the amounts in both currencies, actual conversion rate and separately shown fees; let the accounting method handle any exchange difference.

Step 3 - Connect Supplier Bills and Verify a Controlled Sample#

For supplier-bill reconciliation, connect from Wise separately. Check an existing legitimate unpaid bill and confirm the resulting payment and fee entries before relying on wider automation.

In Wise, open the business profile, then Settings → Accounting integrations → QuickBooks, or the current apps-and-software connection screen, and authorize the correct company. Review connection settings such as importing unpaid bills and marking paid bills. QuickBooks multicurrency must be enabled for bill-paid automation.

1. Confirm the imported bill. Verify supplier identity, amount, currency, due date and whether it has already been paid elsewhere.
2. Check payment authority. Make only a genuine, due and approved supplier payment through the intended Wise workflow. Keep its reference and current status.
3. Review the accounting update. Confirm the bill-paid entry and Bank Charges fee; a failed or pending payment needs investigation before any correction or repeat.
4. Check the bank feed separately. Match its debit to the existing payment and fee treatment. Do not add another expense because the feed item has arrived later.
5. Log timing and exceptions. Record source/payment, import and accounting-update times without treating them as the same event.
6. Rehearse the fallback using saved records. Locate missing history and define non-overlapping file boundaries. An accounting fallback does not authorize paying a bill again.

A studio has already paid a £500 supplier bill through another provider, but the bill is still unpaid in QuickBooks. Wise can import it as unpaid. Check the payment evidence and record the existing payment correctly before initiating another one; the imported unpaid status is not proof that the supplier is still owed £500.

Expand use when each sampled item has one explainable accounting treatment, each currency balance maps correctly and exceptions have owners. A small pilot reduces exposure; it does not guarantee all future cases or make payment reversals available.

What Does the Connection Automate, and What Still Needs Review?#

Keep downloaded-transaction review, supplier-payment verification and formal statement reconciliation as distinct jobs. Observe refresh timing and use a review schedule that matches transaction volume.

The bank feed imports transactions; Wise’s bill connection can mark a bill paid and record fees. Neither promises that every receipt, refund, conversion or tax classification is correct without review. New customers do not have Wise’s legacy advanced matching/card-expense settings.

1. Measure each path separately. Record bank-feed freshness and bill-status update timing. A real-time unpaid-bill list does not guarantee real-time bank-feed import.
2. Review in fixed windows if helpful. Group downloaded items for accounting review; do not imply that Wise exposes a manual batch-sync switch.
3. Keep payment checks live. A payment that is pending, failed or returned needs its own status and supplier-balance review even if the accounting entry already exists.
4. Check before reauthorization or reconnecting. Retain last imported dates and account mapping. Review the first new items for overlap.
5. Use manual history import selectively. Import only identified missing dates/transactions, keeping file references and mapping. When the feed recovers, match or exclude genuine duplicate downloaded items rather than adding them again.
6. Retain the runbook. Record connections, currencies, owners, authorization expiry, review schedule and support contacts.

Common mistakes that cause reconciliation drift and how to recover fast#

Reconciliation differences can come from configuration, timing or bookkeeping. Identify the source item before changing settings or deleting entries.

After an initially clean setup, inspect changes in staff access, account mapping, import boundaries and automatic rules. A repeated small error can become a large closing-balance difference.

1. Recheck the affected currency map. Confirm profile, company, account and period before making corrective changes.
2. Review automation and access changes. Check bank rules and any legacy advanced settings that may create entries; restrict configuration changes to approved operators.
3. Work the exception queue. Identify source, downloaded item and register record. Prioritize duplicates, wrong amounts and missing history, with an owner and a carried-forward explanation when unresolved.
4. Correct using the appropriate workflow. A duplicate awaiting feed review may be excluded; an incorrect match/add may need Undo. Posted or reconciled records require accounting review before changes. Do not mass-delete a period or force a balancing entry.
5. Resolve actual payment status separately. A stale feed is not payment failure. Confirm with Wise and the supplier balance before any repeat instruction.
6. Use a controlled gap import only when needed. Preserve the downloaded file, selected dates and mapping, then check for overlap when the connection returns.

If a client invoice needs clearer fields or payment references, the free invoice generator can help prepare it. The bank feed still needs to match the actual collection to the recorded invoice payment.

Use this copy-paste checklist to run weekly and keep cashflow predictable#

Run a weekly checklist for access, feed freshness, bill payments and unresolved differences, then complete formal statement reconciliation for the chosen period.

Increase review frequency during a first connection, high transaction volume or an incident. A quiet feed is not proof of a quiet account: compare its latest transaction date with Wise’s statement.

1. Confirm access and consent. Review connection owners and displayed expiry; renew through the actual prompt before access lapses.
2. Reconcile source activity. Compare currency statements, feeds and register entries, including transfers and fees. Confirm that downloaded items are matched or correctly added once.
3. Check supplier payments. Verify bill-paid status and charges against actual Wise payment references, including anything paid outside Wise.
4. Review exceptions. Keep amount, currency, reference, owner, next action and expected review date for every material difference.
5. Check client collections. Separate unpaid invoice balances from paid collections awaiting settlement. Follow up only the genuinely outstanding amount; a fee or pending payout is not automatically a client underpayment.
6. Finish statement reconciliation. Use the statement’s opening balance, ending balance and date. Investigate differences rather than entering an unexplained adjustment.
7. Maintain recovery records. Save support cases and non-overlapping manual-import boundaries, then check recovered feed items before adding them.

Wise’s help guidance currently states that data-sharing authorization expires after ninety days. Record the actual consent expiry shown in each connection and set a reminder; reauthorize through the documented prompt and check the first returned items for continuity and overlap.