> For the complete documentation index, see [llms.txt](https://www.zerabooks.com/help/llms.txt).
# Verify a statement with AI
When a statement doesn't tie, ZeraBooks can re-read the original document line by line and propose only the fixes that make it tie. You apply them with one click.
## When to use it
Use AI verification when a month shows an orange **!** because the statement itself doesn't add up (the **Statement doesn't tie** flag) and you're not sure which line or balance was misread.
It's offered only while the statement is off by some amount. A statement that already ties shows "Available when the statement doesn't tie — this one has nothing to verify."
## Run the verification
1. Go to **Accounting** › **Reconciliations**.
2. Click **Review…** on the account's card, or click the orange **!**.
3. On the right, open **Flags & suggestions**.
4. Under **AI verification**, click **Verify against the document**. The button reads **Re-reading statement…** while ZeraBooks transcribes the document line by line and checks it against your rows.
## Read the suggestions
Each suggestion names the problem, explains the fix, and quotes the line from the document it's based on.
| Suggestion | What ZeraBooks found |
| --- | --- |
| **Missed line** | A line printed on the statement is missing from your rows |
| **Phantom line** | A row isn't on the statement |
| **Sign flipped** | Money in was read as money out, or the reverse |
| **Amount misread** | An amount doesn't match the document |
| **Date misread** | A date doesn't match the document |
| **Balance misread** | The printed opening or closing balance was read wrong |
ZeraBooks proposes only fixes that make the statement tie. If it finds none, it says so ("No document-backed fix found." or a note explaining why), and you can fix the month by hand. See [Fix a month that doesn't tie](https://www.zerabooks.com/help/reconciliations/fix-a-month-that-doesnt-tie).
## Apply the fixes
- **One fix at a time:** click **Apply** on a suggestion. A message confirms it, and says "The statement now ties." when it does.
- **Fixes that only work together:** the panel says "These fixes tie only together — apply all." Click **Apply all**.
While **Apply all** runs, the panel shows **Repairing statement…** and a progress bar ("3 of 5 fixes written"). Each fix is re-checked against the statement as it lands.
{% hint style="warning" %}
Keep this screen open until the repair finishes. Leaving midway can leave the month half fixed, and your browser asks before you leave.
{% endhint %}
When every fix is written, the panel reads **Statement repaired** and the month's dot updates. If a fix fails, it reads **Repair stopped**; run **Verify against the document** again to see what remains.
## Frequently Asked Questions
When is "Verify against the document" offered?
Only when the statement is off by an amount other than zero. A statement that already ties has nothing to verify.
Does AI verification change my books on its own?
No. It only proposes fixes. Nothing changes until you click **Apply** or **Apply all**.
Why is Apply missing on the suggestions?
The fixes only make the statement tie together, so they're applied as a set. Click **Apply all** at the top of the suggestions.
What does "Repair stopped" mean?
One of the fixes couldn't be written, often because the rows changed in the meantime. The fixes marked **Fixed** are saved. Click **Verify against the document** again to see what's left.
The verification found nothing. What now?
Check the printed balances with **Fix statement details…**, or add and remove rows in **Edit**. If the whole statement was read badly, remove it in **Banks & Cards** and upload a clearer copy. See [Fix a month that doesn't tie](https://www.zerabooks.com/help/reconciliations/fix-a-month-that-doesnt-tie).
Can AI verification fix a ledger difference?
No. It compares your rows with the statement document. A **Ledger difference** comes from something else on the account, such as a journal entry or an opening balance; the panel lists the journal entries touching the account that month.
---
## Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://www.zerabooks.com/help/reconciliations/verify-a-statement-with-ai.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
The full index is at https://www.zerabooks.com/help/llms.txt. An MCP server with `searchDocumentation`, `getPage` and `askQuestion` tools is at https://www.zerabooks.com/help/mcp.