Locking Periods

Locking Periods in Bitwave

Ensuring the integrity and accuracy of financial transactions is paramount in any accounting system. In Bitwave, one way to safeguard transaction records is by implementing period locking. This feature allows users to restrict modifications to transactions within a specified period, providing a safeguard against accidental deleting or ignoring transactions.Once transactions are locked, you cannot alter them, and no new transactions will sync into Bitwave during the locked period.

Let's explore how to lock a period in Bitwave:

How to lock a period:
● Navigate to Accounting: Begin by accessing the accounting section located on the right-hand side of the application.

● Locate “Period End Close”

● Click on Enable Transaction Locking

● Set Lock Date: Specify the end date for the period you wish to lock. For example, if you intend to
lock transactions up to December 31, 2023, enter this date accordingly.

● Save Changes: After entering the desired lock date, click "Save" to apply the changes.

● Confirm Locking: To confirm that transactions are successfully locked, navigate to the transaction overview. Locked transactions will be indicated by a small lock icon next to them.

Period locking often aligns with the closing of accounting periods, ensuring that financial data remains static for reporting purposes

Unlocking and Modifying Period Locks:

Should the need arise to unlock a period or modify the lock date, users can easily manage these settings within the
Bitwave platform:

● Navigate to Accounting: Begin by accessing the accounting section located on the right-hand side of the application.

● Locate “Period End Close”

● Click Unlock All

● Click “Confirm” to Unlock transactions

● Editing Lock Date:

Similarly, users can edit the lock date by accessing the period close settings and adjusting the specified date as needed. Remember to save changes after editing the lock date.

Note that transactions with uncategorized or unignored statuses cannot be locked in Bitwave. Ensure all transactions are appropriately categorized or ignored before implementing period locks.