Depreciation schedules
When the schedule arrives as a scan
Sometimes the schedule is a clean PDF printed straight from the suite. Sometimes it's a photocopy of a printout, scanned crooked, emailed as an attachment. Both are workable; they need different expectations.
Text layer or no text layer
If the scan has been through OCR, it has a text layer and we can read it. If it's a pure image, we say so immediately and charge nothing — run it through your scanner's OCR or Acrobat's and upload again. There's no point pretending otherwise and billing you for a guess.
Confidence scores exist for exactly this
Every extracted row carries a confidence score. Damaged or ambiguous rows are flagged and surfaced first on the reconciliation screen, so your attention goes where the scan is weak instead of spread evenly over rows that were perfectly legible.
The tie-out is your safety net
A scan is exactly where a misread digit is most likely. It's also where the totals check earns its keep: a transposed 4 and 7 shows up as a difference you can see, on a row we can name.
Questions
- Should I use the Verified tier for scans?
- It's the case it exists for. A second independent pass over every row costs less than finding the error in a later year.
- My scan is sideways.
- Rotate it and re-save before uploading. Orientation is one of the few things worth fixing on your end first.