Tie out
Sub-ledgers agreed to the general ledger, with the differences named rather than discovered at review.
Flowwiz / Month-end closeClose on time, with
[The close]
Close on time, with
the reasons written down.
Close is where receivables, payables, and reconciliation have to agree. The exceptions agents already found are the ones that hold it up.
Clear the exceptions
Unapplied cash, disputed invoices, and unvalidated bills surfaced as close blockers, not surprises.
Sign off with the reasons
A reviewer checklist with owners and blockers, so the audit trail explains the month.
Close workflow
Five steps from sub-ledger to sign-off.
Every step is a check your team already performs. The difference is that the state is read from the records rather than reconstructed at period end.
- 01Tie out
AR and AP sub-ledgers agreed to the general ledger, with reconciling items listed.
- 02Reconcile
Every bank account matched, unapplied cash cleared or explained.
- 03Accrue
Accruals and prepayments posted from the same invoice and contract context used during the month.
- 04Explain
Flux analysis written from the movements behind it, not reverse-engineered afterwards.
- 05Sign off
Reviewer checklist with owners, blocking items, and a complete audit trail.
Close · March18 of 25
✓Bank reconciliation · all 4 accountsTreasuryDone
✓AR sub-ledger tied to GLARDone
✓AP sub-ledger tied to GLAPDone
!Unapplied cash: $9,200 awaiting allocationARBlocked
!Harbour Freight rate variance: needs a decisionAPBlocked
·Accruals and prepayments postedControllerIn progress
·Intercompany balances agreedControllerIn progress
·Flux analysis: revenue and operating costFP&ANot started
·Reviewer sign-offControllerNot started
What blocks a close
It is never one large thing.
Close slips on a hundred small items, and most of them were already visible during the month. The difference is whether anyone was holding them.
Receivables side
- Unapplied cash awaiting allocation
- Disputed invoices not yet resolved
- Short payments left open
- Credit notes not issued
- Promises to pay that have lapsed
Payables side
- Bills awaiting approval
- Rate or term variances unresolved
- Goods received not invoiced
- Accruals not yet posted
- Duplicate bills under review
Review
Everything a reviewer needs, on one screen.
A reviewer should not have to ask what changed. The movements, the exceptions, and the decision behind each one are already recorded.
- 01Movement
The balance and the change from the prior period.
- 02Reason
The transactions and events that produced it.
- 03Exception
Anything unresolved, with its owner and age.
- 04Decision
What was decided, by whom, and when.
- 05Record
Posted to the audit trail with the rest of the month.
Coverage
What close draws on.
Close does not need a separate set of records. It reads the state of everything the other workflows have been maintaining all month.
- 01Sub-ledger to GL tie-out
- 02Bank account reconciliation
- 03Unapplied cash identification
- 04Accrual and prepayment posting
- 05Intercompany balance agreement
- 06Flux analysis with underlying movements
- 07Close checklist with owners
- 08Blocking item escalation
- 09Reviewer sign-off workflow
- 10Journal entry preparation
- 11GL coding exception routing
- 12Period-lock and audit trail
FAQ
Before you go further.
Does Flowwiz replace our close checklist?
No. It keeps the checklist honest. Every item is backed by the actual state of the records rather than someone’s recollection of whether it was done.
How does close relate to the other workflows?
It reads their state. Unapplied cash comes from reconciliation, disputed invoices from collections, unvalidated bills from payables. Close is where those threads are checked against each other.
Can we keep our own close calendar?
Yes. Milestones, owners, and dependencies are configured around the calendar you already run.
Does it post journal entries?
It prepares entries and posts them into your accounting system through the integration, subject to the approval rules you set.
How does flux analysis get written?
From the transactions behind the movement, so the explanation cites what actually changed rather than being drafted from the two numbers.
What happens if an item cannot be resolved in time?
It stays on the checklist as an open blocker with an owner and an age, so it is a decision rather than an omission.
Start
See it with your team’s context.
Bring your workflow, your systems, and who approves what.