Invoicing overview

Reonic's invoicing module is built into the Portal, so you can bill your customers for a solar, heat-pump, or wallbox project without leaving the platform. Line items, prices, and tax rates carry over from the signed offer, and the documents end up where your project, contacts, and accounting integrations already live. This page is the section landing: what invoicing is, what it isn't, what you'll find under each sub-guide, and how it sits next to accounting tools like Lexoffice or Sevdesk.

What Invoicing in Reonic Is For

Invoicing turns a quoted project into the money documents that close out the job. It covers the installer to end-customer billing layer: what you charge your customers, across residential PV, heat-pump, and wallbox work in supported countries.

It's tightly coupled with Reonic offers. The fast path for any invoice is from a signed offer: pick the project, pick the variant, and the system auto-fills the line items, prices, tax rates, and contact data, so what was quoted is what gets billed.

You can also bill a customer for general services that aren't tied to a project. Use the from scratch path inside the Invoicing tab: skip the project picker and add line items by hand. See [Invoice](./invoice.md) for details.

What invoicing in Reonic isn't. It's not a full accounting suite. Reonic produces the customer-facing money document and tracks its lifecycle and payment status; book-keeping, VAT returns, and payroll stay in your accounting tool of choice, whether that's DATEV, Lexoffice, or Sevdesk. See Accounting integrations below for how the two layers connect.

Find and Enable Invoicing

Invoicing is a top-level tab in the Portal, a peer to Requests, Offers, Installations, and Settings rather than nested under any of them. The default landing screen is the Document Groups list, with one row per project-and-customer pair plus a count of related documents.

If you don't see the tab in your navigation, run through these checks in order. The first one that applies is your blocker:

1. Country support. Money documents are available to issuers in Germany, Austria, Switzerland, France, the UK, Jersey, and the French overseas territories (see Statutory requirements below).
2. Your role and per-user right. You need Editor or higher, plus the per-user Invoicing right switched on. An admin sets this in Settings > Company settings > Users & Teams. Accounts with the Viewer role can't create invoicing documents, and the create actions stay hidden for them.
3. Issuing details. An admin completes Settings > Company settings > Invoicing > Issuing details once. Until this is filled in, every create action blocks with the banner "You have to set your company information before creating any documents and review the document prefixes & number circles."

Set Up Issuing Details

Set up issuing details once before any document can be created. This is an admin task (an Editor with the Invoicing right reaches every create action but not the Issuing Details page). It takes about five minutes.

1. Go to Settings > Company settings > Invoicing > Issuing details.
2. Enter your company's legal name, address, VAT number, and registry details. This issuer block prints on every document you send.
3. Set the document number prefixes you want on each document type, for example INV- for invoices, PA- for partial or advance-payment invoices, CN- for credit notes, OC- for offer confirmations. Each document type has its own counter and prefix template.
4. Enter your bank account details. Optionally enable the EPC QR-code payment block, useful for DACH customers paying via their banking app.
5. Click Save.

Every Editor-or-higher in your workspace with the Invoicing right can now create and send documents.

The same issuer block appears on every document, company-wide; there's no per-document override. If your company invoices under multiple legal entities, talk to your Reonic account manager about your setup. This is also the page where you later update your bank details, IBAN, or EPC QR block. Changes apply to documents issued from that point forward; documents already in Issued status stay unchanged.

Grant Invoicing Access to a Colleague

By default, new colleagues can see the Invoicing tab but can't issue documents. Give them access in three steps:

1. Go to Settings > Company settings > Users & Teams, then select the colleague you want to grant access to.
2. Set their role to Editor or higher and switch on Invoicing.
3. Click Save.

The user picks up the change on their next page load. To revoke later, switch the per-user Invoicing right off in the same place; the rest of the user's permissions stay untouched. This is also how you keep the Invoicing tab out of view for colleagues who should work only in your external accounting tool.

What Invoicing Capabilities Exist

The module covers a full set of money and supporting documents. Each has its own sub-guide.

Money documents (available to supported issuer countries, see Statutory requirements below):

