End-to-End Business Process: AP/AR Netting with a Single S/4HANA Business Partner

SAP S/4HANA • Finance Knowledge Base

End-to-End Business Process: AP/AR Netting with a Single S/4HANA Business Partner

How the unified Business Partner architecture replaces clunky ECC customer-vendor linking with native, automated cash-flow netting.

One of the most immediate financial advantages of moving from SAP ECC to the S/4HANA Business Partner (BP) architecture is the ability to seamlessly handle entities that are both a customer and a vendor. In ECC, linking a customer (XD01) and a vendor (XK01) to offset accounts payable against accounts receivable was a manual process prone to master data errors. In S/4HANA, the centralized BP model natively supports AP/AR netting — dramatically streamlining cash flow management and period-end clearing. This guide walks through the exact end-to-end process of setting up a unified partner, posting overlapping transactions, and executing a net financial clearing.

📌 The Business Scenario

Your Enterprise (Company Code 1000) buys raw materials from Global Tech Corp, but also sells finished IT hardware back to them. Instead of two separate bank transfers, you want to net the balances.

Accounts Receivable — Hardware Sale$10,000
Accounts Payable — Raw Materials$3,000
Net Amount to Collect$7,000

1

Master Data Preparation T-Code: BP

To enable netting, the partner must exist as a single entity with both FI Customer and FI Vendor roles active, and the clearing link must be established.

Create the General Business Partner

Execute BP → Click Organization → select your BP Grouping (e.g., Internal Number Assignment).

Select BP Role 000000 (Business Partner General) and enter core data: Name (Global Tech Corp), Search Term, Address, Language.

Enter Bank Details under Payment Transactions (only needed once). Save — the system generates BP #100500.

Extend to the FI Customer Role

Switch to change mode, select BP Role FLCU00 (FI Customer). Click Company Code and enter 1000.

In Account Management, assign the AR Reconciliation Account.

In the Payment Transactions tab, check “Clearing with Vendor”.

Save — the system uses CVI to generate the FI Customer number in the background.

Extend to the FI Vendor Role

Switch BP Role to FLVN00 (FI Vendor). Click Company Code and enter 1000.

In Account Management, assign the AP Reconciliation Account.

In the Payment Transactions tab, check “Clearing with Customer”.
Because of S/4HANA Customer-Vendor Integration (CVI), the system automatically links the underlying Customer and Vendor numbers in the background (tables KNA1-LIFNR and LFA1-KUNNR).

2

Operational Postings

Now that the master data is linked, let’s generate the financial liabilities.

Post the Outbound Sales Invoice (AR)

Execute FB70 (Enter Customer Invoice) or process an SD Billing Document (VF01).

Customer: Global Tech Corp (BP #100500) • Amount: $10,000 • G/L Account: Sales Revenue.

Result: An open AR debit of $10,000.

Post the Inbound Vendor Invoice (AP)

Execute FB60 (Enter Vendor Invoice) or process an MM Invoice Receipt (MIRO).

Vendor: Global Tech Corp (BP #100500) • Amount: $3,000 • G/L Account: Raw Material Expense.

Result: An open AP credit of $3,000.

3

Financial Netting and Clearing

With the “Clearing with Vendor/Customer” flags active on the Business Partner, S/4HANA knows that these open items belong to the same financial entity.

Option A — Manual Clearing F-32 / F-44

Execute F-44 (Clear Vendor). Enter the Vendor number and Company Code 1000, then click Process Open Items.

Because the BP is linked, the system pulls in both the $3,000 AP open item and the $10,000 AR open item onto the same clearing screen. Select both — the “Not Assigned” balance shows as $7,000.

You can process a partial payment or leave the $7,000 as a residual item to be collected via bank transfer.

Option B — Automated Payment Run F110

Execute F110 (Automatic Payment Transactions), enter parameters, and run the proposal.

The Payment Program evaluates the BP: sees $10,000 receivable and $3,000 payable, and automatically nets them. Since the receivable is higher, the system will not pay the vendor — it expects an incoming $7,000, preventing an erroneous cash outflow.

✓

Consultant Checkpoints & Troubleshooting

If you’re setting this up for a client and netting fails to pull both items during clearing, check the following:

  • Missing Flags: Ensure both “Clearing with Vendor” and “Clearing with Customer” are checked in the respective BP Company Code roles.
  • Sort Keys: Ensure Sort Keys (e.g., 001 – Posting Date) on both AP and AR reconciliation accounts don’t conflict with your clearing rules.
  • Payment Methods: If using F110, ensure payment methods and terms on both customer and vendor sides align; conflicting block indicators will stop the netting process.
By utilizing the Business Partner architecture correctly, finance teams can drastically reduce manual reconciliation efforts, prevent erroneous cash outflows, and maintain a pristine, real-time view of counterparty risk.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top