Skip to main content

Reconcile inventory to your accounting provider

SKU.io knows what your stock is worth on any day. Your accounting provider, QuickBooks Online or Xero, holds the same figure as the balance of your inventory accounts. Inventory reconciliation compares the two day by day, shows where they part ways, and lets you drill into any day to see what moved. SKU.io is treated as the source of truth for inventory, so a gap is something to explain or adjust in your books.

Before you begin​

  • QuickBooks Online or Xero is connected, and automatic accounting is on.
  • You can manage accounting settings.
  • Each warehouse is mapped to the inventory account it posts to, so SKU.io knows which stock belongs to which account.

Open it​

Go to Accounting → Reconciliation and open Inventory, or go straight to Inventory reconciliation. The Connection at the top right names the provider it reads. With no accounts chosen yet, the page asks you to earmark some.

Inventory reconciliation before any accounts are earmarked

Choose the accounts to reconcile​

  1. Click Earmark accounts, or Configure & sync at the top right. The Configure & sync panel opens.

  2. Under Earmark inventory control accounts, tick each account that holds inventory in your books, such as Inventory Control and Inventory In Transit. Accounts that look like inventory accounts carry a Suggested chip. Select Suggested ticks them all.

    Each row shows the account's Provider match, the account it matched in QuickBooks or Xero, the Warehouses mapped to it, and SKU.io's Current SKU value for them.

  3. Click Save Earmarks.

The Configure & sync panel, with the earmark list

An earmarked account needs something in SKU.io to compare against. Most accounts get that from a warehouse mapped to them. Your inventory in transit, accrued purchases and goods received not invoiced accounts are valued without one, including any in-transit account a product uses instead of the default. Any other earmarked account with no warehouse mapped to it has nothing to compare against: map a warehouse to it, or remove the earmark.

Pull the balances from your books​

SKU.io reads your provider's general ledger for the earmarked accounts and keeps a copy, so it can rebuild the provider's balance for every day. The bar at the top of the panel shows how much of your history it holds so far.

  1. In Configure & sync, click Sync provider GL….
  2. Choose how far back to read:
    • Since last sync re-reads only what can still change: everything after your books were last closed in your provider.
    • Back to opening balance reads everything back to your inventory start date.
    • Custom from date reads from a day you pick, no earlier than the inventory start date.
  3. Check the Estimated provider API calls, and click Start Sync. It runs in the background.

Sync provider GL for a QuickBooks connection

QuickBooks Online costs one report call per month of history and has no daily allowance, so the dialog only shows the estimate. Xero limits how many calls you make in a day, so the dialog also shows how much of today's allowance the sync uses, and a long history may take more than a day. SKU.io refreshes the recent days every night on its own.

When Xero can't share its journals

Rebuilding Xero's balance for every day needs permission to read Xero's journals. If your Xero connection doesn't have it, the sync says so in the job tray and still captures your opening balance. Where it can be fixed, the message tells you to reconnect Xero and run the sync again. Until both balances exist for a day, the comparison reads Nothing to compare yet: no day has both balances. instead of showing the account as matched.

Two more buttons in the panel rebuild one side or the other: Rebuild SKU values recomputes SKU.io's daily inventory value, which costs no provider calls, and Re-anchor opening balance re-reads the provider's balance on your opening day.

Read the comparison​

Once accounts are earmarked and synced, the page shows a summary (Open divergence, Accounts diverging, Divergent months and Data as of) and a row per account:

ColumnWhat it shows
SKU valueWhat SKU.io says the stock in that account is worth.
Provider GLThe account's balance in your books.
DivergenceThe difference, with which side is ahead.
Awaiting syncEntries SKU.io has made that haven't reached your provider yet. These close on their own.
Opening gapThe difference on your opening day.
Divergent monthsMonths whose movement didn't match, even if the balance nets back to zero later.
StatusFor example Matched, Opening gap, Ongoing gap or Resolved.

Use Period to look at one year. Click an account to see it day by day, and a day to see the transactions behind its movement, grouped by type.

Close a gap​

  • An opening gap is a difference that was already there on your opening day, usually history from before you started using SKU.io. Click Reconcile opening on the account. The dialog separates the part that is only waiting to sync, which needs nothing, from the true residual, and can post an adjusting journal to your provider for the rest.
  • An ongoing gap opened after your opening day. Click Reconcile ongoing to open Reconcile ongoing divergence. It shows where the gap came from, month by month and by transaction type, and proposes an adjusting journal: pick the balancing account, check the debit and credit, and post it.

An adjusting journal syncs to your provider like any other entry. To reconcile a whole period at month end, the close checks read these comparisons. See Inventory and the close.

Lock everything before a new opening baseline​

When you set a new opening baseline in Reconcile opening, the dialog offers Also set my Accounting Start Date to date and lock everything before it. Tick it to do both in one step:

  • Your Accounting Start Date moves to the baseline date.
  • Your hard close date moves to the day before it, so nothing before the baseline can change or sync, while the baseline day itself stays open and reconcilable.

This is the one way to set a hard close date that doesn't fall on a month end. It needs the Period Hard Close permission under Accounting on the Roles screen, and it only moves the date forward. It's refused if the baseline is in the future, if your hard close date is already later (lower it first), or if it would lock a month you've closed. In that last case, move the hard close date from Accounting → Settings → Close instead. You can move the hard close date later from its card there.

Changes carried out of a locked period​

A locked period is everything on or before your effective lock date: your hard close date, or a provider lock date you enforce, whichever is later. The reconciliation keeps every locked day at the value it had when it was locked. If a later edit changes what inventory was worth inside the lock (a corrected bill for goods received before the lock, for example), you see it as Carried forward from the locked period in the breakdown by type:

  • Inside a locked month, it holds the edit back, so the month still totals what it was locked at.
  • In the first open month, it releases the change. With Book locked-period carry-forwards on (Accounting → Settings → General), an adjusting journal with a reference starting INV-LOCK-CF- is booked on the first open day against your default cost of goods sold account and faces it in your books, so the row balances.
  • While that setting is off, nothing is booked, so the row shows the change on the SKU.io side only. Review the amount, then turn booking on.

This journal isn't a reconciling adjustment of the kind Reconcile ongoing proposes, so don't plug it a second time.

Only locked months carry changes forward. A month you've closed but haven't locked takes the edit on its true date instead: its figures change, it shows as Closed – restated, and it asks you to re-sign it off. See When a closed month changes.

Each night, SKU.io measures the carry-forwards and lists them in the Locked Accounting Period Changed alert. A carry-forward at or above the Review threshold under Accounting → Settings → General is called out as large enough to consider restating instead: lower the hard close date, fix the period, then move the date forward again. See How the hard close date works and Lower or clear the hard close date.

Next steps​

Last verified: