Payment UpdateWeek of Nov 2
A late report is not missing money. Two Lightspeed sync delays, and how to close the day when the numbers disagree
TL;DR
On October 26 Lightspeed's status page logged delayed payout reporting while deposits kept landing on schedule. The next evening a traffic spike backed up the sync between Restaurant O-Series and connected accounting platforms, and some venues were still waiting on October 29. Here's what happened, why a deposit, a sales report and a ledger disagree, and how I'd close the day without turning a sync delay into a real error.
What happened
Heads up if you close out on Lightspeed: two sync delays last week, the week of October 26, and in both cases the money was fine.
On October 26, 2026 Lightspeed's status page logged delayed payout reporting for its Hospitality product. The notice said the issue affected reporting only, and that funds continued to be deposited on the normal schedule. It cleared in about five hours.
The next evening, October 27, a traffic spike created a queue in the sync between Restaurant O-Series and connected accounting platforms. Lightspeed said data was secure and the backlog was working through. By the late update on October 29, most venues had caught up, and some were still being processed. Lightspeed marked it resolved on November 2.
Two different systems, same shape: the money landed, the numbers on the screen ran late.
What it means for you
Say the bank shows $5,000 and the POS report shows $4,200. Did $800 disappear? Usually not. Those numbers are made up, but the gap is real, and it happens on every platform, not just this one.
The deposit, the sales report and the accounting ledger are three different systems that update at three different speeds. The bank posts when the processor settles. The POS report posts when its payment reports sync. The ledger posts when the accounting integration runs. When one of them is behind, the gap looks like a loss, and the natural move is to fix it: book the difference, key a manual adjustment, make the screens agree.
That's how a sync delay becomes a real error. The next morning the late system catches up, the adjustment is still there, and now the books are wrong by exactly the amount you "fixed".
If it were my counter
I'd check the status page before I touched the books.
If the provider says reports are delayed and funds are on schedule, I'd leave the numbers alone, note the gap, and close the day tomorrow when the sync is through. If it's the deposit that's late, that's a different problem and a different call, to the processor, today, because a late deposit is about your money and a late report is about a screen.
Reconcile first, adjust last. Most "missing" money is a timestamp.
Questions owners ask
Was any Lightspeed money actually lost last week?
Not according to Lightspeed's status page. The October 26 notice said deposits were on the normal schedule while reporting lagged. The October 27 to 29 issue was a sync delay to accounting platforms, with data described as secure. Check your own deposits against your bank to confirm.
How do I tell a reporting delay from a deposit delay?
Look at the bank first. If the deposit is there and the POS or accounting report is short, it's a reporting delay, and the provider's status page will usually say so. If the deposit itself hasn't arrived on its normal day, call the processor.
Should my POS show me these three states separately?
It should. A good dashboard tells you what was sold, what was settled to your bank, and what has synced to accounting, as three numbers with three timestamps. If yours blends them into one figure, ask the provider how to see them apart. Our own POS shows what was sold and what has settled as separate numbers.
Sources
