Lightspeed K-Series to Accounting | Understanding and Reconciling Transitory Balances

If your daily sales in Lightspeed K-Series don't match the revenue that landed in your accounting journal, and there's no obvious missing sync or refund to blame, the cause is almost always a transitory balance: one or more orders that were still open on the POS when the business day closed.

Lightspeed already counts that order as revenue for the day it happened. Your accounting integration only ever receives closed receipts, so it can't count that revenue until the order is actually settled, sometimes a day later, sometimes longer. The two systems are simply looking at the same money at two different moments in time.

This article explains what transitory balances are, why they cause a temporary (or sometimes permanent) mismatch between Lightspeed and your accounting, how to spot and reconcile them, and how to stop them from happening in the first place.

What is a transitory balance?

You'll see this described with slightly different words depending on where you're looking:

In your accounting reports and journals, we call these transitory receipts or transitory balances.
Inside Lightspeed K-Series itself, the same thing is called a transitory order or transitory account.

They're the same thing: an order (or "receipt") that was opened on the POS during one business day but wasn't closed, meaning it wasn't paid, voided, or otherwise settled, before that business day ended (by default, Lightspeed's business day cuts over at 5:29 AM).

Common reasons an order is left open overnight:

A guest's tab, room charge, or running account was never settled at close.
A payment failed or was interrupted (e.g. a card terminal or network issue) and staff moved on without retrying it.
The venue briefly switched to standalone/offline mode while an order was still linked to a pending payment.
An order was accidentally left open by staff during a busy shift or at clock-out.
A technical glitch on the POS or a dropped connection during checkout.

None of these are unusual on their own: they happen at almost every venue occasionally. The issue is what happens to the reporting once they do.

Why this creates a mismatch with your accounting

Your accounting integration only ever pulls in closed receipts, so it has no way to book revenue for an order that's still sitting open on the POS. Lightspeed's own reporting, however, doesn't wait for the order to close: it recognizes the revenue on the day the order actually happened, using two lines you'll find in the Payments section of the Business report:

Carried forward: the total value of orders still open at the end of this business day, pushed into tomorrow. This line adds to today's reported takings, because Lightspeed still wants today's report to reflect today's activity.
Carried over: the value of orders inherited from yesterday that are still open. This line appears as a negative amount on today's report, because those takings were already counted yesterday and shouldn't be counted twice.

Together these form the Total transitory figure on the Business report. As long as that figure isn't zero for a given day, expect your Lightspeed sales total and your accounting revenue for that day to disagree, not because anything is broken, but because the two systems are recognizing the same sale on different dates.

How a transitory order plays out over several days

The clearest way to understand this is to follow a single unpaid order through time. Below are three realistic scenarios.

Scenario 1: The guest comes back and pays a few days later (a timing difference)

A restaurant has a running tab of €120 that a regular guest usually settles "next time they're in." It stays open past the day's close, and it takes a couple of days before it's finally paid.

