Flowgrammer

Canadian n8n workflows for CFOs

Review CAD revenue, expenses, budget variance and tax-reserve estimates with n8n. Download original reporting and reconciliation workflows with audit records.

Download original Canadian finance workflows

Flowgrammer's free Canadian finance pack includes eight preparation workflows, three approval-controlled delivery workflows and an internal error-alert workflow. Start with the complete Canadian finance ZIP or choose a JSON file below. No email is required.

Download Format and status
Bank and ledger reconciliation review Importable n8n JSON; setup required
CAD financial and tax-reserve report Importable n8n JSON; setup required

Read the setup guide, install the private PostgreSQL review queue and load the synthetic test inputs before enabling any workflow. These original Flowgrammer files are separate from the community templates linked further down. You need n8n hosting, PostgreSQL and your own credentials; connected services may charge fees.

The preparation workflows accept reviewed structured exports. Gmail/OCR, bank-feed and other source connectors are not included. The invoice workflow checks extracted fields and document metadata; your source adapter must verify actual file size, type and page count before extraction. The package has local calculation, SQL permission and workflow-structure checks; importing and executing it in your own n8n and accounting test accounts remains a required setup step.

Configure CAD, GST, HST and QST

Each workflow starts with a Settings block. Currency defaults to CAD, locale to en-CA and timezone to America/Toronto. Configure the client ID, transaction province, separate tax components, tax-inclusive flag, reviewed rate dates, tolerances, reminder cadence and batch limits. Non-CAD records and unsupported tax treatments stop for review.

The standard-rate examples support Ontario HST at 13%, Nova Scotia HST at 14%, HST at 15% in New Brunswick, Newfoundland and Labrador and Prince Edward Island, and GST at 5% in Alberta and the territories. Québec uses GST at 5% plus QST at 9.975%, both calculated on the selling price before GST. At CAD 100 before tax, the Québec example calculates GST of CAD 5.00 and QST of CAD 9.98 with per-line cent rounding. Tax-inclusive values are backed out before calculating the components.

Rates were checked on 29 October 2026 against the CRA rate table and Revenu Québec's calculation rules. A reviewer must confirm registration, place of supply, taxability and the applicable transaction date. Your office province alone does not determine the tax. PST provinces, mixed or exempt supplies, credit notes and special tax rules require custom review. These workflows do not calculate statutory payroll deductions, determine ITC eligibility or file tax returns.

Keep approval and recovery visible

Dry-run mode is on and delivery is disabled in every download. Preparation writes a review result or exception to a private database. Stable source IDs, revisions and action-stage keys prevent repeated preparation of the same external action. A separate reviewer login approves the exact stored recipient or ledger payload; the workflow login cannot approve it. Approvals expire after 24 hours if unclaimed. All reminder sends, including final notices, require approval.

QuickBooks delivery creates a sales invoice without emailing it; Xero delivery creates an ACCREC draft. Map the organisation's own customer/contact, item/account and Canadian tax codes first. Receipts intended as expenses remain review-only. Payroll checks and reconciliation proposals do not release payroll or post journal entries.

The package records preparation, exceptions, approval and delivery outcomes in an audit table. Database operations use bounded retries. External writes use a single reserved action and provider keys where available; an uncertain response must be reconciled before retrying. Connect the included error-alert workflow in n8n settings and test its SMTP credential. Keep sensitive documents in approved storage; alerts contain workflow references rather than document contents.

Start with close exceptions and management reporting

For cfos and controllers, the useful starting point is a repeatable handoff with a visible owner. Connect the source record to a preparation queue, then send the accountant or finance reviewer the fields needed to decide the next action. Set the acceptance test before choosing how many steps to automate.

For this guide, start with this example: The ledger export and board-pack draft disagree about a cash total. The expected output is specific: Show both source versions and the unresolved variance for the controller. This is an implementation scenario, not a claim about a deployed client system.

Compare the starting points

These entries offer components for close exceptions and management reporting; they are not a complete role-specific package. Keep the publisher's original template separate from your adapted version so you can review changes. A proposed build has no executable template attached.

Reconcile bank payments with ERP invoices, Google Sheets, and Slack

Free template. Map identifiers and fields to your systems. The accountant or finance reviewer reviews exceptions before any send or write.

Apps listed in the research: Google Sheets; Slack.

Reconcile cash balances in Google Sheets with OpenAI explanations

Free template. Map identifiers and fields to your systems. The accountant or finance reviewer reviews exceptions before any send or write.

Apps listed in the research: Google Sheets; OpenAI.

Monitor budget variance with Google Sheets, Gemini, Slack, and Gmail

Free template. Map identifiers and fields to your systems. The accountant or finance reviewer reviews exceptions before any send or write.

Apps listed in the research: Gmail; Google Gemini; Google Sheets; Slack.

