FBN1 — Accounting Document Number Ranges
FBN1 maintains the number ranges for accounting documents by company code and fiscal year. Each document type points to a number range, so FBN1 decides which numbers documents receive and whether numbering is internal or external. Missing intervals for a new fiscal year are a classic cause of posting errors in the first days of the year.
Maintains number range intervals for accounting documents per company code and fiscal year.
Published 31 Oct 2026· 480 words
What FBN1 is for
Accounting documents need unique, traceable numbers, often required by law to be continuous. Number ranges are defined per company code, interval and fiscal year, and document types reference them. FBN1 lets finance create, copy and check these intervals, including the current number status.
When it is used
It is used during implementation, before every new fiscal year when intervals are year-dependent, and when new company codes or document types are added. Support teams use it when a posting fails because no number range exists for the year. In India and several other countries, invoice numbering rules for GST mean billing-related ranges get extra attention from tax teams.
How it is used in practice
Select the company code and display or change intervals. Create intervals for the new year, or copy them from the previous year, matching the number range keys used by document types. Internal ranges are assigned by the system; external ranges require the number to be entered. Number ranges are usually transported carefully or maintained directly in each system, according to the project's rules.
Fields and objects that matter
- Company code and number range key
- Fiscal year of the interval, or 9999 for year-independent ranges
- From and to numbers and the current number status
- External numbering indicator
- Document types in OBA7 that reference each number range key
How to prove it in the data
Check the document type in OBA7 to see which number range key it uses, then confirm in FBN1 that an interval exists for that key and fiscal year. After posting, the document number in FB03 should fall inside the interval and the current number status should have advanced.
ECC vs S/4HANA
FBN1 remains in S/4HANA and is part of year-end preparation checklists. Document types and number ranges still drive document numbering in the Universal Journal, so the same year-end routine applies after a conversion.
Common pitfalls and how they show up
Number range problems usually appear at year end, when the first posting of the new year fails in every company code at once.
- No interval for the new fiscal year, so postings fail on the first day
- Transporting number range status and overwriting the current number in production
- Overlapping ranges for different document types, making audits harder
- Using external numbering where internal numbering is expected
- Intervals close to exhaustion that nobody monitors until postings stop
Whose problem this is
Owned by general ledger configuration and the year-end closing team. Basis or the transport team should agree how number ranges move between systems, because transporting intervals with their current status can overwrite production numbering.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
Source: ERPClimb — https://erpclimb.com/sap-tcodes/fbn1ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.