Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

Partner functions describe who plays each role in a sale: ordering, receiving goods, receiving the bill and paying. One organization may fill several roles, or different organizations may fill each.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Sales and Distribution connects customer orders, logistics and billing. Each stage has its own documents, quantities and status, so one stage’s success does not prove the whole sale is complete.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for Sold-to, ship-to, bill-to and payer: Read SAP sales partner roles correctly
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SD partner-function concepts for sales operations, master-data and integration support. ERP and S/4HANA documentation supports roles and determination; BP roles, multiple-address handling and document overrides vary by edition, release and configuration.

Documentation review on 14 November 2026 used the available official SAP indexed excerpts; several SAP Help pages returned no readable full text. The worked case and proposed checks are original illustrative teaching material, not execution evidence from a customer SAP system. Exact fields, permitted actions and behavior must be confirmed against the installed product, release and configuration.

A MANUFACTURING EXAMPLE

Read the customer's equipment delivery roles

One sale can involve four parties

Sold-to: Head office. Ship-to: Regional branch. Bill-to: Finance office. Payer: Central payments team
What to notice: Ordering, receiving goods, receiving the invoice and paying need not be performed by the same party.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Sold-to
Head office
Ship-to
Regional branch
Bill-to
Finance office
Payer
Central payments team
Words you’ll meet in this guide
Sales order
A record of a customer’s order.
Delivery
A document organizing goods to be sent.
Billing
The process that creates a customer charge.
HANA
SAP’s database platform.
API
A defined interface through which programs exchange data or request actions.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Sold-to party → Ship-to and bill-to → Payer. Conceptual diagram for Sold-to, ship-to, bill-to and payer: Read SAP sales partner roles correctly.
Apply the idea: A customer's head office orders equipment for another operating site, while a separate organization receives and pays the invoice.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Read the customer's equipment delivery roles

    A customer's head office orders equipment for another operating site, while a separate organization receives and pays the invoice.

  2. The four partner functions answer four different questions

    The sold-to places the order, the ship-to receives the goods, the bill-to receives the invoice and the payer settles it.

  3. Audience and prerequisites

    This guide is for sales operations, SD support, master-data owners and integration analysts.

  4. Worked sale: head office orders for a branch

    In our fictional order 47000123, sold-to C100 is Central Purchasing, ship-to C210 is the North Branch, bill-to C310 is the Finance Office and payer C410 is Central Payments.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.