• [Invoice](./invoice.md): the main full or final invoice for a finished project, called Schlussrechnung in German. Most projects need one.
• Partial invoice: bill a project in stages, with four flavours (Advance Payment, Progress, Partial, Completion) and three generation modes (Percentage, Scheme, Remaining). Useful for staged billing on long projects, for example 30% deposit, 40% interim, 30% completion.
• Credit note: comes in two kinds. A reversal credit note reverses all or part of an issued invoice; this is the refund and correction path, since refunds are modelled exclusively as credit notes. A standalone Commission credit note is a self-billing document created from a contact, with no parent invoice and no VAT, used for paying out commissions. You create each one yourself.

Supporting documents (available in every country, no country gate):

• Offer confirmation: confirms an accepted offer before invoicing. German-speaking installers use this as their Auftragsbestätigung; the prefix is free text. Convert it into an Invoice in one click via Duplicate into type.
• Purchase order: your company orders from a supplier. Same document mechanics as an invoice, just facing the other way (your customer here is your supplier).
• Delivery note: records what physically arrived on site, with line items. A per-document hide-pricing option lets you issue it as a pure goods list, items and quantities only, no prices or totals.
• Letter: a free-form document (title, subtitle, message, locale) with a number and PDF, for formal customer correspondence that doesn't fit any of the other types.

Reimbursement. Reonic doesn't have a dedicated Reimbursement document type. The closest workflows are a credit note (when you're refunding money already paid) or a partial invoice with a negative adjustment (when reimbursing for a specific component). Talk to your accounting partner if your jurisdiction requires a distinct Erstattung document.

All documents share the same Draft > Issued > Voided lifecycle, the same per-workspace numbering with type-specific prefixes (INV-, PA-, CN-, OC-), and the same rule that documents stay unchanged once Issued. The same editor pattern applies across all types (line items, rebates, locale, footer), with type-specific fields appearing as relevant. The supporting-document editor drops the money-specific fields: no Skonto (early-payment discount), no payment status, no QR code.

Staged Billing with Partial Invoices

When a project is large or long enough that a single final invoice at the end isn't workable, bill it in stages. The fast path is from the signed offer: create the Final Invoice first (it can stay in Draft), then click Create partial invoice off it. Pick a generation mode and a flavour label per row (Advance Payment, Progress, Partial, Completion):

• Percentage: for example 30% deposit, 60% interim, remaining.
• Scheme: preset multi-row patterns like 30/40/30 or 50/50, spawned in one batch.
• Remaining: the open balance after earlier partials.

Each partial inherits the offer's line items, tax rates, and currency, so what was quoted is what gets billed. Partials sum against the parent Final Invoice automatically, so the customer is billed once for each line item.

Accounting Integrations

Reonic invoicing produces customer-facing money documents; the books live in your accounting tool. Reonic talks to the major German-speaking tools, plus a regional option for Switzerland.

Supported integrations (configured on the offer and signature side, not on each invoice send):

• Lexoffice — Germany — Customer + offer + signed-document records — Manual: Send to [tool] on the signed offer
• Sevdesk — Germany — Customer + offer + signed-document records — Manual: Send to [tool] on the signed offer
• Bexio — Switzerland — Customer + offer + signed-document records — Manual: Send to [tool] on the signed offer

For DATEV, the pattern installers use is a monthly close-of-month: run the Download data action at Invoicing > Reports, which produces a ZIP (a summary.csv plus the issued invoice PDFs). The CSV isn't DATEV-formatted; hand it to your tax adviser, who maps it on the DATEV side.

What this means in practice. Keep one system of record per invoice. Either invoice in Reonic and use the monthly export for your DATEV or Lexware close, or invoice in Lexoffice and leave Reonic invoicing switched off for those users. Issuing the same invoice in both places creates double records.

Your Reonic Subscription Billing

There are two billing relationships in Reonic, and they're easy to mix up.

1. You (installer) to your end customer. This is the Invoicing tab. Reonic produces the document; you collect payment.
2. Reonic to you (installer). This is your Reonic subscription. Reonic produces the document; you pay Reonic.

For the second one (what Reonic charges you, where your Reonic invoice lives, how you pay your monthly subscription), go to Settings > Company settings > Licenses & Billing. Open any line to view or download the PDF. The Invoicing tab shows the documents you issue to your customers, not your own subscription invoices.

When a teammate asks "where do I see invoices," disambiguate first: invoices you've issued to customers (the Invoicing tab) are a different surface from invoices Reonic charged you (Settings > Company settings > Licenses & Billing). The two share nothing.

