Incoming Credit Memos
mseDoc365 receives xInvoices (XRechnung CII or UBL, also inside a ZUGFeRD PDF) from a FunctionServer import folder or by e-mail. The file name does not matter. Whether a received document is an invoice or a credit memo is decided only after the XML was read, from EN16931 field BT-3 (Invoice type code):
| Syntax | Element |
|---|---|
| CII (XRechnung) | ExchangedDocument/TypeCode |
| UBL (XRechnung-UBL / Peppol) | Invoice/InvoiceTypeCode or CreditNote/CreditNoteTypeCode |
| Type codes | Created purchase document |
|---|---|
| 80, 82, 84, 130, 202, 203, 204, 211, 295, 325, 326, 380, 383, 385, 386, 387, 388, 390, 393, 394, 395, 456, 458, 527, 575, 623, 633, 751, 780, 935 | Purchase Invoice |
| 81, 83, 261, 262, 296, 308, 381, 384, 389, 396, 420, 457 | Purchase Credit Memo |
Job setup
Inbound jobs (Direction In, FunctionServer folder or e-mail) use the document type RECEIVED.
Do not set them to PURCHASE-INVOICE or PURCHASE-CR.MEMO: those types are assigned by mseDoc365
itself after reading the XML, and the job card rejects them with an error.
What happens to a credit memo
- The step Create invoice creates a Purchase Credit Memo. The vendor's credit memo number (BT-1) is written to Vendor Cr. Memo No..
- Check for duplicate purchase invoice checks open and posted purchase credit memos of the vendor with the same Vendor Cr. Memo No. An invoice with the same number does not block a credit memo, and the other way round.
- Find order, Assign invoice lines and Assign order lines are skipped for credit memos (information Credit memo - no order matching.). A credit memo is never booked against a purchase order; it always becomes its own credit memo.
- Open Created Invoice on the eDoc card and on the xInvoice opens the purchase credit memo.
- When the purchase credit memo is posted, the xInvoice is marked as posted and shows the posted credit memo number, just like a posted invoice.
The credit memo is not applied to the original invoice automatically; apply it in the vendor ledger as usual.