services.krediidiinfo.ee - User contributions [en]

RAXPENSK

2021-11-24T07:45:23Z

Andrus:

== 1. Short description ==

Purpose of the report is to give an estimation of the private persons’ bruto income. Income is calculated from the pension payments. Pension payment makes up certain percent of the bruto income of the person.
Pension registry offers a paid service for querying pension payments of the private persons from last six months. We calculate bruto income estimation about last five full months.
There can be cases when there will be no estimation of the income:

# Person has no active pension account.
# Person has active pension account but has no pension payment obligation permanently.
# Person has active pension account but has no pension payment obligation temporarily.

Pension Registry has created a free web query to request this information. We use this query to determine if the person has payment obligation before the query of the pension payments will be made. We also put the payment obligation change information to the report, if the change happened during last six months.

== 2. Pension Registry’s payment obligation query ==

The information, what can be read out from the Pension Registry’s payment obligation query response:

# The status of the private person’s pension account.
# Information about the periods person have had active pension account.
# Information about the periods person have had pension payment obligation.
# Information about the periods person have paused pension payment obligation.

'''''Example 1:'''''
<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="3870430xxxx" CONTRIBUTION_BEGIN_DATE="20060101" Y_2010="N" Y_2014_2017="N" Y_2020="Y" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>
<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 1 explanation:'''''
* Person has active pension account:
''PENSION_ACCOUNT_STATUS="A"''

* Person has active payment obligation from 01.01.2006:
''<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>''

* Payment obligation was paused two times for this person:
''<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>''

''<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
''

'''''Example 2:'''''

<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="4530624xxxx" CONTRIBUTION_BEGIN_DATE="20030101" CONTRIBUTION_END_DATE="20140101" Y_2010="Y" Y_2014_2017="N" Y_2020="N" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 2 explanation:'''''

* Person has active pension account:
PENSION_ACCOUNT_STATUS="A"

* Person has active payment obligation from 01.01.2003 to 01.01.2014 :
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>

* Payment obligation was paused fro this person:
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>

* Person has no payment obligation since 01.01.2014:
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>

== 3. Pension registry's pension payments query ==

When we receive information from payment obligation query that person had payment obligation in at least one month during last 6 month, the payment obligation query is made. Query response includes all payments to pension registry during last six months. The first payment, which can appear to the response, can be from the query date minus 6 months.

'''''Example of the query response:'''''

<code><pre>
<laekumisedBody>
<ns3:laekumised_maksuametistResponse
xmlns:ns3="http://producers.kpr.x-road.eu/producer/kpr">
<ISIKUKOOD>XXXXXXXXXXX</ISIKUKOOD>
<EESNIMI>XXXXXXX</EESNIMI>
<PEREKONNANIMI>XXXXXX</PEREKONNANIMI>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>7.12</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-15</KUUPAEV>
<SUMMA>7.44</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>32.03</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>14.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>11.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>35.30</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
</ns3:laekumised_maksuametistResponse>
</laekumisedBody>
</pre></code>

== 4. RAXPENSK xml report from Creditinfo ==

