Credit Management: Credit Check, Blocked Sales Order and Release
A new order pushes the customer's credit exposure over its limit. The automatic credit check blocks the order, so no delivery can be created until a credit manager reviews and releases it — in ECC with VKM1, in S/4HANA through a documented credit decision.
Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.
Digital twin
01A new order arrives
Order 10000170: 50 EA for ₹1,00,000. The credit check runs when the order is saved.
Business scenario
Demo Retail Pvt. Ltd. has a credit limit of ₹5,00,000. It already owes ₹3,50,000 and has ₹70,000 of open orders. A new order for ₹1,00,000 arrives.
All companies, numbers and documents are fictional demo data.
Step-by-step flow
- 01
A new order arrives open in twin
Order 10000170: 50 EA for ₹1,00,000. The credit check runs when the order is saved.
Credit risk is checked before goods leave, not after the invoice is unpaid.
- 02
Exposure exceeds the limit open in twin
Exposure ₹4,20,000 + new order ₹1,00,000 = ₹5,20,000 > limit ₹5,00,000. The order is blocked.
The order would take the customer over the limit set by credit management.
- 03
Shipping wants to deliver open in twin
The customer is calling about the goods. What happens next?
Separation of duties: sales should not be able to override credit decisions.
- 04
Delivery refused open in twin
VL01N refuses: the order is blocked for delivery by credit management. The order does not appear in the delivery due list either.
That is the point of the check — goods cannot leave until credit is cleared.
- 05
Credit manager releases the order open in twin
The credit manager sees a long, reliable payment history and releases the order (VKM1 in ECC; a documented credit decision in S/4HANA).
Alternatives would be asking for prepayment, or raising the credit limit — both business decisions, not system workarounds.
- 06
Delivery can now be created open in twin
Shipping creates delivery 80000600. From here the flow is standard order to cash.
The credit check can be repeated at delivery or goods issue if configured.
- 07
Credit check complete open in twin
Order blocked by the credit check, released by credit management, then delivered.
Auditors look for exactly this trail.
SAP documents
Stock impact
This part of the process does not change stock.
Accounting impact
No accounting impact in the steps shown.
Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.
Movement type
This flow spans several documents rather than a single movement type.
Limits the risk of selling to customers who may not pay, by checking credit exposure at order (and optionally delivery) and requiring an authorised release when limits are exceeded.
Transactions & Fiori apps
- VA01 — Create Sales Order (credit check)
- VKM1 — Blocked SD Documents (ECC)
- UKM_BP — Credit Management Business Partner (S/4HANA)
- VL01N — Create Delivery
- Manage Documented Credit DecisionsS/4HANA credit management; availability depends on scope
- Manage Credit Accounts
Differences by SAP version
Classic credit management: FD32 limits, OVA8 checks, VKM1/VKM3 release.
SAP Credit Management: UKM_BP, credit segments, documented credit decisions.
Credit management through Fiori apps; configuration via self-service configuration.
Configuration
ECC credit management (FD32, OVA8)
Configuration dependentCredit control area, risk categories and automatic credit checks (static / dynamic).
S/4HANA credit management (FIN-FSCM-CR)
TypicalReplaces classic credit management: credit segments, scoring, credit rules and documented credit decisions.
Checking points
Configuration dependentWhether the check runs at order, delivery and/or goods issue.
Prerequisites
- Credit account / credit segment for the customer with a limit
- Credit check assigned to the document type (credit group) and risk category
Master data
- Business partner credit data
- Limit, risk class, credit segment.
Organizational structure
- Sales area 1000/10/00
- Credit segment / credit control area (demo)
Tables
| Table | Description |
|---|---|
| VBUK / VBAK | Credit status of the order (VBUK fields moved into VBAK in S/4HANA) |
| UKMBP_CMS_SGM | Credit segment data per business partner (S/4HANA) — requires configuration validation |
Integration
- FIOpen receivables are part of the credit exposure; S/4HANA credit management is an FI-based component.
Common errors
“Order blocked although the customer has paid”
Likely causes: Exposure not yet updated; Oldest open item too old (dynamic check); Risk category very strict
Where to look: Credit exposure display · Credit check configuration
“No credit check happens”
Likely causes: Document type has no credit group; Customer has no credit account
Where to look: OVAK / credit group · Business partner credit data
Troubleshooting
Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.
CHECK 1
Blocked order
- Is the exposure over the limit?
- Who is authorised to release?
- Did a later change trigger a new block?
Interview questions
What does a credit block on a sales order prevent?
Delivery creation (and, if configured, goods issue). The order itself is saved, but it stays out of the delivery due list until released by credit management.
How did credit management change in S/4HANA?
Classic SD credit management (FD32, credit control areas, VKM1) is replaced by SAP Credit Management (FIN-FSCM-CR): credit segments on the business partner, scoring and rules, and documented credit decisions for releasing blocked documents.
Quiz
References
- SAP SE — SAP Help Portal: SAP Credit Management (source)
- SAP SE — SAP Help Portal: Credit Checks in Sales Documents (source)
Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.
Version history
| Version | Change |
|---|---|
| 1.0.0 | Initial version. |