SAP GL Account Master Automation: Create and Maintain GL Accounts from Excel

Lay out and open your sheet

Put each account on a row under headers such as Account Number, Account Group, Type, Description, Field Status Group, Currency, and Tax Category. Open the workbook and bring up the PostNow task pane beside it.

Record the FS00 transaction

Because the account spans two segments on one screen, you capture the transaction once. Start a recording, run a single FS00 creation, and PostNow follows what you do:

• It captures the type and description on the chart of accounts segment
• It records the control, create, bank, and interest tabs of the company code segment
• One capture is enough; the recording then drives every account in the sheet

Save it and PostNow makes it a reusable template, so opening accounts from Excel to SAP never again means working through FS00 yourself.

Look over the recorded screens and fields

PostNow shows the recording as the segments it stepped through and the fields it will set on each. Because it follows the real FS00 layout, a quick read shows what is captured where:

That overview shows, before any mapping, which column belongs to which segment of the account.

Open the Mapping Designer

Selecting the recording fills the Mapping Designer with one line per captured field. Two points apply to accounts:

• Added fields are detected. Extra fields your account group exposes on the recorded tabs are picked up, ready to map.
• You can add more manually. Any field the recording did not reach you place yourself, keeping the full account in one load.

Auto Map and stamp the headers

Set the mapping with Auto Map. Each recorded field is bound to its column and SAP-tagged headers are written into the sheet, so the workbook becomes the template and stays aligned with the recording across both segments.

Set formatting and update flags

Each field's properties govern how its value is typed into the screen: leading zeros on the account number, upper case on codes, trimmed spaces, defaults, and regex. With these set, the replay enters exactly what each segment expects.

When the recording is a change rather than a creation, you flag only the fields the replay should overwrite, so a mass GL account update touches just the controls you intend and leaves the rest of the account untouched.

Check the data in Excel first

Checking before the replay is time well spent: a field-status or account-group error tends to halt the screen mid-run. Validate brings that check forward, testing each row against SAP's length, format, and required-field rules and marking the problem cells, so the sheet is clean before the recording runs.

Confirm against live SAP

Neat formatting still will not prove a value exists, a field status group or tax category can read fine and be missing. To test it, open the field's properties, switch on field validation, and name the check table and field, a field status group against its definition, a company code against T001, or the account group against its setup. Select the cell, run Validate master data, and PostNow checks live SAP for the value.

Shape the load with loops and conditions

When the file needs more than a straight replay, set it up first:

• Loops: the recording steps down your rows, creating one account after another from the same captured flow.
• IF conditions: run only the rows that qualify, for instance setting the open-item fields only on balance-sheet accounts, or skipping rows still missing an account group.

Publish and roll it out to the team

Once the run comes back clean, publish the script. The recording and mapping become something colleagues run unchanged, they open it, paste their accounts, and post, with nothing to rebuild and no need to understand the transaction behind it. One setup becomes the finance team's standard way to load GL accounts.