n8n2erpnext Accounting Nodes
Community n8n nodes for ERPNext/Frappe Accounting workflows covering invoices, payments, journals, GL readback, and financial document integrity.
Accounting automation with ledger readback
The Accounting node connects invoices, payments, journals, and ledger evidence to n8n while keeping ERPNext as the system of record. It is designed for workflows where a successful HTTP response is not enough; submitted documents and their GL impact must remain verifiable.
Supported ERPNext resources
Sales Invoice, Purchase Invoice, Payment Entry, Journal Entry, Account, Cost Center, Fiscal Year, GL Entry, Custom DocType, and Frappe Method.
Operations and API
Accounting resources support Create, Get, Get Many, Update, Delete, Submit, and Cancel. Both Frappe API v1 and v2 document endpoints are supported. Journal Entry API v2 was tested with nested accounts child-table data. Submit and cancel use different Frappe payloads: submit receives { doc }, while cancel receives { doctype, name }.
Connected lifecycle
n8n webhook or schedule -> validation and mapping -> invoice, payment, or journal operation -> GL readback -> allowlisted summary. The package participates in the connected Buying -> Stock -> Selling -> Accounting lifecycle, including linked-document cancellation locks.
Verified behavior
- Draft Journal Entry creation and API v2 update preserved balanced debit/credit totals without creating GL rows.
- Submit created two GL rows for a balanced test entry; cancel produced the expected cancelled ledger rows.
- A business lifecycle test created and paid Sales Invoice and Purchase Invoice documents, submitted payment entries, and verified a balanced closing Journal Entry with debit and credit totals of 1,500.
- Stress/security input was capped at 25 iterations and returned no credential-like leakage.
- Live webhook summaries returned document names, totals, counts, and security status rather than raw accounting documents.
Scope
This package is Accounting-focused. Tax, cost-center, fiscal-year close, and chart-of-accounts behavior must be checked against the target company before importing a workflow artifact.
Integration and security boundary
The node authenticates to Frappe with an ERPNext API credential and supports an internal URL plus Site Host Header for self-hosted deployments. Use a dedicated integration user with scoped roles, explicit fields for read workflows, private or authenticated webhooks, HTTPS, and controlled execution-data retention. Never expose API keys, secrets, authorization headers, raw upstream errors, or full ERPNext documents through a public workflow.
Build and release
Each package is released as an MIT-licensed n8n community node with TypeScript build/lint checks, n8n node-cli validation, npm audit, and packed-artifact review. Install the package from npm or inspect the source at GitHub. Temporary write-test workflows are deactivated after verification.