Ansicht
Dokumentation
RPLM30HR_13 - Tax final settlement
ABAP Short Reference RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
1. Current version of the documentation and Tax final settlement program (RPLM30HR)
This documentation contains information necessary for the generation of the certifications M30 and EKHO concerning the 2013 tax return
as well as of the form M29 and data supply files.
2. Generating tax final settlement forms and data supply files
2.1 Accessing the program
The program can be accessed from the menu: Subsequent activities - Annual - Tax final settlement - Tax return or System - Services - Reports; program name: RPLM30HR.
2.2 Program objectives
The program creates the following forms regarding personal tax return and settlement
- M30 (Income confirmation), M32 - for compressed printing
- form: 2013: HG30 (Income confirmation), HG32 - for compressed printing
- EKHO certificate
- form: 2013: H3EK
- M29form and data supply file
- 2013:
- HG20,,13M29M Private person sum. employment tax 2013
- HG21,,13M29M-02 Declaration family allowance claim I.
- HG22,,13M29M-03 Housing credit allowance detailed data
- HG23,,13M29M-04 Disposition on amount to be transferred to PPF
- HG24,,13M29M-05 Determine 15% HIP of farmer
- HG25,,12M29M Help for the order of claiming allowances
- HG2A,,13M29M-02 Declaration family allowance claim II.
- T29 form (information on tax arrears)
- form: HET4
The program's objective is to prepare these lists for each employee in accordance with the specifications and parameterization options defined in the selection screen.
Forms use the following FORML IDs in table T5H2B:
For 2013:
- M30 form (Income statement): HG30
- EKHO certificate: H3EK
- M30 form (Income statement): HG20
- T29 form: HET4
2.3 Preconditions for running the program
Before running the program, the following basic settings are required:
- The additional tax data (if necessary) can be posted on infotype 307. Further information
about wage types to be posted to this infotype and about using this infotype can be found in the user documentation:
- In the case of employees preparing self-assessment, the fact of self-assessment should be entered in infotype 163, in the last valid record of the given tax year. This is to ensure no tax return (form M29) is prepared for these persons; however, their incomes will be included in form M30. If an employee has multiple relationships with the company - and personnel numbers are linked in infotype 31 -, it is sufficient to indicate the fact of self-assessment for one single personnel number of the employee.
- In case of an employee in multiple relationships, the aggregated processing of
incomes belonging to his/her different relationships (personnel numbers) is only possible if reference personnel numbers are correctly maintained (infotype 31).
If the main personnel number of the employee is selected in infotype 121 (Priority of reference personnel numbers) or 163, the employee's personal data (name, address, tax number, etc.) will be read from this personnel number, and the tax difference, if any, will be settled for this personnel number. When entering the main personnel number, the priority sequence of the personnel numbers need not be defined in infotype 121.
- If necessary, the correction of wage type values for the current year should be performed for each employee (see section 2.10).
Family allowance
If an employee has a family allowance that he/she cannot utilize, or wants to utilize a family allowance that his/her spouse could not use, then - for making use of the allowance (and for preparing form M29M-02) - the dependant code must be checked in infotype 21 in the case of dependants entitling to the allowance, and in the case of a beneficiary dependant, the number of months entitling to the allowance must be specified. The program calculates the amount of the family tax base allowance on subtype 8 of infotype 307 based on the number of beneficiaries / dependants to be considered in monthly breakdown. The amout can be overridden on subtype 3 (Declaration I) of infotype 307.
To split family allowance:
,,Check on subtype 3 (Declaration I) of infotype 307 the Split family allowance field.
,,Enter on subtype 3 (Declaration I) of infotype 307 the amount to be obtained (Family allow. ,,overriding). It not amount is entered here, the program calculates an amount to be obtained ,,from the monthly Tax base allow. max. amount posted on infotype 0163. It this amount is not filled in, the obtained ,,amount is only limited by the consolidated tax base in the return.
,,Enter tax ID and name of the spouse / partner on subtype 1 of infotype 21. Should someone want to split his/her family allowance with 2 ,,spouses / partners, you have to enter on subtype 3 Declaration I of infotype 307 ,,the tax ID of both spouses / partners; this is valid for the relevant data on subtype 1 of infotype 21 ,,as well.
2.4 Filling in the selection screen
2.4.1 Standard selection parameters
The report uses the standard selection screen, where you can select the Data Selection Period and the
personnel numbers of the persons to be processed. This should be the first and last day of the given year (1st January - 31st December).
You should also fill in the dates of the Person Selection Period; in this case, the program only selects
the employees of this period. The period can be specified as up to 31 January of the given year, and the program ignores those personnel numbers which belong to new employees and employees with self-assessment.
Some additional information for defining the period:
- The year specified in the date entered at the first field defines the current year.
- Personal data (name, address, tax identification number, etc.) and company data (name, address, tax number, etc.) will be selected within the full interval of the data selection period. From the data contained in the relevant infotypes, the program uses the last valid data related to the given period.
- Whether the employee belongs to the staff on the payroll or off the payroll will be decided on the basis of the employee group or employee subgroup entered in the Organizational Assignment (1) infotype and valid at the end of the data selection period or when leaving.
- From the data of infotype 193 (data of previous employment, some details of severance pay, etc.), the last valid data will be read from the full interval of the data selection period.
- Data entered in infotype 307 must be valid for 1 January of the year after the current year (i.e. in case of a tax assessment for 2013, the data must be entered for 01.01.2014).
When selecting personnel numbers, take into consideration that if an employee has multiple relationships
and his/her personnel numbers are linked in infotype 31, then the personnel number where the program
searches the data of the employee (name, address, tax identification number) and later settles the employee's
tax difference, if any, must be the only reference personnel number of the employee contained in the given selection.
If the employee's main personnel number is checked in infotype 121, then this main personnel number
should be included in the given selection. In this case, it is irrelevant whether there is another personnel number of the employee in the interval or not.
2.4.2,,Report-specific selection parameters
The standard selection screen now has additional parameters for defining data related to the form to be generated and defining the actual program run:
| Field | Function | When to fill in |
|---|---|---|
| Personnel number | The selection defined in the Select Employee standard selection group can be restricted by filling in these fields. | Always |
| Form code | Form code: | |
| M30: Income confirmation (M30) | ||
| EKHO: EKHO certificate | ||
| M29: Tax settlement (M29) | ||
| T29: Information on tax arrears | Always | |
| Form code (format) | In the T512P (Form format) table, the form is set under this form code. | Always |
| Form code (settings) | The form is set under this form name in table T5H2B (Settings of operations between wage types and variables) | Always |
| M29 supplementary forms | Fields containing the form backgrounds of the attachments of M29 settlement | |
| Test mode | If this field is checked, the program does not generate the file(s) necessary for data supply on a magnetic data medium, and does not analyze which employees were processed during the last program run and included in the data supply file (in update run, no form is generated for these employees). If this field is not checked, the program will run in update run. | Optional |
| Directory name | Specify the directory (access path) where you want to create the data supply files during update run. Technical files containing parameters of update runs will also be created in this directory. At the end of the directory, you should enter a slash (/) character. If you want to run the program in update run again with a new file name in the same directory, you must delete these technical files first. Technical files must always be deleted when entering a new name, or a different directory must be defined where the program has not had an update run before.For more information on technical files, see section 2.4.3. | M29 |
| T29 | ||
| Productive run | ||
| File name | From the M29 form, the file necessary for the data supply on magnetic data medium will be created with the specified name in the specified directory (under UNIX/Windows NT/...!). You do not need to specify the directory name again here. | M29 |
| Productive run | ||
| Recreation of files | If checked, the data supply files entered in the File name field and stored in the work directory (Directory name field) and the technical files belonging to the given form (see section 2.4.3) will firstly be deleted during program run and recreated again to the new selection criteria. This is only available in productive run. | Optional |
| Code page 852 | SAP code page 852 necessary for file generation | Productive run |
| From version 4.7 | ||
| Save processed personnel number | If checked, the processed personnel numbers will be saved under the name specified in the File Name of Personnel Number List field, in the specified directory (Directory name field). | Optional |
| File name of personnel number list | ||
| Submission before deadline | If this field is checked, the correction field on the cover page of the individual return will be empty if this is the first data supply concerning the given employee. | Optional |
| Submission after deadline | If this field is checked, a correction file is generated. Thus, if the employee data has been supplied to APEH before and recorded in table T5H2N, the correction field on the cover page of the individual return will be filled with H, or a T is entered in the deletion field if the return should be deleted. | Optional |
| Only D (delete) decl. | By checking you can generate a deletion document to the return already submitted even if no deletion should be generated from any other reason. If checked, each return in the file generated will be a deletion return. | |
| M30 for not self-assessors too | If this field is checked, form M30 will be generated also for employees that are not defined in infotype 163 as ones preparing self-assessment, i.e. they are 'company assessors'. | M30 |
| Optional | ||
| Skip reference personnel numbers | If this field is checked, the employee's data will not be aggregated on the basis of reference personnel numbers. | Optional |
| Subtype Domestic partner | Here you can define the subtype in infotype 21 where the domestic partner's data are recorded. Note: Parallel use of the subtypes Spouse and Domestic partner is not allowed. | Optional |
| Paying agent's predecessor TaxNo | Optional | |
| Write amounts long form | If amounts longer than 9 digits have to be printed on documents, you can check this option - with a separate form - and the program will pass longer text fields to the form. Separate form background can be used in this case on M30, with fields of appropriate length to accommodate the longer amounts. No such sample company form has been created for M29, so - if it were necessary - it has to be created as a customer-specific form. | |
| Write in not compressed form | Form M30 can alternatively be printed - using a separate print form - in compressed form; check this field, if you want to avoid printing in a compressed form. | |
| Max number of lines a page | Maximum number of lines to be printed per page | |
| Postal address subtype | This field is to specify a subtype of infotype 0006, which contains a shortened address (when 24 chars are enough for street name, street number, apartment, floor, door). This shall be required when reclaiming private pension fund payments if the employee's address is longer than this. | |
| Employee group off the payroll | The employee group or group range should be specified, which contains persons off the payroll. | M29 |
| Employee subgroup Off the payroll | If persons off the payroll are categorized into one or more employee subgroups within the employee group, the subgroup (or range) of off-payroll staff has to be specified here. | M29 |
| Check previous update run | By checking the comparison field, you can start a simulation run and compare the tax differences with the previous update run, i.e. you can find out for whom the tax to be paid/reclaimed has been changed since the last update run. You can access the result list of the comparison by pressing the Tax differences button, or - e.g. in case of a background run - you can save it to a file. To do this, you have to select the Save to file field and enter the file name in the Tax difference file field. The file will be stored in the server directory specified for data supply files. | |
2.4.3 Generated files
In an update run, files necessary for data supply and the file necessary for posting tax arrears will be generated in the specified directory as follows:
| Form (where it is created) File name | File purpose | |
|---|---|---|
| M29 | Name specified in the File name field among the parameters. | Data supply file belonging to the given form. |
| M29 | 'ado.dat', ado_m63.dat | File necessary for posting tax arrears |
For forms where it is necessary to generate file(s) for data supply on a magnetic data medium, during update runs, employees are entered in a separate technical file (in the specified directory) for which the form and/or the relevant record in the data supply file has been prepared:
| Form | File name |
|---|---|
| M29 | m29_processed_personnel_no_<mandant>.dat |
| t29_processed_personnel_no_<mandant>.dat (the latter file contains employee data on tax advance refund or tax arrears on the basis of the M29 form)* |
2.4.4,,Data supply correction
After the data supply has been accepted by APEH, you can only make a correction data supply for the given year for the same employee.
Therefore, when creating data supply files, it will be recorded in the T5H2M table for which employees (i.e. for which personnel numbers) the given data supply file has been generated in the update run. Employee data in the T5H2M table contain the personnel number and tax identification number of the given employee for the actual tax year and form as well as the version number of the update run.
2.4.5,,Version number of the data supply file
When creating a repeated, correction data supply, bear in mind the employees and their tax identification numbers included in the file sent to APEH before, because this is the only way to define the data supply type of persons included in the repeated data supply (correction data supply/deletion) this way.
Each update run automatically generates a version number (which is actually the serial number of the update run). In the T5H2M table, the same version number links the employees included in the same data supply file.
It is possible to generate a data supply file in several update runs. In an update run, all personnel numbers for which data has already been included will be recorded in the technical files listed above; thus, these employees will not be included in a next run, i.e. no employee will be included more than once.
The version number increases with each update run; thus, in the T5H2M table, the same version numbers indicate the employees contained in the same data supply file.
The highest version number of a form in a year indicates the employees included in the data supply file generated during the last update run.
Recording the data supply to APEH in table T5H2N
Having supplied the necessary data to APEH, you should record the version number of the file sent to APEH in the T5H2N table. After each new (correction) data supply on the same form, the version number of the file sent recently must be recorded, in addition to the previous ones. This means that the T5H2N table must contain the version numbers of all (original and all correction) files submitted to APEH for any given form.
In a repeated data supply, this enables the program to decide records with which version numbers in table T5H2M must be taken into account. They contain the employees for which data supply was already performed during the former data supply (for any form).
Target directory requirements in new and repeated data supplies
Every new and repeated data supply must be performed in a 'clean' directory, i.e. files (including technical files) generated during a former data supply, if any, must be removed beforehand.Files generated this time will only contain data of employees (personnel numbers) processed during the new run.
2.4.6,,Creating correction files
By selecting the Submission after deadline option, the program creates a correction document if a return has already been generated for the employee and submitted to APEH (the version number recorded in table T5H2N). A deletion document will be created if a return has already been created for the employee and submitted to APEH, but no return should have been made for him/her in the current run (e.g. changed to self-assessor).
If no return has been created for the employee in the originally submitted file, but you need to create one subsequently, the letter 'H' for correction cannot be stated on the cover page of the individual return according to the filling instructions. Therefore, in such cases you have to select the Submission before deadline option, and you have to create a separate file in a separate run since no correction and original return can be included in the same package.
2.4.7,,Removing unnecessary records from the T5H2M table using the RPUH2MH0 program
In the T5H2M table, all employees (personnel numbers) are recorded with the current version number of the update run that are included in the current data supply file. However, later you will only need the ones generated with the same version number as the version number of the data supply file actually sent to APEH (recorded in table T5H2N).
Unnecessary records can be removed from the T5H2M table using the RPUH2MH0 program.
2.4.8,,Running the RPUH2MH0 program
On the selection screen of the program, you should provide the following data:
Test
If checked, the entries to be removed will be listed but not actually removed.
Year
Form
Records relevant for the given year and for the given form will be considered.
Version number(s) of files submitted to APEH
List here the version numbers of records relevant for the given year and form that you want to preserve in the table. Records with version numbers different from these will be removed from the table.
The program does not allow to remove records belonging to data supplies registered in table T5H2N. The removal of these entries would make impossible the correct determination of the data supply type concerning the employees in correction or supplementary data supplies.
Correction due to tax identification number
When during a repeated, correction data supply the tax identification number of an employee changes as compared to the original data supply, the employee will have two entries in the correction data supply:
One with the correct data and amounts and another with the old tax identification number and amounts of 0.
2.4.9,,Number of records in data supply files
The number of records in the individual data supply files can be seen during update run on the screen that appears when clicking the Settings button.
2.4.10 Downloading data supply files to local directory
You can download the generated files by using the RPUFTRH0 program (transaction PC00_M21_RPUFTRH0). The program can be accessed from the menu: Subsequent activities - Annual - Tax final settlement - Download file from server. You have to enter the name of the file to be downloaded on the selection screen, the directory specified in the Directory name field when creating the data supply in the SAP directory field, and the local directory to where you would like to download the specified file.
2.4.11 Personnel number list
In case of an update run, you can access the list of personnel numbers, for which a return has been created, and the tax amount to be paid or refunded by using the Personnel number list button in the toolbar above the list. The list is in ALV format, and can be downloaded in tabular format.
2.5 Using data specified in infotypes
| Name | Data in list | Data source |
|---|---|---|
| Address | Permanent address | Infotype 6, subtype 1 |
| If no Temporary address is entered | Infotype 6, subtype 2 | |
| Tax number | Tax number | Infotype 163 |
| If not specified and foreign citizen: Passport number (private or official), preceded with an 'X' | Infotype 175 | |
| Passport number | Private passport number, preceded with an 'X' | Infotype 175 |
| If not specified: Official passport number, preceded with an 'X' | Infotype 175 | |
| Address of dependants included in the settlement | ||
| Employee address (see above) | ||
| If on infotype 6 subtype 'Dependant address' is posted: Address of the dependant instead of the employee | Infotype 6, subtype HU01: Here you must specify the serial number of the dependant, too, bearing in mind that '1' is not equal to '01' in the system. A list of the dependants specified in infotype 21 can be queried from the field Sequence number by pressing F4. |
2.6 Generating the forms
If an update run has been performed for an employee, and the employee is included in the data supply file, this means that no other update run of the program is possible with its present version for the same employee.
However, if this becomes necessary, all files (both data supply files and technical files) - related to the given form - must be deleted first; then an update run of the program must be performed for all employees (already processed).
Files can also be deleted automatically by checking the Create new files box before running the program. This way no manual deletion is necessary. If the automatic deletion fails for any reason (see footnote) and the program returns an error message, you must manually delete all files belonging to the given form before the next update run.
This report displays the given form for the specified year for each employee.
In the case of employees in a multiple relationship, the employee will only be listed once; this way, his/her data will appear in a single form, aggregating data from all relationships. This means that running the program for any relationship (personnel number) of the employee will process all relationships of the employee (with all related incomes). The precondition to that is the proper maintenance of the reference personnel numbers of the employee in a multiple relationship (in infotype 31).
Only one user can run the program in update mode in a client. This way double processing and double inclusion of data of an employee in the data supply file can be prevented. During program run, you cannot change table T5H2B (settings of tax settlement) either.
2.6.1,,Form M30: Income statement
Form M30 contains the employee's income liable to contributions and belonging to the given relationship, and aggregated with incomes from all the employment relationships in the case of a multiple relationship.
As an employe may leave and re-enter several times with the same personnel number, therefore, only the last employment of the employee will be included in form generation: the form will include the employee's incomes from the beginning of the last employment or - if the employment started before the current year - from the beginning of the current year until the end of the current year as well as her/his previous incomes (posted to infotype 193 at the time of entry or re-entry).
2.6.2,,Form M29: Employment tax return
An employee's incomes in the given employment relationship (personnel number) - in the case of multiple relationship the aggregated incomes for all relationships - will be included in the M29 form of the employee if he/she:
- is not checked as employee with self-assessment (in infotype 163 for any personnel number),
- however, the relationship where the employee is on the payroll did not cease before 31st December of the current year, i.e. the employee did not leave during the year.
As an employe may leave and re-enter several times with the same personnel number, therefore, only the last employment of the employee will be included in form generation: the form will include the employee's incomes from the beginning of the last employment or - if the employment started before the current year - from the beginning of the current year until the end of the current year as well as her/his previous incomes, if any, (posted to infotype 193 at the time of entry or re-entry).
In update run, enter the name of M29 file necessary for data supply on a magnetic data medium without the file path in the File name, File name (M29/2) and File name (M29/3) fields.
Settlement of an employee entering after tax year end
If the employee goes to another employer after the tax year, he/she can declare that he/she wants the new employer to prepare his/her tax return. For this, the employee must be entered for the previous year in an unused payroll area under a different personnel number, then the incomes obtained with the previous employer must be transferred in the correction subtype of infotype 307. This personnel number can be fully independent of the one where payroll accounting of the employee occurs.
2.6.3,,Preparing M29
The summary table below shows whether the various incomes belonging to a particular personnel number appear on form M29. Some additional information to the table:
- in case of employment relationships linked by a reference personnel number, if any of the personnel numbers does not meet the requirements prescribed for the given form, all personnel numbers of the employee will be rejected
- in case of employment relationships linked by a reference personnel number, if the employee is defined for any personnel number as person with self-assessment, all personnel numbers of the employee will be processed as if defined as a person with self-assessment
- if the employee was on the payroll for the given personnel number but left during the year, he/she won’t be included in M29
- a relationship on the payroll with another relationship on the payrol can only be linked if their data shall be contained combined in a form.
Here you should be careful with cases when an employee left during the year and re-entered under a different personnel number. In such a case, post the incomes belonging to the previous employment - combined with the incomes obtained in the meantime from another employee, if any - in infotype 193.
- If the company prepares his/her tax return on form M29, the personnel numbers must not be linked; in addition, he/she must not be defined as self-assessor for the previous personnel number.
- If the employee chooses that his/her tax return should not be prepared by the company, you have to link both personnel numbers and define the employee also for the previous employment as self-assessor.
| Relationship type | Left during the year? | Self-assessment? | M29 |
|---|---|---|---|
| Staff on payroll | - | x | - |
| Staff on payroll | - | - | + |
| Staff on payroll | x | x | - |
| Staff on payroll | x | - | - |
| Staff off payroll | - | x | - |
| Staff off payroll | - | - | + |
| Staff off payroll | x | x | - |
| Staff off payroll | x | - | + |
2.6.4 Form T29: Information on tax arrears
The Information on tax arrears form uses the results of form M29, since the sum of tax advance and health contribution to be paid or refunded is determined there. The form also uses the payroll result, and reads the amounts deducted and remained as arrears from the RT table.
That is why before T29 - at least for employees for which you want to prepare the T29 form - the program has to be run for form M29 in update mode, and arrears and overpayment amounts have to be transferred to the payroll using the program RPLM30H2, and payroll accounting has to run in update mode. When generating the T29 form, you have to specify the same directory name as for the update run.
2.7 Data of dependants included in form M29-03
For obtaining a family allowance, you should also fill in form M29-03 containing data of dependants entitling for the allowance. Enter the data of dependants as follows:
| Data | Read from | Override option |
|---|---|---|
| Code | Infotype 21 | |
| No.of months for allow. entitlement | Infotype 21 | |
| Name | Infotype 21 | |
| Tax number | Infotype 21 | |
| Place of birth | Infotype 21 | |
| Date of birth | Infotype 21 | |
| Mother's name | Infotype 286 | |
| Nationality | Infotype 21 | |
| Permanent address | Infotype 6 (address of employee appears as address of the dependant). Note: Data entered can be broken down as prescribed by APEH. | Infotype 6, subtype HU01 (Dependant's address). Note: Data entered can be broken down as prescribed by APEH. |
Apart from dependant's code, number of months entitling to allowance and dependant's name, no other data is necessary if the tax number of the dependant is entered in infotype 21.
2.8,,Spouse's or domestic partner's data for splitting family allowance
To split the family allowance, the tax identification number and name of the spouse or domestic partner are necessary. They can be entered as follows:
| Spouse, domestic partner | Data | Read from |
|---|---|---|
| Spouse | Tax number | Infotype 21, subtype 1 |
| Spouse | Name | Infotype 21, subtype 1 |
| Domestic partner | Tax number | Customer-specific subtype of infotype 21, to be specified on the selection screen |
| Domestic partner | Name | Customer-specific subtype of infotype 21, to be specified on the selection screen |
Warning: It is not allowed to enter subtypes Spouse and Domestic partner at the same time for the same employee.
No other data rather than the tax identification number and name of spouse or domestic partner are to be provided.
2.9,,Specifying postal address on M29-05 related to voluntary fund
If an employee will have sheet 05, his/her postal address has to be specified. The address consisting of street, street number, apartment, floor and door cannot be longer than 24 characters. Shortened addresses can be populated using the following options:
- If subtype 7 of infotype 307 contains an address, the program reads the address from that
- The subtype of postal address can be specified on the selection screen, provided that a subtype containing such a shortened address exists in the system. If the subtype is specified on the selection screen, the program reads the address from that, and tries to compress the street name and number, apartment, floor and door fields as much as possible. If the shortened address is within the limit of 24 characters, it will be shown on sheet 05, otherwise it will be added to the error list
- If no Postal address subtype is specified, or no such subtype is posted for the given employee, the program tries to compress the home address
- If the shortened address is within the limit of 24 characters, it will be shown on sheet 05, otherwise the employee will be added to the error list
- When compressing an address, house number will be followed by a full stop, and the additional components (apartment, stairs, floor, door) will be separated by slashes
2.10 Posting wage type corrections
Values of wage types for the current year can be corrected in infotype 307.
For further information about infotype 307 see chapter 3 and the file under Tax calculation - Additional tax data (0307) infotype - Customizing.doc.
2.11 Verifying data supply files
From 2011, the data supply file of the return is not created in the usual textual format as in the previous years, but in imp format.
The file created can be imported to the General document filling program issued by APEH, where you can check it and from where you can submit the data supply to APEH.
You can download the General document filling program issued by tax authority APEH from http://www.apeh.hu.
2.12 Posting tax arrears
The program determines the amount of tax to be paid or refundable tax advance for printing to form M29 (Employment tax return) in update run. These data - along with other data necessary for monthly tax return - will be stored in a file named ado.dat on UNIX/Windows NT/... systems, from where you can post the amount of tax to be paid or the amount of the tax advance to be refunded by using the program RPLM30H2.
3. Infotype 307
In infotype 307 - on the basis of the employee's declarations to the employer and his/her certifications - you have to post additional data necessary for the year-end tax return as well as tax-related data not yet posted during the year.
Furthermore, with this infotype you can directly correct data in the reports of the tax final settlement, as well as record payments to private persons not kept on record in SAP HR (those for whom the tax final settlement is prepared on this basis).
Usage of the infotype is described in detail in Additional tax data (307) infotype - User's manual documentation.
For additional information about wage types included in this infotype, see documentation Data to be posted in infotype 307 - User.doc.
3.1,,Filling in infotype 307
When filling in infotype 307, the following restrictions must be kept or considered:
- In case of an employee in a multiple relationship, you must enter all additional data for the same personnel number. You can use any of the employee's personnel numbers for this purpose.
- Always enter data in the first possible record. For example, if you want to enter the data necessary for claiming the allowance for several insurances, you must do this in a way that records with lower numbers, if any, must contain data related to another insurance (for subtype 1 only; not used at present).
- Specify 1 January of the year after the current year as validity date (from and to) of data entered in the infotype. When created, the infotype appears with the right validity dates.
CPI1466 during Backup Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 46379 Date: 20240601 Time: 024458 sap01-206 ( 703 ms )
