efaktura kvitteringer / acknowledgements format 1. Marts 2012 Dokumentversion 2.7

Transkript

1 efaktura kvitteringer / acknowledgements format 1. Marts 2012 Dokumentversion 2.7

2 Indholdsfortegnelse - Content 1. Dansk beskrivelse (Danish Description) Kvitteringsformat Specielle tegn Definition af fakturaformatet English description (Engelsk beskrivelse) The format Special characters Definition of the format Formatbeskrivelser (Danish) - Format Descriptions (English) ACKNOWLEDGEMENT DETAILS DETAIL ACKNOWLEDGE SUMMARY COUNTS Document types for e faktura Document types for OIO Overall status for both e faktura and OIO File level error codes and messages for invoices sent in e faktura-format File level error codes and messages for invoices sent in OIOXML-format Error codes and messages for invoices sent in e faktura-format Error codes and messages for invoices sent in OIOXML-format How to state ORIG_MQ_MESSAGE_ID Schema (XSD) for acknowledgements Examples of acknowledgements (e faktura format) Status OK All invoices was OK Status OK and ERROR One or more invoices failed Verification Status Error All invoices failed Verification rmal Error Acknowledgement File Error Acknowledgement Acknowledge with error on line level Examples of acknowledgements (OIO format) Status OK The invoice was OK Side e faktura kvitterings/acknowledgements format Side ii

3 Dokumenthistorik Version Dato Ændringer danish Changes english Tilføjet ny fejl kode 9342 n receiver agreement present Tilføjet ny fejl kode 9341 Added new error message Tilføjet flg. nye status koder til kunder, der anvender test-faciliteten; 9331, 9332, 9333, 9334, 9335, 9336, Angivelsen af ORIG_MQ_MESSAGE_ID er uddybet. Added the following Message for Test customer: 9331, 9332, 9333, 9334, 9335, 9336, 9337 The value of the tag ORIG_MQ_MESSAGE_ID _ID is more detailed defined Tilføjet ny fejlkode Added new error code Tilføjet nye fejlkoder og opdateret skemaet Format tilpasset indholdet i OIO formatet Længden på origianal reference er ændret. Fejlkoder er opdateret Added new error codes and updated the schema. Specification adjusted to the content of the OIO format The length of original reference has been changed Error codes are updated. New error codes added for Dependency check and Schema change request Flere fejlkoder er beskrevet More error codes are described Format for tidsstempler er opdateret. ORIG_MQ_MESSAGE_ID og BILL_TO_CUSTOMER_NO er tilføjet til formatet Første version First version The date_time format has been uniformly updated all over the document with YYYY-MM-DDThh:mm:SS.ssssss ORIG_MQ_MESSAGE_ID and BILL_TO_CUSTOMER_NO has been added to the format. Updated Choice Tabel 4 with new Error message codes. e faktura kvitterings/acknowledgements format Side iii

4 1. Dansk beskrivelse (Danish Description) Nærværende dokument gennemgår XML-formatet for kvitteringer i e faktura. 1.1 Kvitteringsformat Nets sender kvitteringer i encoding ISO , såfremt faktura er afsendt i e faktura-format. Er faktura afsendt i OIOXML-format, sender Nets kvittering i encoding UTF-8. For kvitteringer på handelsdokumenter i OIOUBL-format henvises til OIOUBL-vejledningerne. Formatet kan ikke ændres uden samtykke fra Nets Denmark A/S. Nets vil varsle formatændringer med minimum tre måneders varsel Specielle tegn Der accepteres ikke ikke-printbare tegn i filformatet. Følgende tegn må ikke indgå i formatet: < > & Dette bevirker, at ERP-systemerne skal konvertere tegnene iht. nedenstående tabel, inden tegnene sendes til e faktura. På tilsvarende måde skal tegnene konverteres ved modtagelse. Tegn Konvertering i ERP DTD entitet < &lt <!ENTITY lt "&#60;"> > &gt <!ENTITY gt ">"> & &amp <!ENTITY amp "&#38;"> &apos <!ENTITY apos "&#39;"> &quot <!ENTITY quot """> Definition af fakturaformatet Formatet beskrives i tabelform i afsnit 3 Formatbeskrivelse. Kolonnerne i tabellerne har følgende betydning: Navn Name: Angiver start og slut på tagget. Beskrivelse: Kort beskrivelse af, hvilken information tagget indeholder. Description: Engelsk beskrivelse Requirement: Hvis værdien af tagget ligger fast, er krav til værdien beskrevet her. Type: Angiver hvilken type information, tagget indeholder; f.eks. om det er tekst eller dato. Såfremt der står sub level i kolonnen, er det fordi tagget har et niveau, der er beskrevet i en anden tabel med samme navn som tagget. Value: Angiver antallet af karakterer, informationen kan indeholde. A(20) betyder, at den kan indeholde 20 karakterer. Hvis der yderligere er tilføjet altid, eksempelvis A(4) altid, betyder dette, at informationen altid skal være på 4 karakterer. Såfremt typen er decimal, kan værdien eksempelvis være 20.3, hvilket betyder at tallet kan være på 20 cifre før kommaseparatoren og 3 cifre efter kommaseparatoren. efaktura - kvitterterings/acknowledgements format Side 1

5 C/M/D/V: Angiver hvorvidt informationen er conditional, mandatory, dependent eller mandatory fra og med en bestemt version af formatet. Et conditional tag må gerne være der, selvom det ikke er udfyldt. Et mandatory tag skal være der og skal være udfyldt. Et dependent tag skal være der, hvis det tag, det er afhængigt af, er udfyldt. Dog, såfremt N = 1 skal tagget være med, tagget kan dog være tomt. Vs: Angiver, at tagget er mandatory fra og med det angivne versionsnummer. N: Angiver hvor mange gange tagget kan være i formatet. N = 1 betyder, at tagget altid skal være med 1 gang, det kan dog være tomt. Bemærk, at selvom et tag ikke er mandatory, kan N godt stå til 1, og så vil tagget i DTD en være defineret som mandatory. N = 0..1 betyder, at tagget kan være med, eller det kan udelades. N = betyder, at tagget kan være med gange. Dependent: Angiver det tag, som dette tag er afhængigt af. Dependent af angives kun, når C/M/D/V er D. History: Her angives historik for eventuelle ændringer til tagget. Hvis der er tale om et nyt tag, angives f.eks. versionsnummer for oprettelse i formatet; er der tale om en ændring af et tag s definition, angives den tidligere definition samt det versionsnummer, hvori tagget blev ændret. efaktura - kvitterterings/acknowledgements format Side 2

6 2. English description (Engelsk beskrivelse) The present document goes through the format of acknowledgments from e faktura. 2.1 The format Nets sends acknowledgements in encoding ISO , if the invoice is sent in e faktura format. If the invoice is send in OIOXML format, then Nets sends the acknowledgement in encoding UTF-8. For acknowledgements for documents sent in OIOUBL-format, please refer to specification for OIOUBL documents. The format cannot be changed without consent from Nets Denmark A/S. Nets will give notice of changes in the format with a minimum of three months notice Special characters non-printable characters are accepted in the file format. ne of the following characters must be part of the format: < > & This obliges the ERP systems to convert the characters with reference to the table below, before the characters are sent. The characters are to be converted correspondingly upon reception. Character Conversion in the ERP DTD entity < &lt <!ENTITY lt "&#60;"> > &gt <!ENTITY gt ">"> & &amp <!ENTITY amp "&#38;"> &apos <!ENTITY apos "&#39;"> &quot <!ENTITY quot """> Definition of the format The format from e faktura are described in tabular form in section 4 format description The columns in the table have the following meaning: Navn Name: Defines the beginning and end of the tag Beskrivelse: Description in danish Description: A brief description of which information the tag contains. Requirement: If the value of the tag is established, a requirement to the value is described here. This column is only included for the description of HEADER. efaktura - kvitterterings/acknowledgements format Side 3

