Did It Read the Statement, or a Summary of It?
A summary tells you what a document chose to stress. To know whether a number is right, something has to read the source.
Ask an AI assistant to review a forty-page loan agreement and tell you what matters. It comes back in seconds with a neat list: interest rate, term, payment schedule, a couple of covenants. Organized, confident, sensible.
Then ask one more question: did you read the whole document, or a condensed version of it?
Often the honest answer is the condensed version. Many tools pass long documents through a step that shortens them first, then answer from the short version. The fee schedule on page thirty-one, the prepayment penalty in an appendix, the covenant that tightens after year two: those are the parts most likely to fall out.
What a summary is for
A summary keeps what the writer put up front and lets the rest go. That is what it is for. The headline survives. The fine print that qualifies the headline usually doesn't. And it can't know what matters to you, since it knows nothing about your books.
A gist is useful when that's all you need. It falls short once the question is whether a number is right, or whether a clause affects you. In finance, those are usually the questions that count.
Where it shows up in bookkeeping
- A bank statement condensed to "beginning balance, ending balance, 212 transactions," with three bank fees and one returned item lost along the way.
- A vendor contract reduced to "net 30," when the actual terms include a 2% early-payment discount nobody is taking.
- A scanned receipt where half the page didn't read, described as if the visible half were the whole thing.
The rule we follow
When a document matters, the work reads the source, not a description of it. And every review says what it covered:
- Which pages or transactions were read in full.
- Which couldn't be read: scanned pages that didn't come through, attachments that wouldn't open, files in a format that couldn't be parsed.
A review that can't name what it read, and what it couldn't, hasn't really reviewed anything. Ask for that list every time.
The bonus you don't expect
Reading the source closely has a side effect. To finish the thought, you often have to go back and check your own books. Does this fee show up in the ledger? Is this discount being taken? Those answers are rarely in the document. They sit where the document and your books disagree, and only a close reading takes you there.
The takeaway: When anyone, person or software, reviews a document for you, ask for a list of what they read in full and what they couldn't read.
Want these checks running on your books?
We set this up on your books and your rules, and nothing posts without your approval.
Book a call