Document Title: Business Process Design Document

Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 1 of 14

Business Process Design

Document
SAP-BPD-FIN-001
Financial Accounting
Document Revision 1.0

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 2 of 14

BPD REVIEW & APPROVAL

AUTHOR
Functional Area Required Signatures Date
Name: Narendra Ulabala
Author/Originator 07/05/2024

Sign Name:

REVIEWERS
Functional Area Date
Name: Allan Vanderheyden
PMO

Name:
Finance

APPROVERS
Functional Area Required Signatures Date
Name: Allan Vanderheyden
PMO

Sign Name:

Name:
Business Process
Owner
Sign Name:

Name: Liam Eckersley

Finance Lead

Sign Name:

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 3 of 14

Revision History

Should this BPD require changes, a detailed description of the change or changes shall be noted with the next
consecutive revision number.

Revision Revision Revision Description Revised by

No. Date
1.0 07/05/2024 Initial Draft Narendra Ulabala

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 4 of 14

Table of Contents
1. GENERAL EXPLANATION/DESCRIPTION.....................................................................................................5
1.1 S/4HANA Public Cloud and SAP ECC System Integration..................................................................................5
1.1.1. Integration - Accounting Document....................................................................................................5
1.1.2. Accounting Document interface in S/4HANA & ECC............................................................................6
1.1.3. T-Account Representation...................................................................................................................6
2. UNDERSTANDING OF THE ORGANIZATION STRUCTURE TO BE CONFIGURED IN S/4HANA
PUBLIC CLOUD................................................................................................................................................................7
2.1 Organizational Structure..................................................................................................................................7
2.2 Company code to Company.............................................................................................................................7
2.3 Mandatory attributes for creating company code...........................................................................................8
2.3.1. Fiscal Year Variant...............................................................................................................................8
2.3.2. Posting Period Variant.........................................................................................................................8
3. CHART OF ACCOUNTS........................................................................................................................................9
3.1 Account Groups...............................................................................................................................................9
4. ADDITIONAL LOCAL CURRENCIES................................................................................................................9
5. CURRENCY TRANSLATION RATIOS.............................................................................................................10
6. INTEGRATION WITH SALES & DISTRIBUTION.........................................................................................10
7. ACCOUNTS RECEIVABLE.................................................................................................................................10
7.1 Customer Integration as Business Partner (BP)..............................................................................................10
7.2 Accounting for payment receipt in S/4HANA & ECC......................................................................................10
8. TAXATION.............................................................................................................................................................10
9. CONTROLLING AREA........................................................................................................................................10
10. REPORTING..........................................................................................................................................................11
11. CONFIGURATION CONSIDERATIONS FOR FINANCE..............................................................................11
12. DESCRIPTION OF CHANGE IMPACT / BUSINESS BENEFITS.................................................................11
13. DESCRIPTION OF FUNCTIONAL GAPS.........................................................................................................12
14. WORKFLOW, RPA AND AI/ML........................................................................................................................12
15. REPORTS................................................................................................................................................................12
16. INTERFACES.........................................................................................................................................................12
17. CONVERSIONS / MASTER DATA.....................................................................................................................12
18. ENHANCEMENTS................................................................................................................................................13
19. FORMS....................................................................................................................................................................13
20. ROLES, SECURITY AND AUTHORIZATIONS...............................................................................................13
21. IMPACTED PROCEDURES................................................................................................................................13
22. ASSUMPTIONS......................................................................................................................................................13
23. EXTERNAL SUPPORTING PROJECTS...........................................................................................................13
24. APPENDIX..............................................................................................................................................................13

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 5 of 14

1. GENERAL EXPLANATION/DESCRIPTION
Process Definition:
Deluxe Finance process operates using the SAP ERP Central Component (ECC) enterprise system, to manage financial
data located at international locations across multiple companies, currencies, and languages. The SAP Financial
Accounting (FI) module mainly deals with the following financial components in Deluxe.
 General ledger
 Accounts receivable
 Controlling
Process Description:
This document aims to provide an understanding of the proposed Finance business processes in S/4HANA Public
Cloud.

1.1 S/4HANA Public Cloud and SAP ECC System Integration

For Deluxe, the proposed solution is to create an accounting document referring to the S/4HANA Public Cloud billing
document.

