Financial control

<aside> <img src="notion://custom_emoji/7f3a86c4-0e4f-8193-9274-00038d571f22/294a86c4-0e4f-8053-a481-007af138f2db" alt="notion://custom_emoji/7f3a86c4-0e4f-8193-9274-00038d571f22/294a86c4-0e4f-8053-a481-007af138f2db" width="40px" />

This page explains Phase 3 for SAP beginners, functional consultants, and anyone learning how SAP keeps materials and money aligned. In short, Phase 3 shows how SAP uses tolerances, controls, posting periods, number ranges, and limits to prevent mistakes before they happen. It matters because materials management is tightly tied to finance, and small configuration gaps create large operational failures. Use it when preparing a company code for real transactions, and avoid skipping these steps unless you want discrepancies, blocked postings, or audit issues later.

</aside>

Phase 03: Jargon Busting

Step 03-01: Why do you need to create a Company Code before anything else?

Step 03-02: Why maintain Company Code settings before any financial transactions?

Step 03-03: Why it makes sense to think about currencies?

Step 03-04: Why you need to add company code data to the chart of accounts?

Step 03-05: Why price changes from the past can ruin today's margins?

Step 03-06: Why tolerances decide whether your invoices behave or riot?

Step 03-07: Why vendor tolerances stop your invoices from wandering off?

Step 03-08: Why default tax codes stop your invoices from lying?

Step 03-09: Why duplicate invoice control protects you from paying twice?

Step 03-10: Why price variance tolerances keep your procurement honest?

Step 03-11: Why outgoing payment tolerances stop your finance team drowning in noise?

Step 03-12: Why tolerance groups stop your people from spending money they shouldn’t?

Step 03-13: Why assigning tolerance groups keeps financial authority in the right hands?

Step 03-14: Why materials management needs its own company code settings?

Step 03-15: Why accounting documents need their own number ranges?


The Principle