> ## Documentation Index > Fetch the complete documentation index at: https://control-dev.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Open invoice documents > See the invoice PDF, image, or attachment behind a transaction in Control, and let an AI client read it. Control stores the documents your accounting system keeps for an invoice: the invoice image, the supplier's original PDF, and attachments such as receipts or Finvoice XML. You can open them from a transaction, from invoice analytics, and from chat, and an AI client can read their text. You no longer need to sign in to the accounting system to check what a posting was for. ## Availability Invoice documents are available in every workspace. They come from data sources that expose them: | Data source | Documents stored | | - | - | | Procountor | Invoice images and attachments of sales invoices, purchase invoices, travel invoices, and bills of charges | | Netvisor | Sales invoice PDFs; purchase invoice images and attachments | | Easor | Sales invoice PDFs, with the attachments Easor merges into them | Documents load when **Store Invoice Documents** is on for the data source, which is the default, and the matching invoice load is enabled. Invoices on accounts you mask in Procountor are never stored. Documents stay in Control's own storage after the first load; Control does not fetch them from the accounting system each time you open one. ## Open a document in Control * **Transactions:** a paperclip before the receipt description marks a receipt with stored documents. Select it to open the **Documents** pane on the right of the [**Transactions**](https://app.control.dev/financial-statements/transactions) (Financial statements → Transactions) view. The pane shows the receipt's counterparty, date, amount, and entity, lists its documents, and shows the selected one full height. It follows the row you focus, so moving down the grid moves to the next receipt's documents. The same pane opens from a statement drilldown. * **Receipt dialog:** right-click a transaction and choose **Show receipt**. A **Documents** strip lists the receipt's files. With nothing stored it says **No documents from** the source system. * **Invoice analytics:** the invoice detail sheet shows a **Documents** section under the invoice details, with the PDF inline. * **Chat:** when an answer refers to an invoice, the document appears as a chip that opens the same viewer. Select **Download** to save the file. PDFs and images open inline; other file types download. A purchase e-invoice often arrives with both the supplier's PDF and the accounting system's rendering of it. Control shows it once as **Invoice PDF (from supplier)**, with a toggle to show the accounting system's image instead. ## Read a document through an AI client Documents are part of the MCP server, so an AI client connected to Control can answer "what was this charge for" from the document itself. | Tool | What it does | | - | - | | `get_uniform_invoice_documents` | Lists invoices one row per document, with status, counterparty, and amounts. Its `source_document_id` identifies the invoice to the tools below | | `list_invoice_documents` | Lists the stored files of one invoice or one receipt: kind, file name, type, size, and page count, plus a `viewerUrl` that opens them in Control | | `read_invoice_document` | Returns one page of a document's text: the text layer of a PDF, or the content of XML, CSV, XLSX, JSON, and text attachments | When you ask the assistant to show or download an invoice, it gives you the `viewerUrl`. The link opens the receipt's **Documents** pane after you sign in to Control. A scanned invoice or an invoice image has no text layer. Clients that can show images, such as Claude Desktop, receive the page as an image; Control chat and workspace agents receive text only and point you to the document in Control. An empty list is not always missing data. The tool's `hint` says whether the entity has any stored documents at all, whether the invoice load is enabled, and which identifier to pass instead. ## Access and audit * Anyone who can open the entity's transactions can open its documents. A document from another workspace, or a guessed link, is not found. * Every time a document's content or text is read, Control records who read it, when, and through which channel: the user interface, an AI client, or a workspace agent. * Document text is evidence from the accounting system. The assistant treats it as data, never as instructions. ## Troubleshooting | Problem | What to check | | - | - | | No paperclip on a transaction | The receipt may have no documents in the source, the invoice load may be off, or the account is masked. Open **Show receipt** to confirm | | **No documents from** the source system | Turn on **Store Invoice Documents** and the invoice load for the data source, then wait for the next sync | | The assistant says the document is unreadable | The PDF is a scan without a text layer. Open the `viewerUrl` in Control, or ask a client that can show images | | The PDF shows as a download instead of inline | Your browser has no PDF viewer. Download the file and open it locally | ## Related content * [Investigate transactions](https://control-dev.mintlify.site/product-docs/transactions/investigate-transactions.md) * [Connect Procountor](https://control-dev.mintlify.site/product-docs/integrations/procountor.md) * [Connect Netvisor](https://control-dev.mintlify.site/product-docs/integrations/netvisor.md) * [Connect Easor by Talenom](https://control-dev.mintlify.site/product-docs/integrations/easor.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.