1.1.1. Integration - Accounting Document

The required data for creating the Finance document in ECC will be flown from S/4HANA system using the Interface.

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 6 of 14

The S/4HANA provides Revenue GL Account, Customer (BP), Profit center, Plant, Account group and sales value to ECC
to complete to postings.

1.1.2. Accounting Document interface in S/4HANA & ECC.

Sr. No. S/4HANA SALES S/4HANA Accounting ECC Accounting

1 Sales Order - -
2 Delivery Note Book Accrual Revenue (1) Book Accrual revenue (1)
3 Billing document Customer debit (2) Customer debit (2)
4 Incoming Payment Customer Clearing (3) Customer Clearing (3)

2 &3 Will flow from S/4HANA to ECC

4 Will flow from ECC to S/4HANA

(1) Accrual revenue posting against delivery

Accounting Doc Debit / Credit Amount Reference No.
Accrual Revenue Debit 1000 Sales order ref.
Revenue Account Credit 1000 Sales order ref.
COGS/Material

(2) Revenue posting against delivery to the customer

Accounting Doc Debit / Credit Amount Reference No.
Customer Debit 1000 Against Delivery Doc.
Accrual Revenue Credit 1000 Against Delivery Doc

(3) Payment against the Invoice

Debit / Credit Amount Reference No.
Bank A/c. Debit 1000 Against the invoice
Customer Account Credit 1000 Against the invoice

1.1.3. T-Account Representation

Accrual Revenue Account
Debit Credit
Customer Account (2) 1000 Revenue Account (1) 1000

Revenue Account
Debit Credit
Accrual Revenue Account (1) 1000

Customer Account
Debit Credit
Accrual Revenue Account (2) 1000

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 7 of 14

2. UNDERSTANDING OF THE ORGANIZATION STRUCTURE TO BE

CONFIGURED IN S/4HANA PUBLIC CLOUD
2.1 Organizational Structure
The Deluxe Organization structure as maintained in SAP ECC will be used/created in S/4HANA Public Cloud. The
Organization Structure displayed in the following chart will be used as a reference for all the regions of Deluxe.

2.2 Company code to Company

The following company codes will be created in S/4HANA Public Cloud system:
Company
Code Entity Name Region Company
9020 Deluxe EchoStar LLC US 9020
1170 Deluxe Digital Cinema Inc. US 1170
3011 Deluxe Distribution Canada Ltd. Canada 3011
7050 Deluxe Entertainment Distribution India Private Ltd. India 7050
1070 Deluxe Media Inc. US 1070
4100 Deluxe 142 Limited UK 4100
4462 Deluxe Spain Spain 4462
4602 Deluxe Germany GmbH Germany 4602
4501 Deluxe Media France France 4501
4341 Deluxe Ets Italy S.R.L. Italy 4341
4801 Deluxe ETS Belgium Ltd. Belgium 4801
6501 AP Facilities PTY LTD Australia 6501
6504 Deluxe The Vault New Zealand 6504

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 8 of 14

2.3 Mandatory attributes for creating company code

2.3.1. Fiscal Year Variant

Fiscal year variant is mandatory in global setup of company code. We have 2 different FYV in ECC. V3 is used
for India region company codes where the Periods starts from April and all other company codes uses Z1
which starts with January.

However, in S/4HANA Public Cloud, we can have only one FYV. Therefore, V3 will be replaced with K4 for all
company codes. We will use the second ledger as Local GAAP to handle India company codes with V3 FYV.

Company Code Fiscal Year Variant FY Variant

9020 January to December K4
1170 January to December K4
3011 January to December K4
7050 January to December K4
1070 January to December K4
4100 January to December K4
4462 January to December K4
4602 January to December K4
4501 January to December K4
4341 January to December K4
4801 January to December K4
6501 January to December K4
6504 January to December K4

2.3.2. Posting Period Variant

Posting period variant is one of the mandatory configuration in global company setup.
The current set up in ECC will be followed in setting up of the posting period variant in S/4HANA Public Cloud.
One posting period variant by region will be followed here as well.

Company Code Country Posting Period

9020 US US01
1170 US US01
3011 Canada US01
7050 India IN01
1070 US US01
4100 UK GB01
4462 Spain SP01
4602 Germany EU01
4501 France EU01
4341 Italy IT01
4801 Belgium EU01
6501 Australia AU01
6504 New Zealand AU01

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 9 of 14

