Additional eDocuments

Additional eDocuments Available on Moj-eRačun Service

Moj-eRačun service offers the ability to send various eDocuments. Apart from eInvoices, our users can send following eDocuments:

  • Credit Note NEW INFO!
  • Debit Note
  • Receipt Advice
  • Reminder
  • Purchase Order
  • Call off
  • Order change
  • Order response
  • Approval Note, Reject Note
  • Despatch Advice
  • General Document

Guidelines and document examples

You can download guidelines for implementation of additional documents, as well as the XML examples of the documents from the following link:

General Document

GeneralDocumentEnvelope contains UBL 2.1 AttachedDocument node.

Using this document type, you can send any type of document which is not specified in the existing documentation, e.g. a contract in .docx format, an Excel spreadsheet, a picture, etc. Document should be encoded as base64 string and put in Attachment node in UBL 2.1 AttachedDocument.
One of the most applicable examples for implementation of General Document are Open Item Statements. We highly recommend that you enable this feature and instruct yout customers to use it because experiences with using General Document for sending of this documents is extremly positive.

Specification for this type of document can be found on this link

Minimal XML example


    <GeneralDocument>
        <GeneralDocumentEnvelope>
            <AttachedDocument>
                <cbc:ID>ID2</cbc:ID>
                <cbc:IssueDate>2006-05-04</cbc:IssueDate>
                <cbc:ParentDocumentID>ParentDocumentID0</cbc:ParentDocumentID>
                <cac:SenderParty>
                    <cac:PartyLegalEntity>
                        <cbc:RegistrationName>Sender name</cbc:RegistrationName>
                        <cbc:CompanyID>12345678901</cbc:CompanyID>
                    </cac:PartyLegalEntity>
                    <cac:PartyIdentification>
                        <cbc:ID>Sender business unit</cbc:ID>
                    </cac:PartyIdentification>
                </cac:SenderParty>
                <cac:ReceiverParty>
                    <cac:PartyLegalEntity>
                        <cbc:RegistrationName>Recepient name</cbc:RegistrationName>
                        <cbc:CompanyID>98765432198</cbc:CompanyID>
                    </cac:PartyLegalEntity>
                </cac:ReceiverParty>
                <cac:Attachment>
                    <cbc:EmbeddedDocumentBinaryObject mimeCode="application/pdf" 
                    filename="test.pdf">ZGVmYXVsdA==</cbc:EmbeddedDocumentBinaryObject>
                    <cac:ExternalReference>
                    </cac:ExternalReference>
                </cac:Attachment>
            </AttachedDocument>
        </GeneralDocumentEnvelope>
    </GeneralDocument>

Reminder Note Document

ReminderNoteDocument includes two envelopes:

  • ReminderNoteEnvelope - contains UBL 2.1 Reminder and
  • Mandatory AttachedDocumentEnvelope - contains AttachedDocument which is PDF representation of XML file

This document is used for sending reminders for payments. This document is very similar to HR-Invoice, differences being in mandatory fields na cac:ReminderLine XML node.
Specification for this type of document can be found on this link

Minimal XML example (only ReminderNoteEnvelope)


    <ReminderNoteEnvelope>
        <r:Reminder>
            <cbc:ID>ID0</cbc:ID>
            <cbc:IssueDate>2006-05-04</cbc:IssueDate>
            <cac:AdditionalDocumentReference>
                <cbc:ID>ID1</cbc:ID>
                <!--Reminder / opomena = 4 -->
                <cbc:DocumentType>4</cbc:DocumentType>
            </cac:AdditionalDocumentReference>
            <cac:AccountingSupplierParty>
                <cac:Party>
                    <cac:PartyLegalEntity>
                        <cbc:RegistrationName>Sender</cbc:RegistrationName>
                        <cbc:CompanyID>12345678901</cbc:CompanyID>
                    </cac:PartyLegalEntity>
                </cac:Party>
            </cac:AccountingSupplierParty>
            <cac:AccountingCustomerParty>
                <cac:Party>
                    <cac:PartyLegalEntity>
                        <cbc:RegistrationName>Recepient</cbc:RegistrationName>
                        <cbc:CompanyID>987654321098</cbc:CompanyID>
                    </cac:PartyLegalEntity>
                </cac:Party>
            </cac:AccountingCustomerParty>
            <cac:TaxTotal>
                <cbc:TaxAmount currencyID="HRK">125</cbc:TaxAmount>
            </cac:TaxTotal>
            <cac:LegalMonetaryTotal>
                <cbc:PayableAmount currencyID="HRK">125</cbc:PayableAmount>
            </cac:LegalMonetaryTotal>
        </r:Reminder>
    </ReminderNoteEnvelope>

Response Document

Response document includes two envelopes:

  • ResponseEnvelope - contains UBL 2.1 ApplicationResponse and
  • Mandatory AttachedDocumentEnvelope - contains AttachedDocument which is PDF representation of XML file

This document is used for sending confirmations or rejections of received documents.

In order for an approval or rejection to be valid, all of the mandatory fields in ApplicationResponse document must be filled. Reason for approval/rejection, as well as the approved/rejected document, can be found in the cac:DocumentResponse XML node, in which you can, apart from the reference to the document, put the original document.
cbc:StatusReasonCode field in cac:Status XML node defines the type of the response, according to the urn:oasis:names:specification:ubl:codelist:gc:DocumentStatusCode-2.1:

  • Confirmed = approval
  • Rejected = rejection

Specification for this type of document can be found on this link

Minimal XML example for approval response (only ResponseEnvelope)


    <ResponseEnvelope>
        <ar:ApplicationResponse>
            <cbc:IssueDate>2006-05-04</cbc:IssueDate>
            <cbc:IssueTime>01:01:01.000</cbc:IssueTime>
            <cac:SenderParty>
                <cac:PartyLegalEntity>
                    <cbc:RegistrationName>Sender name</cbc:RegistrationName>
                    <cbc:CompanyID>12345678901</cbc:CompanyID>
                </cac:PartyLegalEntity>
            </cac:SenderParty>
            <cac:ReceiverParty>
                <cac:PartyLegalEntity>
                    <cbc:RegistrationName>Receipient name</cbc:RegistrationName>
                    <cbc:CompanyID>987654321098</cbc:CompanyID>
                </cac:PartyLegalEntity>
            </cac:ReceiverParty>
            <cac:DocumentResponse>
                <cac:Response>
                    <cac:Status>
                        <!--Confirmed / Rejected-->
                        <cbc:StatusReasonCode>Confirmed</cbc:StatusReasonCode>
                    </cac:Status>
                </cac:Response>
                <cac:DocumentReference>
                    <cbc:ID>ID23</cbc:ID>
                    <cbc:DocumentType>1</cbc:DocumentType>
                </cac:DocumentReference>
            </cac:DocumentResponse>
        </ar:ApplicationResponse>
    </ResponseEnvelope>

Receipt Advice Document

ReceiptAdviceDocument envelope contains ReceiptAdvice UBL 2.1 document. Full specification for this document can be found on this link.

Minimal XML example (only ReceiptAdviceEnvelope)


<ReceiptAdviceEnvelope>
    <ReceiptAdvice>
        <cbc:ID>ID0</cbc:ID>
        <cbc:IssueDate>2006-05-04</cbc:IssueDate>
        <cbc:IssueTime>01:01:01.000</cbc:IssueTime>
        <cac:DespatchDocumentReference>
            <cbc:ID>123</cbc:ID>
            <!--Despatch advice / otpremnica = 351-->
            <cbc:DocumentType>351</cbc:DocumentType>
        </cac:DespatchDocumentReference>
        <cac:BuyerCustomerParty>
            <cac:Party>
                <cac:PartyLegalEntity>
                    <cbc:RegistrationName>Customer</cbc:RegistrationName>
                    <cbc:CompanyID>987654321098</cbc:CompanyID>
                </cac:PartyLegalEntity>
            </cac:Party>
        </cac:BuyerCustomerParty>
        <cac:SellerSupplierParty>
            <cac:Party>
                <cac:PartyLegalEntity>
                    <cbc:RegistrationName>Supplier</cbc:RegistrationName>
                    <cbc:CompanyID>12345678901</cbc:CompanyID>
                </cac:PartyLegalEntity>
            </cac:Party>
        </cac:SellerSupplierParty>
        <cac:ReceiptLine>
            <cbc:ID>1</cbc:ID>
            <cbc:ReceivedQuantity>10</cbc:ReceivedQuantity>
            <cac:Item>
                <cbc:Name>Item name</cbc:Name>
            </cac:Item>
        </cac:ReceiptLine>
    </ReceiptAdvice>
</ReceiptAdviceEnvelope>

Credit Note / Debit Note

Cdn document encompasses both Credit Note and Debit Note documents. Cdn Document includes two envelopes:

  • CdnEnvelope - contains UBL 2.1 HR-Invoice and
  • Mandatory AttachedDocumentEnvelope - contains AttachedDocument which is PDF representation of XML file

This document is used for sending of Credit Note and Debit Note documents. Because of its large similarity to invoices, this document is the exception in using identical UBL HR-Invoice as do eInvoices.

Difference between Cdn Document and eInvoice is in cbc:InvoiceTypeCode XML node where the code differs. This node should contain following codes:

  • 381 Credit Note
  • 383 Debit Note

NEW INFO!
The EU norm for eInvoices proscribes an important detail concerning Credit Notes. According to the norm, all amounts in Credit Note documents must be positive! We have decided to stress this point because we are aware that there are some ERP solutions which apply negative amounts when creating Credit Notes.