When a project sits in the public sector, SAP PS-CD is often assumed to be in scope. I would pause here.

Some government organisations run simply as high-volume money-in / money-out shared-services platforms. No Funds Management, no statutory billing requirements. In these cases, a lean FI-CA and Convergent Invoicing (CI) implementation is often enough.

The real fork usually comes with the next requirement, and it is a common one in the public sector. A portion, or all of the collected cash needs to be forwarded to a third party. If you have worked with SAP PS-CD, you will know the Revenue Distribution capability. Public sector organisations use it to distribute collected amounts on behalf of third parties.

Assuming a lean FI-CA implementation, Partner Settlement is part of Convergent Invoicing, and it looks very similar to Revenue Distribution. In principle both appear to do the same thing: calculate a share, create credits, and pay out to another party. So the natural reaction is to reuse what already exists.

Can I use these two interchangeably? I will answer straight up. Partner Settlement is not a substitute for Revenue Distribution in every scenario. It depends entirely on what triggers the entitlement. Billing or cash receipt. I will work through why in the rest of the article.

Why does it matter? Because this decision drives the architecture, the scope, and which business functions get activated at the beginning of the project. Those decisions are made early and are usually difficult to reverse later.

Partner Settlement and Revenue Distribution can look interchangeable at a high level, and in several scenarios they produce a similar accounting result. But they are built on different principles, and as shown in the below scenario, the recipient balance does not always end up the same.

2.1 How PS-CD Revenue Distribution works

Revenue Distribution is based on cash collection. There are two functional variants of this capability, classic and enhanced. For simplicity, this article focuses only on the classic variant.

Revenue Distribution distributes only amounts that have actually been collected. The collecting authority is effectively holding money on behalf of third parties.

Nothing is distributed until cash is collected. If a payer pays 50% of the receivable, only 50% is available to distribute. The distribution cannot get ahead of the cash, because the cash is what triggers the distribution.

Technically, the distribution run  picks up cleared items and then the posting run creates the credit postings on the final recipient. A clearing reset on the original receivable reverses the previously distributed amount via a debit posting to the final recipient.

2.2 How BRIM Partner Settlement works

Partner Settlement addresses a commercial revenue-sharing model. An end user consumes a service, and part of the billed amount belongs to a partner.

The partner's share is determined during billing, not at payment receipt. The customer Billable Item (BIT) is split into a dependent partner item, rated, and posted through Convergent Invoicing to FI-CA as a credit memo. The settlement rule in the partner agreement controls timing and risk behaviour.

Non-payment is handled retrospectively, not prevented upfront. If the partner is configured to bear default risk, when the customer item goes into dunning (the item is open or only partially cleared), then the adjustment run reduces the partner entitlement through a debit adjustment processed in the next settlement run. The sequence is as follows: entitlement first, correction later.

2.3 The conceptual difference

The difference is simple:

• Partner Settlement → entitlement based on billed revenue (accrual)
• Revenue Distribution → entitlement based on cash collected

Side by side, by characteristics:

Figure 1  Partner Settlement vs Revenue Distribution – key characteristics

A local government department collects tax from a taxpayer and forwards it in full to the federal level. The taxpayer owes $100 and pays in three steps:

• $60 initially, before the due date 
• $20 after a dunning letter
• $20 via an external collector

Run that through both capabilities, focusing on the recipient's balance:

* After the adjustment run reduces the partner entitlement to match the unpaid $40, assuming the partner bears default risk. Without this, the partner balance stays at 100.

Figure 2  Recipient balance through the collection cycle

As shown in the table, Revenue Distribution forwards funds as cash arrives and always matches collection.

Partner Settlement credits the full entitlement at billing and subsequently reduces entitlement through the adjustment process (assuming it is configured accordingly). Standard Partner Settlement does not provide a payment-driven mechanism that incrementally rebuilds entitlement as subsequent payments are collected.

In comparison, classic Revenue Distribution never exceeds collected cash. Partner Settlement can temporarily recognise entitlement before cash is received, and additional logic is needed if entitlement must subsequently follow the exact cash collection. In the public sector, where distribution must strictly follow collection, that becomes a design constraint.

Not entirely and it really depends on the nature of the entitlement.

In my view, Partner Settlement can fit narrow public sector scenarios where payment is effectively received before the share is paid, for example like in prepaid revenue models.

Revenue Distribution remains necessary when entitlement is strictly cash-based, for instance tax sharing, court-ordered collections, or welfare recovery.

The two capabilities address different business requirements. Partner Settlement follows commercial logic, in terms of what was billed and who owns a share. Revenue Distribution follows cash-based logic and distributes only what has actually been collected.

This distinction is clearly visible the moment payments are delayed, partial, or uncertain, which in public sector scenarios is pretty much business as usual rather than the exception.

The real question is not whether Partner Settlement can produce the same accounting result as Revenue Distribution. The question is whether entitlement starts at billing or only once cash has been collected.

Get the design decision wrong, and the fix later is not a simple configuration change but a different business function or additional custom logic.

Disclaimer: This article is for informational purposes only and does not represent official SAP guidance. The examples and approaches are simplified to illustrate possible technical implementation. This is not a complete solution for production use. Do not apply any solution in a production system without fully testing and confirming it in a non-production environment.