7 Type: Value: C/M/D/V: Specifies which type of information the tag contains; e.g., whether it is text or a date. Provided it says sublevel in the column, the tag has a level that is described in another table with the same name as the tag Specifies the amount of characters, the information can contain. A(20) means that it can contain 20 characters. If altid (always) is added, for example A(4) altid, this means that the information must always be 4 characters long. Should the type be decimal, the value can be 20.3, which means that the number can be 20 digits before the decimal comma 1 and 3 digits after the decimal comma. Specifies whether the information is conditional, mandatory, dependent or mandatory from a certain version of the format A conditional tag may be there, even though it is not filled out A mandatory field must be there and has to be filled out A dependent tag must be there, if the tag it is dependent on, is filled out. In case of N = 1, the tag has to be there. The tag, however, can be empty Vs: Specifies whether the tag is mandatory from the specified version number. N: Specifies how many times the tag can be in the format. N = 1 means that the tag has to be there one time, it can however be empty N = 0..1 means that the tag can be there, or be omitted N = means that the tag can be there times Dependent: Specifies the tag, that this tag is dependent on. Dependent on is only specified, when C/M/D/V is D. History: The history of changes to the tag is specified here. If it is a new tag, e.g. the version number, for creation in the format, should be specified; if it is changes of a tags definition, the former definition and the version number, in which the tag was changed, is specified. efaktura - kvitterterings/acknowledgements format Side 4

8 3. Formatbeskrivelser (Danish) - Format Descriptions (English) 3.1 ACKNOWLEDGEMENT Navn name Beskrivelse Description Requirement DETAILS Detaljeret kvittering Detail acknowledgement Sub level SUMMARY Opsummering af kvitteringsinformationer Acknowledgement summary Type Value C/M/ D/V Sub level Vs N Dependent C C History 3.2 DETAILS Navn name 1Beskrivelse Description Requirement DETAIL Information pr. modtaget faktura Information for a specific invoice Type Value C/M/ D/V Sub level V s N C Depe n- dent History e faktura kvitterings/acknowledgements format Side 5

9 3.3 DETAIL Navn name Beskrivelse Description Requirement ACK_NO SENDER_CVR_NO SENDER_CODE RECEIVER_CVR_NO RECEIVER_CODE BILL_TO_CUSTOMER_NO RECEIPT_NO Kvitteringsnummer fra e faktura Afsenders CVR/SEnummer Afsenders P-nummer eller EAN-lokationsnummer. Har afsender ingen af delene, anføres CVR/SEnummer også her. Modtagers første nøgle (CVR/SE-nummer) Modtagers P-nummer eller EAN-lokationsnummer. Har modtagers ingen af delene, anføres CVR/SEnummer også her. Fakturamodtagers nummer hos kreditor. Dette tag vil ikke være til stede, når faktura er modtaget i OIOXMLformat. Kvitteringsnummer fra fakturaen. Dette tag vil ikke være til stede, når faktura er Receipt number from e faktura Sender s CVR-no or SE-no Senders P-number, EAN-locationnumber. Does the sender have neither of this, then sender s CVR-no or SEno is entered again Receivers CVR-no or SE-no Receivers P-number, EAN-locationnumber. Does the sender have neither of this, then the receivers CVR-no or SE-no is entered again. The recipients number at the creditor. This tag will not be present if the invoice is of Type OIO. Receipt number from the Invoice. generated by the senders ERPsystem. Type Value C/M/ D/V Text A(40) M 1 Vs N Dependent Text A(20) C Text A(20) M 1 Text A(20) C Text A(20) M 1 Text A(20) C Text A(20) C History e faktura kvitterings/acknowledgements format Side 6

10 Navn name Beskrivelse Description Requirement modtaget i OIOXMLformat. present if the invoice is This tag will not be of Type OIO. DATE_TIME Tidspunktet for behandling af e faktura Timestamp for when the invoice was processed by e faktura. The format is YYYY-MM- DDThh:mm:SS.ssssss where: YYYY = four-digit year MM = two-digit month (01=January, etc.) DD = two-digit day of month (01 through 31) hh = two digits of hour (00 through 23) (am/pm NOT allowed) mm = two digits of minute (00 through 59) ss = two digits of second (00 through 59) s = one or more digits representing a decimal fraction of a second Type Value C/M/ D/V Date A(26) altid Vs N Dependent M 1 History DOCUMENT_NO Fakturanummer Invoice number Text A(20) M 1 DOCUMENT_TYPE Fakturatype. Se valgtabel 1a (e faktura) og 1b (OIO). Invoice or credit note See choice table 1a (e faktura) and 1b (OIO). Text A(20) M 1 DOCUMENT_DATE Bemærk, dette er te, this is the invoice Date A(10) M 1 e faktura kvitterings/acknowledgements format Side 7

