Recorded cash flows are not locked. You can correct an amount, change the date, recategorize the income, or delete a row entirely. The banking ledger and any linked records stay in sync automatically.
When to Edit vs Delete
Edit when the cash flow happened but you got a field wrong — wrong amount, wrong date, wrong category, or wrong split between buckets.
Delete when the row should not exist at all — a duplicate entry, a payment that bounced and was already reversed elsewhere, or a row recorded against the wrong deployment.
If you're unsure, edit. Deletes are reversible too (you can re-record the cash flow with the correct data), but edits preserve more of the original audit trail.
Editing a Cash Flow
- Open the deployment — navigate to Capital → Assets and click the deployment
- Open the ledger — choose Activity for a general asset or Payment Tracking for a note
- Click the row's menu — the three-dot menu on the right opens the row's actions
- Choose Edit — the Edit Cash Flow dialog opens with all fields prefilled
- Update the values — change the date, total amount, category, or per-bucket amounts as needed
- Save — the row updates, the banking ledger entry is rewritten to match, and any aggregated metrics (income totals, spread, velocity) recompute on next load
What Fields You Can Edit
| Field | What it controls |
|---|---|
| Received date | When the income was received. Affects which period the row counts toward in analytics. |
| Total amount | The combined inflow for this row. |
| Category | One of Rent, Interest, Dividend, or Other. Affects how the row shows up in income charts. |
| Per-bucket split | For three-bucket cash flows (income / return of capital / appreciation), the share for each bucket. The buckets must still sum to the total. |
For three-bucket cash flows, the dialog enforces that the three buckets sum to the total — you cannot save until they balance.
Deleting a Cash Flow
- Open the row's menu — three-dot menu on the cash flow row
- Choose Delete — a confirmation dialog asks you to confirm. If the row came from a note payment, Policy Stack directs you to the note schedule instead.
- Confirm — the row is deleted, the matching banking ledger entry is removed, and the deployment's totals recompute
Standalone cash-flow deletion has no undo. If you delete the wrong row, you re-record it. Note-payment cash flows are corrected from the note schedule, where deleting the payment also returns its schedule row to Scheduled.
What Syncs and What Doesn't
Every recorded cash flow has a matching row in the Banking Ledger. When you edit or delete a cash flow, the ledger entry is updated or removed in the same operation so the two views never disagree.
Synced on edit / delete:
- Banking Ledger entry — amount, date, category, and link to the deployment
- Deployment-level income totals — recomputed on next load
- Income Stacker aggregate — picks up the change on next view
- Analytics charts (income timeline, year-over-year) — recompute from the updated row
Not synced (intentional):
- Note payment status — if the cash flow originated from a recorded note payment, editing the cash flow does not roll back the note payment's status, and direct deletion is refused. Edit or delete the paid row from Asset Workspace → Payment Tracking if the underlying payment was wrong.
- Net worth snapshots — past snapshots are point-in-time records. They reflect what the data looked like at that moment and do not retroactively update when you edit historical cash flows.
If you edit a cash flow that originated from a note payment, the safer path is usually to edit the note payment itself, which cascades the correction into the linked cash flow + ledger entry.
Audit Trail
Edits and deletes are logged in your account's audit history. The cash-flow row itself does not display an "edited" badge in the UI — the change is silent from the user's perspective — but the activity is captured for compliance and traceability.
Cash flows are append-mostly by design. Policy Stack supports edits and deletes because real-world bookkeeping requires it, but the system assumes most rows stay as recorded. Heavy editing of historical cash flows can make trend analytics harder to interpret — the income timeline reflects the corrected values, not the original timing.