Skip to main content

Invoicing

What it is​

Module for electronic invoicing and for invoicing takings managed outside online payment.

The module keeps a local invoice register that mirrors the gateway: sent invoices to the Exchange System (SDI) and received invoices from suppliers. From here you can also compose an invoice, import an XML already transmitted to the Agenzia delle Entrate, create drafts from bookings and subscriptions not paid online, generate collective invoices per client and period, export the sales register with the VAT summary, and download the branded courtesy PDF.

The gateway remains the source of truth for transmitted invoices; the local register is used for search, checks, and export.

When it is visible​

The Invoicing section (Electronic invoicing group) appears with the enable_einvoicing flag and the finance.einvoicing permission. Administrators see all tabs; Pro profiles with permission can view receipts and sent invoices in read-only mode.

Main sectors​

  • All sectors with takings to invoice
  • Fitness and wellness
  • Appointment-based services

Dependencies​

Can be linked to:

Settings​

In the Settings tab (administrators only) you configure the gateway:

  • Provider: Fattura Elettronica API or OpenAPI.it;
  • Username / Password or API token depending on the provider (the status indicates whether they are configured, without showing the values);
  • Environment: Test or Production;
  • Default sender VAT number;
  • Tax data: series, fiscal time zone, and seller record (name, VAT number, tax code, tax regime, address, email);
  • Invoice copy texts: header (appears below the logo in the courtesy PDF), footer, and legal notes;
  • Prerequisites for online payments: verification of payment provider credentials, invoicing credentials, and seller tax data.

Use Check connection to verify credentials. Fields left empty keep the values already configured on the server.

Sender companies​

The Sender companies tab lists the companies registered on the gateway as invoice issuers. You can add, edit, and delete them, indicating company name, VAT number, tax code, address, legal form, tax regime, administrative contacts, legal representative, and IBAN.

Note: with OpenAPI.it, company name, tax identifier, and email cannot be changed after creation.

Received and sent​

Two tabs with search and pagination:

  • Received — invoices received from suppliers. Unread ones have a dot and feed the badge on the tab; opening the detail marks them as read.
  • Sent — invoices issued by Flo and imported invoices.

Common actions:

  • Sync — downloads updates from the gateway and refreshes the register; Sync this one refreshes a single invoice;
  • Export CSV — exports the sales register for the period (see below);
  • Offline invoice and Collective invoicing — available on sent invoices (see below).