11 Navn name Beskrivelse Description Requirement fakturadato. date. STATUS ACKNOWLEDGE Angives kun når ACKNOWLEDGE_CODE er 9090 Mulige status-koder: OK ERROR Se valgtabel 2. Only stated when ACKNOWLEDGE_CO DE is 9090 Possible codes for indicating overall status: OK ERROR See Choice Table 2 Detailed description of the status Type Value C/M/ D/V altid Text A(5) M 1 Detaljeret statusbeskrivelse Sublevel Vs N Dependent C History 3.4 ACKNOWLEDGE Navn name Beskrivelse Description Requirement ACKNOWLEDGE_CODE Hvis status er OK, angiver dette output-typen (efaktura, OIO, print) ellers angiver det en fejlkode. Se valgtabel 4a (e faktura) og 4b (OIO). If status is OK this tells the output-type. Otherwise this is an error code See Choice Table 4a (e faktura) and 4b (OIO) ACKNOWLEDGE_DESC Kort beskrivelse af koden Description of the acknowledgement code ORIG_LINE_NO Linjenummer fra fakturaen. Udfyldes når der er tale om en fejl på linje- Original line number from the invoice. In case of an error on Type Value C/M/ D/V Vs N Dependent e faktura kvitterings/acknowledgements format Side 8 Deci mal Text A(200 ) Deci mal 6 M 1 C C History

12 Navn name Beskrivelse Description Requirement niveau. line level, this states the line in question. Udfyldes kun i fejlsituationer. Only stated in error situations. Type Value C/M/ D/V Vs N Dependent History 3.5 SUMMARY Navn name Beskrivelse Description Requirement DATE_TIME ORIG_FILENAME ORIG_MQ_MESSAGE_ID Tidspunktet da fakturafilen blev modtaget af e faktura Modtaget filnavn. Om informationen er relevant, afhænger af anvendt kommunikationskanal. MQ Message ID anvendt ved afsendelse af fakturabundtet til e faktura HUB. Om informationen er relevant, afhænger af anvendt kommunikationskanal. Der henvises til afsnit 3.14 How to state ORIG_MQ_MESSAGE_ Timestamp for when e faktura received the invoice file. The format is YYYY-MM- DDThh:mm:SS.ssssss. Refer detail/date_time tag for format description. Original filename for the invoice file. Is dependent on the communication channel used. MQ Message ID used when sending the invoice to e faktura HUB. Is dependent on the communication channel used. Please also refer to section 3.14 How to state ORIG_MQ_MESSAG Type Value C/M /D/V Date A(26) altid Vs N Depe n- dent M 1 Text A(75) C 0..1 Text A(48) C 0..1 History e faktura kvitterings/acknowledgements format Side 9

13 Navn name Beskrivelse Description Requirement STATUS FILE_STATUS FILE_STATUS_TEXT ARR_COUNT PROCESS_COUNT ORIG_REFERENCE ID mht. hvordan feltet udfyldes. Status på forsendelsen Vil være OK hvis alle fakturaer er OK, ellers ERROR. Se valgtabel 2. Status på filniveau Dette vil indholde en fejlkode, såfremt der er opstået en fejl på filniveau. Se valgtabel 3a (e faktura) og 3b (OIO). Beskrivelse af evt. fejl på fil-niveau Antallet af fakturaer i den modtagede fil Antallet af behandlede fakturaer. Skal være ens med ARR_COUNT, ellers er det tegn på fejl. Referencen fra den modtagede XML-fil. Kan ikke angives i hårde fejlsituationer, f.eks. ved E_ID. Overall status for the invoice file. If all invoices are processed without errors, the status is OK, otherwise it is ERROR. See Choice Table 2 Status on file level. This will contain Error codes if there is a file error like Duplicate file, corrupt file etc. See Choice Table 3a (e faktura) and 3b (OIO) Description of the File Error Number of invoices in the received invoice file Number of processed invoices in e faktura for this particular invoice file. If different form ARR_COUNT this indicates an erroneous situation. The reference number from the invoice file. Can not be stated in serious error situations Type Value C/M /D/V Text A(5) M 1 Vs N Depe n- dent Text A(20) C 0..1 Text A(200) C 0..1 Deci mal Deci mal 6 C C 0..1 Text A(40) C 0..1 History e faktura kvitterings/acknowledgements format Side 10

14 Navn name Beskrivelse Description Requirement COUNTS zip- og schemafejl. Dette tag vil ikke være til stede, når faktura er modtaget i OIOXMLformat. Opsummering pr. outputtype. Se valgtabel 4a (e faktura) og 4b (OIO) for hvilke typer koder der bliver optalt. like zip- and schema error situations. This tag will not be present if the invoice is of Type OIO. Type Value C/M /D/V Summary per outputtype. See choice table 4a (e faktura) and 4b (OIO) for which codes that are counted. Sublevel Vs N Depe n- dent C History 3.6 COUNTS Navn name Beskrivelse Description Requirement ACKNOWLEDGE_CODE Kode for output-type Se valgtabel 4a (e faktura) og 4b (OIO), Acknowledgement code. Specifies an output-type See Choice Table 4a (e faktura) and 4b (OIO) ACKNOWLEDGE_DESC Kort beskrivelse til koden Short description of the acknowledgement code COUNT Antal fakturaer med denne status-kode (output-type) Number of invoices which have this acknowledgement code (output-type). Type Value C/M/ D/V Deci mal Text A(200 ) 6 M 1 Vs N Dependent C String A(20) M 1 History e faktura kvitterings/acknowledgements format Side 11

15 e faktura kvitterings/acknowledgements format Side 12

