Why review comes before posting

Reading a document is the slow part. Deciding what it means is the part that can hurt a client if it is wrong. A model can misread a date, attach a ride receipt to the wrong expense, or treat a supplier bill as a sale. Auto-posting that into Tally is not a time saving. It is a correction you will make later, in the books that matter.

AutoBooks puts every extracted row in the Review Grid first. The accountant can change the date, the party, the amounts, the VAT, the ledger, and the voucher type. A keyword rule can remember the next match. An AI suggestion is marked so you can see it was a suggestion. A row that is already in Tally is locked, so a later edit does not quietly rewrite a voucher that has already been sent.

Roles stay separate. Someone can upload. Someone else can review. Sending to Tally is its own permission. A document that is waiting on an approval cannot be added to the trial balance or pushed to Tally until that approval is done.

The point is a short review, not a second data-entry job. The reading is done. The decision stays with the person whose name is on the file.