M7055 – G/L Account Does Not Exist in Company Code – How to Fix It in SAP

July 10, 2026 admin

Fix the M7055 error by extending the missing G/L account to your company code. When posting a goods movement, SAP automatically determines the G/L account through account determination, but the transaction is blocked if the account hasn’t been extended. This prevents incorrect postings and ensures financial accuracy. You must maintain the account in the correct company code using FS00 or through automatic account creation.

Key Takeaways:

SAP blocks goods movements when the required G/L account isn’t extended to the company code, because account determination can’t find a valid posting account.
The error often appears with standard accounts like inventory (13600000) or initial stock balance, which may exist in one company code but not in a newly created one.
Use transaction FS00 with the “Create with Reference” option to copy the G/L account settings from a company code where it’s already active, enabling postings to proceed.

Factors Triggering the M7055 Validation Error

The M7055 error occurs when SAP’s automatic account determination selects a G/L account not extended to the company code where the transaction is posted. Common triggers include incomplete account master data setup and incorrect valuation grouping configurations. Any missing extension prevents posting and displays the message “SAP message M7055 G/L account & does not exist in compa.”

SAP Account Determination Logic

You rely on SAP’s account determination to automatically assign the correct G/L account during transactions. This logic uses condition techniques based on movement types, valuation classes, and transaction keys. When the system finds an account not extended to your company code, it triggers M7055 to block the entry and maintain data integrity.

Company Code Level Data Segregation

Each company code in SAP maintains its own set of extended G/L accounts to ensure financial separation. You must explicitly extend a G/L account to a company code before use. Any attempt to post to a non-extended account results in the M7055 validation error, enforcing strict data boundaries.

Company code level data segregation ensures that financial records remain isolated and compliant across legal entities. You define which G/L accounts are active per company code through the extend G/L account function (transaction FS00). This prevents unauthorized postings and maintains accurate, auditable financial statements specific to each organization unit.

Identification of Commonly Missing G/L Accounts

When setting up a new company code, you may encounter missing G/L accounts that block key processes. The most frequent gaps include the inventory account 13600000 and the initial stock balance account. These omissions can halt inventory postings and material ledger activities, triggering error M7055. Ensuring these accounts exist and are correctly configured prevents costly delays in go-live or month-end closing.

Inventory Account 13600000

You must assign inventory account 13600000 to your company code to record stock values for materials. Without it, goods receipts fail and error M7055 appears during transaction processing. This account is imperative for valuating inventory movements and maintaining accurate financial reporting in SAP MM and FI integration.

Initial Stock Balance Accounts

Initial stock balance accounts support the first-time entry of existing inventory into SAP. You’ll need them when migrating legacy stock data, especially during system conversions or new implementations. Missing this account disrupts initial postings and triggers M7055 errors.

Setting up the initial stock balance account allows you to post opening balances for materials with a prior valuation. This account works in tandem with movement type 561 and is critical during data migration. If omitted, you cannot load historical stock, which compromises reporting accuracy and audit readiness from day one.

How-to Resolve the Missing Account Error in SAP

To fix the M7055 error, use transaction FS00 with the Create with Reference option. This method copies account settings from a working company code, ensuring consistency and preventing configuration mismatches. You avoid manual entry errors by replicating proven configurations, making it the fastest, most reliable solution for missing G/L accounts.

Utilizing Transaction FS00

You access FS00 to manage G/L account master data across company codes. When the error appears, enter the missing account number and select “Create with Reference.” Choose a company code where the account already works correctly to ensure accurate field-level replication, including currency, tax settings, and reconciliation flags.

Applying the Create with Reference Methodology

Start by identifying a company code where the G/L account functions properly. In FS00, use the reference option to mirror its configuration into the affected company code. This eliminates discrepancies in account group, field status, and posting permissions, resolving the M7055 error in minutes with minimal risk.

Using Create with Reference in FS00 ensures all technical attributes-like account currency, consolidation treatment, and line item display-are copied exactly. You maintain compliance and avoid hard-to-trace posting issues that arise from manual setup. Always verify the reference account’s settings before copying, as errors in the source will propagate to the target company code.

Tips for Efficient Account Extension Across Company Codes

Use a working company code as your template to replicate G/L account configurations accurately in new entities. This method ensures consistency and reduces configuration errors. Include all relevant account assignments and field statuses from the source. After referencing a proven setup, extend the account with confidence. For details on resolving “Account does not exist in the company code“, consult SAP’s official guide.

Identifying Reliable Reference Templates

Select a company code already using the G/L account successfully as your blueprint. Confirm it has complete master data, correct field status settings, and active integration with modules like MM or SD. A live, error-free environment ensures reliability. After verifying operational stability, use it to extend the account safely.

Validating Copied Account Parameters

Review all transferred settings including currency, tax codes, and reconciliation flags to confirm accuracy. Even minor mismatches can trigger errors like M7055. After copying, always test in a non-production system first.

Once the account is extended, drill into each parameter to ensure alignment with the source company code. Pay close attention to field status groups, account currency, and line item display settings, as discrepancies here often cause posting issues. After confirming all values match the working template, proceed with activation in the target environment.

To wrap up

With these considerations, you must extend the inventory account 13600000 using transaction FS00 to the relevant company code. This action ensures automatic account determination for goods movements functions correctly and resolves the M7055 G/L account error in SAP.

FAQ

Q: What does the error ‘M7055 – G/L Account Does Not Exist in Company Code’ mean in SAP?

A: This error appears when SAP tries to post a goods movement, such as a goods receipt or transfer, and needs to update a general ledger (G/L) account linked to the transaction. SAP uses account determination to find the correct G/L account based on movement type, valuation class, and other factors. If the required G/L account has not been extended to the company code where the posting is happening, the system cannot proceed and displays message M7055. The transaction is blocked until the missing account is created in that company code.

Q: Why does the G/L account not exist in the company code even though it’s used elsewhere?

A: G/L accounts in SAP are defined at the chart of accounts level but must be individually extended to each company code that uses them. When a new company code is set up, not all accounts are automatically available. Common accounts like inventory (e.g., 13600000) or initial stock balance accounts are often overlooked during configuration. If a goods movement triggers an account that hasn’t been extended, the system flags it with M7055 because the account data-such as tax settings, field status, or currency-is missing for that specific company code.

Q: How can I fix the M7055 error in SAP?

A: To resolve the error, use transaction FS00 (Maintain G/L Account). Open the account that is causing the issue and choose ‘Create with Reference’. Select a company code where the account already exists and works correctly. The system copies all necessary settings-like account group, field status, and tax codes-into the affected company code. After saving, the account is now active in that company code, and the blocked goods movement can be retried successfully.

Q: Which G/L accounts are most commonly missing in new company codes?

A: Inventory accounts such as 13600000 and initial stock balance accounts are frequently missing when setting up new company codes. These accounts are necessary for goods receipts, especially during stock transfers or initial inventory entries. If account determination points to one of these accounts and it hasn’t been extended to the company code, M7055 will occur. Checking these standard accounts early in the setup process prevents delays during live transactions.

Q: Can I prevent the M7055 error from happening again?

A: Yes. After identifying the missing account, extend it using FS00 with reference to a working company code. To avoid future issues, review the list of G/L accounts used in account determination (transaction OBYC) and ensure all required accounts are extended to every active company code. Running a consistency check with program RFBILA00 or using transaction FAGLL03 to display account assignments per company code helps spot gaps before they cause errors.