Payment Options for End Customers

When you send an invoice, the only payment detail it carries is a bank-transfer instruction: your IBAN, plus an optional EPC QR code for scan-to-pay. There's no payment-type selector on the document: no Pacht (lease), no financing, no direct debit or SEPA, no card. Pacht exists only as an offer-economics view tied to Bees & Bears, and never flows into invoicing, so a customer asking to invoice a leased installation hits two walls at once: commercial projects are blocked (see below), and there's no lease payment mode even on residential.

On the invoice PDF:

• Bank transfer. Your IBAN and BIC from issuing details print on the receipt PDF by default. The customer transfers the amount manually; you reconcile when the money lands.
• EPC SEPA QR code (optional, DACH-friendly). A scannable QR on the receipt PDF pre-fills IBAN, amount, and remittance in the customer's banking app. It cuts down on typos and makes reconciliation easier. Enable it per-invoice or set the default in issuing details.

Not on the invoice:

• Point-of-sale (POS) payment. Reonic doesn't provide an in-app pay-by-card or POS terminal flow for end customers. There's no pay-by-link, no card payment, no pay-via-Reonic surface. Customers pay you offline.
• Direct debit or SEPA mandate. Reonic doesn't manage SEPA mandates or auto-charge. If you collect via SEPA direct debit, the mandate lives outside Reonic; you mark the invoice paid when the debit clears.
• A customer payment portal. End customers don't have a Reonic-hosted page to view or pay invoices. The PDF in the email, plus the receipt PDF with bank details and EPC QR, is the entire customer-facing surface.

The customer-facing surface is the PDF in the email plus the receipt PDF, and customers pay by bank transfer. If proactive transparency matters to your customers, email them when invoices, partial invoices, or credit notes are issued.

Financing. Reonic integrates with financing providers, including Bees & Bears and EOS, on the offer side. The financing handshake happens at offer signature, so by the time an installation invoice is issued, the financing is already routed via the offer. For the providers available in your workspace, contact the support chat.

Activation and Access

Three things enable invoicing:

1. Country. Your issuer country must be on the supported list.
2. Role and per-user right. Editor or higher, plus the per-user Invoicing right switched on.
3. Issuing details. A one-time admin task in Settings > Company settings > Invoicing > Issuing details.

To give a specific colleague access, see Grant invoicing access to a colleague above.

If your workspace doesn't show the tab and your country is supported, the most likely cause is that issuing details haven't been set up yet.

Statutory Requirements: e-Invoicing, e-Rechnung, SDI, Factur-X

The rules for what counts as a legally valid invoice diverge fast, country by country. Here's where Reonic sits.

Supported issuer countries (the country gate):

• Germany (DE)
• Austria (AT)
• Switzerland (CH)
• France (FR)
• United Kingdom (UK)
• Jersey (JE)
• French overseas territories: Martinique, Guadeloupe, Réunion, Saint-Martin, Saint-Barthélemy, Saint-Pierre-et-Miquelon, French Guiana

Inside this list, the Invoice, Partial Invoice, and Credit Note options are available. Supporting documents (offer confirmation, purchase order, delivery note, letter) work everywhere with no country gate, so an installer outside this list can still issue offer confirmations and delivery notes through Reonic, just not the money documents.

Country-specific behaviour inside the supported list. The editor looks the same in every supported country. Country-specific VAT rules (DE Kleinunternehmer, FR TVA mention, UK CIS), legal text, number-format conventions, and PDF templates apply automatically based on your issuing-details country.

Statutory e-invoicing formats. Reonic generates standard PDF invoices. For statutory artefacts that require a structured format, route through an accounting partner:

• Germany e-Rechnung / XRechnung. The XRechnung XML format required for certain German B2B and public-sector scenarios isn't produced by Reonic; generate it in your accounting tool downstream.
• Italy SDI (FatturaPA). Italy isn't on the supported issuer list. Reonic doesn't generate FatturaPA XML and doesn't push to SDI.
• France Factur-X / Chorus Pro. Reonic generates standard PDF invoices for FR issuers. The hybrid PDF+XML Factur-X format isn't produced by Reonic, and Chorus Pro submission isn't integrated.

In each case, Reonic invoicing can still serve as your internal project-billing layer, with the compliant invoice generated downstream.

