The Importance of Document Types in SAP FI: What Do SA, KR, KZ Really Mean and Change?

Introduction

In the SAP Financial Accounting (FI) module, countless financial documents are recorded every day. To ensure the system understands what these documents represent and manages the process flow correctly, a 'document type' must be defined. However, this field is often skipped by users or defaulted to 'SA' without much thought. In reality, document type is not just a combination of letters—it is a key parameter that tells SAP which module, function, and process a document is related to.In this article, we will explain what document types are, why they are so important, and what makes commonly used types like SA, KR, and KZ different. We will focus especially on their impact on processes like F110 payment runs, e-ledger integration, reporting, and authorizations.

What is a Document Type?

Every financial transaction in SAP is recorded as a document. To let the system understand what kind of transaction it is, which module it belongs to, and how it interacts with other processes, a document type is assigned.Examples of document types:- SA: General ledger entry- KR: Vendor invoice- KZ: Vendor payment- DR: Customer invoice- DZ: Customer incoming payment- AB: Transfer or manual adjustmentEach document type is processed differently by the system, appears in different reports, and is subject to different authorization rules.

Real-World Impacts of Choosing the Right Document Type

        • SAP Document Flow

A vendor-related expense entered with SA will not be linked to the vendor account. The same entry with KR, however, will appear in the vendor account and show up in FBL1N.

        • F110 Automatic Payment Program

SA entries are not picked up in the F110 payment run. KR entries are considered open items for vendors and are included automatically in the payment proposals.

        • Reporting & Filtering

Document type is frequently used as a filter in reports. In FAGLL03, FBL1N, and FBL5N, you can choose to exclude SA or include only KR document types.

        • Authorizations

Different document types can be controlled via separate authorization objects (e.g., F_BKPF_BLA). Some users may be allowed to post KZ and KR but not SA.

        • E-Ledger and Legal Reporting

Only certain document types are captured in legal reports or e-ledger exports. KR entries go directly to the ledger, while SA entries may be skipped or flagged.

        • Document Number Ranges

Each document type can have its own number range. This makes it easier to track and categorize transactions by their document number.

Comparison Table

Document Type	Purpose	Report Visibility	F110 Payment Eligible	E-Ledger Inclusion
SA	General ledger entry	Visible in FAGLL03 (not in vendor/customer views)	No	Depends
KR	Vendor invoice	FBL1N, FAGLL03	Yes	Yes
KZ	Vendor payment	FBL1N, payment reports	-	Yes
DR	Customer invoice	FBL5N, SD integration	-	Yes
DZ	Customer payment	FBL5N, bank integration	-	Yes

Conclusion

Choosing the correct document type in SAP FI is not just a technical detail—it determines how the system processes, integrates, and reports financial transactions. Incorrect document types can lead to missing data in reports, payment failures, or compliance risks. Therefore, selecting the appropriate type based on the purpose of the transaction is essential for technical accuracy, financial transparency, and operational integrity.