Working with Vault and cross-type moves
How the Vault behaves as an operational catch-all and when moving a document type is useful.
Vault is a real document family
Vault records are counted alongside invoice, claim, statement, and supplier items. In the UI they are labeled as Others in some places, but they still behave as a tracked document type with dedicated list and approval pages.
Cross-type moves help repair classification mistakes
Both the general table and approval table expose Change Doc Type actions. That strongly suggests Vault is used not just for storage but also for staging and recategorization.
Keep Vault guidance pragmatic
The useful explanation is when to leave a file as Vault and when to move it into one of the finance-oriented families so downstream approval, payment, and export rules apply correctly.
Continue with adjacent workflows
Uploading and classifying documents
What happens when a file is added, how business scoping works, and where the five document types appear across the product.
Document statuses, approvals, and archives
How list tabs and status mutations are wired, including processing, accurate, approval, and archive transitions.
Using the AI prompt workspace
What the in-product prompt assistant can do, how sessions are stored, and why exports are part of the chat workflow.