How e-invoices are delivered

An e-invoice is structured data that the receiver’s own invoice system reads, not a document the debtor opens. Quiddly sends it through its e-invoice broker, Crediflow, which delivers it on to the receiver. The client is the sender, not Quiddly.

There are two routes, both chosen with the E-invoice distribution channel:

Route	For	Network
Company e-invoice (B2B)	Debtors that are companies	Peppol, through the receiver’s operator
Private person e-invoice (B2C)	Debtors that are private persons	The consumer banks’ e-invoice network (e-faktura)

The debtor decides which route an invoice takes. An invoice goes the private person route only when every condition under Private persons is met. Otherwise it is sent as a company e-invoice.

What Quiddly sends

For every e-invoice Quiddly builds an XML document from the invoice and sends it to the broker together with the invoice PDF, and the invoice attachment if there is one.

Format. There is no single format for everyone. Quiddly builds the XML in UBL 2.1. By default it uses an older Peppol layout, and a client can instead be set up to send Peppol BIS Billing 3.0. Which one a client gets is a setting that Quiddly support manages. The broker delivers the document to the receiver’s operator.
Sender. The sender is the client. Quiddly finds the client at the broker from the client’s E-invoice Reference B2B (GLN or Peppol ID) and organisation number.
VAT number. The client’s VAT number is sent as the sender’s VAT identifier in the XML. Fill it in on the client, because without it that tag is missing and the receiver’s validation can fail on it.
Layout at the receiver. The XML holds the invoice data, and the Quiddly PDF travels as an attachment. The invoice the debtor sees in their own system is built by the receiving system from the XML, so Quiddly cannot control its layout, and it can look different from the PDF.

How the receiver is found

For a company e-invoice Quiddly asks the broker which party the debtor is. It tries these in order and stops at the first search that gives exactly one party:

The debtor’s organisation number together with E-invoice reference B2B (the GLN).
The debtor’s Peppol ID, if one is set.
The GLN alone.
The organisation number alone.
If the debtor has no organisation number, the organisation number inside a Swedish VAT number.

When exactly one party is found it is saved on the debtor and used for later invoices. The receiver must also accept e-invoices from the sender. If it does not yet, Quiddly sends an invitation to the debtor’s e-mail address automatically and the invoice fails until the receiver has accepted it. An invoice can therefore fail for a missing e-mail address on the debtor as well.

If no party, or more than one party, is found, the e-invoice fails with the message search receiver party must have only one result. Quiddly then opens an errand of the type Failed E-invoice no receiver for that debtor, with the reason and the parties that matched. The same happens on the sending side, as Failed E-invoice no sender, when the broker cannot identify the client uniquely.

To fix a receiver that is not found uniquely:

On the debtor, open the E-invoice section and check E-invoice reference B2B, Peppol ID and the organisation number. On the invoice and on the client, the + next to E-invoice Reference B2B opens Search E-invoice reference B2B, where you search the broker by GLN, Peppol ID, organisation number and country code and choose the match.
If several parties share the same details, a more specific GLN or Peppol ID is needed, and the end customer may have to update their GLN with their own operator.

If the e-invoice fails and the invoice allows it, the next channel in the client’s fallback order is used, see Onboard Client. An errand is opened when the invoice does not allow a fallback channel, or when the e-invoice fails validation.

Private persons (B2C)

A private person receives the invoice in their internet bank. An invoice goes the private person route only when all of these are true:

The debtor is a private person and Allow e-invoice is ticked on the debtor.
The client has a B2C e-invoice issuer address. This is the address that e-invoice sign-ups in the banks are registered against. It is Default B2C e-invoice issuer address on the client. For Norway it is set per country under B2C e-invoice issuer address per country. A client that is based in another country, for example one in a Swedish environment, needs a NO address there to reach Norwegian recipients.
The debtor has a B2C e-invoice recipient address. Quiddly looks it up once and saves it on the debtor. It exists only when the person has signed up in their internet bank for e-invoices from that sender, so a person who has not signed up is not reachable this way.

The invoice also has to be distributed by E-invoice: either it is booked with E-invoice as its distribution method, or E-invoice comes up in the client’s fallback order on the Distribution tab, where the channel must be Enabled.

The Distribution tab of a client showing the distribution channel rows, including the E-invoice (ELECTRONIC_INVOICE) channel with its Enabled checkbox.

The private person route uses the same E-invoice channel in every country. It is a different channel from KIVRA, which is the digital mailbox and a separate channel in the distribution settings.

When it does not go out

What you see	Likely cause	What to do
search receiver party must have only one result, or the errand Failed E-invoice no receiver	The broker found no party, or several, for the debtor’s details	Check E-invoice reference B2B, Peppol ID and the organisation number on the debtor
Failed E-invoice no sender	The broker found no client, or several, for the client’s details	Check E-invoice Reference B2B and the organisation number on the client
The receiver is invited and the invoice fails	The receiver has not accepted e-invoices from the client	Make sure the debtor has an e-mail address, and ask the receiver to accept the invitation
The receiver’s invoice looks different from the PDF	The receiving system builds its own image from the XML	Nothing to fix on Quiddly’s side
No e-invoice attempt at all, and no error	The invoice is on the Reminder service product, where Quiddly does not distribute the invoice	E-invoice needs a product where Quiddly distributes the invoice
A reminder or interest invoice was not sent as e-invoice	Reminders are not distributed as e-invoice, and interest invoices only go in Peppol BIS 3.0, never to private persons	Use e-mail or letter, see Setup Invoice Profiles