Odoo Invoicing: Customer Bills, Payments, and Payment Follow-Up

Introduction

Odoo Invoicing is where operational reality becomes auditable numbers: invoices, bills, payments, and bank reconciliation should trace back to the sales or purchase documents that created them.

Finance teams often inherit data entry from colleagues because systems are not connected, which delays close, weakens cash visibility, and hides margin problems until too late.

The Invoicing module, together with the right localization, helps you post consistently, approve spend, and report by period without rebuilding journals in spreadsheets every month.

CFOs, controllers, and accounting managers evaluating Odoo will see how peers structure day-to-day finance, not only year-end reporting.

Invoicing is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Invoicing: Customer Bills, Payments, and Payment Follow-Up states the storyline for stakeholders approving budgets.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Invoicing.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Invoicing is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

Your controller exports three CSV files before every board meeting, then spends the weekend fixing VLOOKUP errors. Operations is not wrong on purpose; the invoices simply never matched the shipments in one system.

Finance teams spend too much time retyping operational data instead of analyzing exceptions. When invoices, bills, and bank lines are disconnected, close cycles drag and cash visibility lags.

Sound familiar? Teams usually hit these walls:

• Month-end built from exports instead of live sub-ledgers
• Approvals happening outside the system of record
• Tax or multi-company complexity handled in shadow spreadsheets

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Invoicing, and measure what changes.

Top 10 Invoicing Use Cases

10 use cases for Odoo Invoicing, ranked from Level 1 (easy, do it this afternoon) to Level 10 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Issue your first numbered customer invoice with VAT Level 1 — Easy

Level 1 is the simplest possible Invoicing action: one user, one customer, one invoice. No automation, no Sales link, just a clean PDF with the right VAT rate.

Here's how you'd do it in Odoo:

1. Open Invoicing, Customers, Customers, New, and fill in name, billing address, VAT number, and payment terms.
2. Go to Invoicing, Customers, Invoices, New, and pick the customer you just created.
3. Add one product line with quantity, unit price, and the right VAT rate; Odoo computes totals.
4. Click Confirm: the invoice gets a sequence number and moves to Posted.
5. Click Send and Print: the customer receives the PDF with all legal mentions.

What you get: A clean, numbered, legally compliant invoice goes out in 90 seconds, with zero Word template and zero retyping.

2. Bill a confirmed sales order in one click Level 2 — Easy

Level 2 introduces the Sales-to-Invoicing bridge: the Create Invoice button on every sales order. This is the first lever once Sales is also in Odoo.

Here's how you'd do it in Odoo:

1. Open the confirmed sales order in Sales, Orders, Orders.
2. Click Create Invoice and pick Regular invoice, Down Payment, or Final invoice.
3. Review the pre-filled lines, taxes, payment terms, and analytic distribution.
4. Click Confirm; the invoice posts with its own sequence number, linked to the sale.
5. Click Send and Print; the chatter logs the email and customer read receipt.

What you get: The sales-to-invoice cycle drops from ten minutes to a single click, and finance never retypes a quantity or a price again.

3. Activate online payment so customers pay from the PDF Level 3 — Easy

Level 3 adds the Pay Now button, an Invoicing feature that turns email into cash without your team chasing card details on the phone.

Here's how you'd do it in Odoo:

1. Go to Invoicing, Configuration, Payment Providers, and enable Stripe, Mollie, Adyen, or PayPal.
2. Paste the API keys, then toggle Test mode off when you are ready for production.
3. Send any posted invoice by email: the message body and the PDF embed a Pay Now button.
4. The customer pays by card; the invoice flips to In Payment, then Paid after bank reconciliation.
5. Failed payments raise an activity on the finance team for same-day follow-up.

What you get: DSO drops 10 to 15 days within a quarter, and finance focuses on exceptions instead of card-on-file calls.

4. Cancel and replace a posted invoice with a credit note Level 4 — Medium

Level 4 uses credit notes, the Invoicing feature that keeps corrections traceable. Mistakes become a clean audit chain, not a Tipp-Ex moment.

Here's how you'd do it in Odoo:

1. Open a posted invoice that contains the wrong amount or the wrong line.
2. Click Add Credit Note and pick Refund and Issue New, or Modify and Cancel.
3. Adjust the lines on the new draft and Confirm; the credit note gets its own legal number.
4. The credit note auto-reconciles against the original to neutralize the receivable.
5. Reporting, Credit Notes shows you patterns when the same customer keeps appearing.

What you get: Any auditor traces the full original, credit, replacement chain in under a minute, and finance stops dreading corrections.

5. Brand the invoice PDF with your logo, colors, and legal footer Level 5 — Medium

Level 5 uses Document Layout, the no-code customization Invoicing inherits from QWeb. One settings change updates every PDF your customers will ever receive.

Here's how you'd do it in Odoo:

1. Open Settings, Companies, and upload the company logo, then set the primary brand color.
2. Go to Invoicing, Configuration, Document Layout, and pick Bold, Striped, or Boxed.
3. Add a footer with IBAN, VAT number, support email, and the tagline you want on every PDF.
4. Click Preview on a sample invoice; check font, colors, page break, and totals block.
5. Send a test invoice to yourself before flipping the new layout on for real customers.

