DEV Community: Farzam Saadat

Expense Report Automation with n8n: Design the Review Process First

Farzam Saadat — Sat, 03 Oct 2026 14:21:47 +0000

Expense report automation moves employee submissions through consistent data collection, checks, record creation, and review notifications. A useful workflow makes missing information and exceptions visible. It does not, by itself, establish whether an expense is legitimate, tax-deductible, approved for reimbursement, or paid.

Before choosing nodes in n8n, decide what your expense process needs to prove. Who submitted the expense? What was purchased? Is the record complete? Who reviews an exception? Where is the decision recorded? These questions determine whether automation improves control or simply moves incomplete information faster.

Separate intake, review, approval, and payment

Treat these as four different stages. Intake captures the request. Review checks the information against the company’s rules. Approval records an authorized decision. Payment settles the approved obligation through the business’s payment process.

Conceptual flow: validation and exception checks are automated; approval and payment stay with people and the business’s payment process.

A confirmation email should say that the expense was received, not approved. Similarly, a status such as No Exception Flagged should not be interpreted as a payment instruction. This distinction matters when employees and reviewers rely on automated messages to understand what happens next.

A first project can automate intake and review routing while leaving approval and payment in the team’s existing process. State that boundary explicitly in the workflow specification and employee instructions.

Choose fields that support the review

Capture a submission ID, employee identifier, transaction date, merchant, amount, currency, business purpose, and supporting-document reference where required by company policy. Include the project or department if costs need to be allocated. Store a submission timestamp separately from the transaction date.

The amount should be numeric, but a number alone is not enough: 250 USD and 250 EUR are different records. If the workflow supports only one currency, make that visible on the form. If it supports several, define how comparison thresholds work before building a conversion step.

Keep original submitted values alongside corrected values when a reviewer makes a change. A useful record explains what changed, who changed it, and why. Avoid overwriting the original business purpose or amount without an identifiable review history.

Apply explicit validation rules

Separate incomplete or invalid submissions from policy exceptions. A missing employee identifier is a data problem. An amount above a company review threshold can be a valid submission that needs additional attention. Each deserves a different message and status.

Decide how refunds, credit notes, and corrections are handled. A workflow designed only for positive reimbursement requests should route negative values to a separate process rather than silently discarding them. Test dates, blank fields, decimal amounts, and unexpected currency values.

Write the rules in plain language before translating them into conditions. For example: if the amount exceeds the company’s chosen threshold, retain the submission and notify the designated reviewer. The threshold is a business choice, not a universal accounting standard.

Flag possible duplicates without assuming fraud

A duplicate check can compare employee, merchant, transaction date, amount, and currency. A repeat receipt identifier can provide another signal when it is reliably captured. Normalize text carefully so minor differences in capitalization do not hide a match.

These checks produce candidates for review. Two legitimate purchases can have the same amount and merchant on the same day. Conversely, the same expense may be entered with a different merchant spelling. Keep the reason for the match visible and allow a reviewer to resolve it.

Distinguish duplicate expenses from repeated processing of one submission. A stable submission ID can stop the same intake event from creating another record after a retry. At higher volumes, enforce uniqueness in the storage layer; a separate spreadsheet lookup followed by a write can race with another execution.

Create a reviewer queue that people can use

Store the request with a status, exception reason, assigned reviewer, and review timestamp. Suggested statuses include Received, Needs Information, Review Required, Approved, Rejected, and Paid. Use only the statuses your actual process supports, and define who can set them.

The reviewer notification should include the submission reference and a link to the authorized record. It should explain why review is needed without spreading receipt images or unnecessary personal details across multiple inboxes. Restrict access to the people who need it.

For a modest pilot, a spreadsheet can make records easy to inspect. n8n provides integrations for Google Sheets and Google Drive. Storage choices still need to account for permissions, concurrency, retention, and how review decisions are recorded.

A worked example: three submissions, three outcomes

Consider a fictional business that has chosen USD 500 as an additional-review threshold. This is an illustrative internal rule, not a recommended legal or tax limit.

