Documents connected to the transaction they explain.
A financial document workflow is complete only when an authorised reviewer can move from a transaction row to its source, understand what was confirmed and see what remains unresolved. Storage, recognition and review are separate steps in that chain.
Written by the Fundamental View editorial team. Updated 28 October 2026. All examples are fictional; no client transaction or public evidence file is used.
From document to reviewed record
- Add the transaction. Use the configured personal interface or enter a record manually. Required fields and supported formats are agreed during implementation.
- Prepare the document for recognition. Names, account numbers and other identifiers are masked before the document reaches the recognition model. Inspect the actual configured data flow rather than treating masking as a universal guarantee of anonymity.
- Check extracted details. The model helps prepare an entry from a PDF or image. A person checks amount, date, counterparty and required context before saving. Unclear information remains a review task.
- Keep the source connected. Store the supporting file in the configured Google Drive structure and link it to the register entry using the record identifier.
- Retrieve and review. Return from the register to the source, check what was recorded and identify remaining exceptions.
Your documents stay in the agreed workspace
The register and evidence live in the client's own Google Workspace. Fundamental View is the tool used to keep them in order, not the place where the operational record is held. Access ownership, support access, retention and exit still need explicit configuration and responsibilities; client-owned storage alone does not make every access path safe.
What a useful record connects
| Field | Illustrative value | What the reviewer checks |
|---|---|---|
| Record ID | EXAMPLE-2026-0001 | The same identifier is used in the record and filename |
| Entity | Example Holding A | The source belongs to the intended structure |
| Date | 14 September 2026 | The field's date meaning is defined |
| Amount | 1,250.00 EUR | Original amount and currency match the source |
| Document | EXAMPLE-2026-0001-invoice.pdf | The reference opens for an authorised reviewer |
| Review state | Confirmed in this illustration | A person, not recognition alone, completed confirmation |
| Evidence location | Private folder reference | No public share link is required |
Define exceptions before connecting the tools
| Exception | Do not do | Useful operational response |
|---|---|---|
| Unreadable page | Guess missing values | Request a readable source and keep the entry unconfirmed |
| Missing required field | Insert a plausible default | Record the gap and its owner |
| Repeated submission | Create another transaction automatically | Check the stable ID and source relationship |
| One document, several entries | Duplicate files without context | Link each relevant row while preserving one source relationship |
| Correction after confirmation | Overwrite without an agreed history | Follow the configured correction and review process |
Test retrieval with someone who did not enter the record
Ask another authorised person to start with the register row. Without asking the original operator, can they identify the entity, amount, date meaning, evidence and unresolved questions? Then verify that an unauthorised test account cannot open the same source. A workflow that stores every file but fails either retrieval or access control is incomplete.
When this workflow is useful—and when it may not be
It is relevant when documents arrive through several channels, evidence is stored separately from entries, or reporting repeatedly requires reconstructing context. If a consistent internal procedure already provides reliable retrieval and review, a smaller process change may be sufficient. The reviewed operational record does not establish investment performance, tax treatment or completeness of formal accounts.
How Fundamental View fits
Fundamental View combines personal intake, anonymised document recognition, human confirmation, Google Drive evidence and a structured register in the client's Workspace. Direct bank and custodian feeds are not in the first version. Required document types, exception handling and support boundaries are agreed for the implementation.
Related guides
- Define the record and its review states
- Map data handling and access responsibilities
- Test AI confidentiality claims
- Run an evidence retrieval check
- Prepare implementation and acceptance cases
Discuss your workflow
Describe the record-keeping problem you want to solve. Please do not include confidential financial information or documents in the enquiry.
Discuss implementation