Ecommerce Accounting Integrations: From Order to Bank Deposit
Learn how to connect store, marketplace, payment, and accounting data without duplicate revenue. Follow a payout through fees, refunds, tax, and reconciliation.
Connecting a store to accounting software is easy to describe and harder to verify. An app can say it syncs Shopify or Amazon while your books still show unexplained deposits, missing fees, or the same sale twice. The useful question is: Can you trace one order through the payment processor and into a reconciled bank deposit?
The four records behind a sale
- Store or marketplace: the order, discount, shipping charged to the customer, tax, refund, and product sold.
- Payment processor or marketplace settlement: fees, holds, adjustments, and the amount scheduled for payout.
- Accounting system: revenue, tax liability, fees, refunds, inventory or COGS, and a clearing account for money not yet deposited.
- Bank: the actual deposit and its date.
These amounts rarely match line for line. A store may report the sale on Monday, the processor may take its fee on Tuesday, and the payout may reach the bank on Thursday. A refund or reserve may affect a later payout. Your goal is to explain the differences, not force all four screens to display the same number.
For example, a payout containing $100 in sales, $20 in refunds, and $3 in payment fees would be $77 before tax, reserves, or other adjustments. Recording only the $77 bank deposit as revenue loses the gross sales, refund, and fee detail. Adding the store's $100 sales record and treating the $77 deposit as new revenue counts income twice.
Decide which connection owns each job
| Connection | It should supply | What to confirm |
|---|---|---|
| Store or marketplace to payout connector | Sales and settlement components | Are discounts, refunds, gift cards, tax, shipping income, and fees mapped separately? |
| Connector to QuickBooks or Xero | Entries in the right accounts and periods | Does it create duplicates alongside an existing native app or manual import? |
| Bank feed to accounting | Deposits and withdrawals | Do deposits match a clearing balance rather than create new sales? |
| Inventory system to accounting | Value of stock and cost of sold units | Which system owns quantities, unit cost, and adjustments? |
| Accounting and operations sources to analytics | Reports for decisions | Are sources complete for the dates being compared? |
Set up and test one payout
1. Record the current state
List the store, each marketplace, the processors that collect payment, the bank accounts receiving deposits, your accounting system, and every app already posting transactions. Note whether Shopify Payments, PayPal, or another processor handles each order type. A diagram on one page is enough. This step exposes duplicate connectors before you turn on another sync.
2. Agree on the account mapping
Ask your bookkeeper how the connector should classify product sales, discounts, shipping income, sales tax, processor fees, refunds, gift cards, and settlement clearing balances. Inventory purchases and COGS need their own policy. The correct treatment can depend on your country and accounting method, so have the person responsible for the books approve the mapping.
3. Start with a closed, representative payout
Choose a settlement that includes at least one refund or fee, not the cleanest possible sale. Compare the source settlement report with the entries sent to your ledger. Check amounts, currency, dates, tax handling, and the account used for the eventual bank deposit. Keep the source report as evidence.
4. Reconcile the bank deposit
The deposit should clear the amount held in transit. A difference needs an explanation: a reserve, delayed refund, processor adjustment, conversion fee, split payout, or mapping error. Do not plug a difference with an unexplained journal entry just to make the bank screen green.
5. Check the next month
An integration that works for one payout can still put sales into the wrong period or miss a later refund. Review the payout clearing account, sales by channel, tax liability, and COGS at month-end. Recheck after plan changes, new payment methods, or a new marketplace connection.
Common causes of mismatched numbers
- A net payout was booked as sales. Fees and refunds disappear from the P&L. Compare the settlement components with the accounting entry.
- Two connectors posted the same orders. Disable the duplicate path only after confirming which entries each app created and agreeing on cleanup with your bookkeeper.
- The store and processor use different dates or currencies. Match by order, settlement, and payout identifiers rather than only by calendar day.
- Inventory cost did not reach COGS. Sales can reconcile while reported gross profit is still wrong.
- A report is incomplete. Missing channels or a stale sync can make a dashboard look precise while omitting costs. Check source status and the period shown.
Where Nummbas fits
Build the accounting trail first. Once you can explain a payout and trust the books, analytics can help you decide which products, channels, and costs need attention.