Compliance
Source tracing and audit trails for financial analysis
Trace source-linked figures to original document lines. Review recorded edits, report finalizations, reopenings, and access activity.
Source tracing gives reviewers the original document evidence behind a financial figure. An audit trail records the people, changes, and report events around the analysis.
In SpreadSpace, reviewers can follow a source-linked figure to its supporting line, inspect recorded changes, and see when a report was finalized or reopened for further work.
Start with the line that supports the number
A total on its own cannot explain its origin. In SpreadSpace, source-linked figures open the supporting document at the relevant line on the original page. For derived figures, reviewers can examine contributing detail and follow the linked inputs back to their evidence.
That connection carries into financial spreading, the in-app spreadsheet, and report exhibits. When an income statement is mapped to your chart of accounts, the original reported lines remain part of the review. A familiar account label does not have to separate the analysis from its source.
See who changed the financial analysis
Recorded edits to extracted financial values identify the responsible user, the time, and the before-and-after values. A later reviewer can inspect the change in the activity history and return to the source document to understand the basis for the analysis.
Authorized reviewers can examine activity in the relevant record. Organization audit reporting also supports searching, date filters, and CSV export, so a review can focus on a person, period, or event. Access to that history follows workspace permissions and record access.
Track report finalization and reopening
Finalizing a report is an explicit action. It locks the report against editing and records who finalized it and when. Finalized spreads have their own approved snapshots, keeping the approved financial data distinct from work in progress.
Reopening a finalized report for editing is also explicit. It records the responsible user and time, unlocks the report, and advances its version while retaining the previous final PDF. If someone returns later to revise the report, the reopening is part of its recorded history.
Viewing a finalized report and reopening it for editing are different events. Closing a browser tab does not finalize a report and is not recorded as a report-close event. Reviewers use the report’s lifecycle history to establish whether it remained finalized or went back into revision.
Review report activity
Recorded report activity includes views of finalized reports, downloads, and printing, alongside creation, updates, finalization, and reopening. That gives authorized reviewers a way to examine how a report was prepared and used after the initial analysis.
Repeated views and routine autosaves may be grouped into a single activity entry. Report-view tracking applies to finalized reports associated with a record; opening a draft or a reusable company template is not the same event. The activity history provides context for review without implying that every click or browser-tab movement is recorded.
Keep the audit context inside your workflow
The spreadsheet, source-document review, and report workspace can be embedded inside your own application. Analysts and reviewers can follow the evidence and work through the report while staying in the system they already use.
Your integration can subscribe to report finalization and reopening events through webhooks, so your backend can distinguish the approved record from work that is under revision. Recorded history is available for review; integrations can use those events to drive their own workflow and notifications.
Make the next review easier to follow
Bring a financial report and the questions a later reviewer would need to answer. Follow a source-linked figure to its supporting line, examine a recorded edit, and review the history of finalization and reopening.