What you get: Invoices look like part of your brand; customers complain less and pay faster, and finance stops apologizing for the design.

6. Bill the same retainer customers every month with Subscriptions Level 6 — Medium

Level 6 connects Invoicing to Subscriptions, the bridge for recurring revenue. Retainers, SaaS, memberships, all renew without a recurring spreadsheet.

Here's how you'd do it in Odoo:

1. Install Subscriptions, then create a recurrence template with one month, no end date.
2. Create a product Monthly Retainer tied to the subscription template, with the right price and tax.
3. Sell the subscription once per customer; the contract handles every renewal date.
4. Configure the email template; include the period (Month, Year) in the subject line.
5. Verify the first auto-invoice fires on the next billing day; it is sent and paid online.

What you get: Recurring revenue is collected automatically; one operations hire avoided per 500 active contracts.

7. Chase late customers with automated follow-up levels Level 7 — Hard

Level 7 introduces Follow-up Levels, the dunning engine baked into Invoicing. This is the payment follow-up feature highlighted in the blog title.

Here's how you'd do it in Odoo:

1. Go to Invoicing, Configuration, Follow-up Levels and create tiers at 7, 14, 30, and 45 days.
2. Per level, set the email template, the optional call-back activity, and the stop-delivery flag.
3. On each customer record, pick a Follow-up Plan: Standard, Premium, or Strict.
4. Each morning, the scheduled action emails the right level automatically to overdue customers.
5. Finance's My Activities view only lists the red cases that need a human phone call.

What you get: Finance reclaims one full day a week, and cash arrives ten days earlier on average.

8. Switch on country e-invoicing for legal compliance Level 8 — Hard

Level 8 activates the e-invoicing layer: structured XML the tax authority can read. France 2026, Belgium Peppol, Italy SDI, all share the same Invoicing layer.

Here's how you'd do it in Odoo:

1. Go to Settings, Apps and install the country localization (France, Belgium, Italy, Spain).
2. Open Invoicing, Configuration, Electronic Invoicing and enable Peppol, Factur-X, or SDI.
3. Register the company on the access point or PDP; paste the credentials in Odoo.
4. Send any invoice: Odoo generates and signs the structured XML, then pushes it automatically.
5. Track delivery status (sent, received, accepted, rejected) directly on the invoice chatter.

What you get: Compliance with the 2026 mandate without a custom integration, and zero rejected filings.

9. Invoice in multiple currencies with analytic distribution per project Level 9 — Hard

Level 9 turns Invoicing into a margin sensor: multi-currency plus analytic distribution. Every invoice line carries the project, department, and FX truth.

Here's how you'd do it in Odoo:

1. Open Settings and enable Multi-Currency; activate the daily ECB rate refresh.
2. Go to Invoicing, Configuration, Analytic Plans and create Projects, Departments, Geographies.
3. On each invoice line, set an analytic distribution: for example 60 percent Project A, 40 percent Project B.
4. Issue the invoice in the customer's currency; the FX gain or loss entry posts at the day's rate.
5. Reporting, Invoiced Revenue, group by Analytic Account to see margin per project, per currency.

What you get: The CFO sees revenue and margin per project and per currency in real time, not as a year-end Excel reconstruction.

Designing analytic plans that survive a CFO change, and aligning Multi-Currency with the chart of accounts, is a typical Dasolo audit-grade setup.

10. Run an autonomous AR command center across Invoicing, Bank, AI, and Dashboards Level 10 — Expert

Level 10 is the full operating system: bank feed posts itself, AI scores who to chase, Helpdesk handles disputes, Knowledge runs the policy, dashboards refresh live.

Here's how you'd do it in Odoo:

1. Connect the bank feed (Plaid, Ponto, or direct bank API) so transactions land in Invoicing every morning.
2. Train an AI rule on past payment behavior; each open invoice gets a Safe to At Risk score.
3. Studio Automation: At Risk invoices trigger a priority follow-up and assign a senior collector.
4. Disputes raised in the customer portal open a Helpdesk ticket with the invoice and chatter attached.
5. Knowledge holds the collection playbook; one click loads the right tone, tier, and legal mention.
6. A Spreadsheet AR Live dashboard tracks DSO, aging, dispute rate, and AI accuracy in real time.
7. ISO 20022 SEPA payment files generate from the bank journal for reverse-payment runs to suppliers.

What you get: One AR operator does the work of a five-person team, DSO drops twenty plus days within two quarters, and finance stops being the bottleneck of cash.

Wiring the AI scoring, banking APIs, Helpdesk SLAs, Knowledge playbook, and live dashboards is the cross-app, banking-grade architecture Dasolo runs as a partner-led engagement. Most teams need an outside team to assemble these pieces correctly the first time.

When Expert Help Makes Sense

If levels 1 to 6 fit your world, you can often succeed with standard Odoo Invoicing, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 7 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Invoicing includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo