Month-end & advisory
Two surfaces close out your month and tell you what to do next. Monthly Close runs the whole period-end routine in one click — checks readiness, computes and posts the adjusting entries, then locks the month so nothing can be backdated into it. Virtual CA is the advisor that sits on top: a ranked feed of what needs you, merging exceptions, deadlines and a risk band. Close first, then work the feed.
Monthly Close — one click to a sealed month
/dashboard/monthly-closeturns the period-end checklist into a single guided action. You pick a month (it defaults to last month), run it, review what it proposes, then commit. The orchestration is real double-entry: every adjustment it books lands in your ledger and shows up in the Trial Balance, P&L and Balance Sheet.
- Readiness check — a set of checks runs across bank reconciliation, unposted drafts, GST and other categories. Each returns
pass,warnorblock, with a one-line reason and a link to fix it. - Proposed adjustments — OnGravy computes the period-end entries automatically: depreciation on your fixed assets, accruals from recurring templates, prepayment amortization, and a tax provision on the period’s taxable income. Each proposed entry shows its amount and a confidence score.
- Preview vs commit — Preview runs the checks and shows the proposed entries without writing anything. Commit posts the adjusting entries and then locks the period. Nothing is written until you commit.
- Blockers gate the close — if any check is a
block, the close is refused with the reason. You can clear the blocker and re-run, or deliberately override to close anyway. Overriding is an explicit choice, never the default. - Lock the period — on a clean commit, the month is locked: a trial-balance snapshot is hashed and Merkle-sealed so the closed state is tamper-evident.
| Auto-computed entry | What it books |
|---|---|
| Depreciation | Periodic depreciation on the fixed-asset register |
| Accruals | Period-end accruals from your recurring templates |
| Prepayment amortization | The month’s slice of tracked prepayments |
| Tax provision | A provision on the period’s taxable income |
The lock is what makes month-end stick. Once a month is locked, OnGravy will not accept a backdated posting into it — a journal dated inside a locked period is refused. That is the whole point of closing: the numbers you reported stop moving underneath you. To post into a closed month you must reopen it first, which is itself an audited action. See Teams & permissions for how period locks and the audit trail work together.
Re-running a close on an already-locked month is refused cleanly (with a “reopen it to re-run” message) rather than double-posting.
Virtual CA — a ranked “what needs you” feed
/dashboard/virtual-ca is your proactive advisor. It reads your live books and merges three signals into one prioritised list:
- Exception findings — anomalies and unresolved items from the exception engine.
- Compliance deadlines — what’s due, from the compliance calendar.
- A scrutiny risk band — a Low / Medium / High read on how your books would look under scrutiny.
The top of the page is a headline plus an urgent count, the risk band, and a books-closed indicator that tells you whether the current period has been closed. Below it, items are ranked by severity (Critical → High → Medium → Low), each with a short explanation and an action link that takes you straight to the place to resolve it.
Virtual CA is advisory. It surfaces and links — it does not post entries, file returns or act on your behalf. You (or your CA) take the action from the link. It is the “what should I do?” layer; the doing still runs through the same review and approval flow as everywhere else in OnGravy.
How the two fit together
A typical month-end: open Virtual CA to see whether the books are closed and what’s outstanding, clear the exceptions it flags, then run Monthly Close to post the period-end adjustments and lock the month. The close’s readiness check and Virtual CA’s feed overlap on purpose — both point you at the same loose ends before you seal the period.
Gotchas & good to know
- Preview writes nothing. Only Commit posts the adjusting entries and locks the month.
- A blocker stops the close unless you override — and override is a deliberate, visible choice.
- A locked month rejects backdated postings. If a journal into a past month is refused, the period is closed — reopen it to post.
- Auto-adjustments need their inputs. No fixed assets means no depreciation entry; no tracked prepayments means no amortization. The coverage summary tells you what it found.
- Virtual CA never acts for you. Empty feed means nothing needs you right now; it does not mean anything was auto-resolved.