STAKKER ES Book an assessment
Call

How to Automate Invoicing and Payment Tracking for an Autónomo (Self-Employed Freelancer)

Samuel Martínez, 29 July 2026. 12 min read. Translated from the Spanish original.

Invoicing as an autónomo (self-employed) is more than filling in a PDF. It's remembering to send it on time, chasing payment, reconciling with the bank,…

If you’re an autónomo, you know that invoicing isn’t just filling in a PDF and sending it. It’s remembering to do it on time, chasing payment, reconciling with the bank, updating your tracking spreadsheet and making sure the tax office doesn’t catch you out on a wrong number. Every month, many hours are lost on tasks a machine can do better than you.

This article shows you how to automate the whole cycle, from the moment you finish a job until the money lands in your account and your accounts update themselves. No invented figures, no promises of magic, just real tools and workflows that work in 2026.

This page is for information only and is not binding advice. Each case is tailored after a diagnosis.

TL;DR

Why automate invoicing and payment collection

Manual invoicing has three problems:

  1. Dead time. Filling in fields, looking up client details, calculating VAT, exporting a PDF, writing an email. If you invoice a fair number of jobs each month, that’s hours you’re not getting paid for.
  2. Forgetting. You finish a job, deliver it, and forget to invoice until the client asks or until you close the month. You lose cash flow.
  3. Slow payment. You send the invoice, the client shelves it, you don’t chase because it feels awkward, and you get paid at 45-60 days when your terms were 15.

Automating doesn’t just give you those hours back. It also improves your cash flow because reminders go out on time, without you having to remember. And it reduces errors: if the invoice is generated from CRM data, there’s less risk of getting the CIF (Spanish tax ID number) or the description wrong.

Which parts of the cycle can be automated

The full cycle runs from finishing a job until the money is in your account and your accounts are up to date. These are the stages that can be automated:

1. Logging the finished job

If you use a CRM, a Kanban board or a spreadsheet, you can set it up so that moving a card to “Completed” or marking a row as “Invoice” triggers the next step. If you work alone and don’t have a CRM, this step stays manual: you flag that an invoice is needed.

2. Generating the invoice

The automation takes the job details (client, description, amount, date) and calls the API of your invoicing software (Holded, Quaderno, FacturaDirecta, Stripe Invoicing if you take payments online) to create the invoice. The PDF is generated automatically, with your template, your logo and the correct serial number.

3. Sending to the client

The invoice is emailed automatically, with a personalised subject line and body. You can include a payment link if you use a payment gateway (Stripe, Redsys, PayPal) or simply your bank transfer details.

4. Payment reminders

If the invoice isn’t marked as paid within X days (5, 10, 15, depending on your policy), the system sends a reminder. You can schedule several: a friendly one at 7 days, a firmer one at 15, a final one at 30. All without you having to remember.

5. Bank reconciliation

When a payment arrives in your account, the system compares the amount and reference with outstanding invoices and marks the right one as paid. This requires a connection to your bank via API (BBVA, Santander, N26 and Revolut allow it) or automatic download of CSV statements.

6. Updating the CRM and accounts

The paid invoice updates the status in your CRM, triggers a thank-you email if you want one, and sends the data to your accounts spreadsheet or to your accountant. If you use accounting software (Holded, Quaderno), the integration is direct.

Tools involved in the chain

There is no single tool that does everything. A typical automation combines three or four pieces:

Invoicing software

You need one with an API. Popular options in Spain:

If you already use one without an API, you’ll have to switch or accept that part of the flow stays manual.

CRM or job log

It can be:

What matters is that you can read from it who the client is, what job was done, how much it costs and when it was finished.

Automation layer

This is where you connect the pieces. Three options:

If your volume is low (under 1,000 operations a month), Zapier or Make are comfortable. If you invoice more or want full control, self-hosted n8n is the best value for money and power.

Bank with an API

For automatic reconciliation you need your bank to expose transactions via API. Most neobanks (N26, Revolut, Qonto) and some traditional banks (BBVA, Santander) allow it. If your bank has no API, you can download CSV statements every week and have the automation process them, but you lose real-time data.

Typical automated flow (from CRM to bank)

Let’s go through a real example, without inventing client names or STAKKER figures. Imagine you’re a freelance designer using Notion as your CRM, Stripe Invoicing for invoicing and n8n for automation.

Step 1: Job finished

You finish a logo. In Notion, you move the project card to the “Completed” column and fill in the “Amount” field (€300).

Step 2: Automation trigger

N8n watches for changes in that Notion database every 5 minutes (webhook if Notion supports it, polling if not). It detects that there’s a new card in “Completed”.

Step 3: Invoice generation

N8n reads the client, description and amount from Notion, calls the Stripe Invoicing API and creates the invoice. Stripe assigns a number, calculates VAT and generates the PDF.

Step 4: Sending to the client

Stripe emails the invoice to the client, with your customised template and a payment link (card or bank transfer).

Step 5: Reminders

If after 7 days the invoice is still unpaid (Stripe knows because nobody has clicked the link), n8n sends a friendly reminder by email. At 15 days, a firmer one. At 30, you can set it to alert you via WhatsApp or Telegram so you can phone them yourself.

