The quick answer
The error "Posting period ... is not open" means the posting date on your document falls in a period that isn't open for that account type. SAP controls which periods accept postings through the posting period variant, maintained in transaction OB52. The fix is to open the correct period range in OB52 for the relevant account type — and make sure the variant is actually assigned to your company code.
Key takeaways
- SAP only accepts postings in open periods — controlled by the posting period variant.
- Open/close periods in OB52, per account type (+, A, D, K, M, S).
- Start with account type
+— it applies to all types. - If nothing changes, the variant may not be assigned to the company code.
What the error means
To keep the books controlled, SAP only lets you post into periods that are deliberately open. Once a month or year is closed, postings to it are blocked so figures can't change after reporting. When your document's posting date lands in a closed period, you get this message.
It's not a bug — it's period control doing its job. The fix is either to post with a date in an open period, or (if you legitimately need that period open) to open it in OB52.
How period control works
One chain explains it — and points you straight at the fix:
The posting period variant is assigned to your company code. Inside it, OB52 holds an open interval (a From/To period + year) for each account type. Your posting is allowed only if its date sits inside the open interval for the account type involved.
| Indicator | Applies to |
|---|---|
+ | Valid for all account types (set this first — it's the master switch) |
A | Assets |
D | Customers (Accounts Receivable) |
K | Vendors (Accounts Payable) |
M | Materials |
S | G/L accounts |
Why it happens
Month-end or year-end closed the period and it hasn't been reopened. The most common cause.
You opened + or S but the posting involves a vendor (K) or customer (D) whose range is still closed. The account type in the error tells you which one.
You edited a variant, but your company code isn't linked to it — so your changes have no effect. Check the assignment (transaction OBBP).
For goods movements, the material period is controlled by MMPV, not OB52. A "posting only possible in periods" message on a goods movement points to the MM period close, a different transaction.
How to fix it, step by step
Read the error — note the period and account type
The message gives the period and year (e.g. 004 2026) and often the account type. Note both.
Open transaction OB52
Type OB52. You'll see the open period intervals, listed by posting period variant and account type.
Find your posting period variant
Locate the rows for the variant assigned to your company code. (Unsure which variant? Check the assignment in OBBP.)
Open the period range
For the relevant account type (start with +), set the From period / year and To period / year in interval 1 so they include your posting date. Save.
Check interval 2 & special periods if needed
Interval 2 (often for period-end or restricted to an authorization group) and special periods 13–16 (year-end) may also need opening for closing postings.
Retry — or, for a goods movement, check MMPV
Repeat the posting. If it's a goods movement still blocked, the material period needs rolling in MMPV — that's the MM period close, separate from OB52.
Why SAP Shows 'Posting Period Not Open'
The error message 'Posting period XXX/XXXX is not open for account type X in company code XXXX' appears when you try to post a financial document — an invoice, a payment, a journal entry, or a goods movement with financial impact — and the system determines that the accounting period your document falls in has not been opened.
SAP controls posting periods to prevent users from accidentally posting into a previous period after month-end closing is complete, and to prevent backdated postings that would alter already-reported financial statements. This is a deliberate control, not a malfunction.
Step-by-Step Resolution
Step 1: Note the exact error message
The error message tells you: the period (e.g. 007/2026), the account type (A=assets, D=customers, K=vendors, M=materials, S=GL accounts, V=contract), and the company code. Write these down — they tell you exactly what to check in OB52.
Step 2: Go to OB52
Transaction OB52 (Open and Close Posting Periods) shows the posting period variant assigned to the company code. It displays which periods are currently open for each account type. This is where 99% of posting period errors are resolved.
Step 3: Check the current period settings
In OB52, locate the row for your company code's posting period variant and the relevant account type. You will see fields for From Period 1, To Period 1 (the primary open range) and From Period 2, To Period 2 (a secondary range, often used for the previous month during transition). Verify that the current period falls within one of these ranges.
Step 4: Open the required period
If authorised, you can update the period range directly in OB52 to include the period required. In most organisations, opening or closing periods requires authorisation — the system will stop you if you do not have the S_ALR_87003642 authorisation object. If you do not have this authorisation, escalate to the SAP FICO consultant or BASIS administrator who does.
Step 5: Consider the document date vs posting date
Users sometimes confuse the document date (the date on the invoice or journal) with the posting date (the SAP accounting period the document will post into). If you need to post an invoice dated last month into the current open period, change the posting date — not the document date. The posting period is determined by the posting date, not the document date.
The fastest resolution for end-users: Contact your SAP support team or FICO consultant and provide the exact error message including the period, account type, and company code. They will either open the period or advise you to change your posting date. Do not attempt to change the document date to avoid the error — this creates data integrity issues.
How to Prevent Recurring Posting Period Errors
Most recurring posting period errors are caused by process gaps rather than configuration issues:
- Maintain a period-open/close calendar: Document which person is responsible for opening periods, when periods are opened (typically the last business day of the prior month), and when periods are closed (typically 3-5 business days after month-end). Distribute this calendar to all finance users.
- Open two periods simultaneously during month transition: In OB52, configure Period 1 as the current month and Period 2 as the prior month. This gives you a window to process late-arriving documents from the prior period without error, then close the prior period once confirmed.
- Separate document date from posting date in user training: Train users to understand that the document date is informational (the date on the supplier invoice) and the posting date determines the accounting period. Most period errors occur because users do not know they can change the posting date.
- Restrict OB52 access: Only authorised users (typically the FICO team lead and one or two approvers) should be able to open or close periods. Unrestricted OB52 access leads to periods being accidentally opened or left open.
For year-end specifically: open period 13 (or your first special period) only during the year-end closing process, and close it immediately once year-end entries are complete. Leaving special periods open after year-end can lead to unintended postings in a closed fiscal year.
FAQ
The error 'Posting period XXX/XXXX is not open for account type X in company code XXXX' means that the accounting period your document is trying to post into has not been opened in SAP's period control configuration. SAP controls which periods are open to prevent accidental backdated postings and to enforce month-end and year-end closing discipline.
Go to transaction OB52 (Open and Close Posting Periods). Locate the posting period variant for your company code. Check that the current period is within the open period range for the relevant account type. If the period needs to be opened and you have authorisation, update it directly. If not, contact your SAP FICO consultant or system administrator who has the OB52 authorisation.
OB52 is the SAP transaction for managing posting periods — controlling which fiscal periods are open for financial postings in each company code. It shows the open period range for each account type (A=assets, D=customers, K=vendors, M=materials, S=GL, V=contract) and allows authorised users to open or close periods. OB52 is the primary resolution point for posting period errors.
Account types in SAP period control are single-letter codes that identify the type of account being posted to: A (Asset accounts), D (Customer/Debtor accounts), K (Vendor/Creditor accounts), M (Material accounts), S (GL/Balance sheet accounts), V (Contract accounts). The + symbol covers all account types simultaneously. A posting period error will specify which account type is blocked — check that specific account type in OB52.
The document date is informational — it is the date printed on the invoice or journal (the date the business event occurred). The posting date determines which accounting period the document posts into. If you receive an invoice dated last month but want it to post in the current open period, change the posting date to today — do not change the document date. The posting period error is triggered by the posting date, not the document date.
Only if that previous period has been reopened in OB52. Once a period is closed (removed from the open period range in OB52), no further postings can be made to it without an authorised user reopening it. Many organisations have strict policies about reopening prior periods — it requires finance management approval because it affects already-reported financial statements.
Special periods (periods 13, 14, 15, 16 in a standard 12-month fiscal year) are additional accounting periods used during year-end closing. They allow year-end adjustments, auditor entries, and closing entries to be separated from regular month-end transactions. Special periods are only opened during the year-end process and should be closed immediately once all year-end entries are complete.
A fiscal year variant is the configuration object that defines a company's financial year — when it starts and ends, and how periods are numbered. A company with a January-December year uses a different fiscal year variant than one with an April-March year. The fiscal year variant is assigned to each company code and determines how posting dates map to period numbers. Incorrect fiscal year variant assignment is a less common but possible cause of posting period errors.
A posting period variant is a grouping object that links multiple company codes to the same period control settings in OB52. Instead of configuring periods separately for each company code, you can assign multiple company codes to the same variant and manage their period openings centrally. Large organisations with many company codes use posting period variants to simplify period management.
Typically the SAP FICO team lead, finance manager, or a designated controller with OB52 authorisation. Many organisations restrict OB52 access to 2-3 people maximum. The period-open responsibility is usually documented in a month-end checklist and the person responsible receives a reminder from the finance calendar. End-users who encounter a posting period error should contact this person.
If an active posting period is accidentally closed in OB52, all subsequent postings with dates in that period will fail with the posting period not open error. The fix is straightforward — reopen the period in OB52. However, any transactions that failed during the closed period may need to be reposted once the period is reopened. This is why OB52 access should be restricted to authorised users only.
Yes — goods movements in SAP MM (posted via MIGO) create financial documents in SAP FICO. If the FICO posting period is closed, MIGO will also fail with a posting period error on the financial document, even though the MM material document posts successfully. This causes a split — a material document exists but no accounting document — which must be resolved by reopening the period and reposting the accounting document.
A typical SAP FICO month-end sequence: (1) Post all accruals and recurring entries; (2) Run depreciation (AFAB); (3) Run payment runs and clear open items; (4) Perform bank reconciliation; (5) Run CO allocations and assessments; (6) Generate and review financial statements; (7) Get sign-off from finance management; (8) Close the period in OB52. The posting period is closed only after step 8 — never before financial statements are approved.
Yes — they are different errors with different causes and fixes. The posting period error relates to time control (which fiscal periods are open). Account determination errors relate to configuration (which GL accounts SAP should post to for a given transaction type). Both are common FICO errors, but they are diagnosed and resolved in completely different places.
VoiSAP SAP FICO training covers all common FICO errors — including posting period management, account determination, tolerance group configuration, and period-end closing — with hands-on practice on a real SAP S/4HANA system. Contact: voisap.com, +1-416-569-4606, contact@voisap.com.