Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validation fails due to wrong value in tag <compensation> #34

Open
ErikSeverini opened this issue Feb 25, 2020 · 13 comments
Open

Validation fails due to wrong value in tag <compensation> #34

ErikSeverini opened this issue Feb 25, 2020 · 13 comments

Comments

@ErikSeverini
Copy link

We are implementing the SAF-T reporting and run into errors when validation the XML-file via upload at Skatteetaten. The file has passed validation when using the SAF-T XML-validator provided by Skatteetaten (SaftXmlValidator.exe). We have the following error message when uploading:

SAF-T 2020-01.xml
The 'urn:StandardAuditFile-Taxation-Financial:NO:Compensation' element is invalid - The value 'TRUE' is invalid
according to its datatype 'http://www.w3.org/2001/XMLSchema:boolean' -
The string 'TRUE' is not a valid Boolean value. On line number: 1, line position: 1790709.

It seems to be the that does now accept the value TRUE (and later on FALSE). However, the format description for the XML-file has these values for the tag. Here the definition is:

XML Element Description Type Req Rep Example
Compensation Indicates the Tax Code is used for compensation xs:Boolean O 0..U true

Thiss is the example provided:

n1:TaxTable
n1:TaxTableEntry
n1:TaxTypeMVA</n1:TaxType>
n1:DescriptionMerverdiavgift</n1:Description>
n1:TaxCodeDetails
n1:TaxCode14</n1:TaxCode>
n1:DescriptionInngående avgift, høy sats</n1:Description>
n1:TaxPercentage25</n1:TaxPercentage>
n1:CountryNO</n1:Country>
n1:StandardTaxCode1</n1:StandardTaxCode>
n1:Compensationyes</n1:Compensation>
n1:BaseRate100</n1:BaseRate>
n1:BaseRate60</n1:BaseRate>
</n1:TaxCodeDetails>
</n1:TaxTableEntry>
</n1:TaxTable

And this is how our file looks:

MVA Merverdiavgift E1 Purchase of remote services from abroad 25% 0.000 NO 86 TRUE 100.0

Has anyone seen this and was is the action? Any help will be much appriciated - thanks.

@TomEkenes
Copy link

Hi Erik
We have seen the same some places without solving it yet. Assume related to latest released notes. Have you found solution for this yet or waiting for OSS.
BR Tom Ekenes

@ErikSeverini
Copy link
Author

Hi Tom,
Thanks for your reply.

In fact we tried uploading the file in zipped version. Here no validation is done during upload. Later we receive acceptance from Norwegian Tax. We have then asked Norwegian Tax whether they have an error on their side. Still we have no answer from them.

Meanwhile SAP released note 2886281 addressing - among others - this error. Description for this is "After generating the SAF-T Financial file for Norway, does not have the correct values". I have asked out technical guys to implement this note. Once implemented and tested I will this thread.

BR, Erik Severini

@TomEkenes
Copy link

TomEkenes commented Mar 13, 2020 via email

@TomEkenes
Copy link

Hi Erik

We have gotten rid of the previous issue, but another new has been introduced:
Linje: 1, posisjon: 282257 - The element 'Customer' in namespace 'urn:StandardAuditFile-Taxation-Financial:NO' has invalid child element 'Address' in namespace 'urn:StandardAuditFile-Taxation-Financial:NO'. List of possible elements expected: 'RegistrationNumber, Name' in namespace 'urn:StandardAuditFile-Taxation-Financial:NO'.

So, another waiting game for new note.

BR Tom.

@ErikSeverini
Copy link
Author

Hi Tom.

Thanks a lot. I am still waiting for the 2886281 note implemention but it seems that this note resolved the issue. Maybe I will run into the other problem like you, but we will see. I will keep you updated here.

Have a great day!
BR, Erik

@ErikSeverini
Copy link
Author

Hi Tom.

It tool some time to have the note implemented, but we got it now. We are now at the same level as you. We also got the same error as you. I tried adding the missing tag manually and then the file passes validation. The tag is and it should be between and . I also noted that this tag was there in previous files but has disappeared now .

This is how the modified file looks.



1.10
NO
2020-04-06
SAP EU
SAP ERP 6.0
2005


Company

Address
Lysaker
1366
NO
StreetAddress

Did you manage to get any further?

BR, Erik

@ErikSeverini
Copy link
Author

Oops - something went wrong with the formatting when sending the message. What I mean is that the tag RegistrationNumber should be inserted between tags Company and Name.

Does that make any sense?

@TomEkenes
Copy link

TomEkenes commented Apr 6, 2020 via email

@ErikSeverini
Copy link
Author

Hi Tom,

I think we are missing 2 notes. The latest note implemented is 2894075. I see now 2 more notes released after this - 2907856 and 2908369. Are you referring to one of these? We will have them implemented as well.

It seems that the solution is not really complete for Norway as SAP constantly releases new notes.

And obviously we will not modify the files. I just tried it to see if it worked,

BR, Erik

@TomEkenes
Copy link

TomEkenes commented Apr 6, 2020 via email

@ErikSeverini
Copy link
Author

Hi Tom,

Sorry to bother you again. We have now implemented the following notes in this sequence:

  1. 2907856
  2. 2894075
  3. 2908369
  4. 2912756 (this note was released on 9th April)

We still have the same error as described above. that there is a RegistrationNumber tag missing between the Company tag and Name tag. So, the notes did not help. Did I understand you corretly that you had the same problem, but the notes did solve this?

Thanks again for your help.

BR, Erik

@TomEkenes
Copy link

TomEkenes commented Apr 15, 2020 via email

@ErikSeverini
Copy link
Author

Hi Tom.

I just want to give you a short feed back. Note implementation on our side is done by an external team and they confirm that the notes have been implemented in the correct sequence (this is 2907856 before 2894075). But, as 2894075 is addressing exactly the problem, I am not completely sure. However, I am not that technical so I cannot verify myself.

I will update you again when we have news.

Once again, thanks a lot for your help with this.

BR, Erik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants