Online store connected to an accounting system

What to Know Before Connecting Your Store to Your Accounting System

Connecting a store to an accounting system is usually presented as a one click setup. Install the connector, authorize both sides, and your sales appear in your books. For a simple store selling a handful of products in one country, it often really is that easy.

For everyone else, the connection is the easy part. The decisions underneath it are what determine whether your accounts balance at the end of the month, and most of them are easier to make before the first order syncs than after a few hundred have.

Decide What Should Actually Sync

Not everything in a store belongs in an accounting system, and pushing everything across creates noise that someone has to maintain.

Sales and refunds almost always belong there. Payouts from your payment provider do too, because those are what actually hit your bank. Customers are a judgment call, and often the answer is no: your accounting system does not need a record for every one time buyer, and thousands of thin contact records make it harder to use.

Products and stock are usually better left in the store unless you are doing full inventory accounting, which is a larger commitment than most small stores need. The rule of thumb is to sync what affects the numbers, and leave what only affects operations where it already lives.

The Summary or Detail Decision

This choice shapes everything that follows. Either each order becomes its own entry in your accounts, or each day becomes a single summary entry covering all of it.

Detail is useful when you need to find one customer’s transaction quickly or your accountant wants order level visibility. It is also noisy: a busy store can add thousands of entries a month, which makes reconciliation slower and the file heavier.

A daily summary keeps the books clean and is usually what accountants prefer for higher volume stores. The tradeoff is that answering a question about one order means going back to the store rather than looking it up in the accounts.

There is no universally right answer, but there is a wrong process: choosing by accident, discovering the consequence three months later, and unpicking it by hand.

Where the Numbers Disagree

When a store and an accounting system show different totals, it is nearly always one of the following.

Payment Fees and Payouts

A customer pays one hundred. Your payment provider takes a fee and deposits slightly less, often several days later and bundled with other orders. Your store records the full sale, your bank shows the net deposit, and the two will never match unless the fees are recorded as an expense and the payout is matched to the orders it contains.

This is the single most common reason store and bank figures disagree, and it is also the one most likely to be set up incorrectly by default.

Refunds, Partial Refunds, and Chargebacks

A full refund is straightforward. A partial refund, a refund that excludes shipping, or a refund issued after a month is where connectors differ in behavior. Chargebacks add a fee and a separate reversal, sometimes weeks later.

Decide how each of these should appear in your books before they happen, because correcting them afterward means adjusting entries that have already been reconciled.

Tax Calculated in Two Places

Stores usually calculate tax per line item. Accounting systems often calculate on the invoice total. Both are reasonable, and they produce small differences that compound across a month.

One system should be authoritative for tax and the other should record what it is told rather than recalculating. Which one depends on where your filings come from.

Discounts, Gift Cards, and Store Credit

A gift card is not revenue when it is sold, it is a liability you owe. It becomes revenue when it is redeemed. Many connectors treat the sale as income immediately, which overstates this month and understates next.

Discounts have a similar subtlety: recording the reduced amount hides how much you discounted, while recording gross with a discount line shows it. The second is usually more useful to the business.

Shipping Charged Against Shipping Paid

What a customer pays for delivery and what you pay a carrier are separate numbers, often on different days. Treating one as the other hides whether your shipping is profitable, which for many stores is a meaningful part of the margin.

Orders That Never Complete

Abandoned carts, failed payments, and orders canceled minutes after they are placed can all create records in a store. Whether any of them should reach your accounts depends on how your connector treats an order that exists but was never paid, and the safe default is that only completed payments create financial entries.

Currency

If you sell in more than one currency, the rate at the time of sale, the rate when the payout lands, and the rate your accounting system uses will differ. Those differences are real and need a home in your accounts, rather than being rounded away.

Subscriptions and Recurring Charges

Recurring billing adds its own complications. A renewal is created by a different process than a normal checkout, it may be attempted several times before it succeeds, and a failed payment that later goes through can land in a different period than the invoice.

If you sell subscriptions, confirm specifically how renewals, retries, and cancellations appear in your accounts. Connectors that handle one time orders correctly do not always handle renewals the same way, and the gap usually goes unnoticed until the numbers stop matching.

When Does a Sale Count?

The store says an order exists when payment succeeds. Accounting might recognize it when the invoice is raised, when the money arrives, or when the goods ship, depending on your arrangements and where you operate.