Exports, Reports, and Dashboard Figures

Reonic invoicing produces customer-facing PDFs; the reports layer aggregates those documents for sales tracking, tax-adviser hand-off, and dashboard reporting.

Export to your tax adviser. There's no scheduled or automatic push of invoices to a tax adviser, and no DATEV-formatted export. The standard pattern is a monthly close-of-month: an admin opens Invoicing > Reports > Download data and downloads a ZIP (a summary.csv plus the issued invoice PDFs), then hands the CSV to the tax adviser, who maps it on the DATEV side. Lexoffice, Sevdesk, and Bexio receive the customer and signed-offer records when you click Send to [tool] on the signed offer, a manual step at the offer stage (see Accounting integrations above); the issued invoice itself isn't auto-pushed.

Export per-customer sales data to Excel. From Invoicing > Reports, the Download data export ships as a ZIP whose summary.csv you open in Excel or Google Sheets and filter by customer to get a per-customer sales history. There's no in-app Export to Excel button on a customer page; the Reports download is the route.

What the Reports dashboard shows. The Reports surface (Invoicing > Reports) reports invoicing totals only: invoiced, collected, outstanding, and overdue, across an Overview tab and a Collections tab. There's no win-rate, no pipeline metric, and no drill-down by user, project type, or product category on this surface.

Net vs gross in the Reports dashboard. The editor on each invoice shows net, tax, and gross simultaneously. The Reports dashboard reports gross totals. If the tax-basis setting (accrual vs cash) in Settings > Company settings > Invoicing > Issuing details changes, the report can shift how a paid-in-period invoice appears; talk to your account manager if the figures look off.

What's in This Section

This Invoicing section has one sub-guide per document type and one cross-cutting reference:

• [Invoice](./invoice.md): full or final invoice creation, edit, void, credit note, payment tracking, lifecycle.
• Partial invoice: staged billing with the from-offer fast path; flavours and generation modes.
• Offer confirmation: confirms an accepted offer (the Auftragsbestätigung use case). Convertible to invoice.
• Letter: formal free-form correspondence with a document number.
• Reimbursement: refund workflows (credit-note-based).

Use the table of contents on the left to jump to a specific document type. If you're new to the module, start with [Invoice](./invoice.md): it covers the most common end-to-end flow and references the other documents along the way.

Things to Know

The clean mental model: Reonic is the document producer and customer-billing tracker, while your accounting tool is the book of record. Reonic shows you what you've billed and what's still owed; your accounting tool tells you what's in your books and what you owe in tax. Don't try to make Reonic do the accounting, and don't try to make your accounting tool produce the customer-facing PDF when Reonic's already doing it from the offer.

• Lexoffice, Sevdesk, and Bexio pushes are offer-side, not invoice-side. The push is the manual Send to [tool] step on the signed offer, not something that happens when you send the invoice.
• Commercial invoicing isn't supported. Commercial projects are blocked in the create modal. Use your accounting tool for commercial billing.
• Bulk actions don't exist. Each invoice is issued, sent, and marked paid individually. There's no list-view Issue all or Mark paid all. Archive is also per-document; there's no list-view multi-select archive. Archiving a Document Group cascades to all its children automatically, but archiving individual documents in bulk takes one click per document.
• Archive only affects list visibility. Draft and Voided documents (per-row), or a whole Document Group (cascade), can be hidden from default list views without changing their accounting state. Issued money documents can't be archived directly; void first, then archive the voided document. To clear the Overdue flag on an issued invoice, void it or update its payment status.
• Currency is one per document. You can't mix two currencies on one invoice. To switch currencies on an existing draft, void it and start over.
• No recurring or subscription invoicing. Each invoice is created manually, or duplicated from a previous document. If you bill maintenance contracts on a recurring cadence, that lives outside Reonic.
• No mobile invoicing surface. The Reonic Mobile App doesn't include the invoicing module; it's Portal-only.
• Installation completion doesn't auto-fire an invoice. When an installation closes, the Document Group exists, but issuing the final invoice is a separate manual action in the Invoicing tab.
• Skonto (early-payment discount) isn't a dedicated field in the editor. To apply one, use a document-level rebate with an if paid by [date] note in the description.

Last updated on October 2, 2026