Step 02-01: Why do we copy the Chart of Accounts?

This page explains why we copy the Chart of Accounts for anyone building a clean and reliable S/4HANA prototype. In short, copying the CoA gives you a stable financial backbone that is yours alone instead of shared with strangers. It matters because every posting in the system depends on a predictable and controlled account structure. Use it when you want fast, safe financial posting in a rented or shared sandbox and avoid it only if you already operate with a protected and fully governed CoA.

</aside>

Why this decision matters long before the first posting

Every SAP system has one quiet, immovable truth: if your Chart of Accounts doesn’t exist, nothing moves. No postings. No goods movements. No trial balance. Not even the dignity of a failed simulation run.

But when you're building a prototype, you are not trying to validate the metaphysics of financial classifications. You’re trying to answer a simpler question:

Does the system breathe? Does it post? Can we run the scenario?

This is why copying a standard COA (like SAP’s INT) isn’t laziness. It’s strategic acceleration. The INT chart is universal, widely used in examples online, and perfectly adequate for a prototype whose purpose is to reveal integration behaviour — not design IFRS-compliant ledger structures.

Copying a COA is the cleanest way to avoid derailing a prototype with debates about account numbering philosophy.

Jargon Busting (WHAT this actually is)

A Chart of Accounts (COA) is the directory of all general ledger accounts. Think of it as the financial filing cabinet that tells SAP where every posting belongs.

It’s defined at client level and then assigned to each company code.

A Financial Statement Version (FSV) sits on top of it — the reporting skeleton that turns accounts into balance sheets and P&L statements.

The INT COA is SAP’s “international” baseline. Neutral. Generic. Boring — in exactly the way you want your prototype to be.

WHEN copying the COA becomes the only sane option

When you’re building a prototype to validate cross-module behaviour, time is your scarcest resource.

When the goal is “show me the posting flow,” not “design my future finance governance,”

→ copying INT gives you instant coverage of every scenario you need to test (sales, purchases, adjustments, inventory, material movements).

When you need to teach the system how to behave (not how to win an audit),