Submission A is a complete USD 86 request with no matching prior entry. Record it as received and place it in the normal review queue. Submission B is a complete USD 620 request. Preserve it and flag the amount rule. Submission C is USD 86 with the same employee, merchant, date, and currency as A. Flag a possible duplicate and show the matching record.

None of those outcomes automatically establishes reimbursement approval. The reviewer still considers the business purpose and supporting information. If C is a legitimate second purchase, the reviewer records the explanation instead of deleting the match history.

Test failure recovery as well as the happy path

Test a valid submission, missing fields, a boundary amount, a possible duplicate, a repeated submission ID, and a failed notification. For the USD 500 example, test 499.99, 500.00, and 500.01 so the meaning of greater than versus greater than or equal to is deliberate.

Also test what happens when the record is saved but the email fails. Recovery should not insert the same expense again. n8n’s error workflow mechanism can support failure alerts [S2], but someone must own investigation and recovery. Define the response before rollout.

Do not mark an item paid because an email was sent or an approval checkbox changed. If payment tracking is later added, use an authorized payment result and a traceable reference as the basis for that status.

Measure the result without overstating savings

Track missing-information rates, time to first review, unresolved exceptions, and manual touches per submission. Compare equivalent periods and record the number of requests in each sample. A faster intake step can coexist with a slow approval queue, so measure the stages separately.

My expense intake and review demonstration illustrates an initial rules-based approach using sample data. This guide describes broader design choices and proposed controls; it does not imply that every feature discussed is included in that demonstration. My accounting and finance background informs the emphasis on records and review boundaries.

Common questions

Can n8n automatically approve expenses?

A workflow can be configured to apply business-defined decisions, but that should follow an approved policy and clear authorization. The intake-and-review approach here keeps reimbursement decisions with a person.

Do I need AI to read receipts?

No AI is needed when employees submit structured fields. Receipt extraction is an optional extension. If added, validate the extracted amount, currency, date, and merchant before relying on them; unclear results should go to review.

Is this a substitute for accounting software?

This design coordinates submissions and review. It does not replace a general ledger, reconcile accounts, or determine tax treatment. Any later accounting integration needs explicit mappings and approval rules.

Start with one expense category

Pilot a narrow category with agreed fields, reviewer ownership, and test cases. To map an appropriate first version, discuss your expense workflow and share how submissions currently reach your finance team.

How Much Does n8n Automation Cost for a Small Business?

Farzam Saadat — Sat, 03 Oct 2026 12:19:51 +0000

By Syed Farzam Saadat | Published October 2, 2026 | Updated October 2, 2026 | 11 min read

n8n automation pricing has two main parts: the platform and the build. The platform costs about €20 to €50 a month on n8n Cloud, or roughly $5 to $40 a month if you host it yourself. The build, meaning the workflows themselves, typically costs from under $1,500 for a simple workflow to $5,000 or more for a connected system.

Most pricing pages only show you the first part, which is why small business owners are often surprised by the total. This guide breaks down every cost layer with 2026 numbers, shows how n8n counts usage, and walks through three worked examples so you can estimate your own first-year cost before you talk to anyone.

Key takeaways

n8n bills per execution (one full workflow run), not per step and not per user.
n8n Cloud: Starter €20/month for 2,500 executions, Pro €50/month for 10,000, billed annually.
Self-hosting: the software is free, the server is roughly $5 to $40/month, and upkeep costs your time.
Build cost: roughly under $1,500 for simple workflows, $1,500 to $3,500 for typical multi-step ones, $5,000 to $15,000 for connected systems.
The most common budget trap is a polling trigger that burns executions all month.

What does n8n automation pricing include?

n8n is a workflow automation platform that connects your apps (a website form, a CRM, email, WhatsApp, accounting software) and moves data between them without manual work. When people search for n8n automation pricing, they are usually asking about four separate cost layers:

