Review and recovery
Filter and inspect transaction history
Use History filters, inspect before-and-after values and transaction outcomes, and export the complete company audit trail.
On this page
Find the transaction
Open History, or use a holder’s History button or a security form’s View history link to start with a record filter.
| Filter | Enter |
|---|---|
| Record | A record or stakeholder ID. Use a record’s History link to fill this without copying the ID manually. |
| Actor | A name or account ID. |
| Action | An action such as exercise. |
| Transaction | The transaction ID displayed on a History entry. |
| Recorded from / through (UTC) | The entry-time date range, not the transaction’s effective date. |
Choose Apply filters. Use Load more while older history remains available. “No matches on this page” is not a statement that the entire history has no matches; continue loading when the page offers it.
Inspect original values and dates
Choose View changes on an entry. Review the recorded time, actor, explanation, transaction ID, and changed records. Updates show the fields that changed with Before and After values. Creations and deletions show the recorded values.
Expand Full record as JSON when you need the complete stored record. Field names there are data identifiers. The effective date describes when an event applies to the cap table; the recorded time describes when the app recorded the operation. A backfilled issuance can have an earlier effective date than its recorded time.
Read the outcome before interpreting a change
| Outcome | Meaning for review |
|---|---|
| Completed | The recorded operation completed. Inspect its changes for the resulting records. |
| In progress | The operation has not reached a final recorded outcome. |
| Rolling back | Recovery is reversing the attempted changes. |
| Rolled back | The attempted operation was reversed. Its presence does not mean the proposed changes remain applied. |
| Rejected | The operation was refused. Review the explanation before retrying. |
If an operation remains unfinished, follow the app’s recovery prompts and check its outcome before re-entering the transaction. Repeating an operation that completed can duplicate an issuance or import.
Recognize incomplete earlier history
The initial baseline records the first observed state of a company. It does not identify unknown earlier actors or manufacture a transaction trail from current balances. Legacy activity is labeled incomplete.
An imported backup can carry a source history archive. An import entry provides Download source history when that archive is present. Those source events remain evidence from the imported company; they are not newly verified actions in the destination company.
Export the complete history
Export JSON and Export CSV export the entire recorded history, including outcomes and original values, regardless of the current filters. The page states this scope. A filtered view is useful for investigation, but the export is not limited to those visible entries.
Use JSON when retaining the structured archive. If you prepare a smaller extract from the CSV, retain the complete original and label the extract’s selection. History is retained through working-data imports, wipes, and restores within the company. Deleting the company removes its permanent history, so export it first when retention is required.