Finance Documents
Browse, search and export every finance document in Muin, such as every bank statement from last quarter, filter by type, status, tag and date, and understand how a document attaches to a transaction.
Finance Documents is the explorer over every financial document in your workspace, with the filters you need to find one and the export you need to hand a list to somebody else.
When you’d use this
- An auditor asks for every bank statement in a date range.
- You want the invoices tagged for one project, as a spreadsheet.
- You need to compare two contracts or two statements side by side.
- A number in Spend Analytics needs checking against the source document.
Find a document
- Open Finance Documents at
/finance/documents. It has no sidebar entry of its own: reach it from a Spend Analytics drill-down, or from the Documents module filtered to finance. - The screen opens pre-filtered to the finance document types: invoices, purchase orders, expense reports and bank statements.
- Narrow it:
- The search box takes a filename, or a
tag:valuepair. - From date and To date limit the range.
- Type:, Status: and Tags: chips toggle on and off. Clear Filters resets them.
- Field Filters filters on the fields extracted from the documents themselves, with a count badge and Clear all.
- The search box takes a filename, or a
- The table shows Filename · Type · Status · Created · Updated by default, 50 rows a page, newest first. Use the column picker to add any extracted field as a column.
- Click a row to preview it. Double-click to open the full document.
Export or compare
- Export offers CSV and Excel. The download arrives as
documents_export.csvor.xlsx. - Select two or more rows and Compare & Synthesize appears. It reads the selected documents together and answers questions across them.
How a document attaches to a transaction
Two mechanisms, and which one applies depends on the transaction:
- A direct link on the transaction. An expense carries its receipt document, a purchase order carries its document. Attach these from the transaction, not from this screen.
- A general attachment link. Any document can be linked to any record, with a relationship type of attachment, reference, version or supporting, a description, and a primary flag.
The document itself does not carry a transaction id. The link always lives on the transaction or in the link record, which is why you attach from the transaction’s own screen.
What it affects
- Nothing on this screen changes a transaction. It finds, previews and exports.
- What a document’s extracted fields say does affect Spend Analytics, which reads amounts and categories from them.
- Changing a document’s status moves it between the Status: chips here and in the aging buckets.
When it goes wrong
| What you see | What it means | How to clear it |
|---|---|---|
| “Unable to load documents” / “The document list could not be loaded. Retry, or check back shortly.” | The document service did not answer. | Click Retry. |
| “No documents found” in the table | Your filters exclude everything. | Clear the type, status, tag and date filters, then narrow again one at a time. |
| An export that never downloads | The export failed. There is no toast for this, so the only sign is nothing arriving. | Narrow the filters to a smaller set and export again. |
| “Session expired. Please log in again.” | Your session ended mid-export. | Sign in again and re-run the export. |
| A document with no extracted-field columns | That document type has no extraction schema, so there is nothing to show beyond the standard columns. | Use the standard columns; the file itself is still there. |
Next step
- Spend Analytics: the charts built from these documents.
- Bills: the transaction a vendor invoice becomes.
- General Ledger and Journal Entries, where the posted side lives.