16 3.7 Document types for e faktura Valgtabel 1a Choice Tabel 1a Beskrivelse Description EFAKTURA_INVOICE EFAKTURA_CREDITNOTE Faktura (oplysningen skal angives med Upper case ) Kreditnota (oplysningen skal angives med Upper case ) Invoice (the information must be stated with upper case) Credit note (the information must be stated with upper case) 3.8 Document types for OIO Valgtabel 1b Choice Tabel 1b Beskrivelse Description PIE "PIE" angiver en elektronisk regning (PI "PIE" defines an Electronic Invoice (PI Elektronisk) Electronic) PCM "PCM" angiver en elektronisk kreditnota. "PCM" defines an Electronic Credit te. PIP PCP "PIP" angiver en papirbaseret regning (PI Papirbaseret). Er ikke understøttet. PCP angiver en papirbaseret kreditnota. Når fakturatype. Er ikke understøttet. "PIP" defines a paper based invoice (PI Paper based). Cannot be used. PCP defines a paper based credit note. Cannot be used. PIETEST Test udgave af PIE. Test version of PIE PCMTEST Test udgave af PCM. Test version of PCM PIPTEST Test udgave af PIP Test version of PIP PCPTEST Test udgave af PCP Test version of PCP e faktura kvitterings/acknowledgements format Side 13

17 3.9 Overall status for both e faktura and OIO Valgtabel 2 Choice Tabel 2 Beskrivelse Description OK Fil OK File OK ERROR Fil ikke OK File not OK 3.10 File level error codes and messages for invoices sent in e faktura-format Valgtabel 3a Choice Tabel 3a Beskrivelse Description 9107 Forkert angivet værdi for antallet af fakturaer Invalid Number Of Invoices i bundtet Forkert checksum på bundt-niveau Invalid Total Checksum 9110 Skema-fejl Schema Validation, Failed 9112 ZIP-fejl ZIP File, Corrupt 9114 Filen er en dublet File is a duplicate 9127 Ingen documenter i leverance. Fil derfor afvist. At least one document is required. File rejected For mange documenter i leverancen. Fil derfor afvist. The maximum number of documents is exceeded. File rejected Forkert PI Reg.Nr. Invalid FI Registration number 9301 Ugyldigt XML. Skema fejl. Serious XML Parsing Errors have occurred. Bundle cannot be split into separate invoices. e faktura kvitterings/acknowledgements format Side 14

18 3.11 File level error codes and messages for invoices sent in OIOXML-format Valgtabel 3b Choice Tabel 3b Beskrivelse Description 9110 Skema-fejl Schema Validation, Failed 9112 ZIP-fejl ZIP File, Corrupt 9301 Ugyldigt XML. Skema fejl. Serious XML Parsing Errors have occurred. Bundle cannot be split into separate invoices Error codes and messages for invoices sent in e faktura-format Valgtabel 4a Choice Tabel 4a Beskrivelse Description Always use text from acknowledgement as description refers to tag in question 9001 E faktura dokument afsendt, normal slut status E aktura Document Sent, rmal End Status 9002 OIO dokument afsendt, normal slut status OIO Document Sent, rmal End Status 9003 Dokument afsendt som print, normal slut status 9004 Dokument afsendt som ekort, normal slut status 9005 OIO dokument sendt til VANS, normal slut status 9090 Modtager ukendt, faktura er printet, normal slut status 9099 Dokument ikke afsendt, afsluttende fejlstatus Document Sent to Print, rmal End Status Document Sent to ECard, rmal End Status OIO Document Sent to Vans, rmal End Status Receiver unknown, document is printed, rmal End Status Document t Sent, Final Error End Status 9101 Ugyldig serviceleverandør, faktura fejl Invalid Service Provider, Invoice Error 9102 Ugyldig fakturaafsender, faktura fejl Invalid Legal Sender, Invoice Error 9103 Ugyldig postkode, faktura fejl Invalid Post Code, Invoice Error 9104 Forkert fakturatotal, faktura fejl Invalid Invoice Total, Invoice Error Included in Count section e faktura kvitterings/acknowledgements format Side 15

19 9200 <Fejlbeskrivelse fra VANS>, VANS fejl <text from VANS >, VANS error 9106 Forkert momsprocent, faktura fejl Invalid VAT_PCT, Invoice error 9108 Forkert checksum på faktura niveau Invalid Document Checksum 9113 Forkert totalbeløb før moms på linjen, Invalid faktura fejl AMOUNT.AMOUNT_EXCL_VAT, invoice error 9116 Forkert momsbeløb på linjen, faktura fejl Invalid AMOUNT.VAT_AMOUNT, 9117 Forkert totalbeløb efter moms på linjen, faktura fejl invoice error Invalid AMOUNT.AMOUNT_INCLUDING_V AT, invoice error 9118 Forkert gebyr momsbeløb, faktura fejl Invalid CHARGE.AMOUNT.VAT_AMOUNT, invoice error 9119 Forkert gebyr beløb efter moms, faktura fejl 9120 Forkert fakturarabatbeløb excl. moms, faktura fejl Invalid CHARGE.AMOUNT.AMOUNT_INCL UDING_VAT, invoice error Invalid T_INV_DISC_AMOUNT_VAT_EXCL, invoice error 9121 Forkert totalbeløb incl. moms, faktura fejl Invalid T_AMOUNT_VAT_INCL, invoice error 9122 Forkert totalbeløb excl. moms, faktura fejl Invalid T_AMOUNT_VAT_EXCL, invoice error 9123 Forkert total momsfribeløh, faktura fejl Invalid T_AMOUNT_VAT_FREE, 9124 Forkert fakturarabat momsbeløb, faktura fejl 9125 Forkert fakturrabatbeløb incl. moms, faktura fejl invoice error Invalid T_INV_DISC_VAT_AMOUNT, invoice error Invalid T_INV_DISC_AMOUNT_VAT_INCL, invoice error 9126 Forker t total momsbeløb, faktura fejl Invalid T_VAT_AMOUNT, invoice error 9129 TEST_FLAG er sat, dokument afvises Unsupported TEST_FLAG used. e faktura kvitterings/acknowledgements format Side 16

