Every financial transaction in SAP is recorded as a document. These terms define the structure, classification, and control of those documents, ensuring an organized and auditable trail of all financial activities.

Document Type

A Document Type is a two-character key used to classify different business transactions (e.g., ‘DZ’ for Customer Payment, ‘KG’ for Vendor Credit Memo).

• Why it matters: This acts as a template for transactions. It enforces business rules before a posting is even made, preventing a user from, for example, accidentally posting a customer payment to a vendor account and ensuring every transaction is uniquely numbered for a clean audit trail.

Posting Key

A Posting Key is a two-digit numerical key that controls how a line item is posted. It determines the account type, whether the posting is a debit or a credit, and the field status of the screen.

• Why it matters: This is a fundamental control mechanism that prevents illogical entries. It ensures the integrity of every single line item by strictly defining the debit/credit relationship and the type of account being posted to (e.g., you can’t credit a vendor with a key meant for a customer).

Document Number Range

A Document Number Range is a defined range of numbers that the system assigns sequentially to newly created documents. Each Document Type is assigned to a specific number range for a fiscal year.

• Why it matters: It provides a unique, sequential, and gap-free identifier for every financial document, which is a critical requirement for legal compliance and auditing. It ensures every transaction can be uniquely traced and accounted for.

Understanding these document principles allows us to see how transactions are captured. Next, we will explore the sub-ledgers where specific business partner transactions are managed, starting with Accounts Receivable for customers.