F5 266 — F5 266 — Enter a Name and City for One-Time Account Postings

One-time accounts are shared customer or vendor master records used for occasional business partners. Because the master record does not identify the individual partner for every transaction, SAP stores the actual partner name and address with the document. F5 266 is raised when required transaction-specific one-time account data—particularly name and city—is missing. SAP support documents this in S/4HANA migration of AP/AR open items and similar FI posting scenarios.

A migration file may identify a one-time account but omit the corresponding one-time account detail structure. An interface can post to a CPD account while sending only customer/vendor number and amount. Mapping may populate street or country but leave name or city empty. A source system may not distinguish normal accounts from one-time accounts, so it does not know extra partner data is required. Custom BAPI code sometimes fills standard customer or vendor line structures but forgets the dedicated one-time account data structure.

Confirm that the customer or vendor master is configured as a one-time account. Inspect the source document or migration record and locate the transaction-specific name, city, country and other required partner fields. In migration cockpit, review the object template and error details for the affected open item. In BAPI or interface scenarios, inspect the relevant one-time account structure and its line-item reference. Verify that the correct customer/vendor line is linked to the address data. Compare a successful one-time posting with the failing payload.

Populate the required one-time partner details at the document level and repost or reload the migration record. Correct source-to-target mapping so every one-time item carries the partner identity required by SAP. If the account should not actually be a one-time account, use the proper regular customer/vendor or business partner instead of inventing address data. For recurring migration errors, add validation before submission so records missing name or city are rejected in staging rather than failing deep in the accounting interface.

Maintaining a generic name and city on the shared one-time master record defeats the purpose of transaction-specific partner identification and can produce misleading accounting documents. Another bad workaround is switching the posting to a normal account that does not represent the real partner. The document must either use the correct regular business partner or carry the actual one-time partner details with the posting.

FI-AR and FI-AP own the one-time account design. Migration or integration teams own the transaction-specific data mapping. Master-data teams should confirm whether the account is intentionally CPD or one-time. ABAP teams are involved when custom BAPI code fails to populate the required structure. For migration, the source-data owner should supply the real partner name and address rather than asking the SAP team to generate placeholders.

Do not assume that because the one-time customer or vendor master exists, the transaction needs no extra partner data. Validate city as well as name. Check line-item references in interfaces so one address is not attached to the wrong payable or receivable line. During migration, distinguish one-time account records before transformation. After posting, verify that the actual partner name appears correctly in document display and reporting.

For recurring one-time account postings, the clean design is to identify CPD records before they reach FI and require the transaction-specific partner fields in the source contract or migration template. This avoids late accounting failures and preserves an auditable link between the shared one-time master account and the actual legal or commercial counterparty on each document. In migration rehearsals, include explicit completeness checks for name, city, country and line-item linkage so the error is found during staging rather than during final load.