SAP functional issueObjectBilling document not released to accountingModuleSD_O2C

Billing Document Stuck Without an Accounting Document

A billing document is not released to accounting when SAP cannot generate the FI accounting document behind it, usually because account determination cannot find a G/L account, the posting period is closed, a required CO account assignment is missing, or the tax code has no account assigned. The billing document itself exists and can be printed, but no financial posting occurs until the underlying determination gap is fixed.

Covers why a saved billing document shows no accounting document, ranked by how often each cause actually occurs in live systems. Walks through the check sequence across SD account determination, FI period control, and CO account assignment, and separates data fixes from configuration changes that need a transport.

Published 16 Sept 2026· 1,109 words

The business symptom

Billing sends the invoice to the customer, or the intercompany invoice goes out, but finance says the amount never landed on the customer's account or in revenue. Someone in AR asks why a document that clearly exists in SD is not in the customer's open item list. Collections cannot dun for it. Revenue reporting for the period is short by exactly the value of that invoice. In the system the billing document shows a status line indicating it has not been passed to accounting, sometimes with a specific error text, sometimes just a blank accounting document field. The person who created the billing document usually assumes it is done because printing or output worked fine, and only finds out days later during period-end reconciliation that nothing posted.

The configuration behind it

  • Account determination incomplete: the account determination procedure attached to the billing document type finds no entry for the combination of chart of accounts, sales organization, account assignment group of the customer, account assignment group of the material, and account key. This is the single most common cause and throws an explicit 'no account found' style error.
  • FI posting period closed for the billing date. SD allows the billing document to be created and priced, but the period lock in financial accounting rejects the posting, leaving the SD document orphaned from FI.
  • Missing CO account assignment. A revenue or cost element requires a cost center, profit center, or internal order and none is derived, so controlling rejects the posting even though the G/L account itself is correctly determined.
  • Tax code determined on the item has no G/L account maintained in tax account determination, or the tax code does not exist in the company code in question, common after a new company code goes live before tax configuration is copied over.
  • Exchange rate missing for the currency pair and date when the billing currency differs from the company code currency, so FI cannot translate the amount.
  • Customer or material master account assignment group is blank, which silently breaks the key combination the account determination table expects, producing the same symptom as a missing condition record but with a different root fix.
  • Reconciliation account missing, blocked, or invalid on the customer master, which is a data issue rather than a determination table gap.
  • Number range for the accounting document type exhausted or not maintained for the fiscal year, rare but seen right after year-end if the range was not extended.

What to check

  • VF03 on the billing document, check header status and open the accounting document log to read the exact error text rather than guessing from the symptom alone
  • If account determination is implicated, run the account determination analysis from within the billing document environment menu to see which key combination was searched and what was missing
  • OB52 to confirm whether the posting period covering the billing date is open for the relevant account types
  • If the error references a cost element or CO object, check the cost element master and the default account assignment configuration, and confirm cost center or profit center master data is not blocked
  • FTXP for the tax code in the company code, and the tax account determination configuration if the tax code exists but has no account
  • OB08 for the exchange rate table if a foreign currency is involved
  • Customer master reconciliation account and account assignment group, and material master account assignment group, both usually checked via the respective master data display transaction

How to prove it in the data

Pull billing documents within the affected posting period or billing date range where the accounting document number field is blank despite the billing document existing and having a net value. Cross-reference against the account determination analysis log for those documents to isolate whether the missing key combination is the same across all of them, which points to one configuration gap rather than scattered master data issues.

Resolution path

If account determination is missing a condition record, that is a customizing table entry, not master data, and in most landscapes it moves through a transport even though it looks like a quick table maintenance change; adding it directly in production without a transport creates a landscape inconsistency that surfaces later. If the posting period is closed, opening it in OB52 is a controlled FI activity, not something SD should do unilaterally, since it affects every other document in that period. If a CO account assignment is missing, the fix is usually a default account assignment configuration change, which needs a transport and CO sign-off. If a tax code has no G/L account, that is a tax account determination configuration fix, also transported. If the cause is a blank account assignment group on a customer or material master, that is a straight data correction with no transport required. Once the underlying gap is closed, the billing document does not need to be recreated; it can usually be released to accounting directly from the same transaction that showed the error, which reprocesses the existing document against the corrected determination.

The fix people try first (and why it fails)

The reflex fix is to cancel the billing document and create a new one, assuming something went wrong with that specific document. It fails because the account determination gap, closed period, or missing CO assignment is a configuration or master data condition, not a document-specific defect, so the replacement billing document hits the identical error. A worse variant is posting the revenue manually through a general FI journal entry to make the number appear in accounting, which breaks SD-FI reconciliation permanently and leaves the original billing document still unreleased and now duplicated in the ledger.

Whose problem this is

Joint between SD and FI/CO. SD confirms which account determination procedure and key combination the billing document is using and whether master data account assignment groups are populated. FI or CO owns period control, G/L account creation, tax account assignment, and default CO account assignment. The handover note should carry the billing document number, sales organization, the exact error text from the accounting document log, and the specific key combination or period that failed.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-functional-issues/billing-document-not-released-to-accountingERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.