Ansicht
Dokumentation

/SAPPCE/DPC_CHANGE_TAXCODE1 - Down Payment Chains - Tax Rate Change for Germany

/SAPPCE/DPC_CHANGE_TAXCODE1 - Down Payment Chains - Tax Rate Change for Germany

TXBHW - Original Tax Base Amount in Local Currency   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

,,Purpose

As of January 1, 2007, the standard tax rate in Germany will be increased (SAP Note 976257). This report is part of the conversion of down payment chains that are not finally settled.

You create new tax codes to map the new tax rate (SAP Note 117983). The tax codes with the old standard tax rate are not changed to ensure the correct continuation of transactions with the old standard tax rate. Transactions with the old standard tax rate affect down payment chains that were settled before December 31, 2006:

  • Incoming or outgoing payments or clearings
  • Creation of adjustments.

The procedure for converting down payment chains that are not finally settled from the old tax rate to the new tax rate comprises the following steps:

  1. Execute this report to convert the tax code in the contract of the down payment chain and, if necessary, create transactions for the tax rate change. The relevant transactions for the subsequent taxation and the open items with old tax codes and partial payments for transactions with old tax codes are blocked for payment.
  2. Payments or clearings of the open items with new tax codes are still created using the transaction in accounting. New transactions such as partial invoices or final settlement can be created as usual using the processing transaction for the down payment chains.
  3. The report for deleting the payment block for the open items of the subsequent taxation, partial payments for transactions with old tax codes, and open items with old tax codes must be executed at period-end closing at the latest. The report checks whether the criteria for the subsequent taxation for the respective down payment chain are fulfilled, and removes the payment block from the relevant accounting documents if necessary.
  4. The accounting documents for the subsequent taxation can be paid or cleared using the usual transactions in accounting.

If a down payment chain in the contract contains the tax code with the old standard tax rate, but there are no transactions posted yet, the report enters the tax code with the new standard tax rate instead of the tax code with the old standard tax rate into the contract. All other steps listed above under 1 to 4 are not required.

The report supports the following tax codes:

  • Tax codes without tax jurisdiction
  • Tax codes with reverse charge
  • Deferred tax codes (credit-side)
  • Deferred tax codes with reverse charge (credit-side).

The following rules still apply when you change the tax code:

You cannot change from a non-deferred tax code to a deferred tax code if the cumulated values of a down payment chain are not zero (see SAP Note 788020).

You cannot change from a deferred tax code without reverse charge to a deferred tax code with reverse charge if the cumulated values of a down payment chain are not zero (see SAP Note 793942).

Integration

Prerequisites

You have created new tax codes that contain the new tax rate.

Features

For debit-side down payment chains, use transaction /SAPPCE/DPC_TAX01_D Deb. DP Chains - Tax Rate Change.

For credit-side down payment chains, use transaction /SAPPCE/DPC_TAX01_K Cred. DP Chains - Tax Rate Change.

This report carries out the following steps:

  • It checks if the change from the specified old tax code to the specified new tax code is allowed.
  • It checks if the down payment chain is not finally settled.
  • It checks if the specified posting date is after the posting date of the last posted partial invoice or advance payment of the down payment chain.
  • In the contract of the down payment chain, the new tax code is replaced by the old tax code. The report updates the change history in the contract of the down payment chain when the change is executed.
  • It creates transactions for the tax rate change.
  • Using a credit memo with old tax codes, the report writes off all previously posted values such as invoiced amount, security retention amount, special retention amount, and incidental costs. The user specifies the posting date of the credit memo on the selection screen. The report also blocks the credit memo for payment, since the subsequent taxation is not triggered until later. The user enters the value of the payment block on the selection screen. The name of the new transaction that is created is: TC Credit Memo.

  • If old transactions are not completely cleared, the report creates an open item for each transaction in a separate transaction with the new tax code for the open amount. Security retention amounts, special retention amounts, and incidental costs are included when the new open item is created, as a percentage of the amount already paid. The following information is copied from the old open item to the new open item:

,,,,Due date

,,,,Terms of payment

,,,,Payment method

,,,,Payment block

,,,,The name of the transaction created consists of TC from OI (Tax Change from Open Items) and the first 25 characters of the name of the old transaction.

  • Transaction with new tax code whose amount corresponds to the received payment including cash discount for the down payment chain. Security retention amounts, special retention amounts, and incidental costs are included as a percentage of the paid amount. The user enters the posting date of the accounting document on the selection screen. The accounting document is blocked for payment, since the subsequent taxation is not triggered until later. The user enters the value of the payment block on the selection screen. The name of the new transaction that is created is: TC Previous Payments.

  • It sets the payment block in accounting documents of the open items with old tax codes.
  • It sets the payment block in partial payments for transactions with the old tax code.

You can use a second report to delete the set payment blocks for the subsequent taxation transactions, open items with old tax codes, and partial payments for transactions with the old tax code.

  • For debit-side down payment chains, use transaction /SAPPCE/DPC_TAX02_D Deb. DP Chains - Delete Payt Block.
  • For credit-side down payment chains, use transaction /SAPPCE/DPC_TAX02_K Cred. DP Chains - Delete Payt Block.

For detailed information about the second report, see the relevant report documentation.

Selection

From the selection screen, you can select down payment chains based on different criteria.

The selection criteria are:

  • Company code
  • Down payment chain number
  • Customer or vendor
  • Old tax code

The following data must also be specified to run the report:

  • New tax code
  • Posting date for which the tax rate change documents should be created
  • Payment block that should be set for the open items of the subsequent taxation

The Test Run indicator is used to execute the program in test mode, that is, the transactions that are created for the tax rate change.

You can enter frequently used criteria for the selection of down payment chains on the selection screen and save them in a selection variant. Once you have made your selection, you see the list of transactions that are created for the tax rate change. Transactions for subsequent taxation are blocked for payment.

Standard Variants

Output

The application toolbar provides a number of standard functions such as Details, Sort, Set and Delete Filter, Export, and various functions for display variants.

If only the tax code in the contract of a down payment chain has been changed and no new transactions have been created, there is an entry in the output list with transaction fields that do not contain any entries.

Restrictions

Due to the different amounts of the invoiced amount, security retention amount, special retention amount and incidental costs, and the account assignment of previously posted transactions and the new transactions that have been created, there can be rounding differences in cent amounts. This is due to the fact that each accounting document is consistent in itself, but for calculating the tax from the gross amount, it is important in how many subtransactions the posted transactions have been posted.

Activities

Example






BAL_S_LOG - Application Log: Log header data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 9656 Date: 20240416 Time: 184643     sap01-206 ( 172 ms )