From an invoice's detail you can:

  • download the PDF (the gateway's, where available), the branded PDF (courtesy copy with company logo and texts), the XML, and the SDI notification (where the provider exposes it);
  • Forward via email — sends the branded PDF to a recipient with an optional message (requires email sending to be enabled);
  • Resend an already transmitted invoice to the SDI;
  • Duplicate a sent invoice to reuse its data in a new one;
  • open the linked invoice when the document is a credit note.

Composing an invoice​

In the New tab (administrators only) you can:

  • fill in the structured fields: sender VAT number, recipient (with Prefill from customer to search a customer by name or email), document (type, date, number, reason, linked document), payment (terms, method, due date, IBAN), lines (description, unit price, quantity, VAT rate, unit of measure, VAT nature);
  • or send an already-validated FatturaPA raw XML, without reprocessing it (only for providers that accept XML).

Available document types: TD01, TD02, TD03, TD04, TD05, TD06, TD24, TD25. For TD04 and TD05, indicating the linked document (number and date of the original invoice) is mandatory.

Select Send invoice to transmit to the SDI.

Importing an XML from the Agenzia delle Entrate​

Also in the New tab you find Import XML from Agenzia delle Entrate: choose a complete FatturaPA XML and select Import into register. The import does not use provider credentials: it creates a local draft that you can review and send to the SDI from the Sent tab (see below).

Drafts and sending to the SDI​

A draft (imported, composed, or automatically generated) stays local until you send it:

  1. in the Sent tab the row is marked To send (or Credit note (draft) if it is a TD04);
  2. use the send icon in the row or the Send to SDI button in the detail;
  3. confirm: the draft is transmitted to the Exchange System with the configured provider.

If sending is rejected deterministically, the draft stays retryable with the attempt history and a translated error. If the outcome is uncertain, the invoice moves to Requires review and must be reconciled on the provider before retrying.

Offline invoicing​

For takings managed outside online payment, you can create drafts linked to the origin:

  • Invoice from booking — from the Sent tab → Offline invoice → Booking: enter the booking ID, the gross amount (optional; if empty, uses the activity price), and an optional description;
  • Invoice from subscription — from the customer subscription detail → Invoice, or from the Sent tab → Offline invoice → Subscription: the amount is pre-filled from the plan price and can be overwritten.

Rules:

  • a booking already paid online, covered by a subscription, or already invoiced cannot have a second invoice;
  • a subscription paid online is invoiced by the payments flow, not from here;
  • the invoice is born as a draft with its own fiscal numbering: review it and send it from the register;
  • the recipient uses the user's billing data; a valid tax code or VAT number is required.

Collective invoicing​

From Sent → Collective invoicing you generate one draft per selected client, aggregating over a date range:

  • bookings that are not cancelled, not paid online, not covered by a subscription, and not yet invoiced;
  • shares of plans started in the period, not yet invoiced.

Limits: maximum 366-day range, maximum 100 clients, maximum 200 lines per client. A period already invoiced for the same client cannot be invoiced again. For each client, the result indicates: draft created with number, nothing to invoice, period already invoiced, or error.

Sales register and VAT summary​

From Sent → Export CSV choose the period and download a file with:

  • one register row per sent invoice not in draft: date, number, document type, counterparty, VAT number, and total (credit notes have a negative sign);
  • one vat_summary row per VAT rate and nature, with taxable amount and tax, derived from the transmitted XML;
  • one unparsed row with the count of invoices whose XML is not readable, so the two sections stay reconcilable.

Limits: maximum 366-day range and 5,000 rows per export. The file is semicolon-separated and ready for Excel in Italian.

Credit notes​

Credit notes are TD04 documents linked to the original invoice (number and date). They are created:

  • from the composer, selecting TD04 and indicating the linked document;
  • automatically when a refund is confirmed after the invoice was issued: Flo prepares a TD04 draft linked, with the refunded lines and amount, to review and send from the register.

Drafts never reuse an already-assigned number, and an identical second refund does not create a duplicate document. If e-invoicing is off, the refund stays valid and the missing note is reported in the order.

Branded PDF and email​

  • Branded PDF: courtesy copy generated from the invoice data, with logo, header below the logo, footer, and configured legal notes. It is also available for received invoices.
  • Email forwarding: from the invoice you can send the branded PDF to any recipient with an optional message.
  • Automatic lesson email: after a booking payment, when the invoice is issued Flo sends the client an email with the PDF and a message identifying the purchase (activity and date). If email sending is disabled, sending results as Not sent.

SDI states​

In the register, the state is the one reported by the gateway. Flo treats successful transmission outcomes (INVI, PREN, CONS, NONC, ACCE, DECO) as confirmed and deterministic rejections (ERRO, RIFI) as cases to correct before retrying; an uncertain outcome stays in Requires review until verified on the provider.

  • To send — local draft not yet transmitted.
  • Sent — document transmitted, awaiting or with final SDI outcome.
  • Rejected / Discarded — deterministic rejection: correct the data and retry.
  • Requires review — unconfirmed outcome: verify on the provider before any retry.

Best practices​

  • Fill in the Tax data and invoice copy texts carefully: they apply to all company invoices.
  • Keep the series and fiscal time zone aligned with accounting.
  • Before sending an imported or refund-generated draft, re-read lines, amounts, and the linked document.
  • Use Sync regularly to align SDI states and the receipts badge.
  • Export the register at month end and keep the CSV with the VAT summary for the accountant.
  • If an invoice requires review, first verify on the provider portal and then retry from the register.