3. CHART OF ACCOUNTS
Since the billing is being processed in S/4HANA Public Cloud, the chart of accounts should be in sync with the ECC
system.
GL mapping will be precise and accurate if we use the same COA where Interfaces are called for posting the Finance
documents related to final billing from Sales Order.

Co. Company Name Country Chart of Country GRP COA

Code Account COA
9020 Deluxe EchoStar LLC US 1000 9000
1170 Deluxe Digital Cinema Inc. US 1000 9000
3011 Deluxe Distribution Canada LTD Canada 1000 9000
7050 Deluxe Entertainment Distribution India Private Ltd. India 1000 9000
1070 Deluxe Media INC US 1000 9000
4100 Deluxe 142 Limited UK 1000 9000
4462 Deluxe Spain Spain 1000 2000 9000
4602 Deluxe Germany GmbH Germany 1000 5000 9000
4501 Deluxe Media France France 1000 3000 9000
4341 Deluxe Ets Italy S.R.L. Italy 1000 6000 9000
4801 Deluxe ETS Belgium Ltd Belgium 1000 4000 9000
6501 AP Facilities PTY LTD Australia 1000 9000
6504 Deluxe The Vault New Zealand 1000 9000

3.1 Account Groups

The Account Groups will be maintained for grouping of General Ledger under the Chart of Account in company
code in the following format.
Chart of Account Acct. Group Name From No. To Number
1000 GL GL 0000000 ZZZZZZZZZZ

4. ADDITIONAL LOCAL CURRENCIES

For Local GAAP and IFRS we need to use the currency settings.
Company Code Country 1st Currency 2nd Currency
9020 US USD USD
1170 US USD USD
3011 Canada CAD USD
7050 India INR USD
1070 US USD USD
4170 UK GBP USD
4100 UK GBP USD
4462 Spain EUR USD
4602 Germany EUR USD
4501 France EUR USD
4341 Italy EUR USD
4801 Belgium EUR USD
6501 Australia AUD USD
6504 New Zealand NZD USD

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 10 of 14

5. CURRENCY TRANSLATION RATIOS

Currency Translation ratios between company code currencies and other transaction currencies will be maintained in
S/4HANA.
It will be done every month on the last day of the month. No Interface is under consideration as it is done only once in
a month. This will be carried out manually.

6. INTEGRATION WITH SALES & DISTRIBUTION

It is an important part of the system setup. The current logic in ECC will be considered for derivation of Revenue
accounts in S/4HANA.

This will be updated in Detail after finalizing the solutions in next meetings.

7. ACCOUNTS RECEIVABLE
The Accounts Receivable module will be interfaced with the SAP ECC system. All the accounting documents processed
by billing in S/4HANA Public Cloud will be interfaced with the SAP ECC. All relevant details such as Customer number,
billing date, where the posting will be completed, and the account receivable balances, will be displayed to that
particular customer.

Customer Integration as Business Partner (BP)

Business Partner integration will be configured as follows:
1. In S/4HANA, customer is replaced with Business Partner (BP). Therefore, Deluxe Customers will be configured
and integrated as Business Partners. Effectively, all the customers will be created as Business Partners in the
system.
2. External customer number identification functionality will be used to recognize the ECC customers in
S/4HANA Public Cloud.
3. Reconciliation account (G/L) will be maintained for Business Partners in S/4HANA with reference to ECC
system Master data.

7.1 Accounting for payment receipt in S/4HANA & ECC

Interface is required to update Payments received from customers to be updated in both ECC & S/4HANA system.

8. TAXATION
Taxation will be configured as follows in S/4HANA:
1. For USA and Canada, the Vertex will be enabled and used for tax derivation.
2. For other countries, Tax procedures will be configured as per the current tax setup defined in the ECC.

9. CONTROLLING AREA
The controlling module is mainly used for profit center accounting in Deluxe Media Inc. The Profit center in final
accounting document will flow from the Materials & Services in S/4HANA Public Cloud.

The following Controlling areas will be created in S/4HANA Public Cloud. We will have one Controlling area.
Company Code Controlling area Controlling area currency
9020 1000 USD
1170 1000 USD

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 11 of 14

