Register Login

FICO Important Legal Change CZ VAT Ledger Statement year 2016 Interview Questions and Answers

FICO Important Legal Change CZ VAT Ledger Statement FAQ' s

VAT ledger statement 2016 for Czech Republic, tax control report, VAT Control Statement, frequently asked questions.

General questions

Question G1: We need  information whether SAP is preparing solution for legal change  of VAT law 235/2004 effective from 1.1.2016 according §101c and following. Change introduces obligation to submit so called „Kontrolni hlaseni“ (Vat audit ledger) to tax authority in given structure and specified content and data file.

Answer G1: Please see related 2153601 - Legal Change CZ Vat Ledger Statement for 2016, there are information related to preparation of solution. 15.7.2015 Additionally we have to notify that still there was not published final version of Guide for VAT ledger and any information about XML data file structure (form). So unfortunately any planned date may be still subject of change.
11.8.2015 Update of preliminary Guide and new preliminary XSD structure was published in the meantime. Additional update of XSD was released on 10.8.2015 and 1.10.2015. SAP is analysing documents and working on solution.16.11.2015 Solution was released - see updated information in related  2153601.

Question G2: What is general scope of planned solution, which SAP application are concerned?

Answer G2: As the law requirement is similar to Slovak VAT ledger (introduced in 2014), based on this experience the scope of planned solution for Czech republic is the same - SAP FI report (based on RFUMSV00) which collects data  from FI. In case you are additionally using FI-CA (contract accounting based solution used e.g. by utilities), we plan to prepare also solution for this component (solution will prepare data on FI-CA side and this data could be transferred and integrated into FI report).

Question G3: How can we find related to CZ VAT ledger?

Answer G3: Please use standard  search methods (like by component) or please use lists of related  We also plan to include official English name of report (used by Czech tax administration)  "VAT Control Statement" as part of text or name.

Specific functionality questions

Question S1: We need  information about details of solution.

Answer S1: Please solution is still under preparation, see related  2153601 - Legal Change CZ Vat Ledger Statement for 2016, for availability planning.
15.7.2015 at current date is fully missing specification of XML data file. So please understand, that we are limited in providing detailed information and that there may be changes in planned functionality before it is released (see also disclaimer below).

11.8.2015 Update of preliminary Guide and new preliminary XSD structure was published in the meantime. Additional update of XSD was released on 10.8.2015 and 1.10.2015. SAP is analysing documents and working on solution. Still there may be changes in planned functionality before it is released.
16.11.2015 Solution was released, functionality mentioned in text below as planned  was included. Documentation of solution was attached to main installation  2213503.

Question S2: VAT document number - according the Guide to VAT ledger, the report should contain VAT document number, how is planned to be handled?

Answer S2: Similar requirement occurred in Slovakia, if you have implemented it please use the same for Czech. Czech version will expect VAT document number in BKPF-XBLNR field (same as for Slovak report). As this field is used also as reference payment number (variable symbol), there may be conflict for example if vendor provides different number as invoice number. As this is project depending (depends on agreement with vendor and also specific implementation on your side), planned solution will enable choice of alternative field used as storage of VAT document number by user specific extension (BADI). In BADI code you will be able to specify alternative field (e.g. BKTXT or other) which suits better to your process conditions and use for example logic - in case this field is not empty replace default value read from XBLNR.

Question S3: VAT registration number (Czech language -"DPH DIC") of partner of transaction, where the planned solution will expect this registration number?

Answer S3: Planned solution is expecting VAT registration number in field BSET-STCEG, in case it is missing there, planned solution will search for this number on document lines BSEG-STCEG.

Usage of other field can be enabled by implementing customer specific BADI functionality. Also for pure GL document (no business partner posting), if it should be reported in VAT ledger, you have to ensure filling in mentioned fields (or your specific field) during document preparation.

Question S4: How will planned solution fill in VAT related date (e.g. “DPPD” or “DUZP”) for example in section A2 column 4 or B1 column 4?

Answer S4: Planned solution will present value either from “Document date” or “Posting date” or “VAT reporting date” (VATDATE). Setup in new customizing table will determine which one of them is used for given company code. In case you need present on statement different date (for specific cases), planned solution will allow to modify default selection of date by user specific extension (BADI method).

Question S5: How will planned solution fill in value of Code of fulfilment regime “Kod rezimu plneni” (for example in section A4 column 11)?

Answer S5: Planned solution will determine this code on the base of VAT code provided in reported transaction. Setup in new customizing table will allow assign this Code of fulfilment regime (like 2 for “used goods” or 1 for “travel service”) to VAT code you select for this specific regime.

