Back to Home Page Ilmoitin.fi  

Reading the report

The check process will give you results that show whether the filing is formally correct. If it must be corrected, the check result will help you find the problems. Use the software that had made the filings to correct the errors in them.

Report description

The report shows the checkup results separately for each data element. Their names and numbers are shown. If included in the keyManager filing, the report will also show the filer's identification number.

If the entire record is correctly submitted, the data elements will be colored green and you can see the words 'Formal requirements are fulfilled'. If there are errors, the data elements will be colored red and all the errors will be enumerated on separate lines.

The error line shows the ID of the data element. It is either an identifier (for the identifier:information format) or a position (for the fixed-length format). However, sometimes the ID is not known. Thus no ID is shown if the error cannot be pinpointed as a line-specific error. Furthemore, the error line shows the value, if known, of the relevant data element. Then is shows a text explaining the nature of the error. For more information, see Description of error types.

Example of report table:

Tax return of business operations, corporation (6B) (VSY06B20) Filer's identification number 6606611-7
Formal requirements are fulfilled
Tax return of business operations, corporation (6B) (VSY06B20) Filer's identification number 6606611-7
Error Data element error 177 (1) If auditors have handed in their report (177=1), also populate position 178 to show auditors' approval or disapproval.
Remark Data element remark 180 (1) Is this indeed an Other enclosure, not a statutory enclosure or a tax form?
Tax return of business operations, corporation (6B) (VSY06B20) Filer's identification number 6606611-7
Data element remark 365 (VSY062) You have filled out Form 6B to report depreciation expenses. Please file Form 62 to specify.
Data element remark 364 (VSY062) You have filled out Form 6B to report depreciation expenses. Please file Form 62 to specify.

Description of error types

Error types can be categorized as follows:

  • missing mandatory information
    Example: "Mandatory information Taxpayers name missing from record".
  • conditionally required information is missing
    for example,
    "Report either interest (104) or principal (106) in the record" or
    "If Date of 'commencement of the payment' (538) is populated, populate Date of decision to pay out dividend (537)" or
    "If you used the date of birth, write name, address and postal code".
  • the code does not relate to the record
    example: "Code 502 does not relate to record VSRAERIE"
  • the data content is not compatible with the format requirements set out in the Data Record Specification
    for example,
    "Invalid characters in the integer. Negative integers are not permitted. Use comma as the separator character" or "Invalid date format" or
    "Invalid Business ID or Personal Identity Code"
  • the data content is not compatible with the permissible values set out in the Data Record Specification
    for example,
    "Error in data. Possible values are A, B, C, 0" or
    "Invalid country code. See form no VEROH 7809 for permitted values"
  • data element content does not comply with the calculation rules
    for example,
    "Deduction of excess tax at source (510) cannot exceed Tax At Source (509)" or
    "Shares of work efforts (100 + 102) do not add up to 100%"
  • data element content does not comply with the relevant special rules
    for example,
    "Period of no activity (056) cannot extend further than 6 months into the future" or
    "You cannot populate positions 40 to 79 if Type of Payment is 2 (repayment of shareholder loan). One record can only include one Type of Payment." or
    "The year in the date should be the tax year".

Errors that cause interruption

Some critical errors in the filing can cause the checkup procedure to halt. In this case, the filer should correct the errors before Ilmoitin.fi can complete the checking procedure.

"Cannot send the record for the year XXXX" - In this case, Ilmoitin.fi is trying to check the contents of a filing that does not follow the valid Data Record Specification or has an erroneous year. Most annual information returns are intended to have either the calendar year, the payment year or the taxable year as the year of reference. Other information returns only have the year included in a certain date, e.g. the date of payment. Nevertheless, the Data Record Specification contains instructions for correctly indicating the year.

"The record contains no year. The year is mandatory. Verify aborted." - Ilmoitin.fi searches for the relevant checkup rules on the basis of the indicated year. If the filer has failed to give the year, there will be no relevant Data Record Specification to which Ilmoitin.fi could start comparing the filing. Most annual information returns are intended to have either the calendar year, the payment year or the taxable year as the year of reference. Other information returns only have the year included in a certain date, e.g. the date of payment. Nevertheless, the Data Record Specification contains instructions for correctly indicating the year.

"Error. Only the following years are valid XXXX, XXXX" - The check feature is designed for testing electronic filings over a two-year period on the condition that a Data File Specification continues to be in force. However, this rule does not concern the checking of tax returns for self-assessed taxes because they are not bound by tax years.

"Batch does not start with 000. Verify aborted." - If the format of the filing is identifier:information, the start code 000 should always show in the beginning. If it is not there, Ilmoitin.fi cannot recognize the type of the filing, and cannot check it.