Cost layer	What it covers	Typical cost pattern
1. Platform	n8n Cloud subscription, or a server if you self-host	€0 to €50/month for most small businesses; $5 to $40/month for a server
2. Build	Designing, building, testing, and documenting the workflows	One-time; from under $1,500 to $15,000 depending on scope
3. Connected tools	CRM, email platform, WhatsApp, AI model usage, and other apps	Varies by tool; often already in your budget
4. Ongoing care	Monitoring, fixes, and changes when apps update	A few hours a month, or a small retainer

A simple way to remember it: first-year cost = platform + build + connected tools + ongoing care. Most comparisons stop at the platform line, which is usually the smallest number.

How much does n8n cost per month?

n8n Cloud is priced by monthly executions rather than by seat. Here are the published plans in 2026. n8n lists prices in euros, and annual billing is about 17% cheaper than paying month to month.

Plan	Annual billing	Monthly billing	Executions / month	Concurrent runs	Best for
Community (self-hosted)	Free software	Free software	No plan limit (server-bound)	Depends on server	Technical users
Cloud Starter	€20/month (€240/year)	About €24	2,500	5	Solo owners and first production workflows
Cloud Pro	€50/month (€600/year)	About €60	10,000	20	Growing small businesses
Business	About €667/month	Quote or annual	40,000	Higher	Teams that need SSO, Git, and environments
Enterprise	Custom	Custom	Custom	200+	Large organizations

In US dollars, third-party 2026 breakdowns put Starter at roughly $20 to $25 and Pro at roughly $50 to $65 a month, depending on the exchange rate and billing choice. For most small businesses, Starter or Pro is enough. Business costs about 13 times Pro for four times the executions, so it only makes sense if you need its governance features.

What counts as an execution in n8n?

An execution is one complete run of a workflow, no matter how many steps it contains. If a new lead triggers a 10-step workflow 1,000 times in a month, that is 1,000 executions. Task-based tools such as Zapier count each action step separately, which is why the same automation can cost very different amounts on different platforms.

How fast do n8n executions add up?

Your workflow design affects the bill as much as the plan does. A polling trigger checks an app for new data on a schedule, and every check can count as an execution. A webhook trigger runs only when something actually happens.

Check frequency	Runs per day	Executions per month
Every 5 minutes	288	8,640
Every 15 minutes	96	2,880
Every 30 minutes	48	1,440
Every hour	24	720
Webhook (event-based)	Only when an event occurs	Equals your real event volume

A single workflow that checks every 15 minutes uses 2,880 executions, which already exceeds the 2,500 included in Starter. Use webhooks or native app triggers wherever the app supports them, and poll less often where it does not.

Is n8n free for small businesses?

The self-hosted Community Edition has no license fee and no execution cap set by a plan, so the software is free. You pay for the server instead. Published 2026 guides put a basic VPS at about $4 to $7 a month, a production-hardened setup at around $12, and heavier workloads (for example, 20,000 executions a month with memory-hungry workflows) at $20 to $40 for a server with 4 GB of RAM and 2 vCPUs. n8n Cloud has no permanent free plan, only a trial.

The catch is your time. Estimates for a healthy self-hosted instance run about 2 to 4 hours a month for updates, backups, and monitoring, with more in a month when a migration goes wrong. Cloud Pro costs roughly $43 a month more than a $12 server, so if your time is worth $40 an hour, self-hosting stops saving money once upkeep passes about an hour a month. For many small businesses, Starter or Pro is cheaper once time is counted. Self-hosting makes sense when volume is high, data must stay on your own server, or someone technical already looks after your infrastructure.

n8n's Community Edition is source-available under a fair-code license. Running it for your own business automation is the standard use; read the license terms first if you plan to resell n8n as a hosted service.

How much does it cost to hire someone to build n8n automation?

For most small businesses, the build costs more than the platform. Price depends on how many apps are connected, how much branching and error handling the workflow needs, how it is tested, and whether it includes documentation and handover. Published 2026 rate guides and agency pages point to these ranges:

