> ## Documentation Index > Fetch the complete documentation index at: https://docs.trysnapit.com/llms.txt > Use this file to discover all available pages before exploring further. # Bank statements > Upload a bank statement, check its balances, and let SnapIt mark the invoices it paid. # Bank statements A bank statement is the record of what really happened in your account. SnapIt reads every transaction on it, checks that nothing is missing, and suggests which of your open invoices each payment settles. When you confirm a match, the invoice is marked paid and its payment reminders stop. You can then send the payments to Xero or QuickBooks. Nothing is marked paid until a person confirms it. ## Upload a statement **1. Open Upload** Go to **Upload → Upload a Bank Statement**, or **Bank statements → Upload statement**. Owners and reviewers can upload. **2. Choose one file** Upload a PDF statement or your bank's CSV export, up to 50 MB. PDFs are read up to 50 pages. Each statement uses workspace credits, like an invoice upload; reprocessing is free. **3. Wait for the transactions** The statement page updates by itself when the transactions are ready. Long PDFs take a few minutes. ### What SnapIt reads * **CSV:** SnapIt looks for the header row by its column names: a date column plus an amount, debit, or credit column, and optionally description, reference, balance, and currency. Account details above the header are skipped. Dates are read day-first unless the file contains a date that is only valid month-first. * **PDF:** SnapIt reads the text on every page and extracts each transaction's date, description, reference, money in, money out, and running balance. Page headers, page numbers, and subtotals are skipped. Scanned statements without readable text are read from the first 8 page images instead. ## Check the balances SnapIt adds every movement to the opening balance and compares the result with the printed closing balance. It also checks each printed running balance against the row before it. | Result | What it means | | - | - | | **Balances tie out** | Opening balance plus every movement equals the closing balance. No rows are missing. | | **Needs review** | The balances are off, a running balance does not follow, a row has no date, or not every page was read. The statement page lists which. | | **Failed** | The file could not be read. The reason is shown on the statement. | When the balances do not tie out, or could not be checked (for example a CSV without a balance column), the statement page asks you to confirm that you have checked the rows before you can confirm payments. Fix a misread row with the pencil button; the check runs again when you save. > [!TIP] > > Click a row to see where it was read on the PDF page, outlined in amber. Rows read from page images, or from pages that were turned before reading, show their page without an outline. ## Match payments to invoices Money in is matched to your open customer invoices, and money out to your open supplier bills. Each suggestion shows a score and why it was suggested: * **Invoice number:** the invoice number appears in the bank description or reference, with or without separators. * **Exact amount** or **Partial amount:** the payment equals, or is less than, what the invoice still owes. * **Payer name:** the customer or supplier name appears in the bank text. * **Date fits:** the payment date falls around the invoice and due dates. Suggestions marked **Likely** score 80 or more; **Possible** ones score 50 to 79. Duplicate, rejected, fully paid invoices and employee claims are never suggested. For each transaction you can: * **Confirm** a suggestion. The payment is recorded on the invoice, which stops its reminders. * **Reject** a suggestion. That invoice is not suggested for the transaction again. * **Find invoice** to choose an invoice yourself and enter the amount. Use this to split one transfer across several invoices; together they cannot exceed the transaction. * **Ignore** a transaction that pays no invoice, such as bank fees, payroll, or transfers between your accounts. * **Undo** a confirmed match. The payment comes back off the invoice. Use **Refresh suggestions** after you upload new invoices. The statement shows **Done** once every transaction is confirmed or ignored. ## Send payments to your books Once Xero or QuickBooks is connected, **Send payments to books** records each confirmed payment against the invoice in your ledger: 1. Choose the bank account the statement belongs to. Accounts come from your connection's synced chart of accounts. 2. SnapIt sends one payment per confirmed match. Each row shows **Sending to ledger**, **In ledger**, or **Ledger failed** with the reason. Requirements and limits: * Each invoice must already be published to the same books. Publish it first, then send its payment. * Xero only accepts payments on approved invoices. * Xero connections made before payment support was added must be reconnected once in **Settings → Integrations**. * Zoho Books does not receive payments from SnapIt yet. * A payment that is in your ledger cannot be undone in SnapIt; remove it in the ledger first. ## Permissions | Action | Owner | Reviewer | Viewer | | - | - | - | - | | View statements and suggestions | Yes | Yes | Yes | | Upload, review, confirm, and send payments | Yes | Yes | No | | Delete a statement | Yes | No | No | A statement with confirmed payments cannot be reprocessed or deleted until those matches are undone. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.