# SAP Credit Management Checklist: Setup, Credit Checks and Release > Source: https://netray.co/tools/sap-credit-management-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A checklist for setting up and reviewing SAP credit management in SD, from credit control area to blocked-order release. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP SD consultant - SAP FI consultant - Credit controller ## Tool **Kind:** checklist **Scoring Note:** Items marked critical should be settled before go-live. A system that passes all critical items has a working base, the rest tighten control. **Groups:** #### Organization and master data **Items:** **Text:** Credit control area defined (OB45) and currency chosen **Critical:** true **Text:** Company codes assigned to the credit control area **Critical:** true **Text:** Credit control area for each sales area determined, by default or by rule **Critical:** true Risk categories defined (OB01) with agreed business meaning Credit groups defined for document and delivery types **Text:** Customer credit data loaded in FD32 or the credit segment **Critical:** true Credit limit review process owner named Customer hierarchy and credit limit rules agreed for group accounts #### Credit check rules **Items:** **Text:** Automatic credit control entries maintained (OVA8) per control area, risk category and credit group **Critical:** true **Text:** Check types chosen: static, dynamic, open order horizon, maximum document value **Critical:** true Open item and oldest item checks agreed with finance Next review date and payment history checks considered **Text:** Action when a check fails chosen: warning, error or status set **Critical:** true Credit relevant item categories confirmed **Text:** Credit check at order and at delivery separated by design **Critical:** true **Text:** Credit groups assigned to sales document types and delivery types **Critical:** true #### Release and processing **Items:** **Text:** Blocked documents list (VKM1) and released list (VKM3) tested **Critical:** true **Text:** Release authorization defined and segregated from order entry **Critical:** true Behavior of released orders after changes agreed (reset credit status) Credit status field visible in order, delivery and billing flows Email or workflow notification to credit controllers set up Process for a customer who pays after a block documented Goods issue behavior for credit blocked deliveries tested #### S/4HANA and reporting **Items:** **Text:** Decision recorded: classic SD credit management or SAP Credit Management (FSCM) **Critical:** true Business partner credit profile maintained (UKM_BP) where FSCM is used **Text:** Credit exposure and open order values checked against FI balances **Critical:** true Credit master data replication tested for interfaces Exception report for orders released above limit created Periodic review of risk category and limits scheduled **Text:** Test cases cover limit exceeded, overdue items and new customers **Critical:** true Cut-over plan covers credit exposure for open orders at go-live ## Content **Intro:** Credit management stops orders and deliveries to customers who are over their credit limit or overdue. Done well it protects cash flow without slowing every sale. This checklist walks through the setup in the order that normally works. **Sections:** #### How to use the checklist **Body:** Work through the four groups in order: organization and master data, check rules, release process and reporting. Tick each item as you confirm it in the system, and note any gaps. Items marked critical are the ones that most often cause live problems. Export the completed list as PDF to attach to a design review or a go-live readiness pack. **Bullets:** - Use it in design workshops with finance - Run it again before every major release - Use it for audit evidence of control design - Keep one copy per credit control area #### How classic SD credit checks work **Body:** In classic SD credit management, the credit control area groups company codes and sets the currency. For each combination of control area, risk category and credit group, the entries in OVA8 specify what to check, such as static limit, dynamic limit with open orders over a horizon, the maximum document value and overdue open items. The credit group is attached to the sales document type in OVAK and the delivery type in OVAD, so the same customer can be checked differently at order and delivery. **Bullets:** - Static check: open orders, deliveries and billing against the limit - Dynamic check: open orders within a time horizon - Document value check: single document limit - Open items check: overdue receivables from FI #### Reading the status **Body:** When a check fails, SAP sets a credit status on the document and may block delivery. Credit controllers use VKM1 to see blocked documents and release, reject or correct them. After release, a later change to the order can reset the status if values change, so test change scenarios. In FSCM credit management, credit exposure, scoring and cases move to the business partner and the UKM transactions, with a different data model. #### Common mistakes **Body:** Frequent mistakes include running checks at order and delivery with the same settings and annoying users twice, forgetting to assign a credit group to new Z document types, and loading credit limits without a clear risk category policy. Another one is giving the same users order entry and release rights. Also test large group customers, where one limit covers many accounts and exposure must be summed correctly. **Cta:** If credit controllers spend their day exporting blocked orders to spreadsheets, we can build a read-only SAP agent that shows blocked documents and exposure in one place, with release left in SAP. **Faq:** #### What is a credit control area in SAP? **Answer:** It is an organizational unit that holds credit limits and exposure for one or more company codes. It carries the currency used for credit values and is defined in OB45. Every customer credit segment belongs to exactly one credit control area. #### What does OVA8 do? **Answer:** OVA8 maintains the automatic credit control rules. Each entry defines which checks run for a credit control area, risk category and credit group, and what happens when a check fails, for example a warning, an error message or a status block. #### How do I release a credit blocked order? **Answer:** Use VKM1 to list blocked sales documents, select the document and release it. VKM3 shows the already released list and VKM4 covers all documents for a customer. Release needs the proper authorization, which should be separated from order entry. #### Do I need FSCM Credit Management? **Answer:** Not always. Classic SD credit management is enough for many mid-sized companies with simple rules. FSCM suits groups that need scoring, central exposure across systems and case handling. Check your S/4HANA release for what is supported and recommended. ## Search terms sap credit management checklist, sap credit control area OB45, OVA8 automatic credit control, sap credit check configuration, FD32 credit limit, VKM1 blocked sd documents, sap credit management setup steps, sap sd credit block release --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json