Study guide

8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options

SAP S/4HANA Sales C_TS462

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure

1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration

2 Chapter 2: The Order-to-Cash Process and Sales Master Data

2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling

3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements

3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries

4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs

4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders

5 Chapter 5: Pricing and the Condition Technique

5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement

6 Chapter 6: Availability Check (ATP) and Delivery Scheduling

6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements

7 Chapter 7: Delivery Processing and Embedded EWM

7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries

8 Chapter 8: Billing and Integration with Financial Accounting

8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options

9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output

9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables

10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core

10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels

11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition

11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM

8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options

Key Takeaways Explain This Topic AI

Before the accounting document is created, you can still change the billing date, pricing, account determination, and output determination data of a billing document.

Reference number types A to F (customer reference, sales order, delivery, external delivery, billing document, external delivery if available) are set in copying control and transferred to accounting.

If the FI document type field of the billing type is empty, all billing documents are posted with document type RV; a separate document type per billing type allows separate evaluations and number ranges.

The negative posting indicator in the billing type lets credit memos and cancellations post on the same side as the receivable so account totals return to zero, if the company code permits negative postings.

SAP S/4HANA Output Management is the default for billing documents (NAST can be re-enabled per SAP Note 2267376), and BAdI SD_BIL_FLEX_NUMBERING assigns number range intervals and prefixes of up to five characters per billing type.

Last updated: October 2026

The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options

When a billing document is saved, Sales and Distribution hands the commercial result to Financial Accounting. The S46150 unit Describing the Interface Between Sales and Distribution and Financial Accounting explains the settings that shape this hand-over, and the course appendix adds the output and technical options that billing specialists use. Account determination itself is covered in section 8.6.

Link to Financial Accounting

The system transfers the billing data of invoices, credit memos, and debit memos to Financial Accounting and posts them to the correct accounts. Until the accounting document has been created, you can still change the following data in the billing document:

  • Billing date
  • Pricing
  • Account determination
  • Output determination data

After the billing document has been released to accounting, these changes are no longer possible.

Posting Block

Normally, the accounting data is transferred automatically. For certain billing types you might not want this, so you set a posting block for the billing type. The accounting documents are then generated only after you release the billing documents. This lets you create the billing documents first, print them, and transfer them to Financial Accounting later, which can also improve system performance. The course adds a key detail: the system generates all or none of the accounting documents. If the posting block is active, or if errors occurred in account determination, no controlling documents are created either; nothing is posted until the block is removed or the error corrected.

Reference Numbers and Assignment Numbers

Copying control for billing documents decides which number is transferred to accounting as reference number and as assignment number . The number types are:

  • Number Type Number Transferred
  • A Customer reference (purchase order number)
  • B Sales order number
  • C Delivery number
  • D External delivery number
  • E Billing document number
  • F External delivery number if available, otherwise the delivery number

These numbers help accounts receivable match incoming payments to open items, for example when customers quote their purchase order number. For invoice lists , billing documents are first created and posted with their own reference numbers; when the invoice list is created, the invoice list's reference number overwrites the reference numbers of the individual billing documents, so incoming payments can be posted with the invoice list number (section 8.4).

Transaction-Related Document Types

Financial Accounting distinguishes documents by document type , stored in the document header. Without further settings, the system gives all SD billing documents the FI document type RV . In the Document type field of the billing type, you can maintain a different document type for each billing type. This enables differentiated evaluations and separate number assignment in Financial Accounting; if the field is empty, RV continues to be transferred.

Head Office and Branches

A head office and its branches can be represented with SD partner functions (for example, a branch as sold-to party and the head office as payer) or with the Head office field in the accounting segment of the customer master. Previously, the accounting segment had to be maintained for both customers; if accounting data was missing for the branch, billing documents could be created but not transferred to accounting.

The Branch/Head office field in the billing type controls which partner function in the billing document is transferred to Financial Accounting, that is, whether the sold-to party or the payer is entered as the customer of the accounting document. If the field is left blank, the system ignores the relationship stored in the accounting Head office field. For all other settings, the relationship stored in Financial Accounting has priority over the SD partner functions.

Negative Postings

In the standard system, cancellations and credit memos are posted on the opposite side of the customer account from the receivable. The account totals then show sales on both sides, so the total is greater than zero even though nothing was sold. Some customers require credit memos and cancellations to post on the same side as the receivable, so the totals line can return to zero.

To do this, activate the Negative posting field for the billing types for credit memos and cancellations. The information is transferred through the FI/CO interface. Two limitations from the course:

The setting changes only the display of open items and account totals ; it has no effect on processes in Financial Accounting.

Negative postings happen only if they are permitted for the company code .

Value-Dated Credit Memos

For credit memos, the billing type can control whether a credit memo is posted with its own value date , so it becomes due on that date in accounting instead of following the payment terms that would otherwise apply.

Output Management for Billing Documents

In SAP S/4HANA, SAP S/4HANA Output Management is used for billing documents by default . The classic NAST approach can be enabled again with a specific Customizing parameter (SAP Note 2267376). Output Management is the strategic framework, and future developments are made only there. Adobe XFA is the default form technology, but SAPscript, Smart Forms, and Adobe Forms are still supported. The course names its main benefits:

  • Extensibility through broad use of CDS views
  • BRFplus for flexible output parameter determination
  • One solution across SD, MM, FIN, and other applications
  • Full SAP Fiori integration
  • State-of-the-art email support with multiple recipients and templates

Compared with NAST, Output Management supports only the print, email, XML, and IDoc (on premise) channels by default. Decision tables with condition columns and result columns determine the output type, receiver, channel, printer settings, and form template; rows are processed top to bottom, so the most specific conditions should come first, and tables can be exported to and imported from Microsoft Excel (sections 9.6 and 9.7).

The General Billing Interface

Besides the Create Billing Documents app with its omnichannel approach (EBDRs), the general billing interface remains available. It lets you invoice external documents , such as orders and deliveries not created in the SAP system. You prepare the data in a sequential file in a specified format, fill a minimum of required fields (for example, the customer master and the sales organization), and supply the remaining fields from the file or let the system determine them ( optional fields , for example material master and price components). You can include external reference numbers such as external delivery or order numbers.

Flexible Billing Document Numbering and Prefixes

With the filter-enabled BAdI SD_BIL_FLEX_NUMBERING , newly created billing documents of a billing type can be assigned to custom number range intervals and, optionally, number range prefixes , depending on header fields of the billing document. Example from the course: a corporation with companies in eight countries uses interval G1 for F2 invoices of the German company and interval F1 for those of the French company, to satisfy country-specific legal numbering requirements. Prefixes of up to five characters can be combined with the intervals: prefix ABC with interval 0000001-9999999 can produce billing document number ABC1234567 . Prefixes open new number spaces (for example, prefix AB with the same limits as interval 19 doubles the available numbers) and make documents recognizable, such as DE for German and FR for French documents.

  • Topic Key Setting
  • Delay transfer to accounting Posting block in the billing type; release with VF02 or VFX3
  • Payment matching Reference and assignment number types A - F in copying control
  • Separate FI evaluation FI document type per billing type (default RV )
  • Head office pays for branches Branch/Head office field in the billing type
  • Zero account totals after cancellation Negative posting in the billing type, if the company code allows it
  • Country-specific invoice numbers BAdI SD_BIL_FLEX_NUMBERING with intervals and prefixes