Managing Polish KSeF Requirements with SAP S/4HANA Cloud Private Edition & SAP S/4HANA
ByAinvest
Monday, Aug 11, 2025 2:33 am ET1min read
SAP--
Process Overview
For the outbound process of sales invoices, the following process flow is applicable:
1. Maintain Official Document Number Types: Create ODN types such as ZKSeF for Poland B2B KSeF reference numbers.
2. Map Official Document Number Type to Internal Type: Map custom ODN types to SAP-delivered internal types to ensure accurate document number derivation.
3. Configure Official Document Number Type Characteristics: Set properties such as length and processing methods.
Implementation Steps
1. Maintain Official Document Number Types: Use the transaction “ODNTYP” to create and maintain ODN types. For example, create ZKSeF for Poland B2B KSeF reference numbers.
2. Map Official Document Number Type to Internal Type: Use the transaction “ODNINTTYP” to map custom ODN types to SAP-delivered internal types. For Poland, map to PLKSEF.
3. Configure Official Document Number Type Characteristics: Use the transaction “ODNTYPC” to set properties such as length and legal timestamp. For ZKSeF, configure the length to 35 characters and enable the legal timestamp.
Example Use Cases
- Supplier Invoice via MIRO: Enter invoice data and press “Additional Fiscal Data” to enter the KSeF number.
- Customer Invoice via KSeF Portal: Submit the invoice and receive it via the EDocument Cockpit, with the KSeF number visible on the header.
Availability and Integration
The solution is available for SAP S/4HANA Cloud Private Edition & SAP S/4HANA Versions 1709 – 2025. Customers can install the feature package or refer to the note collection in SAP Note 3565339 for additional details. Direct integration with SAP Document and Reporting Compliance to sync KSeF numbers from the tax portal is also available soon.
References
[1] https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/how-you-can-manage-polish-ksef-requirement-in-sap-s-4hana-cloud-private/ba-p/14175579
[2] https://www.globenewswire.com/news-release/2025/08/06/3128373/0/en/Multiple-ProcessWeaver-by-Elemica-Solutions-Achieve-SAP-Certified-Integration-with-SAP-S-4HANA-Cloud.html
SAP customers in Poland can manage KSeF requirements using the Official Document Numbering (ODN) Framework in SAP S/4HANA Cloud Private Edition & SAP S/4HANA. The process involves maintaining ODN types, mapping types to internal types, and configuring ODN type characteristics. The ODN Framework can help fulfill the new legal requirement of KSeF (Dz.U. 2023 poz. 1598) for outbound and inbound processes, including sales invoices and vendor invoices.
SAP customers in Poland are now able to manage the KSeF (Klasyfikator Systemu Ewidencji Faktur) requirements using the Official Document Numbering (ODN) Framework in SAP S/4HANA Cloud Private Edition & SAP S/4HANA. The process involves maintaining ODN types, mapping types to internal types, and configuring ODN type characteristics. This framework helps fulfill the new legal requirement of KSeF (Dz.U. 2023 poz. 1598) for both outbound and inbound processes, including sales invoices and vendor invoices.Process Overview
For the outbound process of sales invoices, the following process flow is applicable:
1. Maintain Official Document Number Types: Create ODN types such as ZKSeF for Poland B2B KSeF reference numbers.
2. Map Official Document Number Type to Internal Type: Map custom ODN types to SAP-delivered internal types to ensure accurate document number derivation.
3. Configure Official Document Number Type Characteristics: Set properties such as length and processing methods.
Implementation Steps
1. Maintain Official Document Number Types: Use the transaction “ODNTYP” to create and maintain ODN types. For example, create ZKSeF for Poland B2B KSeF reference numbers.
2. Map Official Document Number Type to Internal Type: Use the transaction “ODNINTTYP” to map custom ODN types to SAP-delivered internal types. For Poland, map to PLKSEF.
3. Configure Official Document Number Type Characteristics: Use the transaction “ODNTYPC” to set properties such as length and legal timestamp. For ZKSeF, configure the length to 35 characters and enable the legal timestamp.
Example Use Cases
- Supplier Invoice via MIRO: Enter invoice data and press “Additional Fiscal Data” to enter the KSeF number.
- Customer Invoice via KSeF Portal: Submit the invoice and receive it via the EDocument Cockpit, with the KSeF number visible on the header.
Availability and Integration
The solution is available for SAP S/4HANA Cloud Private Edition & SAP S/4HANA Versions 1709 – 2025. Customers can install the feature package or refer to the note collection in SAP Note 3565339 for additional details. Direct integration with SAP Document and Reporting Compliance to sync KSeF numbers from the tax portal is also available soon.
References
[1] https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/how-you-can-manage-polish-ksef-requirement-in-sap-s-4hana-cloud-private/ba-p/14175579
[2] https://www.globenewswire.com/news-release/2025/08/06/3128373/0/en/Multiple-ProcessWeaver-by-Elemica-Solutions-Achieve-SAP-Certified-Integration-with-SAP-S-4HANA-Cloud.html

Stay ahead of the market.
Get curated U.S. market news, insights and key dates delivered to your inbox.
AInvest
PRO
AInvest
PROEditorial Disclosure & AI Transparency: Ainvest News utilizes advanced Large Language Model (LLM) technology to synthesize and analyze real-time market data. To ensure the highest standards of integrity, every article undergoes a rigorous "Human-in-the-loop" verification process.
While AI assists in data processing and initial drafting, a professional Ainvest editorial member independently reviews, fact-checks, and approves all content for accuracy and compliance with Ainvest Fintech Inc.’s editorial standards. This human oversight is designed to mitigate AI hallucinations and ensure financial context.
Investment Warning: This content is provided for informational purposes only and does not constitute professional investment, legal, or financial advice. Markets involve inherent risks. Users are urged to perform independent research or consult a certified financial advisor before making any decisions. Ainvest Fintech Inc. disclaims all liability for actions taken based on this information. Found an error?Report an Issue



Comments
No comments yet