Skip to main content

Understanding What We Read From Your Accounting Integration

  • Updated

Connecting your accounting software is one of the first things you'll do in Weel, and it's fair to ask exactly what data we access. This article covers what Weel reads, writes back and never touches for Xero, MYOB AccountRight, QuickBooks Online and NetSuite, plus how each connection stays secure. Details differ by platform, so find your own section below.

How It Works

What's the same across every integration

  • Weel never reads your payroll data, on any integration.
  • Weel never changes or deletes a record it didn't create; your existing accounts, contacts and transactions stay untouched.
  • Disconnect anytime from Settings > Integrations.
  • Your accounting provider's consent screen may list broader permissions than Weel actually uses. The sections below show exactly what Weel reads and writes in practice.
  • Connecting alone doesn't change anything in your books. Nothing is written until you have Weel transactions ready to sync.

Xero

What we read

  • Chart of accounts, filtered to active Expense, Asset (excluding Bank and Inventory types), Liability or Revenue accounts. Equity accounts, system accounts and inactive accounts are excluded. Xero is the only platform where Revenue-classified accounts are included. See Understanding Which Accounts You Can Map in Weel for the full breakdown across platforms.
  • Tax rates.
  • Tracking categories (Xero's own classes and tracking options), genuinely synced.
  • Your active supplier list, a real bulk-synced list of active contacts, not a per-transaction lookup.
  • Your organisation details and accounting period lock date, checked proactively before every export. Xero exposes two lock dates (a general period lock and an end-of-year lock); Weel uses whichever is later.

What we write back

  • Card transactions, plus Bills and Reimbursements processed through Accounts Payable. Both export as Xero invoices, and Xero blocks a payment against a period you've locked (see How to enable automatic lock period handling for what happens then).
  • Receipts and tax invoices, attached to the transaction.
  • New suppliers, created automatically if no existing contact matches on name.
  • A genuine live Bank Feed into your dedicated Weel account in Xero, created automatically once your Xero integration is verified. Transaction data and coded expense data arrive as two separate streams you match against each other in Xero's Reconcile tab. See Understanding the Xero Bank Feed for the full mechanics and timing.

What we don't read

  • Your actual business bank account, balances or transactions. Weel only reads back its own dedicated Weel account inside Xero (and, narrowly, that account's own balance via a Xero report, when the right access is granted; never your real external bank account).
  • Your payroll data.
  • Your customers or the invoices you send them. Weel doesn't interact with your accounts receivable.
  • Data it didn't create. One limitation worth knowing: once a refund transaction is exported, Weel currently can't reverse it from the Xero side. You'll need to fix that one directly in Xero.

How your connection is kept secure

Xero uses genuine OAuth2, token-based authorisation. You log in with Xero, not with Weel, and no Xero password or other Xero credentials are ever stored by Weel.

MYOB AccountRight

What we read

  • Chart of accounts: active Expense, Other Expense, Asset (excluding Bank type), Cost of Sales or Liability accounts. Equity, Income, Other Income, header and inactive accounts are excluded.
  • Tax codes.
  • Jobs, imported as a single tracking field named "Job Code". MYOB doesn't have a separate Classes or Locations concept like Xero and NetSuite; Jobs is the one tracking mechanism it syncs.
  • Your active supplier list, genuinely bulk-synced like Xero, not a per-transaction lookup.
  • Your organisation details and accounting period lock date, checked proactively before every export.

What we write back

  • Bills, exported as MYOB Purchase Bills. Paying the bill in Weel records the payment against it automatically. Reimbursements export separately as Spend Money transactions.
  • Bills export to MYOB is currently in beta and rolling out progressively. If it isn't switched on for your account yet, these payments won't export automatically; contact help@letsweel.com to have it enabled.
  • Card transactions, plus receipts attached to each.
  • New suppliers, created automatically if no existing contact matches on name.
  • A dedicated Weel ledger account, created directly in your MYOB chart of accounts. Unlike Xero, this is a genuine account you reconcile manually in MYOB, not a live bank feed.
  • MYOB is the only platform where Weel can genuinely reverse a transaction it created, by posting an equal and opposite entry, rather than requiring a manual fix on the MYOB side.

What we don't read

  • Your actual bank account, balances or transactions.
  • Your payroll data.
  • Your customers or the invoices you send them.
  • Data it didn't create.

How your connection is kept secure

Most MYOB connections use MYOB's current, token-based "granular scopes" authorisation. You log in with MYOB and choose your company file during MYOB's own consent screen, and no MYOB password is stored by Weel. A smaller number of older connections still use MYOB's legacy company-file login, which asks separately for your company file's own user ID and password; those credentials authenticate that specific company file and are stored against your integration record, unlike every other flow in this article. This legacy path is being phased out. If you're setting up MYOB for the first time today, you'll get the newer, password-free flow.

QuickBooks Online

(The QuickBooks integration is currently available to Australian Weel businesses only.)

What we read

  • Chart of accounts: active Cost of Goods Sold, Expense, Fixed Asset, Other Current Asset, Other Expense, Accounts Payable or Other Current Liability accounts. Bank, Accounts Receivable, Credit Card, Long Term Liability, Equity, Income, Other Income and inactive accounts are excluded.
  • Tax rates and tax codes.
  • No tracking categories. Unlike the other three platforms, QuickBooks tracking categories (Classes and Locations) aren't imported or used; there's no field to tag spend to a class or location on this integration.
  • Not a bulk supplier list. Unlike Xero and MYOB, Weel doesn't maintain a browsable list of your QuickBooks vendors. At the point of export, Weel checks for a matching Vendor, Customer or Employee by exact name (QuickBooks shares one name namespace across all three) and creates a new vendor if nothing matches.
  • Your organisation details and accounting period lock date, checked proactively before every export.

What we write back

  • Card transactions only. Bills and Reimbursements aren't currently exported to QuickBooks. If you use those features alongside a QuickBooks integration, reconcile those payments manually; see Understanding QuickBooks Support for Bills and Reimbursements.
  • Approved card transactions export as QuickBooks Purchase records (Deposit records for refunds), with receipts and tax invoices attached.
  • New vendors are created automatically when no match is found.
  • A dedicated Weel ledger account ("Weel Expenses Account"), created directly in your QuickBooks chart of accounts. You reconcile it manually, not through a live bank feed; see How to reconcile transactions in QuickBooks.
  • Weel currently can't reverse a refund (Deposit) it created in QuickBooks if it needs correcting.

What we don't read

  • Your actual bank account, balances or transactions.
  • Your payroll data.
  • Your customers or the invoices you send them, though the same-namespace name matching above can occasionally match an existing Customer record by name. This never pulls in your customer list, invoices or balances.
  • Data it didn't create.

How your connection is kept secure

QuickBooks uses genuine OAuth2, token-based authorisation. You log in with QuickBooks, not with Weel, and no QuickBooks password is stored by Weel.

NetSuite

NetSuite connects a little differently to the other three. It's set up with the help of your Customer Success Manager rather than a self-serve Connect button, and during setup you choose whether to also enable a live Bank Feed connection.

What we read

  • Chart of accounts, Classes, Departments, Locations, and Customer/Client records, imported so you can code spend against them. NetSuite's synced account list is broader than Xero, MYOB or QuickBooks (it can include Bank and Accounts Payable-type accounts too), because Weel can't automatically create your dedicated NetSuite account the way it does elsewhere; you or your implementation specialist choose which existing NetSuite account to designate.
  • Tax rates.
  • Not a bulk supplier list. Like QuickBooks, Weel checks for a matching Vendor by exact name at export time and creates a new one if nothing matches, or, if your business has chosen this option, always attributes exports to a single shared "Weel" vendor instead of creating individual ones.
  • No proactive lock-date check. Unlike the other three platforms, Weel doesn't check the accounting period lock date in advance for NetSuite. If a transaction lands in a locked period, that only surfaces as an export error when the export is attempted.

What we write back

  • Approved card transactions, exported with vendor, GL account, class, department, location and customer/client coding, an invoice attachment, and a link back to the transaction in Weel. Refunds export separately as a NetSuite Journal Entry, a different record type to an ordinary transaction.
  • Bills and Reimbursements aren't currently exported to NetSuite; this integration currently only exports card transactions.
  • If you chose Bank Feed export during setup, Weel also posts a matching bank feed entry against your designated NetSuite account for each transaction, so reconciliation works the same way it does on Xero. If you didn't, you reconcile the designated account manually instead. See How to link your NetSuite account (with Bank Feed export) or without Bank Feed export, depending on which you're on.
  • Weel currently can't reverse or delete a transaction it created in NetSuite if it needs correcting.

What we don't read

  • Your actual bank account, balances or transactions, beyond the reconciliation entry above if you've enabled Bank Feed export.
  • Your payroll data.
  • Your customers' own invoices or account balances. The Customer/Client sync above is for coding spend against a customer or project, not reading your accounts receivable.
  • Data it didn't create.

How your connection is kept secure

NetSuite connects through a secure, hosted authorisation flow. You log in directly with NetSuite through that flow, and Weel never sees or stores your NetSuite username or password.

Good to know

  • This article covers Weel's four pre-built accounting connectors: Xero, MYOB AccountRight, QuickBooks Online and NetSuite. It doesn't cover the Weel Public API (a separate, self-built integration path; see Getting started with the Weel OpenAPI) or Microsoft Dynamics 365 Business Central (currently a Beta, Enterprise-plan, sales-assisted integration with no self-serve Help Centre section yet; contact your account manager if you're on Business Central).

Related Articles