[[brix:en:invoices]] **|** [[brix:en:fa_invoices]]
====== Sending invoices to F1 or F2.0 fiscalisation ======

Who issues paper invoices and until when is described in [[brix:en:invoices:einvoice:paper_invoices]].

If the company has the **//EP_IRA//** setting enabled, the system applies the **//F2.0//** protocol first when an invoice is approved. This applies to all invoice subtypes, including the sale of fixed assets. Companies without this setting cannot send eInvoices.

To send eInvoices the company contracts an information intermediary — **Moj eRačun (MeR)** or **ePoslovanje (Pondi)**; the contracting procedure is described in [[brix:en:integrations:mer]] and [[brix:en:integrations:eposlovanje]]. Support enters the intermediary's credentials into Brix based on a [[brix:en:tickets|support request]]. Fiscalisation under the **//F1//** protocol requires a FINA certificate, see the **//[[brix:en:companies:fiscal]]//** tab.

<note important>
Sending is automatic. When an invoice is approved, the system itself sends it for fiscalisation and delivery to the customer — after that the invoice is **not resent manually**.\\ Manual sending is used only to send a **copy** of an invoice already sent, as described in [[brix:en:invoices:resending]].
</note>

<note important>
The Fiscalisation 2.0 and eReporting system aims at real time. An eInvoice dated more than 15 days ago will pass through the system, but it may become a "red flag" in an audit, because an eInvoice must be issued at the moment of the business event or very soon after it.
</note>

**Exception — F1 fiscalisation**\\ The **//F1//** protocol is applied automatically in the following cases:

  - **Citizens (natural persons)**\\ The invoice is fiscalised under the **//F1//** rules for **all** payment methods. The obligation to send also depends on the //**{Delivery Territory}**// field — only //Domestic// delivery is fiscalised, see [[brix:en:invoices:basic]].
  - **Legal entities**\\ The invoice goes to **//F1//** fiscalisation if the payment method is //Banknotes and coins// or //Card//, provided that the //**{Delivery Territory}**// field is set to //Domestic//.

In all other cases — including legal entities paying by //Bank Transfer// — the invoice is sent under the **//F2.0//** protocol.

An invoice that was not sent to **//F1//** fiscalisation automatically is sent manually with the <color #ffffff/#da1c5f>**F1**</color> button on the **//[[brix:en:invoices:basic]]//** tab. The button is not shown on invoices sent under the **//F2.0//** protocol.

<note important>
Under the Fiscalisation 2.0 rules an eInvoice is sent **to legal entities only**. Invoices issued to natural and temporary persons cannot be sent as eInvoices — they go to fiscalisation under the **//F1//** protocol. The exception are natural persons registered in AMS, see [[brix:en:invoices:ams]].
</note>

<note>
The list of payment methods and their meaning is described in [[brix:en:o_nacinima_placanja]]. Which payment methods are available in a department is set in [[brix:en:departments:npl]]. Partners subject to public procurement also receive the //**{[[brix:en:partners:fina_id|FINA ID]]}**// with the eInvoice.
</note>

Every eInvoice line must carry a Classification of Products by Activity (KPD 2025) code of at least six digits; see [[brix:en:goods:kpd]].

<note tip>
Checking whether an invoice was actually fiscalised under **//F1//** is described in [[brix:en:invoices:fis1check]]. Payment of invoices sent under **//F2.0//** is reported automatically, see [[brix:en:invoices:ereporting]]; advance payments are handled in [[brix:en:invoices:rappf2]].
</note>

===== Customer did not receive the eInvoice =====

Whether an eInvoice was delivered to the customer is checked on the intermediary's portal, with the username and password received from it. Report the error to the **intermediary's technical support**, stating that you use the MICRO PROCESS software. Forward the reply you receive, with the invoice number, to us as a [[brix:en:tickets|support request]].

===== Attachments with an eInvoice =====

All documents in the invoice's **//[[brix:en:tab_dms]]//** tab at the moment of approval are sent with the eInvoice. The rules and limitations are described in [[brix:en:invoices:attachments]].