Purchase Document Type of Incoming eDocuments
Whether an incoming xInvoice becomes a purchase invoice or a purchase credit memo is decided from its type code (BT-3) — see Incoming Credit Memos. Some senders use the wrong type code, for example an invoice type code for a credit note.
Where to see and change it
Incoming eDocuments have the field Purchase Document Type on
- the eDocument lines of the process card, and
- the eDocument card.
| Value | Meaning |
|---|---|
| Invoice | Create invoice creates a purchase invoice. |
| Cr.Memo | Create invoice creates a purchase credit memo. |
| (blank) | No xInvoice read yet, or its type code is unknown. |
Without a manual choice the field shows the type read from the xInvoice.
Changing it
Choose another value before the purchase document is created. mseDoc365 then rewrites the type code of the xInvoice:
- Invoice → type code 380
- Cr.Memo → type code 381
All following steps (duplicate check, order matching, Create invoice) work with the new type, as if the sender had sent that type code.
Once the purchase document has been created, the field can no longer be changed. Delete the created purchase document first if the type is wrong.