Navision 5.0 OIOXML Hotfix
Microsoft har lavet nedenstående opdatering/hotfix til Navision 5 med en række
ændringer/forbedringer til OIOXML.
Download objekterne her:
Læs mere om opdateringen nedenfor:
Microsoft Dynamics NAV DK 5.0 CDCR 23113
The CDCR applies to Local DK Critical Update of OIOXML e-Invoice enhanced Schematron
Validation and TaxTotal’s in Service invoices
Brief Description
Due to a new Schematron validation fields are now cross checked, and evaluated
tighter, to make sure mutual related fields and information in general are valid
as demanded by “Bekendtgørelse om information i OIOXML elektronisk regning til
brug for elektronisk afregning med offentlige myndigheder” encompassed by law
no. 1203 § 7 of December 27. 2003.
Also Changes to Codeunit 13609 and 13610 is included in this hotfix, as an adjustment
to TaxTotals in Service invoices.
This hotfix in total is an enhancement of OIOXML e-invoices.
User Instructions
Schematron
In the Danish configuration, if a customer in NAV is setup with an EAN-location
number, the invoice is not posted on paper, but to a file, typically designated
for Net distribution via a VAN, to be delivered at a public authority.
Errors in the e-invoice might lead to rejection of the invoice at a VAN or at
the receiver of the invoice. Normally the user will then be noticed, but sometimes
notice is only given to the former link in a chain of distributors. In the last
case the users only will experience the invoice is not paid, having trouble to
find out why.
Previously only the individual fields were validated.
Due to a new Schematron validation fields are now cross checked, and evaluated
tighter, to make sure mutual related fields and information in general are valid
as demanded by “Bekendtgørelse om information i OIOXML elektronisk regning til
brug for elektronisk afregning med offentlige myndigheder” encompassed by law
no. 1203 § 7 of December 27. 2003.
TaxTotals
When an OIOXML-file is created for a Service invoice that contains lines with
both positive and negative amounts, the class TaxTotal is created twice in the
OIOXML-file (one instance for the positive values and one instance for the negative
values). Furthermore TaxTotals classes are created for both VAT liable and not
liable lines, which results in up to 4 TaxTotals classes
This bug was missed when service invoices were developed for OIOXML in 5.0
RESOLUTION/Hot fix information
Schematron
Adjustments have been made to comply with the new Schematron validation.
Users will be noticed of possible errors either by entering data in relevant
fields or by the generation of the electronic invoice file, making it possible
to adjust errors before sending the OIOXML file.
For official reference to the demanded changes and enhancements due to the New
Schematron validation, please refer to the public information, at the link
To refer to a general specification of contents and demands to specific fields,
refer to the link
Detailed specified demand in general
According to the public authorities only minor or insignificant errors should
be the result of the new validation, and receivers of e-Invoices have been encouraged
to be flexible during the implementation phase. Anyhow no deadline for the implementation
has been announced so it is up to the individual receiver to decide when to take
the consequence of the new validation.
TaxTotals
According to "Statute on information in the OIOXML Electronic Invoice for use
with invoicing of the public sector organizations" section 5.34 the class TaxTotal
is only allowed 1-2 times in the class Invoice.
Adjustments has been made to avoid the invoicelines with positive and negative
amounts to be split into two instances of the class TaxTotal
Version list
The version list is updated (it's the original versionlist of the DK 5.0 release
plus added "OIO2007.01"); the date is set to 13-06-07) (date of the objects originally
released for this CDCR); the time is set "12:00:00".
Data impact
Because of the changes introduced by the new Schematron for OIOXML as well as
the more strict validation, design changes were made to the current workings of
the OIOXML feature in Navision.
These changes might have an impact on existing posted documents. Since certain
aspects such as the “Unit of Measure” field on the invoices and credit memos are
now mandatory, existing posted documents will not be accepted by the validation
in their current state. The change made to Navision prevents the user from creating
an electronic document if these mandatory fields are not completed.
Another one of these mandatory fields are the “Payment Method Code” field.
Since the “Payment Method Code” field has a one-to-one mapping to the “Payment
Channel” field, it is the “Payment Method Code” which is used to determine the
“Payment Channel” of the electronic document. Thus, an electronic document cannot
be created without the “Payment Method Code” being associated with that document,
and furthermore, a “Payment Channel” being associated with that method.
Since we (Microsoft) cannot determine what the unit of measure for a specific
invoice was or what payment method or channel should have been associated with
a specific posted document, it is impossible for us to provide the partners with
a data fix.
It is suggested that the partners, based on the information provided in this
paper, together with their customers determine what the best approach is to assigning
the correct data to these already posted documents.
The inconvenience is a consequence of the external demand of the Schematron validation.
To install these objects with previous version
The objects are tested primarily for version 5.0. Please, be aware that this
feature might not work in earlier versions and with customer specific changes.
License information
There’s no need to update he customer’s license to use the new objects.
Til toppen af siden
Du skal være logget ind før du kan se eller skrive kommentarer til de forskellige indlæg. Klik her for at logge ind, eller oprette en bruger.