Project type	Typical scope	Typical price range	Typical timeline
Simple workflow	One trigger, two to four apps, little branching (for example, form to CRM plus email)	Under about $1,500	A few days
Multi-step business workflow	Lead routing, onboarding, or invoicing with branching and error handling	$1,500 to $3,500	About 6 to 10 days
Connected automation system	Several workflows, CRM or WhatsApp links, hosting setup, testing, documentation, handover	$5,000 to $15,000	Several weeks
AI-enabled workflow	Adds model calls, prompts, and safeguards to any of the above	Added on top, plus AI usage fees	Varies

On hourly pricing, established automation studios publish rates around $100 to $150 an hour, and surveys of experienced solo specialists report $95 to $235 an hour. Lower-cost freelancers and offshore teams charge far less. Region and experience move these numbers a lot, so treat them as a map of the market, not a quote.

The cheapest quote is not always the cheapest outcome. A workflow with no error handling, no documentation, and credentials stored in someone else's account becomes a black box the moment the builder moves on. Ask for a written scope, error alerts, documentation, and credentials that live in your own accounts.

What else adds to the cost of n8n automation?

Connected app fees. A CRM tier, an email platform, or WhatsApp Business messaging charges its own fees, separate from n8n.
AI model usage. If a workflow calls an AI model, that usage is billed by the model provider, not by n8n.
Hosting extras. Self-hosting adds backups, SSL, and monitoring on top of the server price.
Maintenance. Apps change their APIs and login rules, and workflows occasionally need repair.
Runaway runs. A loop caused by a misconfigured trigger can use up a month of Starter executions in an afternoon.

Three examples: what n8n automation costs in the first year

These examples are illustrative. They combine the platform prices above with the middle of each build range, in US dollars at roughly €1 = $1.10 to $1.15.

Business	What the automation does	n8n setup	Platform cost (year)	Build (one-time)	First-year total
Local service business	New website enquiry goes to the CRM, the customer gets an instant email, the team gets an alert (about 400 webhook runs a month)	Cloud Starter	About $270	$800 to $1,500	About $1,100 to $1,800
Online store	Orders sync to accounting and shipping, with stock alerts and customer notifications (about 3,000 runs a month)	Cloud Pro	About $670	$1,500 to $3,500	About $2,200 to $4,200
Growing operations team	Six or more workflows across CRM, WhatsApp, and reporting (about 15,000 runs a month)	Self-hosted on a VPS	$240 to $480 (server at $20 to $40/month)	$5,000 to $15,000	About $5,200 to $15,500

Totals exclude connected app fees and your own time. The third example is self-hosted because 15,000 monthly runs exceed Pro's 10,000 executions, and the next cloud tier costs far more.

How does n8n pricing compare with Zapier and Make?

The platforms bill different units: Zapier charges per task (each action step), Make charges per credit (each module action), and n8n charges per execution (each full run). For short, low-volume workflows the gap is small, and Make can be the cheapest of the three. For long or frequent workflows, n8n's per-run model usually costs less. One 2026 pricing analysis puts n8n at 5 to 20 times cheaper than Zapier once volume passes roughly 15,000 to 20,000 executions a month.

Platform	Billing unit	Entry paid plan (annual billing)
n8n	Execution (one full run)	Starter, €20/month, 2,500 executions
Zapier	Task (one action step)	Professional, $19.99/month, 750 tasks
Make	Credit (one module action)	Core, about $9/month, 10,000 credits

How can you keep n8n automation costs down?

Prefer webhooks to polling. Event-based triggers only run when there is something to process.
Stop unnecessary runs at the source. Use filters in the source app or webhook conditions so runs only start when needed, because every started run counts.
Add error workflows and alerts. You find out about a failure or a loop in minutes, not at the end of the month.
Start with one high-value workflow. Automate the task that wastes the most hours first, then expand.
Choose a plan on executions and concurrency, not on price alone. Starter allows 5 concurrent runs, Pro allows 20.
Self-host only with capacity. Make sure someone can handle updates, backups, and security.
Agree a fixed scope in writing with any builder, including documentation and handover.

