Locks
A reviewed period depends on records that can change: configuration, journals, capital movements, valuations and fee outputs. Row locks protect particular records under the organization's change-control process. They preserve a state after the relevant review; they do not determine whether that state is correct.
Open Accounting → Accounting Review & Close → Locks to inspect scoped Accounting and Fees records without an active lock. An unlocked record may be appropriate while work continues. A locked Draft would remain proposed accounting, and a Closed period and row-level locks remain distinct controls.
Match the scope
Choose Entity and its Accounting Period. The table lists records without an active row lock; it is not a list of every locked and unlocked record or a register of reviewer approval.
The scoped unlocked grid contains six Accounting records: two GL accounts, the accounting period, Draft journal #1 and its two lines. Accounting, GL Accounts and Journal Lines are expanded. No record was locked or unlocked.
Expand to the actual record
Lock scope follows dependencies as well as transaction dates. A setup account or effective-dated rule can affect period accounting even if it was created earlier; a line depends on its journal and assigned book. Identify the exact owning table and record before considering a lock action, because a grouped count is only a summary of that displayed population.
The grid groups Group → Table → Record and sums Rows within the displayed population. A single-record group can display the record directly. Read Table, Record, Date and Last Edited together. The same numeric ID in another table identifies something else. A consolidated single-record row may not display its table label; confirm the owning table in Accounting Operations or consolidated Data Locks before acting.
The scope is broader than records created during the period:
- GL accounts are entity-scoped setup records without a transaction date.
- Periods, capital accounts and effective-dated rules/terms can be included when their dates overlap the review window. Default posting rules can also apply.
- Journals and their lines can follow the entry date or an overlapping assigned period.
- Valuations, capital transactions and allocation outputs use their respective operational/as-of dates.
- Fee batches, runs and lines follow their applicable period/date and entity relationships.
The scoped table covers Accounting and Fees. It does not replace the consolidated FundOps and other record visibility in Fund Organization → Data Locks.
Use the consolidated view when needed
Select Open consolidated Data Locks in the header to inspect broader Accounting lock visibility. It carries the selected entity and period date window into the installed Data Locks app. Recheck the destination scope after following the link.
Checkboxes select records where row selection is available. Selection alone does not lock them, post journals or close the period. Check whether an explicit Lock selected rows action is available before expecting a lock operation.
Only an authorized user should use an available lock/unlock workflow under the organization's policy. Before a state change, confirm the exact table/record, reason and accounting implications; verify the persisted result afterward.
Investigate an unexpected result
If a record is absent, check the entity, date basis, parent relationship and actual lock state in consolidated Data Locks. If it is unexpectedly read-only, distinguish row locks, period restrictions and role permissions. Ask the responsible owner to resolve the specific issue rather than unlocking broad groups as a workaround.
An empty scoped unlocked table does not prove every fund record is locked, all checks pass, the period is closed or a reviewer approved the close. Conversely, an unlocked record can be perfectly valid during an open review period.
The fictional Draft journal is useful for identifying the distinction: locking it would not turn it into Posted accounting or resolve a source-recognition blocker.