Skip to content
NEWMarketplace and the trig8n Agent: sell what you build, and get plans and changes that are tested before you see them. See what is new

Library / Reports, Analytics & Dashboards

Reports, Analytics & Dashboards

Run month-end close checks and send a management pack with AI commentary

Runs on the second working day, performs seven close checks on trial balance data, and sends a P&L pack with AI-drafted commentary.

What it does

## Run month end close checks and send a management pack with AI commentary Who it is for. Finance teams closing the month by hand from a trial balance and a checklist. What it does - Runs on the second working day or on demand. Pulls this month's and last month's trial balance and the close data. - Seven checks against a materiality figure: trial balance balances, bank reconciled, invoices posted, suspense cleared, VAT control agrees, fixed asset register agrees, receivables over 90 days reviewed. - Builds the P&L against last month with the change on every line; an AI step drafts the commentary from the figures and the check results. - Renders the management pack and distributes it, or BLOCKS the close and sends the failed checks instead. Setup 1. Set base, period and materiality in Config, or replace the HTTP Request nodes with your accounting system (Zoho Books, QuickBooks Online, Xero) nodes. 2. Set the AI credential on the commentary step. Point distribution at your email or Slack node. 3. Activate; the schedule runs on the second working day. All external systems are reached through HTTP Request nodes against base in the Config node, so the whole flow imports and runs against any REST backend; swap any of them for the native n8n node of your system. Built and tested on sample data by Finamatik: https://finamatik.com/work/month-end-close-pack Requirements. n8n 1.100 or later; for the AI steps, a model endpoint at base/llm/complete or the OpenAI or Anthropic node in its place; your own systems reachable over HTTPS. How to customise. Every rule lives in one Code or Config node and is named for what it decides; change the thresholds there, not in the branches.

The steps

  1. Schedule: 2nd working day 08:00
  2. Webhook: run close now
  3. Config
  4. Accounting: trial balance
  5. Accounting: prior period
  6. Accounting: close checks
  7. Merge sources
  8. Run close checks
  9. AI: draft commentary
  10. Assemble pack
  11. Render management pack (xlsx)
  12. Any check failed?
  13. Slack: close blocked, owners tagged
  14. Slack: pack ready

20 steps in total.

Similar automations