Which n8n option fits your business?

Choosing between n8n Cloud, self-hosting, and hiring a builder

Your situation	Best-fit option
Under about 2,500 runs a month and no technical staff	n8n Cloud Starter
2,500 to 10,000 runs a month, or bursts that need more than 5 concurrent runs	n8n Cloud Pro
Above about 10,000 runs a month, with someone technical to maintain a server	Self-hosted n8n
You need SSO, Git version control, or separate environments	Business or Enterprise
You have no time to build or maintain workflows	Hire a builder on a fixed, documented scope

How do you get an accurate quote for n8n automation?

Before you ask anyone for a number, write down five things: the process you want automated, step by step; the apps involved; your expected monthly volume; what should happen when something fails; and who will maintain it afterward. With those, any builder can give you a realistic scope instead of a guess.

If you want to see what a finished workflow looks like, including the diagram and a written breakdown, browse my n8n workflow projects. When you are ready to scope your own, contact me with a short description of your process and we can work out what is realistic.

Frequently asked questions about n8n automation pricing

How much does n8n cost per month?

n8n Cloud starts at €20 a month for Starter (2,500 executions) or €50 a month for Pro (10,000 executions) on annual billing. Monthly billing is about €24 and €60. The Community Edition is free to self-host, but you pay for the server. Business costs about €667 a month.

Is n8n free for small businesses?

The self-hosted Community Edition has no license fee, so the software is free. You still pay for a server, roughly $5 to $40 a month, and for the time to maintain it. n8n Cloud has no permanent free plan, only a trial.

How much does it cost to hire someone to build n8n automation?

Simple workflows often cost under $1,500. Typical multi-step business workflows run about $1,500 to $3,500, and connected systems with several workflows, hosting setup, and documentation range from about $5,000 to $15,000. Prices vary by builder, region, and scope.

What counts as an execution in n8n?

An execution is one complete run of a workflow, regardless of how many steps or nodes it contains. A 20-step workflow that runs once is one execution. Zapier, by contrast, counts each action step as a task.

Is n8n cheaper than Zapier?

Usually, once workflows get long or frequent, because n8n bills per run instead of per step. At very low volume the difference is small, and Make can be cheaper than both. Multiply steps per workflow by monthly runs to compare your own numbers.

Should a small business use n8n Cloud or self-host?

Choose Cloud if nobody technical will maintain a server, because n8n handles hosting and updates. Self-hosting suits high volume, data-control needs, or teams with someone who can manage updates, backups, and security, which takes roughly 2 to 4 hours a month.

Does n8n charge per user?

No. n8n Cloud pricing is based on monthly executions, not seats. Higher plans add collaboration features such as shared projects and admin roles, but the main cost driver is how often your workflows run.

The bottom line on n8n automation pricing

n8n automation pricing is easier to predict than it first looks. The platform is the small, visible cost: €20 to €50 a month for most small businesses, or a cheap server if you self-host. The build is the bigger one-time cost and depends on scope. The biggest surprises come from workflow design, especially polling triggers and missing error handling. Count your expected runs, pick the plan that fits, and agree a written scope before any work starts.

If you want a clear scope and price range for your own workflow, get in touch here.

Sources and methodology

Plan prices were checked against n8n's official pricing page as reflected in 2026 third-party breakdowns from Jet Admin (September 2026), Hackceleration (June 2026), CloudZero, and Coworker. Hosting costs come from Hackceleration, Arahi, and Rapidevelopers guides. Build ranges come from 2026 published rate cards, including a BetonAI survey of 54 automation operators and Achiya Automation's published rates; these vary widely and are not quotes. Euro prices are converted at roughly €1 = $1.10 to $1.15. Examples are illustrative. Prices change, so confirm current numbers before you buy. Last updated October 2, 2026.

About the author.

Syed Farzam Saadat is an n8n workflow automation developer who builds automations for small businesses. Pricing in this guide was last verified on October 2, 2026.