How to create Accounting Key in SAP: OV34

โšก Smart Summary

Account key in SAP links a pricing condition to the correct revenue account, so values post to the right GL account. This resource explains what an account key is, how it drives revenue account determination, and how to create one.

  • ๐Ÿ”‘ Account Key: An account key connects a pricing condition to the type of revenue or deduction account it should post to.
  • ๐Ÿงพ Revenue Posting: It lets SAP post, for example, freight charges to a freight revenue account automatically.
  • โŒจ๏ธ OV34 Transaction: Transaction OV34 creates and maintains account keys.
  • ๐Ÿ”— Pricing Link: Each condition type in the pricing procedure carries an account key in its account key column.
  • ๐Ÿ“Š Determination: Revenue account determination (VKOA) uses the account key to find the right GL account.
  • ๐Ÿ›ก๏ธ Why It Matters: Correct account keys keep sales postings accurate and reconciliation clean.

Create Accounting Key in SAP using OV34

What is Accounting Key?

The account key enables the system to post amounts to certain types of revenue account. For example, the system can post freight charges, generated by the freight pricing condition, to the relevant freight revenue account instead of mixing them with ordinary sales revenue.

A condition type writes its value to a key that is established in configuration, outside the pricing procedure. That key is called the account key in SAP MM and SAP SD. It is a table entry that tells the pricing procedure where to copy the calculated condition values for revenue account determination in SAP. In other words, the account key is the bridge between a pricing condition and the general ledger, so that each type of value, such as revenue, discount, freight, or tax, reaches the correct account. Without account keys, all pricing values would post to the same account, which would make financial reporting and reconciliation far harder.

How Account Keys Drive Revenue Account Determination

On its own, an account key is just a label. Its power comes from revenue account determination, which is the integration point between Sales and Distribution (SD) and Financial Accounting (FI). When a billing document is created, SAP looks at each condition type in the pricing procedure, reads its account key, and uses that key to find the correct general ledger account.

This search is controlled by an access sequence, such as the standard KOFI00, which tries combinations of the chart of accounts, sales organization, and the account assignment groups of the customer and the material. The general ledger accounts themselves are assigned in transaction VKOA against the account key and these criteria. As a result, one account key can point to different accounts depending on the customer or material, which gives the business fine control over how sales values are posted. This flexibility is what lets one pricing procedure serve many customers and product lines while still posting each value to the right account.

How to create Accounting Key in SAP

Below is the process to create an account key in SAP SD.

Step 1) Creating the accounting key.

  1. Enter T-code OV34 in the command field.
  2. Click on the New Entries button.

Execute OV34 and click New Entries to create an account key

Step 2) Enter the accounting key details.

  1. Enter the accounting key and name.
  2. Click on the Save button.

Enter the account key and name, then save

A message “Data was saved” is displayed.

Common Account Keys in SAP SD

SAP delivers several standard account keys, each meant for a different type of value in the pricing procedure, such as revenue, discounts, freight, and tax. Knowing the common keys makes it easier to read a pricing procedure and to set up account determination. The most common ones are:

Account key Used for
ERL Sales revenue
ERS Sales deductions (discounts)
ERF Freight revenue
ERB Rebate sales deductions
ERU Rebate accruals
MWS Sales tax (output tax)

In the pricing procedure, each condition type is linked to one of these keys, for example a discount condition to ERS and a freight condition to ERF. This is how a single invoice can split its value cleanly across revenue, discount, freight, and tax accounts. Rebate keys such as ERU also work with an accrual key so that provisions and payouts are posted separately. Beyond the standard set, you can create your own account keys in OV34 when a specific posting requirement is not covered.

FAQs

An account key is a short label in the pricing procedure that describes the type of value, such as revenue or freight. The GL account is the actual account it posts to. Account keys are mapped to GL accounts in revenue account determination.

Transaction VKOA assigns general ledger accounts for revenue account determination. It links the account key with criteria such as the chart of accounts, sales organization, and customer and material account assignment groups to find the correct account.

The account key is entered in the Account Key column of the pricing procedure, which is maintained in transaction V/08. Each condition type row can carry an account key, and an accrual key where accruals apply.

Yes. AI can suggest the right account key for each condition type and propose GL account mappings from similar configurations, then flag gaps. A finance or SD consultant should still confirm the VKOA assignments before transport.

AI can compare each billing posting with the expected account key and GL account, and flag values that land in the wrong account. Catching this early reduces reconciliation effort and audit findings, while finance confirms each correction.

Summarize this post with: