Changelog

Update 2/2018

Date: 30/9/2018

Dear partners, as we expect the coming of the new legislation which will mandate the use of eInvoices for public entities, we have decided to expand our documentation with few guidelines on implementation of EN (European norm) compliant eInvoices.
You can get more information on our Getting Started page.
Additionally, we have made some changes to our Drivers. You can see details on the Drivers page.

Update 1/2018

Date: 15/7/2018

Dear partners, we have received input from our customers regarding additional services which they would like to use on our service. Therefore, we decided to issue this update of our documentation.
In this update we have added the following:

• API V2 - we have added new API method - MarkPaid

This, new, method enables your ERP solution to send to Moj-eRačun service information whether some invoice is paid or not. Using this method users can easily track whether their invoices are paid and they can automate the process of issuing Reminder Notes via Moj-eRačun service.
If you wish to learn more about this new service feel free to contact us.

Revision 2/2018

Date: 23/2/2018

Dear partners, we have received some input from you that we had some information which is missing in our technical documentation. Therefore, we decided to issue this minor revision of our documentation.
In this revision we have changed the following:

• API V2 - we have added all of the possible error responses

Revision 1/2018

Date: 12/2/2018

Dear partners, we have received some input from you that we had some mistakes in our technical documentation. Therefore, we decided to issue this minor revision of our documentation.
In this revision we have changed the following:

• API V2 - we have cleared the list of possible StatusIds in Query section
• API V2 - we have cleared the list of possible StatusIds in QueryInbox method
• API V1 - we have corrected the view for Send Example Request

Notice 2/2017

Date: 19/5/2017

Dear partners, we have decided to issue this notice to inform you about the following:

• Moj-eRačun service has achieved full interoperability with other service providers in Serbia. This means that if your user, which wants to send eInvoices via Moj-eRačun service, wants to send eInovices to his buyer, which uses some other service provider, you dont't need to integrate your ERP software with the other service provdired. This interoperability is achieved via Moj-eRačun service
• We have added some additional information in Additional documents section so we call upon you to read new information if you have implemented some additional documents, or if you plan to implement them.

Additionally, we would like to remind you that the deadline for adjustments of your ERP softwares to the EU norm expires on June, 1st.
For any additional information feel free to contact us.

Notice 1/2017

Date: 20/3/2017

Dear partners, we are very pleased to inform you that on March 17th, CEN published the results of the vote on several parts of the EU norm for eInvoices. Specifically:

• The EN 16931-1 (invoice model) - approved with 25 positive votes, 0 negative
• The CEN/TS 16931-2 (list of syntaxes) - approved with 24 positive votes, 0 negative

It is very important to emphasize that Moj-eRačun Service followed the European guidelines, and is therefore already in compliance with the aforementioned norm. If there will be any need for additional updates, you will be properly informed.
Additionally, it is important to understand that that Your users can send eInvoices to the governmental bodies and that they don't have any need for other eInovice delivery providers.
Considering all of these informations, we would like to notify you that you should adjust your ERP software to the demands of the EU norm as soon as possible. Deadline for implementation is June 1st, 2017.
You can test whether you are in compliance with the norm by using our validator. For any additional informations, feel free to contact us.

Revision 2/2017

Date: 20/3/2017

Considering the fact that more and more clients are using their ERP solutions for importing eInvoices, we have decided to make a small change to our receive API methods.
Main difference in the new version is that the SoftwareId parameter is now a mandatory property in JSON request. Having this parameter in the request enables us to identify which of the invoices are imported, and which are not, and in turn that enables us to achieve a better diagnostics when we are solving technical difficulties.
Additionally, we have introduced a new API method - NotifyImport. This method should be used together with the Receive method when you are importing eInovices in your ERP solution. For further details on this method, please visit this link.

Revision 1/2017

Date: 17/1/2017

Considering continuing growth and diversification of our clients, we have enabled some changes in our API methods. Specifically, we have expanded value set for parameter which denotes the business unit in our receive method.
New documentation therefore enables you to pass the following values to our service:

• GLN Code - a worldwide uniqe identification code
• Moj-eRačun Service Subject ID - our internal IDs
• Name of the Business Unit

This changes are not mandatory and they do not affect you if you have implemented the initial solution, but they can help you to expand the posibilities of your ERP system.

Revision 3/2016

Date: 6/12/2016

In accordance with standardization of eInvoice format, there was a need for small revision in our documentation. In this revision GTIN (EAN) code is moved from cac:SellersItemIdentitification node to cac:AdditionalItemIdentification.
Both nodes are contained in the cac:Item node. Besided the difference in names, cac:AdditionalItemIdentification enables having multiple codes. Additionally, we advise that you include schemeID and define it as "GTIN" (as shown in examples).
Our online validator is up-to-date with this revision.

Addition 1/2016

Date: 16/10/2016

As you already know, Moj-eRačun Service allows sending of eCredit Notes and eDebit Notes via the same API as eInvoices.
The most important thing to have in mind here is that eCredit Note and eDebit Note use the samo UBL as eInvoices. The only difference between them is in the cbc:InvoiceTypeCode node in the UBL document. Code for eCredit note is 381, and 383 for eDebit note. Other guidelines are the same as the ones for eInvoices stated in Revision 2/2016.
While implementing this documents, you should pay attention to:

• eCredit Note and eDebit Note use new envelope which is described in detail in the documentation for additional documents
• eCredit Note requires that the receiver sends an approval for that eCredit Note. Our web service enables the receiver to create and send this approval. When implementing this approval, you should implement creation of this approval. If you require any assistance with this fell free to contact us
• Approval for Credit note is sent in the form of eDocument which is very similar to the UBL document used for attachments in eInvoice

In conclusion, in order to implement eCredit Note and eDebit Note you are required to make very limited changes. The only change is in implementation of the new envelope, and changing of cbc:InvoiceTypeCode to 381 (eCredit Note) or 383 (eDebit Note)

Revision 2/2016

Date: 25/09/2016

Based on our contacts with our partners, regarding standardization of XML documents for eInvoices, we have created a document
with guidelines to all necessary steps in implementation of eInvoices which are sent from your ERP. This document follows the interoperabile standard which is active since July 2016.
You should specially pay attention to Order Reference element and GTIN (EAN) codes for articles in invoices. These elements are extremly important for the receiving party, because they enable automatic processing. These guidelines also contain all the significant informations for importing the eInvoice in your ERP and how to handle tax schemes.
Our online validator is up-to-date with this revision.