Generate monthly financial reports with Gemini AI, SQL, and Outlook

Free template. Map identifiers and fields to your systems. The accountant or finance reviewer reviews exceptions before any send or write.

Apps listed in the research: AI Agent; Calculator; Google Gemini Chat Model; Microsoft Outlook; MySQL; Think Tool.

Send daily executive financial briefings with Google Sheets, GPT-4o-mini, Notion and Telegram

Free template. Map identifiers and fields to your systems. The accountant or finance reviewer reviews exceptions before any send or write.

Apps listed in the research: AI Agent; Google Sheets; Notion; OpenAI Chat Model; Slack; Telegram.

Month-end close checklist tracker

Custom build concept. Map identifiers and fields to your systems. The accountant or finance reviewer reviews exceptions before any send or write.

Apps listed in the research: Sheets/Notion/Asana; Slack or Teams.

Define the workflow contract

Field Pilot decision
Trigger One new or changed source record relevant to close exceptions and management reporting
Identity The source system's record ID plus its revision or event ID
Input The record, source link and approved checklist
Output A preparation item with missing fields, status and reviewer
Reviewer The accountant or finance reviewer
Stop condition A number lacks its reporting period or ledger source.

Use a form, webhook or scheduled lookup only after checking how the source exposes changes. Validate identifiers and required fields before any AI or transformation step. Write the prepared result to a test table or draft queue. A separate approval step controls the final send or business-system update; changing the model prompt alone does not establish that approval.

Map the close exception register

Use ledger account and reporting period as the source matching key. The reviewer needs these fields: cash total, export version, metric definition, close owner, approval status. Map each field to its actual export column or API property during the pilot; do not guess property names from the template title. Create one item in the close exception register for each unresolved handoff, with its source link and owner.

Map fields and review access

Keep the source identifier, version and link with each output. When a field is missing or contradictory, leave it unresolved and explain what the reviewer needs to confirm. If AI prepares a summary, ask it to cite the supplied record and distinguish a quoted fact from an inference. Deterministic checks should handle required fields and duplicate identifiers.

Use only the information needed for this job. Check every node that sends data to a third party, and agree who can access execution history. Credentials belong in n8n's credential store. Confirm the connected app's permissions and account region before using sensitive records.

Test the handoff before a live run

  1. Use a synthetic example: The ledger export and board-pack draft disagree about a cash total.
  2. Check the review result: Show both source versions and the unresolved variance for the controller.
  3. Remove a required identifier. The record must reach an exception queue rather than an external send.
  4. Replay the same event. The workflow must recognize the duplicate before writing or sending again.
  5. Make the destination fail. The owner must receive an alert with the source ID and a recoverable status.
  6. Test the stop condition: A number lacks its reporting period or ledger source. The reviewer must resolve it before the workflow continues.

Keep an error workflow and an owner for failures. Retry only the failed step, using the original idempotency key or destination lookup. Review the execution log after a retry to confirm that earlier actions were not repeated. n8n error handling and human review are capabilities you configure; neither is evidence that a downloaded template already includes your required controls.

Use the worksheet to scope your build

Download the implementation worksheet to record the fields, approvals and acceptance results. It is an ungated Markdown planning worksheet, not an importable n8n workflow.

A fit call is useful once you can name the queue, source system and reviewer. Discuss this n8n workflow or read how we build AI automation systems.

Technical sources

Compare the tool before building

For connectors, billing and data-location tradeoffs, read the n8n or Make comparison for this work. This collection remains focused on n8n workflow references.

Frequently asked questions

Do the Canadian downloads include GST, HST and QST?

The invoice-review workflow calculates supported standard-rated CAD examples using explicit province and tax-component settings, including separate GST and QST. A reviewer confirms the transaction's place of supply, tax treatment and date. Unsupported or inconsistent records go to exceptions.

Will a download post to QuickBooks or Xero immediately?

No. Imports are inactive, dry-run is on and delivery is disabled. After setup and testing, a separate reviewer must approve the exact ledger payload before a manually run dispatcher can create a QuickBooks sales invoice or a Xero draft.

What should cfos and controllers automate first?

Start with close exceptions and management reporting. Prepare the close exception register from confirmed source records and have the accountant or finance reviewer approve the next action. The selected entries are components to adapt, not a finished package.

Are these ready to use with my accounts?

Templates need credentials, field mapping, access checks and testing in your environment. Some publisher templates are paid, and hosting and connected services may have their own costs.

What does a custom build concept mean?

It is a proposed workflow design drawn from a business pain point, not a working automation or a download from n8n. Flowgrammer would confirm the inputs, reviewer and acceptance test before building it.

Can Flowgrammer help with implementation?

Yes. Bring one recurring task, the systems involved and an example with sensitive details removed to a fit call. We will discuss the smallest useful workflow and the approvals it needs.

Discuss my n8n workflow