20 9130 Ugyldig landekode i fakturaafsenders adresse Document rejected. Invalid bill to Country Code 9131 Antal på linjen er krævet LINE.QUANTITY is required 9132 Brutto salgspris pr. enhed på linjen er krævet 9133 Netto salgspris pr. enhed på linjen er krævet LINE.UNIT_PRICE is required LINE.NET_PRICE is required 9134 Momsprocent på linjen er krævet LINE.VAT_PCT is required 9135 Antal pr. enhed på linjen er krævet LINE.QTY_PER_UNIT_OF_MEASUR E is required 9136 Enhedskode på linjen er krævet LINE.UNIT_OF_MEASURE_CODE is required 9137 Beløb excl. moms på linjen er krævet LINE.AMOUNT.AMOUNT_EXCL_V AT is required 9138 Beløb incl. moms på linjen er krævet LINE.AMOUNT.AMOUNT_INCLUDI NG_VAT is required 9139 Momsbeløb på linjen er krævet LINE.AMOUNT.VAT_AMOUNT is required 9140 Fakturarabat, type er krævet T_INV_DISC_TYPE is required 9141 Fakturarabat, momsbeløb er krævet T_INV_DISC_VAT_AMOUNT is required 9142 Fakturarabat, beløb excl. moms er krævet T_INV_DISC_AMOUNT_VAT_EXCL is required 9143 Fakturarabat, beløb incl. moms er krævet T_INV_DISC_AMOUNT_VAT_INCL 9144 Betalings ID er krævet for den anvendte FI kortart 9145 Betalings ID overholder ikke modulus 10 kontrol 9146 Seneste dato for rabat skal angives, når rabat ved tidlig betaling gives. is required PAYMENT_MEANS.FIK.P_PAYMEN T_ID is required PAYMENT_MEANS.FIK.P_PAYMEN T_ID has an invalid check digit PAYMENT_TERMS.PAYMENT_DIS COUNT_DATE is required 9147 Factoring, betalings ID skal angives FACTORING_INFO.F_PAYMENT_ID e faktura kvitterings/acknowledgements format Side 17

21 9148 Factoring, betalings ID e ikke identisk med FI betalingskortinformationerne 9149 Factoring, seneste dato for rabat skal angives, når rabat ved tidlig betaling gives Betalingstypen stemmer ikke overens med faktisk angivet betalingsmåde Antal kan ikke angives, når der ikke er angivet et varenummer. is required FACTORING_INFO.F_PAYMENT_ID is not equal to PAYMENT_MEANS.FIK.P_PAYMEN T_ID FACTORING_INFO.F_PAYMENT_DI SCOUNT_DATE is required PAYMENT_MEANS.PAYMENT_TYP E is invalid LINE.QUANTITY is invalid 9301 Ugyldig XML XML Parsing Errors have occurred 9311 Skema fejl, ugyldig værdi for feltet. Er mindre end minimum værdi: 9312 Skema fejl, ugyldig værdi for feltet. Er kortere end minimum længde: 9313 Skema fejl, ugyldig værdi for feltet. Er længere end max længde: 9314 Skema fejl, ugyldig værdi for feltet. Overholder ikke dato format: 9315 Skema fejl, ugyldig værdi for feltet. Værdi ikke fundet i valglisten: Schema error. Invalid value for element. It is less than the minimum value: Schema error. Invalid value for element. It is shorter than the minimum length: Schema error. Invalid value for element. It is longer than the maximum length: Schema error. Invalid value for element. It does not conform to the DateTime type required: Schema error. Invalid value for element. It is not in the list of allowed values: 9316 Skema fejl, ugyldig værdi for feltet: Schema error. Invalid value for: 9317 Skema fejl, feltet optræder for få gange: Schema error. An element does not meet the minoccurs constraint: 9318 Skema fejl, feltet optræder for mange Schema error. The element occurs too gange: many times: 9319 Skema fejl, ugyldig værdi i feltet: Schema error. Invalid element content: 9320 Skema fejl, ugyldigt felt. Schema error. Invalid element: 9321 Skema fejl, for mange decimaler er angivet: Schema error. Invalid value for element. The decimal value contains more than e faktura kvitterings/acknowledgements format Side 18

22 9331 e faktura dokument afsendt til test modtager, normal slut status 9332 Print dokument afsendt til test modtager, normal slut status 9333 OIO dokument afsendt til test modtager, normal slut status 9334 Test modtager ukendt, print dokument afsendt til test modtager, normal slut status 9335 Test Customer document not sent, afsluttende fejl-status the maximum total digits: efaktura Document Sent To Test Customer, rmal End Status Print Document Sent To Test Customer, rmal End Status OIO Document Sent To Test Customer, rmal End Status, rmal End Status Test Customer Receiver unknown, document is printed, rmal End Status Test Customer document not sent, Final Error End Status e faktura kvitterings/acknowledgements format Side 19

23 3.13 Error codes and messages for invoices sent in OIOXML-format Valgtabel 4b Choice Tabel 4b Beskrivelse Description Always use text from Included in Count section acknowledgement as description refers to tag in question 9002 OIO dokument afsendt, normal slut status OIO Document Sent, rmal End Status 9099 Dokument ikke afsendt, afsluttende fejlstatus Document t Sent, Final Error End Status 9101 Ugyldig serviceleverandør, faktura fejl Invalid Service Provider, Invoice Error 9102 Ugyldig fakturaafsender, faktura fejl Invalid Legal Sender, Invoice Error 9130 Ugyldig landekode i fakturaafsenders adresse 9154 Ugyldig dokumenttype. Fil er afvist. Kun PCM, PIE, PCMTEST og PIETEST accepteres. Invalid bill to Country Code Invalid Document type. File rejected <Fejlbeskrivelse fra VANS>, VANS fejl <text from VANS >, VANS error 9300 Schematron validering har fundet fejl i fakturaen. Se ACKNOWLEDGE_DESC for beskrivelse af fejlen Skema fejl, ugyldig værdi for feltet. Værdi ikke fundet i valglisten: Schematron validation error. See ACKNOWLEDGE_DESC for details. Invoice rejected Schema error. Invalid value for element. It is not in the list of allowed values: 9317 Skema fejl, feltet optræder for få gange: Schema error. An element does not meet the minoccurs constraint: 9318 Skema fejl, feltet optræder for mange Schema error. The element occurs too gange: many times: 9319 Skema fejl, ugyldig værdi i feltet: Schema error. Invalid element content: 9322 Skema fejl, ugyldig værdi i feltet. Typisk hvis der er angivet bogstaver i et tal-felt Com:BuyersReferenceID er længere end 20 tegn. Schema error. Invalid value for element. Invalid data for the type specified: Com:BuyersReferenceID is longer than 20 characters e faktura kvitterings/acknowledgements format Side 20

24 9330 Com:id er længere end 50 tegn. Com:id is longer than 50 characters 9336 Modtagerkode er ikke et validt EAN lokations-nummer 9337 OIO dokument afsendt til VANS, normal slut status Receiver code is not an valid EAN number OIO Document Sent To Vans, rmal End Status 9341 Invalid CVR/SE/EAN/P number Invalid CVR/SE/EAN/P number 9342 n receiver agreement present n receiver agreement present e faktura kvitterings/acknowledgements format Side 21