Question S6: How will planned solution fill in value for §44 ZDPH in section A4 column 12?

Answer S6: Planned solution will recognize §44 transaction (and mark it in XML) on the base of VAT code provided in reported transaction. Setup in new customizing table will allow mark selected/reserved VAT code as code for this specific regime according to §44 ZDPH.

Question S7: How will planned solution fill in value YES “ANO” of Ratio Used “Pouzit pomer” for example in section B3 column 11?

Answer S7: Planned solution will recognize “Pouzit pomer” transaction (and mark it in XML) on the base of VAT code provided in reported transaction. Setup in new customizing table will allow mark selected/reserved VAT code as code used for this specific regime of partial VAT deduction “Pouzit pomer”.

Question S8: How will planned solution recognize internal reversals and eliminate them from report?

Answer S8: Planned solution will recognize internal reversals in FI on the base of field XREVERSAL from document header BKPF (and number of reversing or reversed document from field STBLG). Documents recognized as reversal will be eliminated from report.

Question S9: How will planned solution recognize documents with value above 10000 CZK inclusive VAT  (sections A4 x A5, B2 s B3)?

Answer S9: Recognition of proper section will be included in planned solution functionality (inclusive limit 10000 CZK) and also exception for §44 (for this specific regime, no limit is checked – but related VAT codes have to be marked in additional new customizing table – see S6 for §44).

For VAT codes, where limit has to be checked by report assign in customizing VAT report section A4 sales or B2 purchases. Documents are moved automatically to A5 or B3 in case the amount is below limit.

For other specific regime “Doklady o pouziti” assign section "A5" for given VAT code and that is all (for any VAT codes assigned to section A5 no limit is checked, they are always reported in A5).

Question S10: Will planned solution allow to display detail documents in summary sections A5 and B3?

Answer S10: Documents in section A5 and B3 will be displayed as summary (as requested by law). There will be function to display on screen detailed FI document from which the summary item in sections A5 and B3 was created, so you could check original FI documents. This function will not be available for documents coming from FI-CA.

Question S11: Will planned solution allow modify report results manually?

Answer S11: No, function for changing report results is not planned. One reason is danger of damaging audit trail and data correctness. In case of error, source data have to be corrected and report recreated.

Question S12: Would it be possible to exclude selected VAT codes?

Answer S12: Yes, planned solution will allow to assign selected VAT code to dummy section “ZZ” and by that to exclude it from report output. Other option will be to use selection parameter for Tax code during report run.

Question S13: Which component shal I use for incidents connected to "VAT Control Statement"?

Answer S13: XX-CSC-CZ-FI

Implementation questions

Question I1: You are not able to activate objects from the 2213503  (for example IDFIVAT_DISPLAY_ALV because of unknown GO_ALV_CONTAINER).

Answer I1: You missed the info 4a (In the "Confirm changes" dialog for the  2213503 Select also all yellow lines! ) in Manual Pre-Implement steps of  2213503. In that case you have to use the "How to unimplement/reimplement" part of the  2193486 and implement it again. If you are sure that you did it right (with the step 4b), or if it will not help, just create an incident (OSS message) with remote connection so we can analyze the issue on your system.
Question I2: IDFIVAT_REPCZ00 transaction (IDFIVAT_REPCZ00 report) ends up with the Short Dump Syntax error in program "SAPLIDFIVAT_ALV ". The field "GO_ALV_CONTAINER" is unknown.

Answer I2: See the "SAP answer I1".

Question I3: You are not able to activate objects from the 2221947 (for example class CL_IDFIVAT_ALV_SCREEN, method EXPORT_XML).

Answer I3: If you didn't select the yellow lines during implementation of the first note - see step 4b in the "Manual Pre-Implement" of the  2213503 - you have to use the " How to unimplement/reimplement" part of the 2193486 (so unimplement 2221947 and 2213503 and do the tricky part) and implement it again. If you are sure that you did it right (with the step 4b), or if it will not help, just create an incident (OSS message) with remote connection so we can analyze the issue on your system.

Question I4: Report _2213503_A ends up with an error message for CUAD IDFIVAT_EXT_DATA_MAINT (The definition of interface IDFIVAT_EXT_DATA_MAINT is inconsistent. Change not possible.)

Answer I4: If you have got SAP_APPL 617 and SAP_BASIS 740/0012 (or higher SP of SAP_BASIS), create an incident (OSS message) with remote connection and user with authorization to run and debug the report and implement a note, so we can solve the issue on your system.

Question I5: Report _2213503_A ends up with the error message Class CL_IDFIVAT_APP_SERVICE,Protected section. Type "IDFIVAT_APP_BADI" is unknown.