Near a month end, this difference decides which period a sale falls into. Agree the rule with your accountant, configure the connector to match, and check the first month end closely. It is far easier to confirm the behavior once than to discover it during a year end.

Inventory Is the Sync People Regret

Syncing stock levels between systems sounds sensible and is the most common source of regret. Stock changes constantly, from sales, returns, damage, recounts, and deliveries, and every one of those is a chance for two systems to drift apart.

Most small stores are better served by keeping stock in one system, usually the store, and handling inventory value in the accounts periodically rather than continuously. Full inventory accounting is worth doing when margins depend on it, but it deserves a deliberate decision rather than a checkbox.

Someone Still Has to Reconcile

An integration moves data. It does not confirm that the data is right, and that distinction gets lost in the setup. Somebody still needs to check that what the store recorded, what the payment provider deposited, and what the accounts show all agree.

The difference a good integration makes is how long that takes. Reconciling a month of automatically recorded sales against payouts is a short task when fees and refunds are handled correctly, and a long one when they are not. That is the real measure of whether the setup is working.

Set a routine and keep it. Monthly is enough for most small stores, weekly during a busy season. The point is to catch a drift of a few dollars while it is still a few dollars, rather than meeting it as a year end problem nobody can explain.

What to Agree With Your Accountant First

Five questions, answered before setup, prevent most of the pain. Which accounts should sales, fees, shipping, and tax land in. Summary or detail. When a sale counts. How refunds and chargebacks should appear. Who reconciles the payouts, and how often.

Your accountant may have a strong preference based on how they file your returns, and following it costs nothing now. Discovering it conflicts with your setup after six months is the expensive version of the same conversation.

Keep the Store as the Record of the Sale

One principle prevents a category of confusion: the store is where an order happened, and the accounting system is where its financial effect is recorded. When the two disagree, the store is the account of events and the books are the account of money.

That sounds obvious until someone edits an order in the accounting system to make a total match. Now neither system is reliable, because one has been altered to hide a difference rather than explain it. Corrections belong where the mistake was made, with the sync carrying the fix across.

It also decides where your team works day to day. Order questions, refunds, and customer history stay in the store. Nobody should need access to your books to answer what happened with an order, and keeping that boundary makes both systems easier to trust.

Test With a Real Month

Before trusting the connection, run it against a period you already understand. Pick a past month, let the data flow, and compare the totals to what you know is correct.

Check the awkward cases specifically: a refund, an order with a discount, one paid in another currency if you take them, and one placed on the last day of the month. Those four cover most of what goes wrong.

When they match, you have something you can rely on at year end. When they do not, you have found the problem in a quiet month rather than during your busiest week, which is the entire point. If you want help mapping how your store, payments, and accounts should fit together, that is part of our integrations work, and it pairs naturally with the wider review in a site audit. For stores that need the storefront itself improved at the same time, that sits with our WooCommerce work.

Frequently Asked Questions

Detail suits lower volume stores and accountants who want order level visibility. A daily summary keeps the books clean for higher volume and is usually easier to reconcile. Choose deliberately with your accountant, because changing it later means unpicking entries that are already reconciled.

Payment providers take a fee and deposit the net amount, often several days later and bundled with other orders. Unless fees are recorded as an expense and each payout is matched to the orders inside it, the two figures will always disagree.

A gift card sale is money you owe, not revenue, until it is redeemed. Recording it as income on the day it sells overstates that period and understates the one where it is used. Check how your connector treats them, because defaults vary.

Usually not. Stock changes for many reasons and syncing it continuously between two systems is a common source of drift. Keeping stock in the store and valuing inventory in the accounts periodically is simpler and sufficient for most small stores.

They need to reduce income in a way your accountant expects, and connectors differ in how they record a refund that crosses a period boundary or excludes shipping. Decide the treatment before it happens rather than correcting reconciled entries later.

Often yes. Ready made connectors cover common setups well. Developer help tends to be worth it when you sell in multiple currencies, run subscriptions, have unusual tax handling, or need behavior the connector does not offer.

Run it against a past month you already understand and compare totals. Include a refund, a discounted order, an order in another currency if you take them, and one placed on the last day of the month. If those four match, the everyday cases will too.

You should be told rather than discovering it during reconciliation. Check whether your connector reports failures and to whom. If the answer is that it retries silently, add a monthly check of the last sync date to your routine until something better is in place.

Ready to Start?

Related Posts