All the detailed information about the report structure can be found in the xml schema RAXPENSK.xsd [https://services.krediidiinfo.ee/schemas/report/RAXPENSK.xsd].

'''''Report contents:'''''

* Report includes the responses from the Pension Registry payment obligation query and pension payment query.

* For better readability of the payment obligation query, we have added payment obligation descriptions:

<code><pre>
<payment_duties>
<payment_duty>
<start_date>2004-01-01</start_date>
<end_date>2021-08-31</end_date>
<meaning>maksekohustus on / sissemaksete tegemine</meaning>
</payment_duty>
<payment_duty>
<start_date>2021-09-01</start_date>
<end_date xsi:nil="true"/>
<meaning>maksekohustust ei ole / maksete mittetegemine</meaning>
</payment_duty>
</payment_duties>
</pre></code>

* If there is error with querying data from Pension Registry or the payment query was not made, the explanation is added to the report. If the comment explains error, then is_error attribute is equal to True:
<code><pre>
<comment is_error="false">Ei tehtud maksuametisse toimunud laekumiste päringut, sest maksete kohustus puudub.</comment>
</pre></code>

* It is possible for the parent to receive parent pension to pension account. In that case we cannot include the sum in bruto wage calculation. If this is the case a warning will be shown in the report:

<code><pre>
"warning": "Isikul võib Pensionikeskuse laekumiste hulgas olla vanemapensioni makseid!"
</pre></code>

* Report includes Bruto wages section with attributes start_date and end_date for showing the period of the wages calculation period. The wages calculation period is different from the pension payments period as there might not be shown all monthly payments from the first and last month of the payments.
Monthly wage will be calculated from the sum of the monthly payments to the pension account. If there is a record about pension registry payment for the person in the Pension Registry’s response the bruto wage will be calculated.

<code><pre>
<gross_salaries start_date="2021-06-01"
end_date="2021-10-31">
<gross_salary>
<year>2021</year>
<month>6</month>
<salary>1991</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>7</month>
<salary>2007</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>8</month>
<salary>2338</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>9</month>
<salary>2352</salary>
</gross_salary>
</gross_salaries>
</pre></code>

* Average bruto wage will be calculated from the monthly wages, which in turn are calculated from pension payments.

<code><pre>
<average_bruto_wage>1561</average_bruto_wage>
</pre></code>

== Testing ==

Testing should be agreed with Creditinfo Estonia

'''Testcodes in pension registry:'''

48206045995
48408301152
47706065008
37610064646
37506274720
37905279571
47212076363
48106165456
38209303547
46508303070

RAXPENSK

2021-11-18T14:45:17Z

Andrus:

== 1. Short description ==

Purpose of the report is to give an estimation of the private persons’ bruto income. Income is calculated from the pension payments. Pension payment makes up certain percent of the bruto income of the person.
Pension registry offers a paid service for querying pension payments of the private persons from last six months. We calculate bruto income estimation about last five full months.
There can be cases when there will be no estimation of the income:

# Person has no active pension account.
# Person has active pension account but has no pension payment obligation permanently.
# Person has active pension account but has no pension payment obligation temporarily.

Pension Registry has created a free web query to request this information. We use this query to determine if the person has payment obligation before the query of the pension payments will be made. We also put the payment obligation change information to the report, if the change happened during last six months.

== 2. Pension Registry’s payment obligation query ==

The information, what can be read out from the Pension Registry’s payment obligation query response:

# The status of the private person’s pension account.
# Information about the periods person have had active pension account.
# Information about the periods person have had pension payment obligation.
# Information about the periods person have paused pension payment obligation.

'''''Example 1:'''''
<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="3870430xxxx" CONTRIBUTION_BEGIN_DATE="20060101" Y_2010="N" Y_2014_2017="N" Y_2020="Y" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>
<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 1 explanation:'''''
* Person has active pension account:
''PENSION_ACCOUNT_STATUS="A"''

* Person has active payment obligation from 01.01.2006:
''<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>''

* Payment obligation was paused two times for this person:
''<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>''

''<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
''

'''''Example 2:'''''

<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="4530624xxxx" CONTRIBUTION_BEGIN_DATE="20030101" CONTRIBUTION_END_DATE="20140101" Y_2010="Y" Y_2014_2017="N" Y_2020="N" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 2 explanation:'''''

* Person has active pension account:
PENSION_ACCOUNT_STATUS="A"

* Person has active payment obligation from 01.01.2003 to 01.01.2014 :
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>

* Payment obligation was paused fro this person:
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>

* Person has no payment obligation since 01.01.2014:
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>

== 3. Pension registry's pension payments query ==

When we receive information from payment obligation query that person had payment obligation in at least one month during last 6 month, the payment obligation query is made. Query response includes all payments to pension registry during last six months. The first payment, which can appear to the response, can be from the query date minus 6 months.

'''''Example of the query response:'''''

<code><pre>
<laekumisedBody>
<ns3:laekumised_maksuametistResponse
xmlns:ns3="http://producers.kpr.x-road.eu/producer/kpr">
<ISIKUKOOD>XXXXXXXXXXX</ISIKUKOOD>
<EESNIMI>XXXXXXX</EESNIMI>
<PEREKONNANIMI>XXXXXX</PEREKONNANIMI>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>7.12</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-15</KUUPAEV>
<SUMMA>7.44</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>32.03</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>14.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>11.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>35.30</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
</ns3:laekumised_maksuametistResponse>
</laekumisedBody>
</pre></code>

== 4. RAXPENSK xml report from Creditinfo ==

All the detailed information about the report structure can be found in the xml schema RAXPENSK.xsd [https://services.krediidiinfo.ee/schemas/report/RAXPENSK.xsd].

'''''Report contents:'''''

* Report includes the responses from the Pension Registry payment obligation query and pension payment query.

* For better readability of the payment obligation query, we have added payment obligation descriptions:

<code><pre>
<payment_duties>
<payment_duty>
<start_date>2004-01-01</start_date>
<end_date>2021-08-31</end_date>
<meaning>maksekohustus on / sissemaksete tegemine</meaning>
</payment_duty>
<payment_duty>
<start_date>2021-09-01</start_date>
<end_date xsi:nil="true"/>
<meaning>maksekohustust ei ole / maksete mittetegemine</meaning>
</payment_duty>
</payment_duties>
</pre></code>

* If there is error with querying data from Pension Registry or the payment query was not made, the explanation is added to the report. If the comment explains error, then is_error attribute is equal to True:
<code><pre>
<comment is_error="false">Ei tehtud maksuametisse toimunud laekumiste päringut, sest maksete kohustus puudub.</comment>
</pre></code>

* It is possible for the parent to receive parent pension to pension account. In that case we cannot include the sum in bruto wage calculation. If this is the case a warning will be shown in the report:

<code><pre>
"warning": "Isikul võib Pensionikeskuse laekumiste hulgas olla vanemapensioni makseid!"
</pre></code>

* Report includes Bruto wages section with attributes start_date and end_date for showing the period of the wages calculation period. The wages calculation period is different from the pension payments period as there might not be shown all monthly payments from the first and last month of the payments.
Monthly wage will be calculated from the sum of the monthly payments to the pension account. If there is a record about pension registry payment for the person in the Pension Registry’s response the bruto wage will be calculated.

<code><pre>
<gross_salaries start_date="2021-06-01"
end_date="2021-10-31">
<gross_salary>
<year>2021</year>
<month>6</month>
<salary>1991</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>7</month>
<salary>2007</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>8</month>
<salary>2338</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>9</month>
<salary>2352</salary>
</gross_salary>
</gross_salaries>
</pre></code>

* Average bruto wage will be calculated from the monthly wages, which in turn are calculated from pension payments.

<code><pre>
<average_bruto_wage>1561</average_bruto_wage>
</pre></code>

== Testing ==

Testing should be agreed with Creditinfo Estonia

'''Testcodes in pension registry:'''

48206045995
48408301152
47706065008
37610064646
47803312958
37506274720
37905279571
47212076363
48106165456
38209303547
46508303070

RAXPENSK

2021-11-18T10:00:37Z

Andrus:

RAXPENSK

2021-11-18T09:40:27Z

Andrus:

RAXPENSK

2021-11-18T09:38:31Z

Andrus:

== 1. Short description ==

Purpose of the report is to give an estimation of the private persons’ bruto income. Income is calculated from the pension payments. Pension payment makes up certain percent of the bruto income of the person.
Pension registry offers a paid service for querying pension payments of the private persons from last six months. We calculate bruto income estimation about last five full months.
There can be cases when there will be no estimation of the income:

# Person has no active pension account.
# Person has active pension account but has no pension payment obligation permanently.
# Person has active pension account but has no pension payment obligation temporarily.

Pension Registry has created a free web query to request this information. We use this query to determine if the person has payment obligation before the query of the pension payments will be made. We also put the payment obligation change information to the report, if the change happened during last six months.

== 2. Pension Registry’s payment obligation query ==

The information, what can be read out from the Pension Registry’s payment obligation query response:

# The status of the private person’s pension account.
# Information about the periods person have had active pension account.
# Information about the periods person have had pension payment obligation.
# Information about the periods person have paused pension payment obligation.

'''''Example 1:'''''
<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="3870430xxxx" CONTRIBUTION_BEGIN_DATE="20060101" Y_2010="N" Y_2014_2017="N" Y_2020="Y" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>
<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 1 explanation:'''''
* Person has active pension account:
''PENSION_ACCOUNT_STATUS="A"''

* Person has active payment obligation from 01.01.2006:
''<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>''

* Payment obligation was paused two times for this person:
''<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>''

''<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
''

'''''Example 2:'''''

<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="4530624xxxx" CONTRIBUTION_BEGIN_DATE="20030101" CONTRIBUTION_END_DATE="20140101" Y_2010="Y" Y_2014_2017="N" Y_2020="N" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 2 explanation:'''''

* Person has active pension account:
PENSION_ACCOUNT_STATUS="A"

* Person has active payment obligation from 01.01.2003 to 01.01.2014 :
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>

* Payment obligation was paused fro this person:
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>

* Person has no payment obligation since 01.01.2014:
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>

== 3. Pension registry pension payments query ==

When we receive information from payment obligation query that person had payment obligation in at least one month during last 6 month, the payment obligation query is made. Query response includes all payments to pension registry during last six months. The first payment, which can appear to the response, can be from the query date minus 6 months.

'''''Example of the query response:'''''

<code><pre>
<laekumisedBody>
<ns3:laekumised_maksuametistResponse
xmlns:ns3="http://producers.kpr.x-road.eu/producer/kpr">
<ISIKUKOOD>XXXXXXXXXXX</ISIKUKOOD>
<EESNIMI>XXXXXXX</EESNIMI>
<PEREKONNANIMI>XXXXXX</PEREKONNANIMI>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>7.12</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-15</KUUPAEV>
<SUMMA>7.44</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>32.03</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>14.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>11.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>35.30</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
</ns3:laekumised_maksuametistResponse>
</laekumisedBody>
</pre></code>

== 4. RAXPENSK xml report from Creditinfo ==

All the detailed information about the report structure can be found in the xml schema RAXPENSK.xsd [https://services.krediidiinfo.ee/schemas/report/RAXPENSK.xsd].

'''''Report contents:'''''

* Report includes the responses from the Pension Registry payment obligation query and pension payment query.

* For better readability of the payment obligation query, we have added payment obligation descriptions:

<code><pre>
<payment_duties>
<payment_duty>
<start_date>2004-01-01</start_date>
<end_date>2021-08-31</end_date>
<meaning>maksekohustus on / sissemaksete tegemine</meaning>
</payment_duty>
<payment_duty>
<start_date>2021-09-01</start_date>
<end_date xsi:nil="true"/>
<meaning>maksekohustust ei ole / maksete mittetegemine</meaning>
</payment_duty>
</payment_duties>
</pre></code>

* If there is error with querying data from Pension Registry or the payment query was not made, the explanation is added to the report. If the comment explains error, then is_error attribute is equal to True:
<code><pre>
<comment is_error="false">Ei tehtud maksuametisse toimunud laekumiste päringut, sest maksete kohustus puudub.</comment>
</pre></code>

* It is possible for the parent to receive parent pension to pension account. In that case we cannot include the sum in bruto wage calculation. If this is the case a warning will be shown in the report:

<code><pre>
"warning": "Isikul võib Pensionikeskuse laekumiste hulgas olla vanemapensioni makseid!"
</pre></code>

* Report includes Bruto wages section with attributes start_date and end_date for showing the period of the wages calculation period. The wages calculation period is different from the pension payments period as there might not be shown all monthly payments from the first and last month of the payments.
Monthly wage will be calculated from the sum of the monthly payments to the pension account. If there is a record about pension registry payment for the person in the Pension Registry’s response the bruto wage will be calculated.

<code><pre>
<gross_salaries start_date="2021-06-01"
end_date="2021-10-31">
<gross_salary>
<year>2021</year>
<month>6</month>
<salary>1991</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>7</month>
<salary>2007</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>8</month>
<salary>2338</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>9</month>
<salary>2352</salary>
</gross_salary>
</gross_salaries>
</pre></code>

RAXPENSK

2021-11-18T09:37:34Z

Andrus:

== 1. Short description ==

Purpose of the report is to give an estimation of the private persons’ bruto income. Income is calculated from the pension payments. Pension payment makes up certain percent of the bruto income of the person.
Pension registry offers a paid service for querying pension payments of the private persons from last six months. We calculate bruto income estimation about last five full months.
There can be cases when there will be no estimation of the income:

# Person has no active pension account.
# Person has active pension account but has no pension payment obligation permanently.
# Person has active pension account but has no pension payment obligation temporarily.

Pension Registry has created a free web query to request this information. We use this query to determine if the person has payment obligation before the query of the pension payments will be made. We also put the payment obligation change information to the report, if the change happened during last six months.

== 2. Pension Registry’s payment obligation query ==

The information, what can be read out from the Pension Registry’s payment obligation query response:

# The status of the private person’s pension account.
# Information about the periods person have had active pension account.
# Information about the periods person have had pension payment obligation.
# Information about the periods person have paused pension payment obligation.

'''''Example 1:'''''
<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="3870430xxxx" CONTRIBUTION_BEGIN_DATE="20060101" Y_2010="N" Y_2014_2017="N" Y_2020="Y" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>
<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 1 explanation:'''''
* Person has active pension account:
''PENSION_ACCOUNT_STATUS="A"''

* Person has active payment obligation from 01.01.2006:
''<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>''

* Payment obligation was paused two times for this person:
''<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>''

''<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
''

'''''Example 2:'''''

<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="4530624xxxx" CONTRIBUTION_BEGIN_DATE="20030101" CONTRIBUTION_END_DATE="20140101" Y_2010="Y" Y_2014_2017="N" Y_2020="N" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 2 explanation:'''''

* Person has active pension account:
PENSION_ACCOUNT_STATUS="A"

* Person has active payment obligation from 01.01.2003 to 01.01.2014 :
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>

* Payment obligation was paused fro this person:
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>

* Person has no payment obligation since 01.01.2014:
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>

== 3. Pension registry pension payments query ==

When we receive information from payment obligation query that person had payment obligation in at least one month during last 6 month, the payment obligation query is made. Query response includes all payments to pension registry during last six months. The first payment, which can appear to the response, can be from the query date minus 6 months.

'''''Example of the query response:'''''

<code><pre>
<laekumisedBody>
<ns3:laekumised_maksuametistResponse
xmlns:ns3="http://producers.kpr.x-road.eu/producer/kpr">
<ISIKUKOOD>XXXXXXXXXXX</ISIKUKOOD>
<EESNIMI>XXXXXXX</EESNIMI>
<PEREKONNANIMI>XXXXXX</PEREKONNANIMI>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>7.12</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-15</KUUPAEV>
<SUMMA>7.44</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>32.03</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>14.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>11.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>35.30</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
</ns3:laekumised_maksuametistResponse>
</laekumisedBody>
</pre></code>

== 4. RAXPENSK xml report from Creditinfo ==

All the detailed information about the report structure can be found in the xml schema RAXPENSK.xsd [https://services.krediidiinfo.ee/schemas/report/RAXPENSK.xsd].

'''''Report contents:'''''

* Report includes the responses from the Pension Registry payment obligation query and pension payment query.

* For better readability of the payment obligation query, we have added payment obligation descriptions:

<code><pre>
<payment_duties>
<payment_duty>
<start_date>2004-01-01</start_date>
<end_date>2021-08-31</end_date>
<meaning>maksekohustus on / sissemaksete tegemine</meaning>
</payment_duty>
<payment_duty>
<start_date>2021-09-01</start_date>
<end_date xsi:nil="true"/>
<meaning>maksekohustust ei ole / maksete mittetegemine</meaning>
</payment_duty>
</payment_duties>
</pre></code>

* If there is error with querying data from Pension Registry or the payment query was not made, the explanation is added to the report. If the comment explains error, then is_error attribute is equal to True:
<code><pre>
<comment is_error="false">Ei tehtud maksuametisse toimunud laekumiste päringut, sest maksete kohustus puudub.</comment>
</pre></code>

* It is possible for the parent to receive parent pension to pension account. In that case we cannot include the sum in bruto wage calculation. If this is the case a warning will be shown in the report:

<code><pre>
"warning": "Isikul võib Pensionikeskuse laekumiste hulgas olla vanemapensioni makseid!"
</pre></code>

* 4. Report includes Bruto wages section with attributes start_date and end_date for showing the period of the wages calculation period. The wages calculation period is different from the pension payments period as there might not be shown all monthly payments from the first and last month of the payments.
Monthly wage will be calculated from the sum of the monthly payments to the pension account. If there is a record about pension registry payment for the person in the Pension Registry’s response the bruto wage will be calculated.

<code><pre>
<gross_salaries start_date="2021-06-01"
end_date="2021-10-31">
<gross_salary>
<year>2021</year>
<month>6</month>
<salary>1991</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>7</month>
<salary>2007</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>8</month>
<salary>2338</salary>
</gross_salary>
<gross_salary>
<year>2021</year>
<month>9</month>
<salary>2352</salary>
</gross_salary>
</gross_salaries>
</pre></code>

RAXPENSK

2021-11-18T09:30:19Z

Andrus:

== 1. Short description ==

Purpose of the report is to give an estimation of the private persons’ bruto income. Income is calculated from the pension payments. Pension payment makes up certain percent of the bruto income of the person.
Pension registry offers a paid service for querying pension payments of the private persons from last six months. We calculate bruto income estimation about last five full months.
There can be cases when there will be no estimation of the income:

# Person has no active pension account.
# Person has active pension account but has no pension payment obligation permanently.
# Person has active pension account but has no pension payment obligation temporarily.

Pension Registry has created a free web query to request this information. We use this query to determine if the person has payment obligation before the query of the pension payments will be made. We also put the payment obligation change information to the report, if the change happened during last six months.

== 2. Pension Registry’s payment obligation query ==

The information, what can be read out from the Pension Registry’s payment obligation query response:

# The status of the private person’s pension account.
# Information about the periods person have had active pension account.
# Information about the periods person have had pension payment obligation.
# Information about the periods person have paused pension payment obligation.

'''''Example 1:'''''
<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="3870430xxxx" CONTRIBUTION_BEGIN_DATE="20060101" Y_2010="N" Y_2014_2017="N" Y_2020="Y" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>
<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 1 explanation:'''''
* Person has active pension account:
''PENSION_ACCOUNT_STATUS="A"''

* Person has active payment obligation from 01.01.2006:
''<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>''

* Payment obligation was paused two times for this person:
''<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>''

''<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
''

'''''Example 2:'''''

<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="4530624xxxx" CONTRIBUTION_BEGIN_DATE="20030101" CONTRIBUTION_END_DATE="20140101" Y_2010="Y" Y_2014_2017="N" Y_2020="N" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 2 explanation:'''''

* Person has active pension account:
PENSION_ACCOUNT_STATUS="A"

* Person has active payment obligation from 01.01.2003 to 01.01.2014 :
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>

* Payment obligation was paused fro this person:
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>

* Person has no payment obligation since 01.01.2014:
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>

== 3. Pension registry pension payments query ==

When we receive information from payment obligation query that person had payment obligation in at least one month during last 6 month, the payment obligation query is made. Query response includes all payments to pension registry during last six months. The first payment, which can appear to the response, can be from the query date minus 6 months.

'''''Example of the query response:'''''

<code><pre>
<laekumisedBody>
<ns3:laekumised_maksuametistResponse
xmlns:ns3="http://producers.kpr.x-road.eu/producer/kpr">
<ISIKUKOOD>XXXXXXXXXXX</ISIKUKOOD>
<EESNIMI>XXXXXXX</EESNIMI>
<PEREKONNANIMI>XXXXXX</PEREKONNANIMI>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>7.12</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-15</KUUPAEV>
<SUMMA>7.44</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>32.03</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>14.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>11.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>35.30</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
</ns3:laekumised_maksuametistResponse>
</laekumisedBody>
</pre></code>

== 4. RAXPENSK xml report from Creditinfo ==

All the detailed information about the report structure can be found in the xml schema RAXPENSK.xsd [https://services.krediidiinfo.ee/schemas/report/RAXPENSK.xsd].

'''''Report contents:'''''

* Report includes the responses from the Pension Registry payment obligation query and pension payment query.

* For better readability of the payment obligation query, we have added payment obligation descriptions:

<code><pre>
<payment_duties>
<payment_duty>
<start_date>2004-01-01</start_date>
<end_date>2021-08-31</end_date>
<meaning>maksekohustus on / sissemaksete tegemine</meaning>
</payment_duty>
<payment_duty>
<start_date>2021-09-01</start_date>
<end_date xsi:nil="true"/>
<meaning>maksekohustust ei ole / maksete mittetegemine</meaning>
</payment_duty>
</payment_duties>
</pre></code>

* If there is error with querying data from Pension Registry or the payment query was not made, the explanation is added to the report. If the comment explains error, then is_error attribute is equal to True:
<code><pre>
<comment is_error="false">Ei tehtud maksuametisse toimunud laekumiste päringut, sest maksete kohustus puudub.</comment>
</pre></code>

RAXPENSK

2021-11-18T09:26:55Z

Andrus:

== 1. Short description ==

Purpose of the report is to give an estimation of the private persons’ bruto income. Income is calculated from the pension payments. Pension payment makes up certain percent of the bruto income of the person.
Pension registry offers a paid service for querying pension payments of the private persons from last six months. We calculate bruto income estimation about last five full months.
There can be cases when there will be no estimation of the income:

# Person has no active pension account.
# Person has active pension account but has no pension payment obligation permanently.
# Person has active pension account but has no pension payment obligation temporarily.

Pension Registry has created a free web query to request this information. We use this query to determine if the person has payment obligation before the query of the pension payments will be made. We also put the payment obligation change information to the report, if the change happened during last six months.

== 2. Pension Registry’s payment obligation query ==

The information, what can be read out from the Pension Registry’s payment obligation query response:

# The status of the private person’s pension account.
# Information about the periods person have had active pension account.
# Information about the periods person have had pension payment obligation.
# Information about the periods person have paused pension payment obligation.

'''''Example 1:'''''
<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="3870430xxxx" CONTRIBUTION_BEGIN_DATE="20060101" Y_2010="N" Y_2014_2017="N" Y_2020="Y" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>
<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 1 explanation:'''''
* Person has active pension account:
''PENSION_ACCOUNT_STATUS="A"''

* Person has active payment obligation from 01.01.2006:
''<PAYMENT_DUTY START_DATE="20060101" DUTY="T"/>''

* Payment obligation was paused two times for this person:
''<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20101231"/>''

''<PAYMENT_DUTY START_DATE="20201201" DUTY="K" END_DATE="20210831"/>
''

'''''Example 2:'''''

<code><pre>
<FIND_PAYMENT_DUTIES xmlns="http://corporate.epis.ee/producer/">
<PERSON PERSON_CODE="4530624xxxx" CONTRIBUTION_BEGIN_DATE="20030101" CONTRIBUTION_END_DATE="20140101" Y_2010="Y" Y_2014_2017="N" Y_2020="N" PENSION_ACCOUNT_STATUS="A">
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>
</PERSON>
</FIND_PAYMENT_DUTIES>
</pre></code>

'''''Example 2 explanation:'''''

* Person has active pension account:
PENSION_ACCOUNT_STATUS="A"

* Person has active payment obligation from 01.01.2003 to 01.01.2014 :
<PAYMENT_DUTY START_DATE="20030101" DUTY="T" END_DATE="20140101"/>

* Payment obligation was paused fro this person:
<PAYMENT_DUTY START_DATE="20090601" DUTY="K" END_DATE="20091231"/>

* Person has no payment obligation since 01.01.2014:
<PAYMENT_DUTY START_DATE="20140101" DUTY="M"/>

== 3. Pension registry pension payments query ==

When we receive information from payment obligation query that person had payment obligation in at least one month during last 6 month, the payment obligation query is made. Query response includes all payments to pension registry during last six months. The first payment, which can appear to the response, can be from the query date minus 6 months.

'''''Example of the query response:'''''

<code><pre>
<laekumisedBody>
<ns3:laekumised_maksuametistResponse
xmlns:ns3="http://producers.kpr.x-road.eu/producer/kpr">
<ISIKUKOOD>XXXXXXXXXXX</ISIKUKOOD>
<EESNIMI>XXXXXXX</EESNIMI>
<PEREKONNANIMI>XXXXXX</PEREKONNANIMI>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-06-14</KUUPAEV>
<SUMMA>7.12</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-14</KUUPAEV>
<SUMMA>32.70</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-07-15</KUUPAEV>
<SUMMA>7.44</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>32.03</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-08-12</KUUPAEV>
<SUMMA>14.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>11.73</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
<LAEKUMINE>
<KUUPAEV>2021-09-13</KUUPAEV>
<SUMMA>35.30</SUMMA>
<VALUUTA>EUR</VALUUTA>
</LAEKUMINE>
</ns3:laekumised_maksuametistResponse>
</laekumisedBody>
</pre></code>

== 4. RAXPENSK xml report from Creditinfo ==

All the detailed information about the report structure can be found in the xml schema RAXPENSK.xsd [https://services.krediidiinfo.ee/schemas/report/RAXPENSK.xsd].

'''''Report contents:'''''

* Report includes the responses from the Pension Registry payment obligation query and pension payment query.

* For better readability of the payment obligation query, we have added payment obligation descriptions:

<code><pre>
<payment_duties>
<payment_duty>
<start_date>2004-01-01</start_date>
<end_date>2021-08-31</end_date>
<meaning>maksekohustus on / sissemaksete tegemine</meaning>
</payment_duty>
<payment_duty>
<start_date>2021-09-01</start_date>
<end_date xsi:nil="true"/>
<meaning>maksekohustust ei ole / maksete mittetegemine</meaning>
</payment_duty>
</payment_duties>
</pre></code>

RAXPENSK

2021-11-18T09:23:05Z

Andrus:

RAXPENSK

2021-11-18T09:22:32Z

Andrus:

RAXPENSK

2021-11-18T09:19:45Z

Andrus:

RAXPENSK

2021-11-18T09:18:48Z

Andrus:

RAXPENSK

2021-11-18T09:17:35Z

Andrus:

RAXPENSK

2021-11-18T09:08:41Z

Andrus:

RAXPENSK

2021-11-18T09:07:54Z

Andrus:

RAXPENSK

2021-11-18T09:07:18Z

Andrus:

RAXPENSK

2021-11-18T09:06:07Z

Andrus:

RAXPENSK

2021-11-18T09:05:10Z

Andrus:

RAXPENSK

2021-11-18T09:04:20Z

Andrus:

RAXPENSK

2021-11-18T09:02:49Z

Andrus:

RAXPENSK

2021-11-18T09:02:14Z

Andrus:

RAXPENSK

2021-11-18T09:01:11Z

Andrus:

RAXPENSK

2021-11-18T08:59:22Z

Andrus:

RAXPENSK

2021-11-18T08:57:47Z

Andrus:

RAXPENSK

2021-11-18T08:57:32Z

Andrus:

RAXPENSK

2021-11-18T08:56:46Z

Andrus:

RAXPENSK

2021-11-18T08:55:13Z

Andrus:

RAXPENSK

2021-11-18T08:53:42Z

Andrus:

RAXPENSK

2021-11-18T08:53:06Z

Andrus:

RAXPENSK

2021-11-18T08:52:03Z

Andrus:

RAXPENSK

2021-11-18T08:51:41Z

Andrus:

RAXPENSK

2021-11-18T08:51:08Z

Andrus:

RAXPENSK

2021-11-18T08:50:13Z

Andrus:

RAXPENSK

2021-11-18T08:46:35Z

Andrus:

RAXPENSK

2021-11-18T08:46:02Z

Andrus:

RAXPENSK

2021-11-18T08:41:55Z

Andrus:

RAXPENSK

2021-11-18T08:37:02Z

Andrus:

RAXPENSK

2021-11-18T08:36:04Z

Andrus:

RAXPENSK

2021-11-18T08:35:47Z

Andrus:

RAXPENSK

2021-11-18T08:34:10Z

Andrus:

RAXPENSK

2021-11-18T08:30:21Z

Andrus:

RAXPENSK

2021-11-18T08:29:48Z

Andrus:

RAXPENSK

2021-11-18T08:28:39Z

Andrus:

RAXPENSK

2021-11-18T08:27:25Z

Andrus:

RAXPENSK

2021-11-18T08:26:19Z

Andrus:

RAXPENSK

2021-11-18T08:24:05Z

Andrus:

RAXPENSK

2021-11-18T08:23:05Z

Andrus:

RAXPENSK

2021-11-18T08:18:31Z

Andrus:

RAXPENSK

2021-11-18T08:12:16Z

Andrus: Created page with " == 1. Short description == Purpose of the report is to give an estimation of the private persons’ bruto income. Income is calculated from the pension payments. Pension pay..."

KiReport en

2021-10-13T07:17:30Z

Andrus:

{| align="right"
| [[Image:Flag of Estonia.svg|border|30px]] [[KiReport|eesti keeles]]
|}
= Introduction =

KiReport is the name of a Web Service based on SOAP protocol for requesting reports about companies and persons. Requested reports are in XML format.

= WSDL =

WSDL is located at [http://services.krediidiinfo.ee/KiReport.wsdl http://services.krediidiinfo.ee/KiReport.wsdl].

= Methods =

== ''getReport'' ==

Report requesting

{| style="border-style: solid; border-width: 1px;"
!
! Name
! Type
! Description
|-
| Input:
| productCode
| xs:string
| Report (product) code
|-
| 
| subjectCode
| xs:string
| Subject code. (Depending on report subject can be a registry code of a company, personal identity code, etc)
|-
| Output:
| xml
| xs:string
| Requested report in XML format.
|}

== ''getAvailableReports'' ==

Requesting the list of available reports.

{| style="border-style: solid; border-width: 1px;"
!
! Name
! Type
! Description
|-
| Input:
|
|
|
|-
|
|
|
|
|-
| Output:
| xml
| xs:string
| Requested available reports list in XML format. XML schema in xsd format is located at [http://www.krediidiinfo.ee/schemas/services/KiReport__getAvailableReports.xsd http://www.krediidiinfo.ee/schemas/services/KiReport__getAvailableReports.xsd] and in png format [http://www.krediidiinfo.ee/schemas/services/KiReport__getAvailableReports.png KiReport__getAvailableReports.png]. An empty tag ''available_reports'' will be given in XML, if a person who requests do not have any available reports.
|}

=Example in PHP =

Example of using KiReport in PHP:

<code><pre>
<?php
/**
* Example of using KiReport web service of Creditinfo AS
* Certificate issued by Creditinfo is needed to use KiReport interface.
*
* @author Rait Kapp <rait@creditinfo.ee>
* @created 18.09.2007
*/

$wsdl_url = 'http://services.krediidiinfo.ee/KiReport.wsdl';
$server_url = 'https://services.krediidiinfo.ee/soap.php?name=KiReport&enc=UTF-8';

$params = array('location' => $server_url
, 'login' => 'online_code' // Online Code issued by Creditinfo client management. Make sure that login value is string type (PHP bug?).
, 'password' => 'passwd'

/* If you want to use certificate, then uncomment this block and comment params login and password!
, 'local_cert' => 'path/certificate.pem' // Here goes path to certificate file.
, 'passphrase' => 'passwd' // Here goes password of certificate.
*/
// , 'proxy_host' => 'cache.neti.ee' // If necessary use proxy and proxy port.
// , 'proxy_port' => 8080
, 'encoding' => 'UTF-8'
);

$client = new SoapClient($wsdl_url, $params);

$productCode = 'RAXXXE';
$subjectCode = '00000000';

$xml = $client->getReport($productCode, $subjectCode);

print_r($xml);

$xml = $client->getAvailableReports();
echo $xml;

?>
</pre></code>

= Debugging =

Developers can always use example report ''RAXXXE'' (''productCode'') for debugging. It is free of charge. The XML Schema of ''RAXXXE'' can be obtained from [http://www.krediidiinfo.ee/schemas/report/RAXXXE.xsd http://www.krediidiinfo.ee/schemas/report/RAXXXE.xsd].

The example of ''RAXXXE'':

<pre>
<?xml version="1.0" encoding="UTF-8"?>
<report xmlns="http//www.krediidiinfo.ee/schemas/report/RAXXXE.xsd">
<date_tag>2007-10-23</date_tag>
<date_time>2007-10-23T10:10:42</date_time>
<int_tag>12345</int_tag>
<decimal_tag>123456.789</decimal_tag>
<string_tag>I am a string</string_tag>
<codes_tag>&amp; ' &quot; &lt; &gt;</codes_tag>
<est_character_tag>õ ä ö ü Õ Ä Ö Ü</est_character_tag>
<subject_code>00000000</subject_code>
</report>
</pre>

The input parameter ''subjectCode'' value is always assigned to the tag ''subject_code''.

= Error Codes =

==-20101 No permission for PRODUCT_CODE! ==

Creditinfo has not granted permission for client to request certain report. To get permissions contact [[Klienditugi| client support]].

== -20102 Subject code value is missing! ==

The input parameter subjectCode has no any value.

== -20103 Invalid subject code value! ==

Specified subject code is in wrong format.

== -10186 No Report ==

There is no any reports for this subject. Example: not submitted annual report is requested.

== -20104 No price registered for product PRODUCT_CODE! ==

The product price is not registered. Please contact the client support.

== -20105 INVALID_TEST_REPORT ==

Test reports are generated for specific subject, product and inquirer. You get the error if one of them is wrong.

== -10184 DATA_NOT_AVAILABLE ==

The report cannot be generated, because there is no any information about the subject in Creditinfo database.

== -10183 INVALID_SUBJECT_CODE ==

Subject code does not exist.