Review, History & Locks

A reviewer may need to ask why an amount changed, identify who changed it, and protect the corrected record. Comments, history and locks support those different jobs.

Investigate the change

A review combines evidence with different records of what happened. A comment records discussion; history records saved changes; workflow logs record processing steps. None replaces the invoice, notice or other support needed to judge whether the saved value is correct.

Start in the app that owns the record. Confirm its table and ID, then use the record's available comments and history controls.

For the saved core example, open Accounting Operations → Journal Entries, select Cedarbridge Example Fund LP and Q3 2026, and select the checkbox for Journal Entry #1. The floating actions include View change history for selected record and View comments for selected record. Change history opens the record side panel with History, Documents, Emails and Comments tabs. Use these actions for the selected record; other tables or reports may not provide them. For a hypothetical expense whose amount changed from USD1,000 to USD1,200, compare the invoice with the saved amount before deciding whether the change is wrong.

Use a comment to ask about the difference and identify the supporting invoice or reason. A resolved comment means the discussion was closed; it does not prove the expense was corrected or reconciled.

Use record history, where available, to inspect saved changes, their author and captured source. History can establish that a field changed. It does not establish that the new amount agrees with the invoice.

If a configured workflow made the change, inspect that run's logs for its steps and results. A failed update step calls for a different investigation from a successful update based on the wrong source input. Then re-open the expense to confirm what was actually saved.

Protect the reviewed record

After the amount, evidence and affected checks agree, an admin can lock the record to prevent supported ordinary edits. Use Data Locks for lock visibility and the owning record for its details. Its FundOps and Accounting tabs list eligible unlocked records; an already locked record will not appear in those queues.

If a protected record needs a correction, an admin must unlock it first. Record the reason, correct the existing record, rerun the affected checks and review the result before locking it again. An unlocked record can begin with the correction.

Know what the result establishes

View/Edit mode changes the interface's editing controls. A record lock protects a saved row. Neither action closes an accounting period.

A clean reconciliation checks the relationships and amounts in its scope. Accounting close has its own period-level process. Use Accounting Review & Close when the question is whether the books are ready to close.

Comments, history and workflow logs appear only on surfaces that support them. If the expected control is absent, check the source record in its owning table or ask an administrator with the exact table and ID; do not infer a review result from the control's absence.