Operations overview

Operations Overview brings the petty cash operating signals into one page. The finance team can see posted document value, net ledger balance, pending review decisions and failed operations. Posted debit and credit totals are grouped by posting month. Unposted document counts are grouped by document type, and an exception queue can be filtered when the team needs to focus on a particular issue.

Use the overview to choose the next record to inspect. A pending review count points the Accounting Reviewer to documents waiting for a decision. A failed operation points to its operation receipt and failure reason. A posted total can be traced through accounting documents and journal lines. The overview gives a starting point for investigation; the underlying records supply the explanation.

• See posted activity. Compare posted document value with debit and credit totals for the selected posting month.
• Find unfinished work. Read unposted documents by type and pending review decisions before moving the cycle forward.
• Investigate exceptions. Filter the exception queue, then open the operation receipt and its parent document.

The same screen serves different questions. The Accounting Preparer checks what source work remains. The Accounting Reviewer looks for decisions and mismatched effects. An Auditor can move from a total to the source records that support it. Keep the review conversation anchored to a document or operation key rather than a number alone.

Choose a daily owner for the pending decision queue and another for operation exceptions if those responsibilities are split. Agree when the team compares the net ledger balance with the petty cash balance it expects. Define how an exception is assigned and what evidence must be checked before it is marked resolved. These routines make the overview actionable in an operating cycle.

Set the organization’s posting calendar before interpreting monthly totals. A late posting date may place a document in a different month from its document date or spend date. When someone questions a monthly number, open the journal and source document rather than assuming those dates are interchangeable.

Start with a small purchase whose accounting document has been approved and posted. Ask the reviewer to locate its posted value and the related debit and credit month. Then inspect a Submitted voucher and a document in Review; they should prompt separate decisions. Add a failed operation case and use its operation key, parent and failure reason to find the attempted effect. The team should be able to say whether the action completed, needs correction or needs further review.

Repeat the exercise with an unposted expense document. The dashboard’s unposted group should lead the preparer to the source record, its lines and any missing review decision. This confirms that the team can move from summary to work item.

• Operations Overview — Posted value, ledger balance, review work and filtered exceptions in one operating screen.
• Operations Needing Attention — Failed and needs-review actions with a concrete reason.
• Documents Awaiting Review — Source documents waiting for the independent accounting decision.

Continue with document approval and reconciliation.