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-channel twin: it is written to serve both, and it leans cross-channel because that is where the money leaks.
| What it detects | Storefront buyers with completed orders who have no matching SAP Business Partner in the customer role. Without the match, invoices cannot post correctly and AR cannot be keyed to the right account. |
| How the join works | The card matches each commerce customer to a SAP Business Partner using the connector’s identity map (email, external customer ID, tax / company identifiers depending on configuration). A customer counts as absent when no Business Partner in the customer role resolves from any of the available keys. |
| SAP side | The Business Partner master in the customer role, plus the partner’s Company Code and sales-area assignments that an invoice needs to post against. A buyer with no Business Partner has no role, no Company Code link, and no AR account. |
| Commerce side | Customers with at least one completed order on Shopify, BigCommerce, Adobe Commerce, or other connected storefronts inside the window. Guest-checkout and newly registered buyers are the usual sources of absent records. |
| Common root cause | Business Partner auto-creation not wired into the storefront order path, guest checkout producing no durable customer key, a B2B buyer onboarded on the storefront before being set up in SAP, or an identity-map mismatch (email on one side, tax ID on the other). |
| How to resolve | Create the missing Business Partner in the customer role (or fix the identity map so an existing one resolves), assign the correct Company Code and sales area, and wire Business Partner creation into the storefront onboarding so future buyers are mastered automatically. |
| Data source / freshness | SAP Business Partner data via OData against the live system; commerce customers and orders via each platform’s API. Vortex IQ polls every 15 minutes by default. |
| Time window | 7D (rolling 7 days) |
| Alert trigger | more than 10 customers with active orders and no matching Business Partner |
| Roles | owner, finance, marketing, operations |
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.| Commerce customer | Channel | Completed orders (7d) | Order value | Match key tried | SAP Business Partner |
|---|---|---|---|---|---|
| j.okafor@gmail.com | Shopify DTC | 1 | £180 | none found | |
| Pennine Joinery | Adobe B2B | 3 | £4,400 | company name + tax ID | none found |
| guest-checkout-8841 | Shopify DTC | 1 | £62 | order ID only | none found |
| Vale Interiors Ltd | Adobe B2B | 2 | £2,950 | partner exists under tax ID, email mismatch | |
| s.ahmed@outlook.com | Shopify DTC | 2 | £240 | none found |
- 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.| Card | Why pair it with Ecom Customers Absent from SAP Business Partner |
|---|---|
| Ecom Orders Missing Matching SAP Billing Document | The direct downstream effect. An order from an absent customer cannot bill cleanly, so it shows up as a missing billing document. The customer gap is often the cause. |
| Commerce Orders Without S/4HANA Cloud Sales Document | The order-creation step. A buyer with no Business Partner often cannot have a Sales Document created against the right account, so the order never reaches SAP at all. |
| AR Balance Live by Company Code | The AR consequence. Invoices keyed to a dummy or wrong customer distort the live AR balance by Company Code. A clean master is the precondition for trustworthy AR. |
| AR Aging on Customers with Active Ecom Orders | The credit-control side. A customer with no Business Partner has no credit account, so they cannot be aged or blocked at all, which is its own risk. |
| SAP Active Customers | The size of the mastered customer base. The gap between active commerce buyers and active SAP customers is a direct measure of master drift. |
| SAP Top Customers by Revenue | If a high-revenue buyer is absent from the master, the revenue ranking in SAP is wrong, because their spend is keyed elsewhere or nowhere. |
| Revenue Gap vs Commerce | Absent customers are one structural reason commerce revenue exceeds SAP-booked revenue: their orders cannot bill, so they never reach the GL. |
| shopify.total_revenue / bigcommerce.total_revenue / adobe_commerce.total_revenue | The channels generating buyers faster than SAP can master them. High new-customer velocity on a channel is where master drift accumulates. |
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.
| Reason | Direction | Why |
|---|---|---|
| Single-key vs multi-key search | Card lower | The card tries every configured key; a manual search on one key finds fewer matches and overstates absence. |
| Customer role vs other roles | Card higher | The card requires the customer role; a name search that ignores role can find a vendor or contact record and wrongly conclude the customer exists. |
| Partial Company Code setup | Card higher | A partner with the customer role but no Company Code / sales-area data cannot be billed; a name search finds it but it is functionally absent. |
| Guest-order policy | Either | Depending on whether guest orders are expected to master, the card may include or exclude them per configuration. |
| Identity-map mismatch | Card higher | A real partner whose keys disagree with the storefront looks absent until the map is fixed. |
| Poll timing | Small | A Business Partner created between two polls appears at the next cycle, so a just-created record can briefly still show as absent. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
| shopify.total_revenue | Every paying Shopify customer should resolve to a SAP Business Partner | High DTC velocity and guest checkout produce buyers faster than auto-creation can master them; email-only identity makes B2B matches fragile. |
| bigcommerce.total_revenue | Every B2B buyer should be pre-mastered before ordering | B2B portals often let a buyer self-register and order before SAP onboarding completes, so the order arrives before the Business Partner exists. |
| adobe_commerce.total_revenue | As BigCommerce | Adobe Commerce B2B company accounts have parent and child buyers; a child buyer may have no Business Partner of their own even when the parent is mastered, splitting orders away from the correct AR account. |