25 3.14 How to state ORIG_MQ_MESSAGE_ID As the MQ_MSG_ID is a bytearray containing binary values it must be hex encoded before it is inserted into the <ORIG_MQ_MESSAGE_ID> tag in the XML-document. Hex encoding means using the characters a-f and 0-9 to represent the hexadecimal byte values of MQ_MSQ_ID. As each halfbyte is expanded into one character the resulting text string(48 characters) is twice the size of the original MQ_MSG_ID(24 bytes). A single byte containing the hexadecimal value x'82' should convert into a string containing the two characters "8" and "2". The acknowledgement XML is ISO encoded and thus the hexadecimal representation of the two characters ("82") is x'3832'. A MQ_MSQ_ID in a message received from Nets will look somewhat like this when properly hex encoded: <ORIG_MQ_MESSAGE_ID>c3e2d840d2f2d8f be829b89aa22bd82</O RIG_MQ_MESSAGE_ID> Please notice, the value must be stated in lower cases! e faktura kvitterings/acknowledgements format Side 22

26 4. Schema (XSD) for acknowledgements <?xml version="1.0" encoding="iso "?> <xs:schema xmlns:xs=" elementformdefault="qualified"> <xs:element name="acknowledgement"> <xs:complextype> <xs:sequence> <xs:element name="details" type="detailstype" minoccurs="0"/> <xs:element name="summary" type="summarytype" minoccurs="0"/> </xs:sequence> </xs:complextype> </xs:element> <xs:complextype name="acknowledge"> <xs:sequence> <xs:element ref="acknowledge_code"/> <xs:element ref="acknowledge_desc" minoccurs="0"/> <xs:element ref="orig_line_no" minoccurs="0"/> </xs:sequence> </xs:complextype> <xs:complextype name="detailtype"> <xs:sequence> <xs:element ref="ack_no"/> <xs:element ref="sender_cvr_no" minoccurs="0"/> <xs:element ref="sender_code"/> <xs:element ref="receiver_cvr_no" minoccurs="0"/> <xs:element ref="receiver_code"/> <xs:element ref="bill_to_customer_no" minoccurs="0"/> <xs:element ref="receipt_no" minoccurs="0"/> <xs:element ref="date_time"/> <xs:element ref="document_no"/> <xs:element ref="document_type"/> <xs:element ref="document_date" minoccurs="0"/> <xs:element ref="status"/> <xs:element name="acknowledge" type="acknowledge" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> </xs:complextype> <xs:complextype name="detailstype"> <xs:sequence> <xs:element name="detail" maxoccurs="unbounded"> <xs:complextype> <xs:complexcontent> <xs:extension base="detailtype"/> </xs:complexcontent> </xs:complextype> </xs:element> </xs:sequence> </xs:complextype> <xs:complextype name="summarytype"> <xs:sequence> <xs:element ref="date_time"/> <xs:element ref="orig_filename" minoccurs="0"/> <xs:element ref="orig_mq_message_id" minoccurs="0"/> <xs:element ref="status"/> <xs:element ref="file_status" minoccurs="0"/> e faktura kvitterings/acknowledgements format Side 23

27 minoccurs="0"/> <xs:element ref="file_status_text" minoccurs="0"/> <xs:element ref="arr_count" minoccurs="0"/> <xs:element ref="process_count" minoccurs="0"/> <xs:element ref="orig_reference" minoccurs="0"/> <xs:element name="counts" minoccurs="0" maxoccurs="unbounded"> <xs:complextype> <xs:sequence> <xs:element ref="acknowledge_code"/> <xs:element ref="acknowledge_desc" <xs:element ref="count"/> </xs:sequence> </xs:complextype> </xs:element> </xs:sequence> </xs:complextype> <xs:element name="acknowledge_code" type="acknowlegementcodes"/> <xs:element name="acknowledge_desc" type="acknowlegementtext"/> <xs:element name="ack_no" type="xs:string"/> <xs:element name="arr_count" type="xs:integer"/> <xs:element name="date_time" type="xs:string"/> <xs:element name="document_date" type="xs:string"/> <xs:element name="document_no" type="xs:string"/> <xs:element name="document_type" type="messagetype"/> <xs:element name="e_faktura_ref" type="xs:string"/> <xs:element name="orig_filename" type="xs:string"/> <xs:element name="orig_mq_message_id" type="xs:string"/> <xs:element name="process_count" type="xs:integer"/> <xs:element name="orig_line_no" type="xs:integer"/> <xs:element name="receipt_no" type="xs:string"/> <xs:element name="receiver_cvr_no" type="xs:string"/> <xs:element name="receiver_code" type="xs:string"/> <xs:element name="bill_to_customer_no" type="xs:string"/> <xs:element name="sender_cvr_no" type="xs:string"/> <xs:element name="sender_code" type="xs:string"/> <xs:element name="status" type="statusvals"/> <xs:element name="file_status" type="filestatuscodes"/> <xs:element name="file_status_text" type="filestatustext"/> <xs:element name="orig_reference" type="xs:string"/> <xs:element name="count" type="xs:string"/> <xs:simpletype name="statusvals"> <xs:restriction base="xs:string"> <xs:enumeration value="ok"/> <xs:enumeration value="error"/> </xs:restriction> </xs:simpletype> <xs:simpletype name="acknowlegementcodes"> <xs:restriction base="xs:string"> </xs:restriction> </xs:simpletype> <xs:simpletype name="acknowlegementtext"> <xs:restriction base="xs:string"> </xs:restriction> </xs:simpletype> <xs:simpletype name="filestatuscodes"> <xs:restriction base="xs:string"> e faktura kvitterings/acknowledgements format Side 24

28 </xs:restriction> </xs:simpletype> <xs:simpletype name="filestatustext"> <xs:restriction base="xs:string"> </xs:restriction> </xs:simpletype> <xs:simpletype name="messagetype"> <xs:restriction base="xs:string"> <xs:enumeration value="efaktura_invoice"/> <xs:enumeration value="efaktura_creditnote"/> <xs:enumeration value="pie"/> <xs:enumeration value="pcm"/> <xs:enumeration value="pip"/> <xs:enumeration value="pcp"/> <xs:enumeration value="pietest"/> <xs:enumeration value="pcmtest"/> <xs:enumeration value="piptest"/> <xs:enumeration value="pcptest"/> <xs:enumeration value=""/> </xs:restriction> </xs:simpletype> </xs:schema> e faktura kvitterings/acknowledgements format Side 25