Answer I5: It occures on some old versions (SAP_APPL 600). This four steps should help:

  • When the Activation screen (the list of objects to be activated) is displayed, create a new session (or skip to another SAP window)
  • Run the SE18 transaction for BAdI IDFIVAT_APP_BADI and click on the Display button
  • Activate the Enhancement

Continue with the activation in the original window - it should end up without errors now
Question I6: Report _2213503_A ends up with the error message "Transformation IDFIVAT_CZ is locked by another user" for object XSLT IDFIVAT_CZ.

Answer I6: The issue is caused by the missing authorization S_DEVELOP for the user, who is running the report.
Question I7: Report _2244343 in Test Run returns error messages.

Answer I7: Do not run the report in the Test Run, skip the first step and perform directly Step 2 Update & Activate.
Question I8: You receive the error message "Missing value for company code ... and parameter CZ_EVAT_FINANCIAL_ID" (or CZ_EVAT_TAX_PAYER or CZ_EVAT_VAT_NO).

Answer I8: Create the missing parameters (CZ_EVAT_FINANCIAL_ID, CZ_EVAT_VAT_NO, CZ_EVAT_TAX_PAYER) the same way as described in the manual steps of SAP  2213503 - Country-specific VAT implementations. Then assign desired values to these new parameters in IMG activity: Financial Accounting - General Ledger Accounting - Business Transactions - Closing - Report - Electronic Communication with Authorities - Define Parameters for Electronic Communication with Authorities (select Return type: ‘0001’; Dominant enterprise/Company code = entity for which an electronic declaration has to be made; Country of reporting authority: ‘CZ’). These missing parameters (among others) are otherwise created during implementation of SAP  1930047 - Legal change: CZ eVAT return, and they are most likely missing in your system because you did not implemented this SAP Note. There is also another description of how to create these parameters in the attachment to this SAP Note (document CZ_VAT Return_Configuration Manual.doc, also in attachment to this message). As it is not required to have this SAP 1930047 implemented in your system as a prerequisite, we will also update the manual steps in SAP 2213503 regarding these three missing parameters.
Question I9: When running Step 2 Update & Activate of the report _2250498_DE an error message occures "The concept will be created in the non-original system".

Answer I9: Run the Step 2 again, the message should disappear and all object should be active.
Question I10: In the maintenance view IDFIVATV_SECT is not possible enter values 'AX' or 'BX' to the field VAT Section

Answer I10: In the transaction SE11 activate domain IDFIVAT_SECTION, data element IDFIVAT_SECTION, maintenance view IDFIVATV_SECT, table IDFIVATT_SECT. It could take a few minutes the changes to take effect.
Question I11: Some warning messages are displayed during Update & Activate step of the _2244343 UDO report (Activation - Unexpected entry in DDXTT: ...)

Answer I11: No problem, you can continue.
Question I12: It is not possible to implement a note from the list.

Answer I12: Some customers had reported problems, which were caused not by "our notes", but "out of date" Snote. So, please, implement the 875986  so you will be "up to date".
Question I13: IDFIVAT_REPCZ00 transaction (IDFIVAT_REPCZ00 report) returns no data

Answer I13: Try to check these questions:

Is the customizing OK? For example a tax code is supposed to lead to a section in XML.

Does the RFUMSV00 report with the same selection criteria give you the expected documents?

Did you implemented the 2241853 ?

Is the right implementation of the FI_TAX_BADI_016 BAdI for CZ active (CL_IM_IMPCZ_TAXREP_016 implementing class), or are you saving tha data yourself by some other way - in some other BAdI implementation?

If you have got more active FI_TAX_BADI_016 BAdI implementations for CZ - does the SET_FLAG_USE_BADI_16 method return 'X' for each of them?
Question I14: You want to implement the 2263444  and you are told that following three already set-up OSS are issued as obsolet (2221947, 2231165, 2244343)

Answer I14: Sorry for the inconvenience. A change of validity of correction instructions for SAP_FIN 617 leaded to a new version of correction instructions and now it seems, that your code is old - even if it is not. Please, do the below steps. Seems like a big issue, but it takes only few minutes, because you do not have to read and repeat manual instructions and you do not have to run UDO reports - you already did it. BUT DO NOT REIMPLEMENT THE 2213503  OR RUN UDO REPORTS because of this issue - it would change the time to solve from minutes to hours!


This message outlines our general product direction and should not be relied on in making a purchase decision. This message is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this message or to develop or release any functionality mentioned in this message. This message and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. The information in this message is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this message, except if such damages were caused by SAP intentionally or through gross negligence.