Assemble the month-end close digest
A month-end digest in a consistent shape, assembled from the systems of record. Built for a finance team that rebuilds the same summary every month by hand.
Stripe
Google Sheets
RevenueCat
Notion
4 steps4 integrationsRuns monthly
The numbers live in four systems. What it costs while the work is still done by hand.
- 01The numbers live in four systems.
- 02Last month's format is never quite this month's format.
- 03The digest is finished the week after anyone needed it.
- Pull revenue$412k billed · $9.1k refunds
- Pull expenses184 rows · June tab
- Pull subs38 new · 11 churned
- Build digestcreate_page · same shape
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Pull the month's revenue and refunds.Stripe
- 02Pull the expense rows.Google Sheets
- 03Pull subscription movement.RevenueCat
- 04Assemble the digest in the shape your team already reads.Notion
The workflow is an editable graph. Reading runs freely; assemble the digest in the shape your team already reads waits for your opt-in approval until you loosen it. The graph is the receipt.
Close, in one shape. Paste this into ModuleX chat, or hit Use this workflow.
assemble the month-end close digest: pull the month's revenue and refunds; pull the expense rows; pull subscription movement; assemble the digest in the shape your team already reads. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Assemble the month-end close digest. A month-end digest in a consistent shape, assembled from the systems of record.
- stripe · list_charges
- google sheets · get_spreadsheet_info
- revenuecat · get_customer
A month-end digest in a consistent shape, assembled from the systems of record.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
- Categorise card spend without the month-end scrambleA categorised transaction list plus a short list of the entries that genuinely need a human. Built for a finance lead reconciling a month of transactions from memory.
- Reconcile payouts against your ledgerA reconciliation summary that names the specific rows to look at, not just a total that is off. Built for whoever matches the payment processor to the accounting sheet each week.
Route a purchase request to the right approverA request that reached the right person, with a record of who approved what. Built for an operations manager who is the bottleneck on every small purchase.
About this use case.
No. It is a summary drawn from your systems; your books remain the record.