Reference
Documents and formats
The lists, for looking something up. Anything not here is a document type you can add yourself.
Document types
| Format | Types |
|---|---|
| EDIFACT | ORDERS, ORDRSP, DESADV, INVOIC, CONTRL, APERAK |
| X12 | 850, 855, 856, 810, 997 |
| UBL | Order, order response, despatch advice, invoice, credit note, project invoice, project credit note, reminder, application response |
The four UBL Danish standards are the sales invoice and its credit note, and the project invoice and its credit note. The module ships no formats; these are imported into Electronic Reporting and used as published, and are not something to author.
Business processes
| Process | Which document |
|---|---|
| Sales order creation | An order arriving from a customer |
| Sales order confirmation | Your answer to it |
| Sales order packing slip | The despatch advice you send |
| Sales order invoice | The invoice you send |
| Purchase order inquiry | The order you send a supplier |
| Purchase order confirmation | Their answer |
| Purchase order packing slip | Their despatch advice, or your goods receipt |
| Purchase order invoice | Their invoice |
| Project invoice | An invoice from the project module |
| Envelope acknowledgement | A receipt for one interchange |
| Document acknowledgement | A receipt for one business document |
The business process, not the document type, is what routes a message. That is why an extended acknowledgement type has to answer with an acknowledgement process in both directions.
Transports
| Type | Networks | Profiles |
|---|---|---|
| AS2 | Point to point only | Not applicable |
| AS4 | Peppol, NemHandel, or direct | Standard, eDelivery, eDelivery v2, ENTSOG |
| SFTP | Point to point only | Not applicable |
Identifier types
| Type | What it is |
|---|---|
| GLN | Global location number |
| EAN | The same, under its older name |
| CVR | Danish company register number |
| SE | Danish tax number |
| P | Danish production unit number |
| VAT | European VAT number |
| DUNS | Dun and Bradstreet number |
States, in one place
| What | Values |
|---|---|
| Tracker state | Settled, waiting, action, overdue, failed, superseded |
| Lifecycle stage | Created, transmitted, stored, processed |
| Health | Ok, degraded, failed |
| Acknowledgement layer state | Not expected, pending, positive, negative |
| Compare verdict | Green, yellow, red |
| Staging status | Not processed, processed, failed, rejected |
| Outbound queue status | Queued, sent, failed |
| Validation mode | Off, warn, block |
| Validation outcome | Valid, advisory, blocking, not applicable, unavailable |
| Confirmation line status | Accepted, changed, rejected |
Order types
A message is anchored to one of four things: a sales order, a purchase order, a project, or a free text invoice. That anchor is what puts it on a flow tracker, and a message without one is still perfectly valid, it is simply only visible in the message log.