n8n use case · Finance and treasury
How to use webhooks with n8n to automate collections and payments: the payment gateway or the bank notifies n8n the moment a payment is received; the workflow checks that the notification is authentic, reconciles the payment with its invoice in Odoo, chases overdue payments in escalating stages and sends management a treasury summary every morning.
Information reviewed on 7 November 2026. Use case implemented with n8n by Binovo FutureAI, Certified n8n Expert Partner.
Money comes in through many channels: card payments on the website, bank transfers, direct debits, Bizum or payment links. Matching each payment to its invoice is usually done by downloading statements and checking them line by line, and overdue payments get chased whenever someone remembers.
Scroll through the steps: on the right, the workflow node working at each moment lights up, along with the data it handles (sample data).
POST /webhook/cobros source: stripe event: payment_intent.succeeded amount: 1,512.50 EUR reference: FV/2026/01877
signature: valid event already processed: no result: continue
invoice: FV/2026/01877 payment: recorded reconciliation: complete invoice status: paid
overdue today: 6 reminder 1: 3 sent reminder 2: 2 with payment link alert to manager: 1
event: charge.refunded invoice: FV/2026/01790 reopened alert: accounting
collected yesterday: 18,420 EUR pending: 96,300 EUR overdue more than 30 days: 7,950 EUR exceptions: 2
Instead of checking at regular intervals, the gateway calls the n8n webhook as soon as the payment is made: Stripe with its events, Redsys with its online notification, and banks or aggregators with an API whenever a transaction comes in. The workflow starts that very second.
Before touching the accounting records, n8n verifies the notification’s signature with the gateway’s secret key and checks that the event has not already been processed. This way nobody can fake a payment, and a repeated notification is never counted twice.
Using the reference, the amount and the customer, the workflow finds the invoice in Odoo, records the payment and reconciles it. If the amount does not match, or a single payment covers several invoices, it is flagged as an exception for the accounting team to decide.
A scheduled workflow checks overdue invoices every day and sends reminders in stages: a friendly notice, a second notice with a payment link and, if the invoice is still pending, an alert to the account manager so they can make a call. When the payment arrives via webhook, the sequence stops automatically.
Events for direct debit returns, refunds or disputes arrive through the same webhook. The workflow undoes the reconciliation, reopens the invoice and notifies the person in charge, stating the reason.
Every morning, a summary lands in management’s email or chat: collected yesterday, pending collection, overdue amounts by age bracket and open exceptions, with links to Odoo. No spreadsheet exports.
| Application | Role in the workflow |
|---|---|
| Stripe, Redsys, PayPal | Payment, refund and dispute notifications via webhook. |
| Banking with an API or PSD2 aggregator | Bank transactions for transfers and direct debit payments. |
| Odoo Accounting | Invoices, payments, reconciliation and collections follow-up. |
| Email and WhatsApp Business | Customer reminders with a payment link. |
| Microsoft Teams or Slack | Exceptions and daily summary for administration and management. |
Do you use other applications? n8n has more than 2,000 integrations and connects to any software that has an API. We cover this in n8n integrations.
A webhook is a web address to which another application sends a notification when something happens. In n8n, the Webhook node creates that address, accepts GET, POST, PUT, PATCH, DELETE and HEAD requests, is secured with basic, header or JWT authentication, and can respond instantly or with the result of the workflow.
It is the building block that turns an automation that checks at regular intervals into one that reacts the moment something happens. More detail in the n8n webhooks guide.
Payment batches prepared from Odoo, approved by the person in charge, with a notification to the supplier once they are paid.
Subscription sign-ups, renewals and cancellations synchronised between the payment gateway, the CRM and Odoo.
The webhook from a contract signature triggers the onboarding invoice and the first payment.
Customers who exceed their credit limit are blocked from placing new orders until they pay.
Before starting, we take a snapshot of the current process and, once the pilot is running, we compare:
It is a web address created by the n8n Webhook node. When another application, such as Stripe or your online store, sends a notification to that address, the workflow starts immediately with the data from the notification.
Yes, if it is done properly: the signature of each notification is verified with the gateway’s secret key, the same event is never processed twice, and the webhook address is protected with authentication.
Yes. Redsys sends a signed online notification when the payment is completed, and bank transactions are obtained through the bank’s API or a PSD2 aggregator.
Yes. A workflow checks overdue invoices every day and sends escalating reminders with a payment link, and it stops as soon as the payment arrives via webhook.
We build it with Odoo because it is our reference ERP, but the same workflow works with other ERPs or accounting software that have an API.
Tell us which payment gateways and banks you use and we will propose a real-time collections workflow.