Step 6: Payment and reconciliation

The client pays by card. Stripe automatically marks the invoice as paid. N8n updates the status in Notion (“Paid”), adds the payment date and triggers a thank-you email.

If the client pays by bank transfer, you can connect n8n to your bank’s API (Revolut, for example) so that it detects the incoming payment and marks the invoice as paid when the amount and reference match.

Step 7: Accounting

N8n exports the paid invoice’s data to your accounting Google Sheets spreadsheet or emails it to your accountant. If you use Holded or Quaderno, the integration is direct and everything is recorded without you touching a thing.

How to start without breaking what you already have

If you’ve never automated anything, don’t try to build it all at once. Go in phases:

Phase 1: Automate invoice generation

Start by logging finished jobs in a Google Sheets spreadsheet. Each time you add a row, Zapier or n8n creates the invoice in your invoicing software. You still send it by hand, but you no longer fill in fields.

Phase 2: Automatic sending

Add one more step: as soon as the invoice is created, the system emails it to the client. Now all you have to do is add a row to the spreadsheet and forget about it.

Phase 3: Payment reminders

Set it up so that if the invoice isn’t marked as paid within X days, a reminder is sent. This requires your invoicing software to have a webhook, or the automation to check the status every day.

Phase 4: Bank reconciliation

Connect your bank and automate it so that when a payment comes in, the right invoice is marked as paid. This is the most technical phase because each bank has its own API and its own way of exposing data.

Phase 5: Updating the CRM and accounts

You close the loop: the paid invoice updates your CRM, your accounts spreadsheet and any other system you use.

You don’t have to reach phase 5 to save time. Even with phases 1 and 2 alone you can win back part of that time.

When it makes sense to hand over the integration

Setting up these automations doesn’t require coding, but it does require understanding workflow logic, reading API documentation and debugging errors when something doesn’t work. If your time is worth more than the cost of handing it over, or if your stack is complex (several CRMs, several payment gateways, a bank with no API), it may be quicker to have someone set it up for you.

STAKKER works with a prior diagnosis and a tailored proposal. There are no fixed prices because every autónomo has different tools, different volume and a different tolerance for risk. The typical process:

  1. A free diagnostic session where we map your current flow, your tools and your pain points.
  2. A proposal with a fixed scope: what gets automated, what stays manual, which tools are used, estimated time.
  3. Phased implementation, testing each phase before moving on to the next.
  4. Handover with documentation so you know how it works and can adjust it yourself if needed.

If you’d rather build it yourself, go ahead. If you’d rather have someone leave it up and running for you, get in touch and we’ll look at your case.

Frequently asked questions

What tools do I need to automate an autónomo’s invoicing?

A CRM or spreadsheet that records jobs and clients, invoicing software with an API (Holded, Quaderno, FacturaDirecta, Stripe Invoicing if you take payments online), and an automation layer such as n8n, Zapier or Make that connects the two. If you take payments by card terminal or bank transfer, add a connection to your bank via API or statement downloads.

How much time do I save by automating invoicing and payment collection?

It depends on volume. An autónomo with a fair number of jobs each month can go from spending several hours a month on invoicing to simply reviewing exceptions. The biggest saving is in payment reminders (zero manual time) and bank reconciliation (from a weekly task to an automatic one).

Can I automate recurring invoices or only one-off ones?

Both. Recurring ones are the simplest: you define a template, issue date and client, and the system creates them on its own. One-off ones need someone (you or a CRM) to log the job, but from there the rest is automatic: generating the invoice, emailing it, scheduling a reminder.

What happens if a client pays in cash or with Bizum?

These payments don’t usually have an API. The typical solution is a quick form (web or WhatsApp) where you or your team confirm the payment manually; the automation marks the invoice as paid, updates the CRM and stops sending reminders. You can also use a Telegram webhook or a button in your internal dashboard.

Is it legal to send automatic payment reminders to clients?

Yes, as long as you have a legitimate basis (a prior contractual relationship) and don’t send unsolicited commercial communications. A reminder about an unpaid invoice isn’t advertising, it’s debt management. That said, keep the tone civil, mind the frequency (don’t harass) and offer a way to get in touch if there’s an error or dispute. This isn’t legal advice; check with your adviser if you have doubts.

Do I need to know how to code to build this system?

Not if you use no-code tools such as Zapier or Make with templates. You do need logic (understanding what triggers what) and patience to connect APIs. If you want full control and zero cost on integrations, self-hosted n8n is the best option, but it requires a server and some reading of documentation. If you don’t have the time, you can hand the setup over to someone who knows your stack.

Next step

If you want to automate your invoicing and payment collection but don’t know where to start, ask for a free diagnosis. We map your current flow, identify what can be automated now and what requires changing tools, and give you a fixed-scope proposal.

If you’d like to explore automation more generally, read the automation page or the guide to n8n if the self-hosted option interests you. And if you want to see how to connect your CRM to other channels (WhatsApp, email, calls), there’s more info in AI automation.

Every case is different. Every stack is different. What works for a freelance designer doesn’t work the same way for a consultant who invoices €10,000 projects every quarter. That’s why we work with a prior diagnosis, with no catalogue prices. Get in touch and we’ll look at your case.

More articles