Day	What happens on the POS	Lightspeed Business report	Accounting
Tuesday	Order opened for €120, not paid by close	Carried forward: +€120 (counted in Tuesday's takings)	€0 received (order still open, nothing to sync)
Wednesday	Still not paid; still open at close	Carried over: -€120 (reversing Tuesday's count), Carried forward: +€120 (pushed on to Thursday). Net effect on Wednesday's takings: €0	€0 received (still nothing to sync)
Thursday	Guest returns, pays the €120 in full	Carried over: -€120, then a new payment of +€120 for the settlement. Net effect on Thursday's takings from this order: €0	€120 received (this is now a closed receipt, dated Thursday)

Look closely at Thursday, the day the order actually closes: Lightspeed's Business report shows a net-zero contribution from this order (the carried-over reversal cancels out the new payment), but your accounting journal or invoice for Thursday will show the full €120 as new revenue, because that's the day the receipt was actually closed and synced. So on the day a transitory balance finally closes, your accounting figure for that day will typically look higher than Lightspeed's Business report total for that same day. The opposite was true on Tuesday, the day it was first opened: Lightspeed had already counted the €120, but accounting had nothing to show yet, so Lightspeed looked higher that day.

Over all three days combined, both systems agree on the total (€120), just recognized on different dates. This is a timing difference, not a data error, and it's exactly what "Total transitory" is measuring: on any given day, Total transitory = Carried forward minus Carried over. When that figure is positive, Lightspeed's report will show more revenue than accounting for that day. When it's negative (more orders closing that day than opening), accounting will show more revenue than Lightspeed's report for that day, which is exactly what happens on Thursday above.

Scenario 2: The order is voided instead of paid (a permanent difference)

Same starting point: a €120 tab opened Monday, still open at close.

Day	What happens on the POS	Lightspeed Business report	Accounting
Monday	Order opened for €120, not paid by close	Carried forward: +€120	€0 received
Tuesday	Staff investigate, decide the order should never have stood, and void it	Carried over: -€120, no offsetting payment → net effect on Tuesday: -€120	€0 received (a voided order is never sent as a receipt)

Here, Monday's Lightspeed report still shows €120 of revenue that will never arrive in accounting, because it was never actually collected. Unlike Scenario 1, this gap does not self-correct: it needs to be understood and, where appropriate, adjusted for in your bookkeeping (for example, by noting it as a write-off rather than treating it as a missing sync).

Scenario 3: Orders are left open for several days in a row (a compounding balance)

If staff don't have a habit of clearing open orders daily, transitory amounts can stack up. For example, if a venue consistently leaves 3 to 5 tabs open overnight, every single day will show both a "Carried forward" and a "Carried over" line, and the Total transitory figure never settles at zero. The mismatch between Lightspeed and accounting becomes a permanent, growing feature of the daily reports rather than an occasional one-off, which is exactly the pattern that makes reconciliation feel impossible if you don't know what to look for.

How to reconcile a day affected by a transitory balance

When a given day's numbers don't line up, don't assume the sync is broken. Check whether a transitory balance explains the difference first.

The formula:

Lightspeed sales total (for the day) − Accounting revenue total (for the same day) = Total transitory (from Lightspeed's Payments section, same day)

If the left side of that equation equals the Total transitory figure shown in Lightspeed, the "mismatch" is fully explained by transitory orders, and there's nothing wrong with your integration.

Worked example:

A venue's Business report for a given day shows:

Category	Lightspeed	Accounting
Sales at 0% VAT	€56.00	€56.00
Sales at 20% VAT	€520.50	€385.00
Total	€576.50	€441.00

The difference is €576.50 − €441.00 = €135.50.

Checking the Payments section of the same day's Business report, the Total transitory line reads €135.50. The two figures match exactly, which confirms the entire gap is explained by orders that were still open, not a missing transaction, a duplicate booking, or a sync failure. No correcting entry is needed; once those orders close, the revenue will flow into accounting on the day they're actually settled.

If the difference between Lightspeed and accounting does not equal the Total transitory figure, that points to something else, such as a refund, a manual adjustment, a payment method that isn't mapped correctly, or a genuine sync issue, and is worth investigating separately.

Where to find the figures you need

In Lightspeed K-Series:

Business report: the fastest place to check. Its Payments section shows "Carried over," "Carried forward," and "Total transitory" for the day.
Monthly turnover report: breaks the same figures down by employee and by device, useful if you need to know who or which till an open order came from.
Open orders report: lists every order that's currently unclosed. Any order here dated before today is, by definition, a transitory order.

In your accounting:

The daily journal entry or invoice generated for that venue, which will only reflect the receipts that had closed by the time the sync ran.

How to resolve open transitory orders

Once you've identified an open order that shouldn't still be there, close it properly rather than leaving it to roll forward again:

Find it. Use the Open orders report (or the Monthly turnover report, if you need to narrow it down by staff member or device) to locate orders left open from a previous day.
Work out why it's still open. Check whether a payment was attempted and failed, whether the guest simply hasn't returned yet, or whether it was left open by mistake. Lightspeed Payments reporting can help confirm whether a card payment actually went through on the payment provider's side even if the order wasn't marked as closed.
Close it appropriately, based on what actually happened:
- If the guest paid in cash, tender the order as a cash payment on the POS.
- If a card payment was taken on a separate/standalone terminal, tender the order using a custom payment method on the POS so it's marked as settled without double-charging the guest.
- If no payment was ever received and none will be, void the order (or discount it to zero) via the Actions menu, rather than leaving it open indefinitely.
Confirm it cleared. Check the next day's Business report. The order should no longer appear on the "Carried over" line, and the Total transitory figure should have moved back toward zero (assuming no other orders are still open).
If you're not sure how to close a specific order safely, contact Lightspeed support before voiding or discounting anything you're unsure about. Some situations (like a payment that may have gone through externally) are worth double-checking first.

Preventing transitory balances

A transitory balance now and then is normal. A venue that shows one on every single day usually has a process gap worth fixing:

Build a real end-of-day routine. Staff should check for open orders as part of closing procedures, not just cash counts. Lightspeed K-Series can also be configured so staff must settle any open orders before they're able to clock out. Enabling that setting removes the human "I'll deal with it tomorrow" factor entirely.
Keep the network stable. A dropped connection mid-payment is one of the most common causes of an order being left in limbo. Optimizing your venue's network for Lightspeed reduces failed or interrupted payments.
Be careful switching to standalone mode. If an order still has a payment pending, close that order out before the till drops into standalone/offline mode, otherwise it's easy for that order to get orphaned.
Review your reports regularly, not just when something looks wrong. A quick daily or weekly glance at the Business report's Total transitory line (or the Open orders report) catches stragglers before they turn into a habit, or into a Scenario 2/3 situation above.