In accounting, a slide error is an amount recorded with its decimal point in the wrong place, so 1,250.00 is booked as 125.00 or 12,500.00. Every digit is right; only the scale is wrong. The difference it leaves divides by 9 or 99, and the two amounts differ by a factor of ten or a hundred.
What is a slide error in accounting?
A slide error moves the whole amount one or more places left or right, as if the digits had slid past the decimal point. The digits stay in order, so it survives a quick glance, yet it is a large error: a slide by one place changes the amount by ninety per cent or by nine hundred per cent.
Slides come in two directions. A slide to the right inflates the amount, as when 85.40 becomes 854.00. A slide to the left shrinks it, as when 3,900.00 becomes 390.00. The first kind often appears when someone types cents without a decimal point into a field that expects whole units. The second kind appears when someone types a trailing zero too few.
A slide can also drop or add zeros without moving the decimal visibly. Keying 20,000.00 as 2,000.00 is a slide, even though the decimal point stayed put on the screen.
Slide error versus transposition error: telling them apart
A slide error and a transposition error both leave a difference that divides by nine, but they damage an amount differently. A transposition reorders two digits and keeps the size roughly the same. A slide keeps the digits in order and changes the size by a power of ten. The source document shows which you have.
A practical test: if the wrong amount and the right amount share every digit in the same order, it is a slide. If they share the same digits in a different order, it is a transposition. A transposition of 4,562.00 into 4,526.00 changes the amount by under one per cent. A slide of 4,562.00 into 456.20 changes it by ninety per cent.
The size of the difference relative to the smaller amount also helps. A one-place slide always leaves a gap of nine times the smaller amount. A transposition never leaves a gap that large; most leave a gap far smaller than either amount.
The arithmetic that exposes a decimal slide
A one-place slide leaves a difference equal to nine times the smaller amount. A two-place slide leaves ninety-nine times the smaller amount. Divide the unexplained difference by 9, then by 99; if either gives a figure that appears in the ledger or on the statement, that figure is your candidate line.
The table below uses example amounts to show the pattern.
| Amount intended | Amount booked | Difference | Difference / 9 | Difference / 99 |
|---|---|---|---|---|
| 1,250.00 | 125.00 | 1,125.00 | 125.00 | 11.36 |
| 85.40 | 854.00 | 768.60 | 85.40 | 7.76 |
| 3,900.00 | 39.00 | 3,861.00 | 429.00 | 39.00 |
| 0.75 | 0.07 | 0.68 | 0.0756 | 0.0069 |
In the first two rows the division by nine returns the smaller amount exactly. In the third row, a two-place slide, the division by 99 does. The last row shows a slide of cents where the decimal was cut short and the remainder dropped, so neither division comes out clean. That case is covered at the end of this post.
Where slide errors come from in bank and ledger entries
Slide errors come from keying and from file formats. Manual entry produces them when a person types 12500 meaning 125.00, or omits a zero. Imports produce them when a CSV stores amounts in cents and the importing system reads them as whole units, or the reverse.
Common sources:
- Ten-key habits. Adding machines with an automatic decimal setting train people to type 12500 for 125.00. The same keystrokes in a spreadsheet give 12,500.
- Exported files. Some systems write amounts in minor units. Mapping that column as dollars multiplies every line by one hundred.
- Bank feeds and rule edits. A mapping change in an accounting system's import settings can slide a whole batch. In ERP systems such as NetSuite, imported statement files go through a parser, and NetSuite bank reconciliation covers how those imported lines are matched.
- The bank itself. A teller can key a deposit with a decimal slide. That is a bank error, and handling a bank error on a bank statement explains how to get it corrected.
How do you correct a slide error once it is found?
Correct a slide error by fixing the original entry if the period is still open, or by posting a correcting entry for the difference if it is closed. Either way, attach the source document that shows the right amount. The correction is for the difference only, not a reversal and re-entry, unless your system makes that cleaner.
For an inflated amount, the correcting entry reverses the excess. If a 125.00 supplier payment was booked as 1,250.00, the books show 1,125.00 too much going out. The correction credits the expense or payable and debits cash for 1,125.00. For a shrunken amount, the entry runs the other way.
When a whole import slid, correct the batch rather than line by line. Delete or reverse the import, fix the column mapping, and bring the file in again. Check one line against the statement before trusting the rest.
Edge case: a slide error hiding in a cents-sized difference
A slide error does not always look large. When the amount involved is a few cents, a slide produces a difference of a few cents too, and it is easy to mistake for rounding. The division tests still work; they just return fractions of a cent that look like noise.
The 0.75 example in the table is typical. A fee of 0.75 keyed as 0.07 leaves 0.68. Divide by nine and you get about 0.0756, which is not a clean figure because the keyed amount was truncated as well as slid. The clue is that 0.07 and 0.75 share their first digit.
Before you write a small gap off, list the lines under one dollar and compare each with the statement. The search order for that case is laid out in why a reconciliation is off by a few cents. PreciseBankFlow reads each statement amount from the PDF, gives it a confidence score and checks that the lines add up to the printed closing balance, so a slide made while copying the statement shows up as a footing difference rather than hiding among the ledger lines.