Daily Cash Flow Records for Teams and Business Managers

A supplier invoice for Rp4,800,000 is due tomorrow, but the spreadsheet balance is Rp650,000 higher than the bank statement. The staff member who handled cash has not turned in a purchase receipt, while the manager assumes a customer paid an invoice in full. The payment decision stalls because the record does not show who received or paid the money, when it happened, what it was for, or which evidence supports it.

Daily cash flow records capture money that actually enters or leaves an organization on the date it happens, then reconcile the record with physical cash, bank accounts, or digital wallets. This guide helps owners, managers and teams establish a routine, separate business transactions from internal transfers, and investigate differences before they spread across reports. Bank Indonesia’s transaction-recording guidance for micro and small businesses includes technical guides and training modules. The examples here show how to make records traceable across people and accounts; adapt fields to your organization’s policies.

Give every team one record to update

When sales keeps one spreadsheet, a cashier uses a notebook, and a project manager saves receipts in chat, the end-of-day summary depends on memory. Choose one master cash book, whether it is a shared spreadsheet or a centralized record. Staff can submit evidence through an agreed channel, while a named owner enters or checks each transaction in the master record.

Use a unique reference such as CASH-261101-001. Useful columns include date, reference, description, category, account, money in, money out, payment method, counterparty, evidence reference, recorder and review status. Keep categories stable. A team that labels the same transport cost as “fuel,” “travel” and “vehicle” cannot compare like with like without cleaning the data later.

Date	Description	Account	In	Out	Evidence	Reviewer
Nov 1	Payment for invoice INV-104	Bank	Rp2,400,000	-	TRF-881	Pending
Nov 1	Packaging purchase	Petty cash	-	Rp185,000	RCP-223	Pending
Nov 1	Deposit cash to bank	Shop cash/Bank	Rp0 net	Rp0 net	SLIP-09	Pending

The last line is a transfer between accounts, not new income or a new expense. Record both sides so each account remains traceable; in a combined report, the entries cancel out. If the spreadsheet cannot pair transactions, mark both lines “internal transfer” and use the same reference.

Record the date money actually moves

An issued invoice is not proof of payment. Record a receipt when funds arrive, then link it to the invoice or order, date received, amount, payment method and remaining balance. A manager can review cash on hand without mistaking orders or sales targets for funds already available.

For example, a customer pays Rp1,500,000 against a Rp2,000,000 invoice on November 1. Record Rp1,500,000 received and Rp500,000 outstanding in the receivables list. An advance received today for work next month belongs in today’s cash record, with a description that identifies it as an advance.

For expenses, use the actual payment date and retain the obligation’s context. An approved purchase order that has not been paid is not a cash outflow today; list it separately with its due date. When payment happens, connect the cash entry to the purchase order, supplier invoice, recipient and authorization. This gives the approver a trail to check and helps the team avoid paying one invoice twice when supplier names differ across records.

Separate owner contributions, loans, loan repayments and owner withdrawals from sales or operating expenses. Each affects the balance but describes a different movement. An operational cash book can help a team track movements; it does not automatically replace formal financial statements or settle tax obligations.

Close each account and assign follow-up

Set a closing time after the last transaction. The cashier counts physical money and compares it with the opening balance plus cash received minus cash paid. A second person can review evidence and corrections. For bank accounts, compare the record with the statement and mark processing payments as pending until the evidence confirms settlement.

Use a consistent close: confirm today’s entries are in the master record; check each line for a description and evidence or an evidence-pending reason; count cash and compare bank balances for the same date; then assign each unmatched item to a person with a follow-up date. If the cause becomes clear, add a correction with a change trail instead of erasing the earlier number.

Suppose petty cash starts at Rp1,000,000, receives Rp650,000 and pays Rp425,000 supported by receipts. The book balance is Rp1,225,000. If the physical count is Rp1,175,000, the Rp50,000 difference is not automatically an expense. Check for an unrecorded receipt, counting error, duplicate entry or cash not yet handed over. Record what the review establishes, not a guess.

Make the summary useful to decision-makers

A daily summary can show opening balance, money in and out by category, closing balance by account, unmatched transactions and obligations due soon. Keep cash available separate from customer invoices that have not been paid. The owner can then review whether a supplier payment fits the cash position rather than relying on sales volume alone.

Each week, compare planned payments with expected incoming funds. Label the basis of each estimate: a customer payment confirmed by a bank record differs from a sales target. Review recurring costs, entries without evidence and vague descriptions such as “operations.” Give each follow-up an owner, due date and status so a finance lead can see which unresolved items affect a decision.

Common mistakes include waiting for every receipt before recording transactions, using a personal account without labeling it, counting internal transfers as income and silently changing old figures. Set a rule for late evidence: enter the transaction as pending, assign a person and deadline, then complete the trail. Use statements and documents to reconstruct older entries rather than relying on memory.

Bank Indonesia’s PTK material describes transaction records and financial statements for micro and small businesses. For a team looking at a structured starting point, the Business Cash Book app page describes transaction categories, account transfers, owner drawings and payable/receivable records. Sora’s business application page explains creating work applications from a described workflow, with roles, branches, approvals and reports. Compare those public capabilities with your team’s needs. For more process guidance, browse Sora’s articles.

Test the routine with one account today

Choose one account, such as petty cash. Write down its opening balance, enter today’s transactions with evidence references, count the physical money and assign each difference to someone for investigation. Leave an unmatched item visible until evidence explains it; do not change a figure just to make the totals agree.

At the next close, use the same fields and compare how quickly the team can trace one transaction. Adjust the categories or handoff rule if staff cannot tell who records a payment or who checks its evidence.