24.01.2013 Page 1 of 5

SAP Note 1232484 - How to use the VAT due date, taxreporting date VATDATE

Note Language: English Version: 11 Validity: Valid Since 17.12.2010

Summary

SymptomThere is a new entry field (VATDATE) in the document header (BKPF) of thefinancial accounting document that can be used as VAT due date or taxreporting date.When a document is being entered (for example FB01, FB60, MIRO) then theVATDATE can be entered or changed on the tax screen. A specific BADIproposes usually the posting date or document date.Once the document is posted the VATDATE can also be changed using thechange transaction FB02. This changeabilty must just be switched on in theusual way.This note describes the features of this functionality and will be amendedcontinuously if necessary.

Other termsVATDATE

Reason and PrerequisitesThe functionality is based on legal requirements in different countries.Incomplete list of currently known countries: Poland, Hungary, Slovakia, Spain.For each country it must be checked whether the functionality fulfills thelegal requirements.The functionality has originally been implemented by note 1023317 inrelease ER2005, its enhancement packages and in ERP2004 and by note 1235415in release 4.70 and 4.6C. As many objects are involved in the correctionthe functionality can only be imported by applying the correspondingsupport package.For Reporting for Eastern European countries see note 1038448.

In order to ensure data transport of the new field VATDATE some programsand structures must be regenerated. Therefore please run the followingprograms:- SAPFACCG- RFBIPPG0

Solution

1. Activation of the functionalityThe functionality can be activated per company code in the usualcustomizing for the company code 'Enter Global Parameters'.(transaction OBY6 or SM30: View V_001_B)For this purpose the new field XVATDATE has been added to table T001.

2. General ruleIf the functionality is active then every financial accounting documentthat is tax relevant ( i.e. contains a tax code in a g/l-line item) musthave a valid date in the field VATDATE. If the document is not taxrelevant, or the functionality is off in the company code, the date will beinitial.

3. Exchange rate determination for tax line itemsThere exists the well established functionality that the local (company

24.01.2013 Page 2 of 5

SAP Note 1232484 - How to use the VAT due date, taxreporting date VATDATE

code) currency amount of tax line items in a document can be calculatedwith a separate exchange rate, different from the exchange rate used forthe other line items of the document. In addition to the already existingoptions the VATDATE can now also be used for the determination of theexchange rate.(transaction OBC8 or SM30: View V_001_V)For this purpose the new value '5' for domain TXKRS has been added.

4. BADI for determining and checking the VATDATEa) Release ERP2005 (ECC 600) and higherThere is a new Enhancement Spot VATDATE_RULES with the BADI definitionVATDATE_VALUES.A default implementation is delivered: VATDATE_VALUES_DEFAULT_SAP(Use transaction SE18 to see the details of the BADI or SE19 to see theimplementations.)

b) Release ERP2004There is a new BADI definition VATDATE_VALUES.A standard implementation is provided: VATDATE_VALUES_SAP

c) Release 4.70 and 4.6CThere is a new BADI definition VATDATE_VALUES_46.A standard implementation is provided: VATDATE_VALUES_SAP46

Common features of the BADI in all releases:Two methods are provided:- VATDATE_DETERMINE- VATDATE_CHECK

Purpose of the BADI:Only the method VATDATE_CHECK is called from standard programs.Within the default implemetation the method VATDATE_DETERMINE is called ifthe document requires a VATDATE but no value has been provided or couldhave been entered so far. The method VATDATE_DETERMINE determines theinitial value that will be proposed, for example on the screens.By default either posting date or document date is proposed, depending inyour customizing in the company code(transaction OBCK).A value that has been provided, proposed or entered will be checked inmethod VATDATE_CHECK whether it meets specific conditions or rules.It is up to the customer to create his own implementation where thesespecific rules are defined. The default rule is that the VATDATE must notbe less than the posting date and document date. A customized message isissued (FF 785) if it is less.

Where has the BADI been implemented?The BADI has been implemented in- the function group TAX1 (taxes)- the program SAPMF05A (entering accounting documents)- the program SAPMF05L (displaying/changing financial accounting documents)- the function group RWCL (general interface to accounting)- the function group SAPLFCJ_PROCESS_MANAGER (Cash Journal)

5. BADI for determining exchange rate for tax line itemsa) Release ERP2005 (ECC 600) and higherThere is a new Enhancement Spot ESPOT_TAX_EXCHANGE_RATE with the BADIdefinition BADI_TAX_EXCHANGE_RATE.A default implementation is delivered: TXKRS_SET_DEFAULT_VATDATE

24.01.2013 Page 3 of 5

SAP Note 1232484 - How to use the VAT due date, taxreporting date VATDATE

b) Release ERP2004 (ECC 500)There is a new BADI definition TAX_EXCHANGE_RATE.A standard implementation is provided: TXKRS_VATDATE_SAPThere an exchange is determined only if the VATDATE-functionality is activeand only for certain reference procedures.

