Invoices

An invoice and a delivery note describe the same shipment from different angles. The invoice adds the payment and tax details a delivery note does not deal with. For many suppliers the invoice is the document their system produces first — and we can issue the delivery note from it.

ISDOC

The Czech national e-invoicing standard, maintained by the Czech Ministry of the Interior. It carries prices and VAT at line level plus a recapitulation per rate, so it covers everything a delivery-note header needs. Besides the goods data we take from it:

invoice number, issue date, tax point date and due date;
identification of both parties including VAT registration numbers, not just company IDs;
the VAT recapitulation per rate — taxable amount, tax and total for each rate;
references to the delivery note and to the customer's order.

The input formats are described in more detail under Accepted formats.

EDI INVOIC

The UN/EDIFACT EDI invoice, commonly in the GS1 EANCOM subset. Unlike a despatch advice it carries prices and VAT at line level, so a delivery note can be issued from it directly, without pairing it with another document. We process it including the Czech XML profiles of the ORION (GRIT) communicator — see EDI.

Invoice exports from accounting and ERP systems

Most accounting and ERP systems can export an invoice to XML or CSV. We handle such an export like any other input — the systems we commonly encounter are listed under Accepted formats. Mapping to the gateway input is on us during onboarding.

How it fits together

The invoice is one of three document flows running through the gateway. Orders come from the customer to you (Electronic orders); delivery notes and invoices travel the other way. All three can be handled in a single integration over a single channel.