Company Code Controlling area Controlling area currency

3011 1000 USD
7050 1000 USD
1070 1000 USD
4170 1000 USD
4100 1000 USD
4462 1000 USD
4602 1000 USD
4501 1000 USD
4341 1000 USD
4801 1000 USD
6501 1000 USD
6504 1000 USD

10.REPORTING
The embedded REPORTS.docx file below contains some sample reporting screenshots.

Some of the standard reports available in S/4HANA cloud

Master Data Reports
Manage Customer Master
Manage G/L Account Master Data

11.CONFIGURATION CONSIDERATIONS FOR FINANCE

1. Company
2. Company Code
A. Fiscal Year Variant
B. Posting Period Variant
3. Controlling area
4. Chart of Account
A. Account Group
5. Additional Currencies
6. Currency Translation Ratios.
7. VKOA – FI-SD integration for billing.
8. Vertex integration
9. Tax procedures (Country)

12.DESCRIPTION OF CHANGE IMPACT / BUSINESS BENEFITS

Number Change Description (Integrations) Impact or Benefit
1 ECC system will only capture Accounting entries
2 No sales orders are created in ECC
3 Tax calculations and billing happens in S/4HANA

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 12 of 14

13.DESCRIPTION OF FUNCTIONAL GAPS

Requirement Number Gap Description Resolution

14.WORKFLOW, RPA and AI/ML

Workflow Workflow Description Unique Reference
Name Requirements WRICEF

15.REPORTS
Report Name Report Description Unique Reference
Requirements WRICEF
Standard SAP FIORI Manage customer and Manage GL master data NA
Reporting reports

16.INTERFACES
Source - Destination Request Info Return Info WRICEF Reference
System
SAP S/4HANA to ECC When goods are delivered the Accrual Account document SAP-FI-001
postings will happen in S4Hana and updated in ECC for Sales.
same doc is flown to ECC
SAP S/4HANA to ECC Billing document details. Account document SAP-FI-002
Customer number, GL account updated in ECC for Sales.
number, Tax, Billing amount, Billing
date
Debit & credit indicator, profit center
SAP S/4HANA to Vertex Tax related information: Tax percentage to SAP SAP-FI-003
Country /Region/Customer/Plant S/4HANA
Taxable procedure
ECC to S4HANA Exchange rates OB08 SAP-FI-004
ECC to S4HANA Payment updates in S4 Incoming payments in S4 SAP-FI-005
S4HANA to ECC BP (Customer) Customer master in ECC SAP-FI-006

17.CONVERSIONS / MASTER DATA

Data Object Description SAP Object Master data
Template
Customer Business partner

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 13 of 14

18.ENHANCEMENTS
Enhancement Enhancement Description WRICEF Reference
Name
Delivery Need to change the GL account during the posting where COGS SAP_FI_007
to be replaced with Accrued Revenue and Inventory with
Revenue based on conditions (Material group)
Billing document Need to change the Revenue GL account during the posting to SAP_FI_008
Accrued Revenue GL
Clearing

19.FORMS
Form Name Form Description Unique Requirements
Billing outputs This will be covered in the Distribution section of the
workshop.

20.ROLES, SECURITY AND AUTHORIZATIONS

Role Description SAP Role(s) Authorization
Requirements
Accounts Receivable SAP_BR_AR_ACCOUNTANT
Accountant
Accounts Receivable SAP_BR_AR_MANAGER
Manager
Billing Clerk SAP_BR_BILLING_CLERK
General Ledger SAP_BR_GL_ACCOUNTANT
Accountant
Cash Management SAP_BR_CASH_SPECIALIST
Specialist

21.IMPACTED PROCEDURES
Functional Area Department Description

22.ASSUMPTIONS
The same Organization Structure from SAP ECC will be replicated in S/4HANA Public Cloud to ensure standard
interfacing between S/4HANA Public Cloud and SAP ECC.
REQUIREMENTS OUT OF SCOPE FOR THIS PHASE.

23.EXTERNAL SUPPORTING PROJECTS

Project # Name Description Owner

Project Medusa
Confidenti
al
 Document Title: Business Process Design Document
Financial Accounting

Document Identifier Rev Page No.

SAP-BPD-FIN-001 1.0 14 of 14

Project Medusa
Confidenti
al