c) Release 4.70 and 4.6CThere is a new BADI definition TAX_EXCHANGE_RATE_46.A standard implementation is provided: TXKRS_VATDATE_SAP46

Common features of the BADI in all releases:Only one method is provided: TXKRS_SET

Purpose of the BADI:The purpose of the BADI is to set the exchange rate for tax line items.The default implementation determines an exchange rate only for billingdocuments and cash journal documents.

Where has the BADI been implemented?The BADI has been implemented ONLY in function group RWCL, the generalinterface to accounting.

6. (Remark: When a financial accounting document is entered directly witha transaction (for example FB01, FB60, MIRO) then it is of course notnecessary that this BADI is being called as the exchange ratedetermination works there in a different way.)

7. Standard reports RFUMSV00, RFUMSV10The standard tax reports RFUMSV00 and RFUMSV10 support the selection ofdocuments according to the VATDATE.For this purpose the field has been added to the logical database BRF.But, in order to prevent that every report using BRF shows the selectoption for the VATDATE although it does not deal with taxes, the field hasbeen added as hidden where it is switched off. For reports RFUMSV00 andRFUMSV10 it has been switched on permanently. But thereby, in other reportusing BRF it can now easily be switched on via the DYNAMIC SELECTIONS.

8. Country specific reports- some reports used mainly in Easter Europe have been adopted.See note 1038448 and related.

9. BAPIsOnly the most important Bapi BAPI_ACC_DOCUMENT_POST supports the entry ofthe VATDATE in its header structure.

10. Batch-InputBatch-Input for FB01 is supported.

11. Document reversalA reversed document has the same VATDATE as the original one. It can bechanged with FB02.

Important:For additional information please also refer to the PDF documentation"Reporting_by_VAT_Due_Date.pdf" attached to this Note.

24.01.2013 Page 4 of 5

SAP Note 1232484 - How to use the VAT due date, taxreporting date VATDATE

Header Data

Release Status: Released for CustomerReleased on: 10.12.2008 14:46:00Master Language: EnglishPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: FI-GL-GL-F Value Added Tax (VAT)

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SAP_APPL 500 500 500

SAP_APPL 600 600 600

SAP_APPL 602 602 602

SAP_APPL 603 603 603

SAP_APPL 604 604 604

Related Notes

Number Short Text

1778054 VATDATE remains empty if only vendor data is entered

1619358 Down payment: Tax rate if BTE 2051 and VATDATE active

1567029 Badi VATDATE_RULES: VF11 w/ new cancellation, FB08 w/ input

1533216 Documentation Updates - Tax Date

1527469 VATDATE tax reporting date not active but ready for input

1489350 FB02: Problems after changing tax reporting date

1484985 Tax reporting date filled even though document w/o tax code

1441194 VATDATE in FB02 cannot be changed due to BSET-STMDT

1439166 RFASLD20: FI-CA interface and tax reporting date

1409792 Retaining tax reporting date even if tax base is zero

1408702 Tax reporting date is not transferrerd during reversal

1404919 Performance of BAdI VATDATE_VALUES and TAX_EXCHANGE_RATE

1391393 VATDATE: Missing reset if not tax-relevant

1391341 VATDATE: Incorrect initialization for direct input

1381149 RFUMSV00: Tax reporting date and electronic advance return

1372794 VATDATE: Incorrect initialization with list editing FBV2

1366172 FB02: Update termination after changing row and VATDATE

1357159 RFUMSV50: VATDATE in transf. postng docs for deferred tax

1355851 VATDATE: BAdI in cash journal proposes incorrect date

1354521 FB10: Field VATDATE not on screen 137

1353606 RE-FX Country Version for Hungary

1352384 Tax reporting date for down payment chains is missing

1347046 VATDATE: Field missing in batch input parking (FBV1)

24.01.2013 Page 5 of 5

SAP Note 1232484 - How to use the VAT due date, taxreporting date VATDATE

Number Short Text

1338580 MR8M: Reporting date is incorrect

1302818 Unable to manually implement Notes 1023317 or 1235415

1299302 Tax reporting date is not saved

1296949 FB02: Error F5 165 after changing VAT date

1293848 VATDATE: Error message FF 786 issued in AC interface

1289293 Polish VAT Workaround around: Maintenance finish

1288600 VATDATE: No forgn curcy translation if tax entered manually

1280152 Legal change on VAT tax date Spain

1270222 Tax reporting date: Manual implementation of Note 1023317

1265692 VATDATE: Entry overwritten due to missing tax code

1235415 Legal Change: Vat Due Date for release 4.6C and 4.70

1179304 Down payment clearing with own tax rate

1162771 FB02: No checks when changing tax reporting date

1137492 Changeability of tax reporting date

1038448 VAT due date: Country specific Reporting + Migration Tool

1023317 Legal Change: Vat Due date

Attachments

FileType

File Name Language Size

PDF Reporting_by_Tax_Date.pdf E 316 KB