E-Invoicing: What to Know Before You Start

What e-invoicing is and how it differs from e-archive: choosing an integrator, integration methods, CRM connection and migration pitfalls.

An e-invoice is not a digital copy of a paper invoice but a new document type with its own rules. Most migration problems come from noticing that difference too late.

Note: this article is general information. Scope, thresholds and obligations change; consult your accountant.

E-invoice or e-archive?

E-invoice

Used when the recipient is also registered in the system. The invoice reaches them through the central platform and they can accept or reject it.

E-archive

Used when the recipient is not registered (most consumers and small businesses). The document is created electronically and delivered by email or a link.

In practice companies use both: e-invoices for corporate customers, e-archive for individuals. It matters that your system checks automatically which category the recipient falls into and picks the right type; deciding manually produces errors.

Integration options

  1. Portal: issuing invoices by hand in the integrator’s web interface. Adequate at low volume, but it means double data entry.
  2. Integrator integration: your own system (CRM/ERP) connects to the integrator’s service. The right balance for most businesses.
  3. Direct integration: connecting your own servers to the central platform. For high volume and special requirements; the technical burden is heavy.

Why the CRM connection matters

The invoice is the last link in the commercial chain. An e-invoicing system disconnected from the CRM produces these problems:

  • The same customer is registered with different details in two systems (legal name, tax number, address mismatches).
  • The sales team cannot see whether an invoice has been issued.
  • Payment status is not visible on the customer record.
  • Cancellations and refunds are run separately in two places.

Producing an invoice from an order record with one click is not only about speed but about data consistency.

Common migration problems

  • Incomplete customer data: without a tax number, tax office and legal name, no invoice can be issued. Screening customer records for these fields before migration is essential.
  • Name mismatches: if the official name on the central platform differs from yours, the document is rejected.
  • Wrong document type: issuing an e-archive document to a recipient within e-invoice scope is invalid.
  • Numbering: series and sequence rules must be defined in advance, with no gaps.
  • Retention: documents must be stored and remain accessible for the statutory period.

A migration plan

  1. Confirm scope and timing with your accountant.
  2. Choose an integrator; ask whether integration with your CRM already exists.
  3. Screen and complete the tax details on your customer records.
  4. Issue a few invoices in a test environment and view them from the recipient side.
  5. Plan a parallel period: check both flows during the first week.
  6. Train the team — especially on cancellation and refund scenarios.

Frequently asked questions

Can I cancel an invoice?

The rejection process for e-invoices and the cancellation rules for e-archive differ, and time limits apply. Learn these scenarios before you migrate; this is where panic most often happens.

Can I still issue invoices if the internet goes down?

Working through an integrator requires connectivity. Plan for outages (a mobile backup connection, preserving document sequence).

How do invoices issued from the CRM reach accounting?

The integrator creates the record; transfer to accounting software happens through the integrator or the accounting package. Settle who runs that flow at the outset.

Next step: to see invoicing from an order record, request a demo.