Month-End Close
Clears the accounts that reconcile at month end and writes the first draft of the close narrative.
The close is the same work in the same order every month, and the part that takes the time is not the judgement but the clearing. The concept reads the exports it is given, clears the lines that reconcile, sets aside the differences it cannot account for, and drafts the narrative in the shape last month's was written in. The judgement stays with the accountant, who would get a draft instead of a blank page. None of it is built yet.
Availability
In Development. Specified, and not built. The run below is the shape the job would take, not a recording of one. Nothing of it runs today, so it cannot be subscribed to and carries no price.
Intended user
A financial controller or an accountant running the same close in the same order every month.
Monthly price
Not purchasable. No price, and no subscribe button until it runs.
Nothing here runs yet, so there is no Subscribe and no Run on this page. Asking for it is what decides which of the five gets built first, and a close variation of it can be quoted as a custom build today.
What this is not.
The corrections worth making before anything else on this page is read, because each one is a thing a reader could reasonably assume and would be wrong about.
- No bank feed and no ledger connector. Neither exists, neither has been agreed with any provider, and reading an export is not the same thing as a live connection.
- No audit assurance. A difference an agent set aside is a prompt for an accountant, not an opinion, and nothing here is evidence to an auditor.
- No measured timing. Nothing has run, so no duration for this work is published anywhere on this site.
- The accountant posts the close. The draft waits until somebody says so.
How the job would go.
Four steps, in order, ending where it stops. No timing is published for any of them: nothing has run, so there is nothing to measure, and a written duration shown as a measurement would be an invention.
Month-End Close, start to finish
Illustrative- Reads the ledger and sub-ledger exports
- Clears the lines that reconcile
- Sets aside the differences it cannot explain
- Drafts the close narrative
Illustrative. The steps are written for this page to show the shape of the job, and none of it is a recording.
What would land when it finishes.
A set of cleared accounts, the differences it could not explain, and a draft narrative waiting for somebody to post it.
| Account | Difference | What it looks like |
|---|---|---|
| 4100 Revenue | +18,420 | Two renewals dated December landed in January |
| 6200 Contractors | -7,150 | One invoice from Arden Freight has not arrived |
The other 16 accounts would clear with nothing to say about them. The accounts, the figures and the month are written for this page.
Illustrative. These rows are written for this page and are never a customer’s data.
Supported inputs
Kinds of source, from accounts you would connect in your own Tools workspace. Which account, and the credential behind it, are yours and never appear anywhere on this site. No named integration is listed, because none has been built.
- General ledger export
- Sub-ledger exports
- Last month's close file
Output
A set of cleared accounts, the differences it could not explain, and a draft narrative waiting for somebody to post it.
IllustrativeApproval boundary
Post the narrative to the close file?
Reading, checking and comparing change nothing outside your workspace and would happen on their own. Anything that cannot be taken back waits for you, and what it is asking about is shown in full rather than summarised.
Month-End Close is in development.
It is specified and not built. Billing does not exist yet and the usage allowance has not been measured, so there is nothing to subscribe to and no price to show. Asking for it is what decides what gets built next; a close variation of it can be quoted as a custom build today, against acceptance cases you write.
The rest of the catalogue.
- Invoice MatchingFinanceChecks every invoice against the order it came from and the goods that actually arrived.
- Incident TriageEngineeringTurns a night of alerts into a short list of grouped incidents, each with somewhere to look first.
- Review Before MergeEngineeringReads a change the way a careful colleague would, before anybody is asked to approve it.
- Idle Cloud SpendEngineeringFlags cloud resources with no recorded activity, works out who owns each one, and estimates what stopping it would save.