Every business that sells online, bills subscriptions or runs a CRM ends up with the same problem: the money moves in one system and the books live in another. Someone exports a CSV, someone else types invoices into QuickBooks or Xero, and at month end the totals do not match the bank. Accounting software integration replaces that manual step with a defined flow of records between your operational systems and your general ledger.
This guide is the starting point for our series on integrations. It explains the patterns that repeat across QuickBooks, Xero, NetSuite and Sage: which records move, the three ways to connect, how to plan a setup, where integrations usually break, and what drives cost. Each section links to a dedicated guide for a specific pair, such as Stripe and QuickBooks or Shopify and NetSuite.
What an Accounting Software Integration Syncs
The ledger is the end of the line. Most integrations push records into it, and only a few read data back out. The objects are similar in every accounting system, even when the names differ.
| Record | Usually comes from | Direction | What it becomes in the books |
| Customers | CRM, e-commerce store, billing system | Into accounting, sometimes both ways | Customer or contact record |
| Products and services | Store catalog, ERP, billing plans | Into accounting | Items mapped to income accounts |
| Orders and invoices | Store, CRM, billing system | Into accounting | Sales receipts or invoices |
| Payments | Payment processor, POS | Into accounting | Payments applied to invoices |
| Payouts | Stripe, PayPal, Shopify, Square | Into accounting | Bank deposits or transfers to clearing accounts |
| Processor fees | Payment processor | Into accounting | Expense entries |
| Refunds and chargebacks | Store, processor | Into accounting | Credit notes, refund receipts or journal entries |
| Sales tax | Store, tax engine | Into accounting | Tax lines and liability accounts |
| Inventory quantities and costs | ERP, warehouse system, POS | Either way, depending on the system of record | Stock levels and cost of goods sold |
| Vendor bills | AP tools, procurement systems | Into accounting | Bills and bill payments |
| Payroll | Payroll and HR systems | Into accounting | Journal entries for wages, taxes, benefits |
| Invoice status, balances | Accounting | Out to CRM or billing | Paid or overdue flags for sales and support teams |
Two decisions shape everything else. First, choose the system of record for each object. If both the store and the ERP can edit inventory, you will get conflicts. Second, decide the level of detail. Some businesses post every order as its own invoice; others post one daily summary journal per channel. Summary posting keeps the ledger small and makes reconciliation against payouts easier. Order-level posting gives better customer history but creates thousands of records a month.
Integration Options
There are three ways to connect an accounting system to the rest of your stack, and most companies end up using more than one.
Native or official connectors. Accounting platforms run app marketplaces (Xero's App Store, for example, groups apps by category such as payroll, payments, invoicing, and bills and expenses), and many payment, commerce and CRM vendors publish their own apps there. These install in minutes and cover the common flow for one pair of systems. The trade off is fixed mapping: you get the fields and posting rules the vendor chose.
Third-party connectors and iPaaS. Dedicated sync apps focus on a narrow problem, often payouts and fees from processors and marketplaces. Integration platforms (iPaaS) offer prebuilt templates plus a visual workflow builder, so a finance or ops team can connect several systems without code. They add a subscription and, usually, pricing tied to volume or the number of connections.
Custom integration through the APIs. Cloud accounting systems expose APIs for their core records. A custom service reads from your billing, store or CRM, applies your own rules (account mapping, entity routing, tax treatment, deferred revenue) and writes to the ledger. It costs more to build and needs an owner, but it does exactly what your process requires.
| Option | Best for | Limits | Cost basis |
| Native or official connector | One common pair, standard posting | Fixed mapping, little control over summaries, tax or multi-entity logic | Often free or a monthly app fee |
| Third-party connector or iPaaS | Several systems, moderate volume, no in-house developers | Per-transaction or per-connection pricing, edge cases still need manual work | Monthly subscription, often tiered by volume |
| Custom API integration | High volume, custom revenue rules, several entities, audit needs | Build time, maintenance, API changes to track | Project budget plus hosting and support |
Which option fits depends more on your posting rules than on the systems themselves. If a connector produces the journal entries your accountant wants, use it. If your team spends days each month fixing what a connector posted, the subscription is not the real cost.
Integration Guides by System
This hub links to the pair-specific guides. Each one covers what syncs, setup steps, limits and costs for that combination.
QuickBooks
Most of our guides start with QuickBooks.
- Stripe QuickBooks integration: payouts, fees, refunds and subscription revenue.
- Shopify QuickBooks integration: orders, payouts, taxes and inventory from a Shopify store.
- WooCommerce QuickBooks integration: store orders plus the Stripe and PayPal payments behind them.
- PayPal QuickBooks integration: PayPal activity and reconciliation, with a short Xero section.
- QuickBooks POS integration: Square, Shopify POS and other point of sale systems.
- QuickBooks CRM integration: HubSpot, Salesforce, Zoho and Dynamics, Online versus Desktop.
- QuickBooks payroll integration: 401(k), HR and time tracking.
- QuickBooks integration for Amazon and Etsy sellers: marketplace settlements and fees.
Xero
The Xero guide focuses on payment processors.
- Xero Stripe integration: connecting Stripe to Xero and reconciling payouts, with a note on Sage Intacct.
NetSuite
The NetSuite guides cover commerce, payments and banking.
- Shopify NetSuite integration: orders, inventory, fulfilment and refunds.
- Stripe NetSuite integration: payment and payout reconciliation.
- NetSuite e-commerce and POS integration: WooCommerce, Square, Amazon, Zoho, PayPal and more.
- NetSuite bank integration: bank feeds, payments and reconciliation.
Sage
Sage products follow the same patterns. The Sage Intacct and Stripe combination is covered inside the Xero Stripe integration guide, and Sage CRM in the QuickBooks CRM integration guide.
How to Set Up an Accounting Integration
The steps below apply whether you install a connector or commission a custom build. Skipping the first three is the most common reason an integration gets switched off after a quarter.
Agree on the chart of accounts mapping
List every income, fee, tax, clearing and liability account the integration will touch. Decide where gross sales, discounts, shipping, processor fees, refunds and chargebacks each land. Have your accountant sign off before anything is connected. A clearing account per processor (for example "Stripe Clearing") makes payout reconciliation far simpler, because each payout then moves one balance into the bank account.
Pick the system of record for each object
Customers usually belong to the CRM, products to the store or ERP, invoices to the billing system and payments to the processor. Write it down. Two way sync is only safe for objects with a clear owner and conflict rules.
Choose summary or detailed posting
Decide whether each sale becomes its own invoice or sales receipt, or whether the integration posts a daily or per-payout summary. Many teams post detail for B2B invoices (customers need statements) and summaries for high volume B2C orders.
Connect in a sandbox or test company
If your accounting system or connector offers a sandbox or test company, connect there first, run a week of real data through it and compare the result with your existing books.
Run a historical cut-over
Pick a start date, usually the first day of a month. Everything before it stays as it is; everything after it flows through the integration. Importing years of history through a connector is slow and often creates duplicates.
Reconcile the first two months by hand
Match each payout to the bank deposit and check fees, refunds and tax totals against the source system's reports. Only when two closes come out clean should you stop checking every line.
Monitor errors
Every connector and custom service will fail sometimes: an expired login token, a deleted item, a closed accounting period. Make sure someone receives the error alerts and has a routine for fixing failed records.
Common Problems and Limits
The same failure points show up in almost every accounting integration we see, whatever the systems involved.
Duplicates. A retried request, a reinstalled connector or a manual entry alongside the sync can post the same sale twice. Integrations need an external ID on every record and a check before each write.
Payouts that do not match the bank. Processors deposit net amounts: sales minus fees, refunds, chargebacks and reserves, sometimes across several days of activity. If the integration posts gross sales without the matching fees and adjustments, the deposit never reconciles.
Sales tax. The store or tax engine calculates tax, but the ledger needs it on the right liability account, by jurisdiction where required. Connectors differ in whether they post tax as separate lines, as a single total, or not at all.
Multi-currency. Orders in one currency, payouts in another and a ledger in a third create exchange differences. You need a rule for which rate applies and where gains and losses post.
Edits after posting. An order changed after it reached the ledger, or an invoice voided in the CRM, has to be handled as an update or a reversal. Many simple connectors only handle new records.
Closed periods. Once a month is closed, late refunds and adjustments must post to the current period. The integration has to know about the lock date instead of failing silently.
API limits. Accounting APIs typically cap the number of requests per minute and per day. Bulk catch-up after an outage can hit those caps, so the integration needs queues and retries, not one request per order in a tight loop.
Desktop versus cloud. Desktop accounting software is usually reached through local connectors or file imports rather than the cloud APIs used for QuickBooks Online or Xero, so check what your version supports before choosing a connector. The QuickBooks CRM integration guide covers this split in more detail.
Costs
The cost of an accounting integration has three parts: the accounting plan itself, any connector subscriptions, and the build and maintenance of custom code.
Accounting plans. QuickBooks Online lists Simple Start at $38 per month, Essentials at $85, Plus at $140 and Advanced at $340 (list prices in November 2026; Intuit often runs introductory discounts); user limits run from 1 user on Simple Start to 25 on Advanced. Xero's US plans are Early at $27 per month, Growing at $59 and Established at $97, with an introductory discount for the first three months. For NetSuite and Sage Intacct, ask the vendor for current pricing.
Connectors and iPaaS. Most connector apps price by monthly order or transaction volume, and iPaaS platforms by connections, tasks or workflow runs. Check the pricing page of the specific app for your pair; the pair-specific guides above list what each vendor publishes.
Custom integration. For fintech work, Itexus states on its fintech software development page that discovery and prototyping engagements "start from around $30,000", and that enterprise fintech projects "often range from $150,000 to $1,000,000+". A single accounting sync is usually a part of a larger platform build rather than a project of that size on its own; the scope depends on the number of systems, entities and posting rules.
When a Custom Integration Makes Sense
Your volume outgrows connector pricing. When connector fees scale with every order and you process tens of thousands of transactions a month, a custom service with summary posting can cost less to run and produce a cleaner ledger.
Your revenue rules are not standard. Subscription tiers, prepaid annual plans that need deferred revenue, usage-based billing and partner revenue shares rarely fit a connector's fixed mapping. Custom logic can split and schedule revenue the way your auditor expects.
You run several entities or ledgers. Sales in one country, billing from another, and a parent company consolidating both means routing each record to the right subsidiary, currency and tax setup. An ERP can hold several entities, but something still has to decide where each record goes.
Reconciliation is a monthly fire drill. If your team spends days matching payouts, refunds and chargebacks, an integration that posts every component of a payout and flags drift automatically pays for itself in close time.
Compliance and audit trails matter. Regulated fintech products need to show where each ledger entry came from. A custom integration can keep the source ID, timestamps and transformation rules for every record, which a generic connector rarely exposes.
How Itexus Can Help
Itexus has delivered "300+ fintech projects delivered for 250+ clients in 23 countries", including "120+ integrations" for neobanks, payment providers, robo-advisors and trading systems.
- Payout reconciliation. For an investment advisory firm, we reconciled Stripe payouts into QuickBooks with revenue by subscription tier, deferred revenue for prepaid annual plans, refund and chargeback categorization and per-state sales tax.
- Real-time accounting sync. For a B2B billing platform, we built real-time synchronization of invoicing and financial data with Xero and QuickBooks.
- CRM, ERP and payment gateways. We connect billing, CRM and payment systems to the ledger, and build middleware when an older system has no API.
- NetSuite. We take on NetSuite integration projects; we have not published a NetSuite case yet.
See the wealthtech case or contact us.
Itexus is a trusted partner
Itexus delivered the app according to the requirements. The team met all development milestones and deliverables. They were efficient, friendly, and cooperative. Itexus team was very timely with updates, a regular meeting cadence, and ad-hoc questions and answers via Slack. The team was very responsive and still is.
Stive Jackson
RMD, Investing Fund
Itexus’ work positions the business well for an imminent launch. They excel at managing their team, presenting frequent product demos to ensure that the project is aligned with development goals. An affordable price structure coupled with remarkable technical skill makes them an attractive partner.
Phill Osolinski
CEO Ryze Rewards
The assigned team was easy to work with and they are especially strong collaborators and communicators. They demonstrated flexibility, professionalism, and trust in everything they did, and completed the work on time and budget.
Sue Wollan Fan
CEO Mango Connects
Itexus excelled at both experimental AI and sprint-oriented UI/UX tasks. Itexus did strong project management work, too, a necessity in such a complicated project.
Jesse Dubin
Senior PM Standard&Poors
They’re a great group of developers who really understand the reality of business.
Andreea Vanacker
CEO SPARKX5
Frequently Asked Questions
What is accounting software integration?
It is a connection that moves financial records, such as customers, invoices, payments, payouts, fees, refunds and taxes, from your operational systems into your accounting software automatically. The goal is to stop retyping data and to make month-end reconciliation a check rather than a rebuild.
How does Xero accounting software integration work?
Xero connects to other systems through apps in its app marketplace and through its API. A connector or custom service authorizes access to a Xero organisation, then creates records such as contacts, invoices and payments there. The Xero Stripe integration guide walks through a typical setup.
Can accounting software integrate with Salesforce?
Yes, through a marketplace app where one exists for your pair, or through a custom integration using both systems' APIs. The usual flow sends accounts and closed deals from Salesforce to the ledger as customers and invoices, and returns invoice status and balances to Salesforce. See the QuickBooks CRM integration guide for the Salesforce section.
What does a custom ERP integration for accounts payable involve?
An accounts payable integration takes vendor bills from a procurement, AP automation or document capture tool, matches them to purchase orders where required, posts them as bills in the ERP or accounting system, and records bill payments once they are made. Custom work is usually about approval rules, multi-entity routing and keeping the payment status in sync both ways.
Should I use a connector or build a custom integration?
Start with a connector if it posts entries your accountant accepts and your volume keeps its price reasonable. Move to a custom integration when you need non-standard revenue rules, several entities, high volume or a full audit trail, or when manual fixes after each sync take more time than the connector saves.
Which accounting software is easiest to integrate?
Cloud systems with public APIs and app marketplaces, such as QuickBooks Online and Xero, are usually the quickest to connect. ERPs such as NetSuite take more setup because there is more to map: subsidiaries, currencies and more record types. Desktop products tend to be the hardest, because they rely on local connectors or file imports.