29 5. Examples of acknowledgements (e faktura format) 5.1 Status OK All invoices was OK <ACKNOWLEDGEMENT> <DETAILS> <DETAIL> <ACK_NO>67ce9d22:102342fdddf:3361</ACK_NO> <SENDER_CODE> </SENDER_CODE> <RECEIVER_CODE> </RECEIVER_CODE> <BILL_TO_CUSTOMER_NO>129020</BILL_TO_CUSTOMER_NO> <RECEIPT_NO>72</RECEIPT_NO> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO>99328</DOCUMENT_NO> <DOCUMENT_TYPE>EFAKTURA_CREDITNOTE</DOCUMENT_TYPE> <STATUS>OK</STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9002</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>OIO Document Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> <DETAIL> <ACK_NO>67ce9d22:102342fdddf:335e</ACK_NO> <SENDER_CODE> </SENDER_CODE> <RECEIVER_CODE> </RECEIVER_CODE> <BILL_TO_CUSTOMER_NO>129020</BILL_TO_CUSTOMER_NO> <RECEIPT_NO>72</RECEIPT_NO> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO>99593</DOCUMENT_NO> <DOCUMENT_TYPE>EFAKTURA_CREDITNOTE</DOCUMENT_TYPE> <STATUS>OK</STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9002</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>OIO Document Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> </DETAILS> <SUMMARY> <DATE_TIME> T13:18: </DATE_TIME> <ORIG_FILENAME>C3E2D840E2F1D8F10F02C2D85B820E58BC9AF175A820EC83.zip</ORIG_FILENA ME> <STATUS>OK</STATUS> <ARR_COUNT>2</ARR_COUNT> <PROCESS_COUNT>2</PROCESS_COUNT> <ORIG_REFERENCE>99804</ORIG_REFERENCE> <COUNTS> <ACKNOWLEDGE_CODE>9002</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>OIO Document Sent</ACKNOWLEDGE_DESC> <COUNT>2</COUNT> </COUNTS> </SUMMARY> </ACKNOWLEDGEMENT> e faktura kvitterings/acknowledgements format Side 26

30 5.2 Status OK and ERROR One or more invoices failed Verification <ACKNOWLEDGEMENT> <DETAILS> <DETAIL> <ACK_NO>666bc9a4:10225bd8b54:-6ccc</ACK_NO> <SENDER_CODE>387553</SENDER_CODE> <RECEIVER_CODE>387553</RECEIVER_CODE> <BILL_TO_CUSTOMER_NO>129020</BILL_TO_CUSTOMER_NO> <RECEIPT_NO>72</RECEIPT_NO> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO> b</DOCUMENT_NO> <STATUS>ERROR</STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9102</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Invalid Legal Sender</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> <DETAIL> <ACK_NO>666bc9a4:10225bd8b54:-6784</ACK_NO> <SENDER_CODE>387553</SENDER_CODE> <RECEIVER_CODE>387553</RECEIVER_CODE> <BILL_TO_CUSTOMER_NO>129020</BILL_TO_CUSTOMER_NO> <RECEIPT_NO>72</RECEIPT_NO> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO> a</DOCUMENT_NO> <DOCUMENT_TYPE>EFAKTURA_CREDITNOTE</DOCUMENT_TYPE> <STATUS>OK</STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9001</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>eFaktura Document Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> </DETAILS> <SUMMARY> <DATE_TIME> T13:18: </DATE_TIME> <ORIG_FILENAME>eFaktura3e.zip</ORIG_FILENAME> <STATUS>ERROR</STATUS> <ARR_COUNT>2</ARR_COUNT> <PROCESS_COUNT>2</PROCESS_COUNT> <ORIG_REFERENCE> </ORIG_REFERENCE> <COUNTS> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> <COUNT>1</COUNT> </COUNTS> <COUNTS> <ACKNOWLEDGE_CODE>9001</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>eFaktura Document Sent</ACKNOWLEDGE_DESC> <COUNT>1</COUNT> e faktura kvitterings/acknowledgements format Side 27

31 </COUNTS> </SUMMARY> </ACKNOWLEDGEMENT> e faktura kvitterings/acknowledgements format Side 28

32 5.3 Status Error All invoices failed Verification <ACKNOWLEDGEMENT> <DETAILS> <DETAIL> <ACK_NO>67ce9d22:102342fdddf:-4532</ACK_NO> <SENDER_CODE>66100</SENDER_CODE> <RECEIVER_CODE>363636</RECEIVER_CODE> <BILL_TO_CUSTOMER_NO>129020</BILL_TO_CUSTOMER_NO> <RECEIPT_NO>72</RECEIPT_NO> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO>99443</DOCUMENT_NO> <DOCUMENT_TYPE>EFAKTURA_CREDITNOTE</DOCUMENT_TYPE> <STATUS>ERROR</STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9102</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Invalid Legal Sender</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> <DETAIL> <ACK_NO>67ce9d22:102342fdddf:-4400</ACK_NO> <SENDER_CODE>66100</SENDER_CODE> <RECEIVER_CODE>020202</RECEIVER_CODE> <BILL_TO_CUSTOMER_NO>129020</BILL_TO_CUSTOMER_NO> <RECEIPT_NO>72</RECEIPT_NO> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO>89122</DOCUMENT_NO> <DOCUMENT_TYPE>EFAKTURA_CREDITNOTE</DOCUMENT_TYPE> <STATUS>ERROR/STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9102</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Invalid Legal Sender</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> </DETAILS> <SUMMARY> <DATE_TIME> T13:18: </DATE_TIME> <ORIG_FILENAME>C3E2D840E2F1D8F10F02C3F85B820E58BC9ADB E86.zip</ORIG_FILENA ME> <STATUS>ERROR</STATUS> <ARR_COUNT>2</ARR_COUNT> <PROCESS_COUNT>2</PROCESS_COUNT> <ORIG_REFERENCE>28996</ORIG_REFERENCE> <COUNTS> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> e faktura kvitterings/acknowledgements format Side 29

