Field Bline Date Is a Required Field for G/L Account 800001: SAP Error Fix with OBB8
An invoice is ready, but SAP will not post it to accounting. The message says that the baseline date is a required field for G/L account 800001, and the billing document stays blocked. This guide explains what the message means, why it appears when a billing document is released to accounting, and how to fix it by maintaining the baseline date calculation of the terms of payment in OBB8. It also shows how to check the result, what to do if the message remains, and how to prevent it. If you run into any errors while following along, feel free to send a screenshot to pramod@learntosap.com for help.
📑 What You Will Learn in This Guide
❌ The Error Message at a Glance
| Item | Value in This Example |
|---|---|
| Error message | Field bline date is a required field for GL account 800001 |
| Field named | Baseline date (written BLINE in the message) |
| G/L account | 800001 |
| Where it appears | When a document is posted to accounting, typically when a billing document is released to accounting |
| Why it appears | The baseline date is required, and SAP could not determine one |
| Fix used in this guide | Maintain the terms of payment 0013 in OBB8 |
The account number and payment terms in your message may differ from this example. The same steps apply with your own values.
✅ What Does "Bline Date Is a Required Field for GL Account 800001" Mean?
The baseline date is the starting point of payment terms. SAP adds the number of days defined in the terms of payment to the baseline date and arrives at the net due date and the cash discount dates. Without a baseline date, the system cannot say when a payment is due. That is why, for some accounts, SAP treats the field as a required entry and stops the posting when it is empty.
The message does not say that the account is wrong or that the document is badly made. It says that one required piece of information is missing at the moment of posting. The question to ask is therefore not "what is wrong with account 800001", but "why did SAP not fill the baseline date by itself?" In most SD cases the answer lies in the terms of payment, which is exactly where the solution in this guide works.
The same message can also be caused by the field status of the G/L account, which makes the field required for every posting. That cause has a different fix and is explained in the guide Baseline Date Required for G/L Account 1213 500061. Read both pages if the steps below do not remove your error.
📋 Where You Meet This Error in SD
This page sits in the SD error series because the message typically appears during billing. When you create an invoice with VF01, SAP creates the billing document and then passes it to accounting, where it becomes an accounting document with a customer line and revenue lines. If any line needs a baseline date and none can be determined, the transfer to accounting fails.
- Creating an invoice with VF01 that posts to accounting automatically.
- Releasing a billing document that was blocked for accounting.
- Posting a credit memo or debit memo that creates an accounting document.
- Posting a manual accounting document to the same account.
When the transfer fails, the billing document usually stays saved but is blocked for accounting. You can correct the cause and release it again, so nothing needs to be typed twice. A related guide, Document saved (no accounting document generated), describes what you see in that situation.
📝 How SAP Determines the Baseline Date from the Payment Terms
When a billing document is posted, SAP copies the payment terms key from the billing document, which came from the customer master or the sales order, and reads the definition of that key. The definition contains the rules for the baseline date. The table lists the main settings that you meet in OBB8.
| Setting | Where | What It Does |
|---|---|---|
| Terms of payment key | Billing document header | Selects the rule set, for example 0013 in this guide. |
| Default for baseline date | OBB8, baseline date calculation | Sets which date is used by default: no default, posting date, document date or entry date. |
| Fixed day | OBB8, baseline date calculation | Moves the baseline date to a given day of the month. |
| Additional months | OBB8, baseline date calculation | Adds a number of months to the baseline date. |
| Payment conditions | OBB8, payment terms lines | Days and percentages for the due date and the cash discount. |
If none of these settings produces a date, the baseline date stays empty, and a required field then stops the posting. The solution in this guide fills the baseline date calculation of the terms of payment, so that SAP can always derive a date.
✅ SAP Error Fix: Bline Date Is a Required Field for GL Account 800001
Follow these steps to correct the terms of payment. The values below match the screenshots.
Solution: OBB8. Go to transaction OBB8, which maintains the terms of payment. In the IMG it sits under Financial Accounting, Accounts Receivable and Accounts Payable, Business Transactions, Incoming Invoices/Credit Memos, Maintain Terms of Payment.
Follow steps. Select the terms of payment: 0013. Open the entry to see its details.

Select the baseline date calculation: fixed day 60 and additional months 1. These are the values from the original screenshot.

