A shared cashbook works best when everyone knows what happens after the transactions are entered. Without a review routine, the same questions return each week: has that payment been entered, why does this amount look different, and who needs to follow up?
Keep the review focused on the records and the next action. You do not need a long meeting or a second spreadsheet to start.
Agree on the book and the period
Start by naming the business, book and dates you are reviewing. A cash book and a bank-record book may show different activity. Two people can both be looking at correct totals while talking about different records.
Choose the same period in the app or report. If you need to compare an export with the current screen, confirm that both use the same dates and available filters. Keep a note of the export’s coverage so a later reader can understand it.
Bring recent changes into view
Ask the people who have been entering records to reconnect and review sync status. A transaction saved on an offline phone may not yet be visible to the rest of the team.
Do not treat missing shared activity as proof that it was never entered. Check pending records before entering it again. If sync is not completing, preserve the local records and investigate the issue instead of clearing app storage.
Review exceptions first
Look for records that need an explanation: a duplicate-looking payment, an unexpected amount, a missing note or the wrong person attached to a transaction. The goal is to identify the event behind the number.
Useful questions include:
- Does the payment method match what happened?
- Is this a cash movement or a customer credit record?
- Was a part payment confused with a full settlement?
- Does the transaction belong to the selected business and book?
- Is there a supporting invoice, receipt or reference?
If a record needs correcting, use the authorized editing flow and keep the context understandable. Avoid compensating entries that hide the original mistake without explaining it.
Decide who does what next
Turn each unresolved question into an action with an owner. One person may need to confirm a supplier payment; another may need to share a customer statement. A specific action is easier to finish than “check the accounts.”
Use the app’s available access roles so a teammate has the permissions needed for their work. Reviewing a report and changing a transaction are different responsibilities. Access should reflect the task rather than simply giving everyone the broadest role.
Keep the record of the review small
Save the relevant report if you need a copy of what was reviewed. Note the selected book, dates and unresolved items. A short record of the decision is usually more useful than screenshots of every screen.
For CashKitab’s local and shared-record behavior, read what works offline and what needs internet. For an access or sync problem, contact support before removing any pending work.
