OPSAVOR docs
Menu

Home › Using OPSAVOR

Reviewing and confirming

OPSAVOR reads every document, but a reading only counts once it has been confirmed. How to check one quickly, fix what was misread, move through a pile, and how automatic confirmation works.

Why confirming matters

An AI reader is fast, but it can be wrong. So OPSAVOR keeps one rule: a reading counts only once someone confirms it. Until then it does not touch your sales, costs or ledger. That is why the figures you see can be trusted.

The list: what is waiting

Open Add & Review. Below the upload buttons, tabs sort your documents, each with a count:

TabWhat is in it
Needs reviewReadings waiting for you, oldest first, which is the order to work through them.
ReadingDocuments still being read. They move to Needs review by themselves.
ProblemsFiles that could not be read, or that OPSAVOR keeps but does not read.
Done / Dismissed / AllWhat has been confirmed, what was set aside, and everything.

Each row shows what the document is (invoice, delivery receipt, daily totals…), the vendor and invoice number, the amount and the document's own date. Search by file name, vendor or invoice number, or filter by type and date. The list remembers your tab and filters on that device.

Add and Review: the location's invoice email address, a note not to upload sensitive data, a drop area with Choose files, Choose folder, Take photo and Scan document, and the tabs Needs review, Reading, Problems, Done, Dismissed and All.
Needs review, oldest first. Each row says what the document is and what it is for.
Add and Review on a phone, with the upload buttons and each document shown as a card.
On a phone each document is a card.

Checking a document

Press Review. The document opens on the left and what OPSAVOR read on the right.

The review panel for a Harbor Ice Co invoice: the PDF on the left; on the right a note that this is the first invoice from this vendor, then vendor, invoice number HI-2207, dates, subtotal, tax, total $185.50, the three lines and the checks; Confirm, Edit and Dismiss at the bottom.
The page beside the reading. This is the first invoice from Harbor Ice Co, so the panel asks you to check it is a supplier you use.
The review panel on a phone, with the document above the reading and Confirm at the bottom.
On a phone the reading sits under the document, with the buttons at the bottom.

Fixing a misread value

  1. Press Edit (or the E key).
  2. Correct the value, for example type 515.50 for the total. You can change lines too, and add or remove one.
  3. If a value was flagged but is right, tick Looks right beside it.
  4. Press Save corrections. The checks run again straight away, so a fixed total clears "does not add up".

Corrected values are marked corrected with what was originally read, and values you vouched for are marked checked by a person. Your corrections also teach OPSAVOR: each one is kept as an example of what the document really said.

Before you confirm

If confirming would need something from you, a Before you confirm box says what, before you press anything:

Lower in the panel for an Ironbridge Bakery invoice: the lines, the checks (amount due $551.50 is $50.00 more than the lines), and Before you confirm, which asks for a reason to confirm it as it stands.
The checks show exactly what does not add up, and the box asks for a reason to confirm it as it stands.

The sentence under the reading says what confirming will do, for example "Confirming books $515.50 owed to Saltmarsh Seafood…".

Daily sales reports

A sales report shows the figures it will book, day by day: net sales, tax, tips, each way guests paid, and more. Each day says whether the payments add up to net sales plus tax and tips: tenders add up, or tenders differ by $12.00. A day that does not add up is not put in the books until it does, and the month-end checklist names it.

A daily totals report in the panel: figures by day, each with gross sales, discounts, net sales, tax, guests and payments, and a red label where the tenders differ from the sales.
Days from a daily totals export where the card and cash payments do not add up to the sales: each day waits until they agree.

Duplicates

If a document looks like one already on file, both are shown side by side: the other page and its vendor, number, date and total. Press It's a duplicate to set this one aside, or Keep both if they are really different.

Moving through a pile

Confirm & next confirms and opens the next document in the list. Skip and Previous move without confirming. Dismiss sets a document aside, and asks why: wrong file, a duplicate, not ours, unreadable, a test, or something else, with an optional note. A dismissed document can be brought back with Undo.

KeyDoes
CConfirm (and go to the next)
EEdit the reading
DDismiss
J or → / K or ←Next / previous
+ − RZoom in, zoom out, rotate
EscClose
Made a mistake?

A confirmed document can be taken back with Take off the books (owners). Its figures stop counting, and you can correct and confirm it again.

Loading a lot of history

Press By day above the list to see one row per day: the documents that cover it, how many still need review, and which reports are missing (daily sales report, payroll) or complete. Click a document to review it. A day that has not finished yet says not closed yet rather than missing.

Automatic confirmation

It can save clicking to let OPSAVOR confirm documents that are clearly right. It is off by default, and there is no switch for it on the screens yet: ask OPSAVOR support to turn it on for your restaurant. It is deliberately cautious:

The weekly digest says how many documents were confirmed automatically, so you always know how much was approved without you.