Every storefront buyer who has no matching record in your SAP customer master is an invoice that cannot post cleanly and an AR balance keyed to nobody. This card counts them.
At a glance
This card watches the customer master, the join that everything else in finance depends on. It takes buyers who have completed orders on a connected storefront and checks whether each one has a matching SAP Business Partner in the customer role. The ones with no match are the problem: their invoices cannot post under the correct role assignment, their AR aging is miskeyed or lands in a catch-all dummy customer, and their credit exposure is invisible to FSCM. This is customer-master drift, and it is the upstream cause of half the revenue-at-risk findings elsewhere in the Nerve Centre. A clean storefront-to-Business-Partner map is the precondition for accurate billing, accurate AR, and accurate credit control. This page covers both the customer-master view and its cross-platform twin: it is written to serve both, and it leans cross-platform because that is where the money leaks.
Calculation
Calculated automatically from your SAP data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A mixed B2B and DTC merchant runs S/4HANA Cloud (Company Code 1000, GBP) with a Shopify Plus DTC store and an Adobe Commerce B2B portal. The 7-day window ends 12 Mar 26. The card reads 14 absent customers, above the alert. A sample is shown.
Four things to notice:
- 14 absent customers trips the
>10alert, but they are not all the same problem. Three distinct root causes are present in the sample alone: genuine new buyers with no Business Partner, a guest checkout with no durable key, and a real partner that exists but does not resolve because the identity keys disagree. The fix differs for each. - Vale Interiors Ltd is the trap. A Business Partner exists, but it is keyed by tax ID while the storefront sent email, so the match fails and the customer looks absent. Creating a second Business Partner here would be the wrong move: it would split the AR and double-count the customer. The fix is the identity map, not a new master record.
- Pennine Joinery is the expensive one. £4,400 of B2B orders over three orders, and no Business Partner at all. Those invoices cannot post under a correct role assignment, so the revenue either stalls in an error queue or lands against a dummy customer where the AR aging is meaningless. This is exactly the kind of order that then shows up on Ecom Orders Missing Matching SAP Billing Document.
- The guest checkout may be acceptable; the B2B gaps are not. A £62 DTC guest order with no durable key is low risk and may post against a generic one-time-customer account. A £4,400 B2B buyer with no Business Partner is a billing and credit-control hole. Triage by value and by channel: B2B absences are urgent, DTC guest noise less so. Pair with Commerce Orders Without S/4HANA Cloud Sales Document to see the order-flow consequence.
Sibling cards merchants should reference together
This card detects the root cause behind several downstream revenue-at-risk findings: a buyer with no place in the customer master. Pair it with the order-flow and AR cards below to see the consequences and trace the fix.Reconciling against SAP
Where to look in S/4HANA Cloud: The closest native equivalents inside the SAP Fiori launchpad are:Manage Business Partner Master Data Fiori app (the BP transaction) to search for a customer in the customer role Maintain Business Partner to view roles, Company Code assignments, and sales-area data Customer Balances / Manage Customer Line Items to see whether AR is landing on a real partner or a dummy account Embedded Analytics: query the Business Partner CDS view in the customer role and intersect with the commerce customer listTo reconcile, take a sample of absent customers from the card, search for each in Manage Business Partner using the keys the connector tried (email, tax ID, external customer ID). If a partner truly does not exist, the absence is real. If a partner exists but under a different key, the absence is an identity-map problem, not a missing master, and the fix is the map. Common mistakes when comparing against SAP’s own reports:
- Searching on one key only. A buyer can exist in SAP under a tax ID while the storefront sent an email. Searching on email alone makes a real partner look absent. Always try every key the connector uses before concluding the record is missing.
- Confusing the customer role with other Business Partner roles. A Business Partner can exist as a vendor or a contact without the customer role. Only the customer role can carry AR and be billed. A partner without the customer role is effectively absent for this card’s purpose.
- Ignoring the Company Code / sales-area assignment. A Business Partner can exist in the customer role but lack the Company Code or sales-area data needed to post an invoice in the relevant entity. That partial setup still breaks billing, even though a name search finds the record.
- Counting guest checkouts as failures. Some DTC guest orders are designed to post against a generic one-time-customer account and never get their own Business Partner. Decide your policy on guest orders before treating every guest as drift.
Cross-connector reconciliation, the killer finding:
The customer master is the single join the whole order-to-cash chain rests on. This table shows where buyers outrun the master, channel by channel.
The most useful pivot is into Ecom Orders Missing Matching SAP Billing Document to see the billing consequence, and into Commerce Orders Without S/4HANA Cloud Sales Document to see the orders that never reached SAP because there was no account to create them against.