# SAP SD Credit Exposure Simulator > Source: https://netray.co/tools/sap-sd-credit-exposure-simulator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Add up the components of credit exposure and test whether a new sales order would exceed the credit limit. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP SD consultant - Credit manager - Order management ## Tool **Kind:** calculator **Currency:** $ **Inputs:** #### Credit limit **Key:** limit **Type:** number **Default:** 500000 **Min:** 0 **Step:** 10000 #### Open receivables (open items) **Key:** open_items **Type:** number **Default:** 180000 **Min:** 0 **Step:** 5000 #### Special liabilities **Key:** special **Type:** number **Default:** 20000 **Min:** 0 **Step:** 1000 **Help:** For example down payment requests or bills of exchange. #### Open billing value **Key:** open_billing **Type:** number **Default:** 60000 **Min:** 0 **Step:** 5000 **Help:** Billing documents not yet transferred to accounting. #### Open delivery value **Key:** open_deliv **Type:** number **Default:** 90000 **Min:** 0 **Step:** 5000 **Help:** Deliveries not yet billed. #### Open order value **Key:** open_orders **Type:** number **Default:** 120000 **Min:** 0 **Step:** 5000 **Help:** Order value not yet delivered. #### New order value **Key:** new_order **Type:** slider **Default:** 75000 **Min:** 0 **Max:** 400000 **Step:** 5000 **Outputs:** #### Current credit exposure **Key:** exposure **Expr:** open_items + special + open_billing + open_deliv + open_orders **Format:** currency **Primary:** true #### Limit utilization **Key:** util **Expr:** if(gt(limit,0), exposure / limit * 100, 0) **Format:** percent #### Headroom before new order **Key:** headroom **Expr:** limit - exposure **Format:** currency #### Exposure with new order **Key:** exposure_new **Expr:** exposure + new_order **Format:** currency #### Utilization with new order **Key:** util_new **Expr:** if(gt(limit,0), exposure_new / limit * 100, 0) **Format:** percent **Primary:** true #### Credit block triggered (1 = yes) **Key:** block **Expr:** if(gt(exposure_new, limit), 1, 0) **Format:** integer #### Largest order that passes **Key:** max_order **Expr:** max(0, limit - exposure) **Format:** currency **Chart:** #### Utilization vs new order value **Type:** line **X:** new_order **From:** 0 **To:** 400000 **Steps:** 40 **Series:** - util_new **Disclaimer:** Static model. The real check can also apply a credit horizon date, check by document type and customer-specific percentage tolerances. ## Content **Intro:** When an order lands in a credit block, the first question is how much of the limit is already used and by what. This simulator adds up the exposure components used in a static credit limit check and shows whether a new order fits. **Sections:** #### How to use it **Body:** Enter the credit limit and the five exposure components for the customer or credit control area. The values correspond to what you see in the credit master data display of the customer: open items from accounts receivable, special liabilities, open billing, open deliveries and open orders. Then set the value of the new order. The result shows the total exposure, utilization and whether a block is triggered. #### How the exposure is built **Body:** Exposure follows the document flow. An order is open until it is delivered, a delivery is open until it is billed, a billing document is open until it is posted to accounting, and posted invoices become open items until they are paid. In a static check all these amounts are summed and compared with the limit. A dynamic check restricts open orders to a horizon so far-future orders do not count yet. #### Reading the result **Body:** If the utilization with the new order is above 100 percent, the system would block the order, depending on the check configured for the document type. The largest order that passes shows how much the sales rep can still book. With the defaults the customer has 470,000 of exposure and can only take 30,000 more, so a 75,000 order triggers a block. **Bullets:** - Review open deliveries that were never billed - Look for unposted billing documents - Ask whether the limit still matches the payment behavior #### Common mistakes **Body:** Many credit blocks are caused by stale documents rather than real risk. Old deliveries with no billing, blocked billing documents and unposted billing keep counting toward the exposure. Clean these up before raising a limit. Also check that the exposure update program and the credit control area are consistent after a migration. **Cta:** We can add a read-only assistant to your SAP data that tells order management which documents drive a credit block and who owns them. **Faq:** #### Is this the same as the old credit management? **Answer:** The components are the same ideas in classic SD credit management and in the newer credit management. Some newer setups use a score and rules, so treat this as the limit-based part only. #### Why is open order value included? **Answer:** Because the company has accepted an obligation to deliver and will invoice later. Counting it protects against many large orders stacking up before any invoice exists. #### Can exposure be negative? **Answer:** Credit memos and unallocated payments can reduce open items. Enter the net open item balance here, and make sure it matches what finance sees. #### What does a tolerance do? **Answer:** Some configurations allow a percentage over the limit before blocking. If yours does, add the tolerance to the limit field. ## Search terms sap credit exposure calculation, sap credit limit check simulation, sap credit exposure components, sap static credit check, sap credit block calculator, sap fd32 credit exposure, sap credit management what if --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json