RAXPENSK

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:

1. Person has no active pension account.
2. Person has active pension account but has no pension payment obligation permanently.
3. 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:

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

Example 1:

<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>

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:

<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>

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:

<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>

4. RAXPENSK xml report from Creditinfo

All the detailed information about the report structure can be found in the xml schema RAXPENSK.xsd [1].

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:

<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>

• 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:

<comment is_error="false">Ei tehtud maksuametisse toimunud laekumiste päringut, sest maksete kohustus puudub.</comment>