Network Exchanges
Network Exchanges: send and receive documents through official networks
Network Exchanges turns each invoice you issue into an e-invoice in the EU standard (EN 16931), ready to download. Where Enlivy is connected to a national e-invoicing system, today Romania's, it also sends and receives them for you.
Create your first e-invoiceFree account, no card needed.
NETWORK EXCHANGES
E-invoices in the EU standard, from your invoices
Create each e-invoice from its invoice. Where Enlivy is connected to the national system, it also sends and receives them.
Every invoice can become an e-invoice in the EU standard (EN 16931), as a Peppol BIS 3.0 file or a national variant. In Romania, Enlivy sends your invoices, brings in the ones addressed to you and shows each status. Elsewhere, you download the file and submit it yourself.
-
Where Enlivy is connected:
invoices go out and come in without uploading files to a government portal by hand.
-
Requirements differ by country:
check which format and channel your country, and your client's, require.
-
Incoming invoices every hour (Romania)
In Romania, Enlivy checks eFactura, the e-invoice system of ANAF, Romania's tax authority, every hour. You review each incoming invoice, then record it or link it to one you already have.
-
Submit to ANAF from Enlivy (Romania)
Submit your invoices for Romanian clients and follow each one until ANAF accepts or rejects it.
-
Every status in one list
See incoming invoices and the status of the ones you submitted in the same list.
-
Linked to the invoice
Each e-invoice sent or received stays linked to its invoice, and you can tag it.
E-INVOICING, EXPLAINED
What e-invoicing is, and which part Enlivy does
An e-invoice is an invoice that software can read without anyone retyping it. Here is what the standards mean, what Enlivy creates and what you still do yourself.
An e-invoice is data, not a PDF
An e-invoice is a structured file, usually XML, that your client's software reads field by field. A PDF is a picture of an invoice for people to read.
EN 16931 sets what an e-invoice contains
EN 16931 is the European standard for the content of an e-invoice: which details it carries, such as seller, buyer, lines and VAT, and what each one means.
Two XML formats, and a PDF with the data inside
An EN 16931 invoice is written as Peppol BIS 3.0 or CII. Factur-X (ZUGFeRD in Germany) is the invoice PDF with the CII file inside. A country can add rules: a national variant.
What Enlivy creates
Peppol BIS 3.0, CII, a Factur-X / ZUGFeRD PDF, and the national variants of six countries, XRechnung in Germany among them. Enlivy checks each file against its rules first.
Where Enlivy sends and receives
Today, Romania's system, for Romanian businesses invoicing Romanian clients. Invoices and credit notes go out; supplier invoices and client objections come in.
What you do everywhere else
Issue the invoice, download its e-invoice file and submit it through your Peppol access point or your country's channel. Enlivy is not a Peppol access point.
FULL LIFECYCLE
A full history for every exchange
In Romania, see what happened to each invoice at ANAF, and when.
Each invoice keeps every exchange with ANAF: when it was received or submitted, its status and the files to download (XML, PDF, ANAF's signature).
-
Track the full lifecycle:
every exchange, from reception to final status, is kept with its date and status.
-
Every attempt stays:
a rejected submission stays on the invoice, next to the corrected one you send after it.
-
See every step
When each invoice was received or submitted, and with what result.
-
Status at a glance
Each exchange shows its status, from pending to accepted or rejected.
-
Checks before sending
Enlivy checks required details, such as your Romanian tax ID (CUI), before a submission goes to ANAF. ANAF's own checks show in the status.
-
Everything in one list
Manage every exchange from one list, with the invoice it belongs to.
THE ANAF CONNECTION
What the ANAF connection does in Romania
Once you connect Enlivy to ANAF, you receive supplier invoices, submit yours and see each status in Enlivy.
- Incoming invoices arrive on their own, or when you ask
Enlivy brings your incoming invoices in from eFactura, so you no longer download the XML files by hand.
- Submit outgoing invoices to ANAF
Submit invoices for Romanian clients to ANAF from Enlivy, yourself or on the schedule you set, and see the status of each submission.
- Review and record without retyping
See the XML data of the incoming invoice next to its fields, then link it to an invoice you already have in Enlivy or record it as a new one.
- See client objections on the invoice
When a client objects to your invoice in eFactura, the objection shows on it. Once ANAF accepts the credit note that corrects the invoice, the objection closes as corrected.
Search
Search by invoice number, company name, tax ID, incoming or outgoing, and more
Results update as you type. Open any exchange to see its details.
Getting started in Romania
-
Connect with ANAF
Sign in to ANAF from Enlivy with the digital certificate you already use for SPV (ANAF’s online portal), on a USB token or installed on your computer, and approve the access. Your organization needs its CUI filled in.
-
Receive incoming invoices
Once connected, Enlivy brings in your incoming invoices on its own. You can also pull them yourself at any time.
-
Submit outgoing invoices
Submit the invoices you issue to Romanian clients to ANAF, yourself or on the schedule you configure, then check their exchange status.
CHOOSE YOUR SUBMISSION FLOW
In Romania: receive every hour, submit when you choose
In Romania, submit each invoice to ANAF yourself or on a schedule you set.
Once your Romanian organization is connected, Enlivy brings in your incoming invoices. You submit invoices for Romanian clients yourself, or turn on scheduled submission. Check each status, and act on a connection warning when one appears.
-
Incoming invoices, on their own:
new ones show in the same list as the invoices you submitted.
-
Scheduled submission:
once you turn it on, Enlivy submits invoices for Romanian clients to ANAF 1, 2, 3, or 4 days after the issue date.
-
Full control when you want it:
submit any invoice yourself at any time, and follow each submission by its status.
-
Review due dates
Choose a submission delay that fits the deadline that applies to your invoices.
-
See what happened
Check the result and any connection warning instead of assuming a scheduled submission succeeded.
INCOMING INVOICES
Review a suggested tax match before registering
When you open an incoming e-invoice from eFactura, Enlivy can suggest a matching tax class from the document and your configured rates. Review the invoice and the suggestion before saving; a missing match does not prevent you from continuing with the ordinary invoice form.
CONNECTION STATUS
Know when ANAF access needs attention
If ANAF blocks access for an expired authorization or a tax-identifier issue, Enlivy records the block and warns the organization. Review the stated reason, correct access, and resume syncing after the connection recovers.
EUROPEAN E-INVOICING COVERAGE
How e-invoices move in each country
For each EU country shown, Enlivy creates an e-invoice file in the EU standard. Check what your country's channel accepts.
-
Check your country
See whether Enlivy is connected to its system or gives you a file to submit yourself.
-
Ask about another connection
Tell us which institution matters to your business so we can assess the integration.
A file Enlivy creates is not proof that the receiving institution accepted it or that every local requirement was met. Check your country's rules before you submit it.
What is e-invoicing?
E-invoicing is sending an invoice as structured data that the receiving software reads on its own, instead of as a PDF or on paper. In the EU the content follows the EN 16931 standard, and the file is written as Peppol BIS 3.0 or as CII.
What is EN 16931?
EN 16931 is the European standard for what an electronic invoice contains: the details it must carry, such as seller, buyer, invoice lines and VAT, and what each one means. Formats such as Peppol BIS 3.0, CII and the national variants (XRechnung in Germany, for example) are ways of writing those details into a file.
Is a PDF invoice an e-invoice?
No. A PDF is made for people to read, while an e-invoice is a structured file that software can process. In Enlivy the same invoice gives you both: the PDF for your client and the XML file for the system that needs it.
Is Enlivy a Peppol access point?
No. Enlivy creates the Peppol BIS 3.0 file for your invoice, but it does not send it through the Peppol network. You submit the file through your own access point or your country's channel.
Which countries can I create e-invoices for?
An invoice that passes the EN 16931 rules can be downloaded as a CII file or as a Factur-X (ZUGFeRD) PDF, whichever country your client is in. A Peppol BIS 3.0 file needs the VAT numbers of both parties, and Enlivy does not create one for a party in Italy, Denmark, Finland or Sweden. When you or your client is in Austria, Germany, Italy, the Netherlands, Romania or Spain, you can also download that country's national variant.
Does Enlivy create XRechnung and ZUGFeRD invoices?
Yes. When you or your client is in Germany, you can download the invoice as an XRechnung file, in UBL or CII. Any invoice can also be downloaded as a ZUGFeRD (Factur-X) PDF, which carries the CII file inside. An XRechnung needs your contact name, phone and email, your payment instructions and a buyer reference. Enlivy has no field for a Leitweg-ID, the routing number German public bodies ask for, so check with a public body before you send it an XRechnung.
Does Enlivy export to DATEV?
Not yet. A DATEV export for your tax advisor is planned and not built. Today you give your advisor the invoice files (PDF, XRechnung or ZUGFeRD) and the monthly data export.
Can I invoice from Portugal with Enlivy?
Not as your certified invoicing software. Portugal asks most businesses to issue invoices from software certified by its tax authority, with an ATCUD code, a QR code and registered series. Enlivy does not have that certification. Certified invoicing for Portugal is planned and not available yet.
Does Enlivy send and receive e-invoices for me?
Only where Enlivy is connected to the national system, and today that is Romania's. A Romanian business sends its invoices and credit notes for Romanian clients from Enlivy, and receives supplier invoices every hour. Everywhere else you download the file and submit it yourself.
API reference
Network Exchanges from the API
Send e-invoices and pull the ones addressed to you, from your own code. A network exchange is one invoice sent to, or received from, a national e-invoicing system; today that system is Romania's (ANAF), for a Romanian organization invoicing Romanian clients. Enlivy builds the UBL document in the EU standard, sends it and follows the answer, so you know whether it was accepted, rejected or is still processing.
Exchanges are outbound (you submit an invoice you issued) or inbound (you pull documents addressed to you). This reference starts with the key action, pushing an invoice onto the network, then covers listing, inspecting, pulling inbound documents, and downloading the signed files. Every exchange carries a status you can poll.
Submit an issued invoice to a network institution. The invoice is the payload; there is no request body. Enlivy generates the compliant UBL, transmits it, and returns the resulting network-exchange record with its initial status. Which institutions an invoice can go to is exposed on the invoice itself.
/organizations/<organization_id>/invoices/<invoice_id> +1# 1. Discover eligible institutions for this invoice.
# invoice.peppol_exchange_push_options lists the institution ids you may push to;
# invoice.peppol_exchanges_pushed lists the ones already sent.
curl 'https://api.enlivy.com/organizations/<organization_id>/invoices/<invoice_id>' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json'
# 2. Push to a specific institution. The id is a string, e.g. "anaf" (Romania / ANAF).
# no request body, the invoice is the document
curl -X POST 'https://api.enlivy.com/organizations/<organization_id>/invoices/<invoice_id>/peppol/anaf' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json'
# The response is the network-exchange record. Poll its `status`:
# pending | processing | success | success_in_exchange_queue | success_pending_archive
# | change_required | rejected | rejected_at_exchange | failed | failed_credentials_expired
# A transport/connectivity failure to the institution returns HTTP 503. const baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const invoiceId = "<invoice_id>";
const institution = "anaf";
const headers = {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
};
// 1. Discover eligible institutions for this invoice.
// invoice.peppol_exchange_push_options lists the institution ids you may push to;
// invoice.peppol_exchanges_pushed lists the ones already sent.
const invoice = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/${invoiceId}` , {
method: "GET",
headers,
}).then((response) => response.json());
// 2. Push to a specific institution. The id is a string, e.g. "anaf" (Romania / ANAF).
// no request body, the invoice is the document
const exchange = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/${invoiceId}/peppol/${institution}` , {
method: "POST",
headers,
}).then((response) => response.json());
// The response is the network-exchange record. Poll its `status`:
// pending | processing | success | success_in_exchange_queue | success_pending_archive
// | change_required | rejected | rejected_at_exchange | failed | failed_credentials_expired
// A transport/connectivity failure to the institution returns HTTP 503. List every exchange with pagination and filtering: scope to one invoice, filter by exchange status or by the linked invoice’s state, and bound by date. This is how you build a compliance dashboard of what’s been sent and where each document stands.
/organizations/<organization_id>/invoices/network-exchanges # filters: status, organization_invoice_id, invoice_state (the linked invoice's state),
# created_at_from/to, updated_at_from/to, ids
curl -G 'https://api.enlivy.com/organizations/<organization_id>/invoices/network-exchanges' \
--data-urlencode 'page=1' \
--data-urlencode 'limit=20' \
--data-urlencode 'status=success' \
--data-urlencode 'include=invoice' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json' const baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
// filters: status, organization_invoice_id, invoice_state (the linked invoice's state),
// created_at_from/to, updated_at_from/to, ids
const query = new URLSearchParams({
page: "1",
limit: "20",
status: "success",
include: "invoice",
});
const result = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/network-exchanges?${query}` , {
method: "GET",
headers: {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
},
}).then((response) => response.json());Retrieve a single exchange: its status, the institution’s exchange and message identifiers, the raw institution response_json, and the names of the generated files. Include parsed_data to get the parsed contents of the exchanged document, or invoice for the source invoice.
/organizations/<organization_id>/invoices/network-exchanges/<peppol_network_exchange_id> # includes: organization, invoice, parsed_data (the parsed UBL as structured data), tag_ids
curl -G 'https://api.enlivy.com/organizations/<organization_id>/invoices/network-exchanges/<peppol_network_exchange_id>' \
--data-urlencode 'include=parsed_data,invoice' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json' const baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const peppolNetworkExchangeId = "<peppol_network_exchange_id>";
// includes: organization, invoice, parsed_data (the parsed UBL as structured data), tag_ids
const query = new URLSearchParams({
include: "parsed_data,invoice",
});
const result = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/network-exchanges/${peppolNetworkExchangeId}?${query}` , {
method: "GET",
headers: {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
},
}).then((response) => response.json());Fetch documents that were sent to you over an institution’s network, supplier invoices delivered through ANAF, for example. Enlivy retrieves and ingests them as inbound exchanges. Bound the sync with date_from.
/organizations/<organization_id>/invoices/network-exchanges/anaf/pull curl -G 'https://api.enlivy.com/organizations/<organization_id>/invoices/network-exchanges/anaf/pull' \
--data-urlencode 'date_from=2026-07-01' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json' const baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const institutionId = "anaf";
const query = new URLSearchParams({
date_from: "2026-07-01",
});
const result = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/network-exchanges/${institutionId}/pull?${query}` , {
method: "GET",
headers: {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
},
}).then((response) => response.json());Pull the artifacts of an exchange: the compliant UBL/XML document, its digital signature, and the human-readable PDF. Each returns a file stream.
/organizations/<organization_id>/invoices/network-exchanges/<peppol_network_exchange_id>/download +2# the signed UBL / XML document
curl 'https://api.enlivy.com/organizations/<organization_id>/invoices/network-exchanges/<peppol_network_exchange_id>/download' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
--remote-name --remote-header-name
# the detached digital signature
curl 'https://api.enlivy.com/organizations/<organization_id>/invoices/network-exchanges/<peppol_network_exchange_id>/download-signature' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
--remote-name --remote-header-name
# the human-readable PDF rendering
curl 'https://api.enlivy.com/organizations/<organization_id>/invoices/network-exchanges/<peppol_network_exchange_id>/download-pdf' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
--remote-name --remote-header-nameconst baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const peppolNetworkExchangeId = "<peppol_network_exchange_id>";
const headers = {
Authorization: `Bearer ${token}`,
};
// the signed UBL / XML document
const xml = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/network-exchanges/${peppolNetworkExchangeId}/download` , {
method: "GET",
headers,
}).then((response) => response.blob());
// the detached digital signature
const signature = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/network-exchanges/${peppolNetworkExchangeId}/download-signature` , {
method: "GET",
headers,
}).then((response) => response.blob());
// the human-readable PDF rendering
const pdf = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/network-exchanges/${peppolNetworkExchangeId}/download-pdf` , {
method: "GET",
headers,
}).then((response) => response.blob());Retrieve the institution-side status and validation details for an exchange, useful when a document comes back as change_required or rejected and you need the reasons to correct and resubmit.
/organizations/<organization_id>/invoices/network-exchanges/<peppol_network_exchange_id>/information curl 'https://api.enlivy.com/organizations/<organization_id>/invoices/network-exchanges/<peppol_network_exchange_id>/information' \
-H "Authorization: Bearer $ENLIVY_API_TOKEN" \
-H 'Accept: application/json' const baseUrl = "https://api.enlivy.com" ;
const token = process.env.ENLIVY_API_TOKEN;
const organizationId = "<organization_id>";
const peppolNetworkExchangeId = "<peppol_network_exchange_id>";
const result = await fetch(`${baseUrl}/organizations/${organizationId}/invoices/network-exchanges/${peppolNetworkExchangeId}/information` , {
method: "GET",
headers: {
Authorization: `Bearer ${token}`,
Accept: "application/json" ,
},
}).then((response) => response.json());Where it fits
Part of these setups
Each page follows one way of selling and shows what your client does, which features you use and what they cost.
- Agencies and studios Optional Adds sending and receiving e-invoices where Enlivy connects to the national e-invoicing system. Everywhere else, you download the EU e-invoice file (EN 16931, Peppol BIS 3.0) and submit it through your country's channel. See the setup
- Course authors Optional Adds sending and receiving e-invoices where Enlivy connects to the national e-invoicing system. Everywhere else, you download the EU e-invoice file (EN 16931, Peppol BIS 3.0) and submit it through your country's channel. See the setup
- Monthly billing Optional Adds sending and receiving e-invoices where Enlivy connects to the national e-invoicing system. Everywhere else, you download the EU e-invoice file (EN 16931, Peppol BIS 3.0) and submit it through your country's channel. See the setup
- Sales teams Optional Adds sending and receiving e-invoices where Enlivy connects to the national e-invoicing system. Everywhere else, you download the EU e-invoice file (EN 16931, Peppol BIS 3.0) and submit it through your country's channel. See the setup
Works together with
- Invoices Issue an invoice and email it to your client. A card payment goes to your own Stripe account and the invoice is marked paid. A bank transfer you mark paid yourself.
- Receipts Record money in and money out, keep the payment file with each receipt, and let Enlivy issue the receipt when you mark an invoice paid with one of the payment methods you set for automatic receipts.
- Taxes Give a product or invoice line a tax class, and Enlivy applies the rate that fits the customer's status and location. For companies based in 32 European countries, Enlivy keeps ready-made classes up to date.
- Payslips Your accountant works out the figures, and you record each amount in Enlivy on its own line, under your country's payroll code. Enlivy checks that the lines match the payslip's totals.
- Data Export Choose the period and the record types, and download one archive for your accountant, with a summary spreadsheet for each type if you want one. Free on every plan.
- MCP Connect Claude, ChatGPT, Cursor, or another MCP-compatible assistant to work with your invoices, contracts, and pipeline, within your own permissions.