Save. SAP asks for a customizing request. Choose an open one or create a new one.
Release the billing document again. Open it with VF02 and release it to accounting, or use the list of billing documents blocked for accounting. The posting should now succeed.
📋 Values Used in This Tutorial at a Glance
| Field | Value in the Example | Note |
|---|---|---|
| Transaction | OBB8 | Maintain terms of payment. |
| G/L account | 800001 | The account named in the message. |
| Terms of payment | 0013 | Replace with the key used in your billing document. |
| Fixed day | 60 | As in the screenshot. Confirm the value with your finance team. |
| Additional months | 1 | Number of months added to the baseline date. |
The numbers come from the original screenshots. Use your own values when you try the steps in your system.
📅 Understanding Fixed Day and Additional Months
Both fields exist to move the baseline date to a convenient point in time. Many companies, for example, invoice during the month but want the payment clock to start at a fixed point, such as the middle of the following month. A fixed day sets the day of the month, and additional months adds whole months.
| Document Date | Fixed Day | Additional Months | Baseline Date (Illustration) |
|---|---|---|---|
| 10.09.2023 | 15 | 1 | 15.10.2023 |
| 28.09.2023 | 15 | 1 | 15.10.2023 |
| 10.09.2023 | none | none | The default date, for example the document date |
The table is only an illustration, because the exact result depends on your settings and release. Test with a real billing document after you save. Also check the field default for baseline date in the same screen. If it is set to no default and no fixed day is given, SAP has no date to use, which is the situation that triggers this error.
📝 Where the Payment Terms Come From
The terms of payment key in the billing document is not typed in the invoice. It is copied from the sales order, which in turn took it from the customer master. In the customer master it can be found in the sales area data, on the billing documents tab, and in the company code data, on the payment transactions tab. If the two differ, the sales document usually wins for billing.
If a customer has no payment terms at all, the baseline date may stay empty too, even though the terms in OBB8 are perfect. So when the error appears for one customer only, check the customer master first, then OBB8. For details on the master data, see Sales area 2001 31 31 is not defined for customers.
🔄 Two Ways to Remove This Error
| Approach | What You Change | Where | Choose It When |
|---|---|---|---|
| Fill the baseline date by rule | The baseline date calculation of the payment terms | OBB8 (this guide) | The account must keep the required field, and SAP should derive the date automatically. |
| Change the field control | The field status group of the G/L account | FS00 and OBC4 | The account should not require a baseline date at all. See Baseline Date Required for G/L Account 1213 500061. |
| Enter it by hand | The baseline date on the document | Payment tab of the document | A single document needs a special date. |
Start with the approach that changes the least. Entering the date by hand affects one document, the payment terms affect every document using the key, and the field status group affects every posting to the accounts using it.
✅ Verify the Fix
After saving in OBB8, release the blocked billing document to accounting again. The accounting document should be created, and the billing document should no longer be blocked. Open the accounting document, look at the customer line item and check the baseline date and the net due date. Compare them with the rule you maintained. Then create one more invoice for another customer who uses the same terms of payment, to confirm that the rule works in general and not only for one document.
💼 Real-World Scenario: An Invoice That Would Not Post
Pradnya Pawar, an SAP SD consultant working with a beverage distributor in Pune, was helping a new sales assistant to release invoices at the end of the day. One billing document stopped with the message that the baseline date is a required field for G/L account 800001, and it stayed blocked for accounting.
Pradnya first checked the billing document. The customer had the terms of payment 0013, but the baseline date had no default. She opened OBB8, selected 0013 and entered the baseline date calculation that finance had agreed. Before she saved, she asked finance who else used 0013, because the change would apply to all of them. They confirmed that it was meant for every customer on those terms.
She saved on a customizing request, tested in the quality system and moved it to production. The assistant released the blocked invoice again, and the accounting document was created. Sales manager Anand Rathi asked for a short note with the terms of payment, the rule and the transport number, so that the next person who sees this message knows where to look.
🔍 What Happens Behind the Scenes
The terms of payment are stored in a customizing table, table T052, with one entry per key. The billing document header, table VBRK, carries the key in its terms of payment field. When the billing document is transferred to accounting, SAP builds the accounting document and fills the baseline date field of the customer line item from the rules of the key. In the accounting line items that field is called ZFBDT.
Before the document is saved, the field status of the G/L account and of the posting key is checked. If the baseline date is required and the field is still empty, the check fails and the message appears. Understanding this order explains why the message names an account, although the cause is often the payment terms that should have filled the field.
❗ Common Mistakes When Fixing This Error
- Changing the terms of payment without checking which other customers use the key.
- Fixing the field status of the account when the real cause is a payment term without a baseline date rule.
- Entering values in OBB8 that nobody in finance has agreed.
- Forgetting the customizing request, so the fix never reaches quality or production.
- Creating the invoice again instead of releasing the blocked billing document.
- Ignoring the customer master, where the payment terms may be missing.
- Testing with one document only, and not with a second customer on the same terms.
🔧 Troubleshooting: When the Message Still Appears
The exact message wording differs by release, so the descriptions below name the symptom rather than quoting a message.
The same message appears after saving OBB8
The transport may not have reached this client, the billing document may use a different terms of payment key, or the document was not released again. Check the key in the billing document header.
The message appears for one customer only
That customer probably has no terms of payment, or has a different key. Check the sales area data of the customer master.
The field is still required but the date is filled
Look at the date format and check that the baseline date really appears in the customer line item of the accounting document.
The terms of payment key does not exist
The key in the document may be wrong. Compare it with the keys in OBB8, and correct the customer master or the order.
The accounting document is created but the due date looks wrong
Review the baseline date calculation and the payment conditions in OBB8. Check the fixed day and the additional months with your finance team.
The field status of the account is the cause
If the terms are correct and the field is still required for every posting, see Baseline Date Required for G/L Account 1213 500061 for the change in FS00 and OBC4.
No accounting document is generated
The billing document may be blocked for another reason. See Document saved (no accounting document generated) and error in account determination.
✅ Best Practices for Payment Terms and Baseline Dates
- Define a baseline date rule in every terms of payment key, so SAP can always derive a date.
- Keep a list of the payment terms keys, their rules and the customers that use them.
- Create a new key for a new rule instead of changing a key that many customers share.
- Agree the rule with finance and keep the approval with the transport request.
- Test with documents of two different customers after every change.
- Maintain terms of payment in the customer master for every new customer.
- Release blocked billing documents the same day, so that revenue is posted on time.
- Review the terms of payment once a year for keys that nobody uses.
🛡 How to Prevent This Error in Future
- Add the terms of payment to the checklist for every new customer.
- Review the field status of revenue accounts, so that a required field does not surprise the billing team.
- Monitor the list of billing documents blocked for accounting every day.
- Train sales assistants to read the message and to forward it with the account, the customer and the billing number.
- Document the baseline date rules in the configuration workbook.
📋 Checklist Before Moving the Fix to Production
| Check | Done When |
|---|---|
| Terms of payment | The key in the billing document is identified. |
| OBB8 rule | The baseline date calculation is maintained and agreed with finance. |
| Other users | The customers using the key were reviewed. |
| Customer master | The customer has payment terms. |
| Field status | The account's field status was checked, if needed. |
| Test | A blocked billing document was released to accounting. |
| Transport | The request is released and imported in order. |
📱 This Message in SAP S/4HANA
The baseline date and the payment terms work the same way in SAP S/4HANA, and OBB8 is still used to maintain the terms of payment. Menu paths, Fiori apps for billing and some fields can differ from the classic examples used here, so confirm the exact steps in your own release. The principle does not change: when a required baseline date is empty, the posting stops, and either the terms of payment or the field status must supply or relax it.
🎓 Interview-Style Questions and Answers
Q: What is the baseline date?
The date from which the payment term days are counted.
Q: Which transaction maintains the terms of payment?
OBB8.
Q: Why can the baseline date be required?
The field status of the G/L account or the posting key marks it as a required entry.
Q: What do fixed day and additional months do?
They move the baseline date to a given day and add whole months.
Q: What is the risk of changing a terms of payment key?
It affects every customer and document that uses the key.
Q: What happens to the billing document when posting fails?
It stays saved and blocked for accounting, and can be released again after the cause is fixed.
📚 Quick Glossary
- Baseline date: the starting date of the payment terms.
- Terms of payment: the rule for due dates and cash discounts, identified by a key such as 0013.
- Fixed day: a day of the month to which the baseline date is moved.
- Additional months: the number of months added to the baseline date.
- Field status group: a set of rules saying which fields of a G/L account are required, optional or hidden.
- Billing document: the invoice or credit memo created in SD.
- Blocked for accounting: a billing document that has not yet been posted to accounting.
- Customizing request: the transport that carries configuration changes between systems.
🎯 Conclusion
The message that the baseline date is a required field for G/L account 800001 means that SAP could not determine the date from which the payment terms start to run. The solution in this guide is to maintain the baseline date calculation of the terms of payment 0013 in OBB8, save the change, and release the blocked billing document to accounting again. Check who else uses the terms before you save, agree the values with finance, and look at the field status of the account if the message remains. If you run into any errors while following along, feel free to send a screenshot to pramod@learntosap.com for help.