A formal period-close/lock feature — freezing a month or year so it can't be edited — isn't available yet.
What this means in practice
Without a hard lock, nothing technically stops a backdated entry from landing in a period you've already closed and reported on. That's a real gap if your business needs a strict, enforced close — but it's also why the activity log matters more here than it would in a system with locking: every change is timestamped and attributed, so even without prevention, you have detection.
Working around it today
- Finish reconciling the period and run your trial balance before treating it as closed.
- Export the reports you rely on (P&L, balance sheet) once you consider the period closed, so you have a snapshot independent of any later edit.
- Agree internally that nobody backdates entries into a closed period without flagging it — a convention, since the system won't enforce it for you yet.
- Check the activity log periodically for entries dated into periods you've already reported on.
⚠️Note: Every transaction is still timestamped and kept in the activity log, so any change made after the fact is traceable even without a hard lock. If a formal period-close matters for how your business reports — a board, an auditor, a lender — let support know; it helps prioritise what gets built next.