33 <COUNT>2</COUNT> </COUNTS> </SUMMARY> </ACKNOWLEDGEMENT> e faktura kvitterings/acknowledgements format Side 30

34 5.4 rmal Error Acknowledgement <ACKNOWLEDGEMENT xmlns:xsi=" xsi:nonamespaceschemalocation="p:\projekter\it-projekter\u220301\opgdoku\infrastruktur\formatbeskrivelse og skemaer\working Examples\Acknowlegement\acknowledgement.xsd"> <DETAILS> <DETAIL> <ACK_NO>6f888027:101f576276b:2f5d</ACK_NO> <SENDER_CVR_NO> </SENDER_CVR_NO> <SENDER_CODE> </SENDER_CODE> <RECEIVER_CVR_NO> </RECEIVER_CVR_NO> <RECEIVER_CODE> </RECEIVER_CODE> <BILL_TO_CUSTOMER_NO>129020</BILL_TO_CUSTOMER_NO> <RECEIPT_NO>29232</RECEIPT_NO> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO> </DOCUMENT_NO> <DOCUMENT_TYPE>EFAKTURA_INVOICE</DOCUMENT_TYPE> <STATUS>ERROR</STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9102</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Invalid Legal Sender</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> </DETAILS> <SUMMARY> <DATE_TIME> T13:18: </DATE_TIME> <ORIG_FILENAME>eFaktura00001.zip</ORIG_FILENAME> <STATUS>ERROR</STATUS> <ARR_COUNT>1</ARR_COUNT> <PROCESS_COUNT>1</PROCESS_COUNT> <ORIG_REFERENCE> </ORIG_REFERENCE> <COUNTS> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> <COUNT>1</COUNT> </COUNTS> </SUMMARY> </ACKNOWLEDGEMENT> e faktura kvitterings/acknowledgements format Side 31

35 5.5 File Error Acknowledgement <?xml version="1.0" encoding="iso " standalone="yes"?> <ACKNOWLEDGEMENT xmlns:xsi=" xsi:nonamespaceschemalocation="acknowledgement.xsd"> <SUMMARY> <DATE_TIME> T12:37: </DATE_TIME> <ORIG_MQ_MESSAGE_ID>c3e2d840d2f2d8f be829b89aa22bd82</ORIG_M Q_MESSAGE_ID> <STATUS>ERROR</STATUS> <FILE_STATUS>9114</FILE_STATUS> <FILE_STATUS_TEXT>File is a duplicate</file_status_text> <ARR_COUNT>0</ARR_COUNT> <PROCESS_COUNT>0</PROCESS_COUNT> <ORIG_REFERENCE> </ORIG_REFERENCE> </SUMMARY> </ACKNOWLEDGEMENT> e faktura kvitterings/acknowledgements format Side 32

36 5.6 Acknowledge with error on line level <?xml version="1.0" encoding="iso " standalone="yes"?> <ACKNOWLEDGEMENT xmlns:xsi=" xsi:nonamespaceschemalocation="acknowledgement.xsd"> <DETAILS> <DETAIL> <ACK_NO>72eda33c-ed63-44a0-9d25-d78d58c7f05e</ACK_NO> <SENDER_CVR_NO> </SENDER_CVR_NO> <SENDER_CODE> </SENDER_CODE> <RECEIVER_CVR_NO> </RECEIVER_CVR_NO> <RECEIVER_CODE> </RECEIVER_CODE> <BILL_TO_CUSTOMER_NO>129020</BILL_TO_CUSTOMER_NO> <RECEIPT_NO> </RECEIPT_NO> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO>103050</DOCUMENT_NO> <DOCUMENT_TYPE>EFAKTURA_INVOICE</DOCUMENT_TYPE> <DOCUMENT_DATE> </DOCUMENT_DATE> <STATUS>ERROR</STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9106</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Invalid VAT_PCT</ACKNOWLEDGE_DESC> <ORIG_LINE_NO>10001</ORIG_LINE_NO> </ACKNOWLEDGE> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> </DETAILS> <SUMMARY> <ORIG_FILENAME>SP1file005.zip</ORIG_FILENAME> <STATUS>OK</STATUS> <FILE_STATUS>OK</FILE_STATUS> <ARR_COUNT>1</ARR_COUNT> <PROCESS_COUNT>1</PROCESS_COUNT> <ORIG_REFERENCE>17:08:12.161</ORIG_REFERENCE> <COUNTS> <ACKNOWLEDGE_CODE>9099</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>Document t Sent</ACKNOWLEDGE_DESC> <COUNT>1</COUNT> </COUNTS> </SUMMARY> </ACKNOWLEDGEMENT> e faktura kvitterings/acknowledgements format Side 33

37 6. Examples of acknowledgements (OIO format) 6.1 Status OK The invoice was OK <ACKNOWLEDGEMENT> <DETAILS> <DETAIL> <ACK_NO>67ce9d22:102342fdddf:3361</ACK_NO> <SENDER_CVR_NO> </SENDER_CVR_NO> <SENDER_CODE> </SENDER_CODE> <RECEIVER_CVR_NO> </RECEIVER_CVR_NO> <RECEIVER_CODE> </RECEIVER_CODE> <DATE_TIME> T13:18: </DATE_TIME> <DOCUMENT_NO>99328</DOCUMENT_NO> <DOCUMENT_TYPE>PIE</DOCUMENT_TYPE> <STATUS>OK</STATUS> <ACKNOWLEDGE> <ACKNOWLEDGE_CODE>9002</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>OIO Document Sent</ACKNOWLEDGE_DESC> </ACKNOWLEDGE> </DETAIL> <SUMMARY> <DATE_TIME> T13:18: </DATE_TIME> <ORIG_FILENAME>C3E2D840E2F1D8F10F02C2D85B820E58BC9AF175A820EC83.zip</ORIG_FILENA ME> <STATUS>OK</STATUS> <ARR_COUNT>1</ARR_COUNT> <PROCESS_COUNT>1</PROCESS_COUNT> <COUNTS> <ACKNOWLEDGE_CODE>9002</ACKNOWLEDGE_CODE> <ACKNOWLEDGE_DESC>OIO Document Sent</ACKNOWLEDGE_DESC> <COUNT>1</COUNT> </COUNTS> </SUMMARY> </ACKNOWLEDGEMENT> e faktura kvitterings/acknowledgements format Side 34