A user posts an invoice or a G/L document and SAP refuses to save it because the baseline date is a required field for the G/L account. The fix is to fill in the baseline date, or to correct the field status group of the account in FS00, or to relax the group in OBC4. This guide explains the message, why the field is required, the three solutions with the original screenshots, how to choose between them, how to verify the result and how to avoid the error in future. If you run into any errors while following along, feel free to send a screenshot to pramod@learntosap.com for help.

| Item | Value in This Example |
|---|---|
| Field named in the message | Baseline Date (BLINE in the message text) |
| Module | SAP FI (Financial Accounting) |
| G/L account | 500061 |
| Company code | 1213 (the number shown next to the account in the message) |
| Why it appears | The field status group of the G/L account sets the baseline date as a required entry |
| Where to fix it | The invoice Payment tab, FS00 and OBC4 |
The account number and company code in your own message may differ from this example. The same steps apply with your own values.
Common error message: "The BLINE (Baseline date) is used to determine the due date of payments. If the field status group of the G/L account has set this field as required, then it must be filled before posting."
The baseline date is the starting point for payment terms. SAP adds the number of days from the payment terms to the baseline date and arrives at the net due date and the cash discount dates. Without a baseline date, the system cannot calculate when a payment is due, which is why some accounts insist on it. In the database the field is called ZFBDT in the accounting line item table, and its screen label is Baseline Date.
Whether a field must be filled is not decided by the screen alone. Each G/L account is linked to a field status group, and that group states, field by field, whether an entry is required, optional or hidden. When the group marks the baseline date as a required entry and the user leaves it empty, SAP stops the posting and shows this message. The message is therefore not a calculation problem. It is a field control setting meeting an empty field.
Work through these checks in order:
| Cause | What Is Wrong |
|---|---|
| Baseline date left empty | The user did not enter a date on the Payment tab, and the account requires one. |
| Payment terms added by hand or left blank | Without payment terms the system cannot propose a baseline date, so the field stays empty. |
| Field status group too strict | The group assigned to the G/L account marks the baseline date as required for every posting. |
| Wrong group on the account | The account was created with a group meant for another purpose, for example a bank or reconciliation account. |
| Posting key makes it required | The field status of the posting key marks the baseline date as required in addition to the account setting. |
| Transport missing | The corrected setting exists in development but has not reached this client. |
In daily work the first two causes are the most common, and the quickest cure is simply to fill in the field. A permanent fix is only needed when the date should not be asked for at all on this account.
Several settings work together before SAP decides whether the baseline date is required. The table lists each one and where it is maintained.
| Setting | Where It Is Maintained | What It Does |
|---|---|---|
| Baseline date | Payment tab of the document line item | The date from which the payment term days are counted. |
| Payment terms | Vendor or customer master, or the document header | Defines the days for the due date and the cash discount. |
| Field status group | G/L account master, FS00, Create/bank/interest tab | Controls which fields are required, optional or hidden for the account. |
| Field status variant | Assigned to the company code | The set of field status groups available to the company code. |
| Group settings | OBC4 | Defines, for each group, the status of every field, for example Payment Transactions. |
| Posting key field status | OB41 | Adds a second layer of field control per posting key. |
SAP combines the field status of the account with the field status of the posting key. In general a required entry from either side wins over an optional one, so a field can be required even when the account group says optional. Exact behavior can differ between releases, so compare with your own system.
The message appears whenever a posting touches the account and the baseline date is empty:
In integrated postings the user may never see the Payment tab, which is why the message sometimes surprises people. The field requirement comes from configuration, not from what the user chose on the screen.
Read the message. Note the G/L account (500061) and the company code (1213) and which document you were posting.
Open the Payment tab of the invoice. Check whether the Baseline Date and the payment terms are filled.
Open the account with FS00. Look at the field status group on the Create/bank/interest tab.
Open the group in OBC4. Check the Payment Transactions section and see whether Baseline date is a required entry.
Check the posting key. Use OB41 to see whether the posting key also requires the field.
First please check Baseline Date and enter the appropriate date (usually the invoice date or posting date).
Enter the Baseline Date under the Payment tab in the invoice.
This is the fastest fix and changes no configuration. It is the right answer when the account is meant to carry a due date and the user simply forgot to fill it in. The date is normally the invoice date or the posting date, as agreed with your finance team.
Post the document again. If the message disappears, no further change is needed.
Go to Tcode FS00. Open the Create/bank/interest tab and click (Create/Change Field Status Group).
Click on the G/L account 500061. Open it in change mode for company code 1213.
Then select the Field Status Group G001 (General with text, Allocation).


Save. Assign a customizing request if the system asks for one.
G001 is used in this example. Before you assign any group, open it in OBC4 and compare its Payment Transactions settings, because a group in your own variant can differ from the standard one.
Go to Tcode OBC4. Click and open the Field Status Group.
Set the setting. In the "Payment Transactions" section, set Baseline date to Optional instead of Required (if the business process allows).


SAVE. Assign a customizing request if the system asks for one.
The three solutions differ in how much they change. Start with the smallest one that solves your case.
| Solution | What Changes | Scope | Choose It When |
|---|---|---|---|
| 1) Enter the baseline date | Nothing in configuration | This one document | The user forgot the date, or the account really needs it. |
| 2) FS00 field status group | The group assigned to the G/L account | One G/L account | The account carries the wrong group for its purpose. |
| 3) OBC4 field status | The field settings inside the group | All accounts using the group | The business agrees that the date is not needed for any of those accounts. |
The table below summarizes every value from the steps above, so you can compare it with your own screen before saving.
| Field | Value Used | Note |
|---|---|---|
| G/L account | 500061 | Replace with your own account |
| Company code | 1213 | Replace with your own company code |
| Baseline date (Solution 1) | Invoice date or posting date | Enter on the Payment tab |
| Field status group (Solution 2) | G001 (General with text, Allocation) | Compare with the group in your own variant |
| Baseline date status (Solution 3) | Optional instead of Required | Only if the business process allows |
Keeping a small table like this in your configuration workbook makes later audits much easier, because anyone can see which values were entered and why.
After saving, repeat the posting that caused the message, for example the same vendor invoice. The error should be gone and SAP should let you save the document. Open the document and check the Payment tab: the baseline date and the net due date should show the values you expect. If you changed the group, post a second document to another account that uses the same group, to confirm that nothing else broke. Finally, reopen FS00 or OBC4 and compare the setting with the table above.
At Learn Pharma in Pune, accounts payable clerk Pooja Patil tried to post a freight invoice that included a line for G/L account 500061 in company code 1213. SAP stopped her with the message that the baseline date is a required field for the account. She asked functional consultant Neha Deshmukh for help.
Neha first opened the Payment tab and found that the payment terms were typed in by hand and the baseline date was empty. She entered the invoice date as the baseline date and the document posted. Because the same message returned for another clerk the next day, Neha opened the account in FS00 and saw that it used a group meant for reconciliation accounts. She switched it to a general group, checked the Payment Transactions section in OBC4 and saved the change on a customizing request.
After testing in the quality system, the transport moved to production. Pooja posted the invoice again without trouble. Neha recorded the change in the configuration workbook so that the next freight account would be created with the right group from the start.
| Symptom | Likely Cause | What to Check |
|---|---|---|
| Same message after saving. | The transport has not reached this client. | Check the request status and import it. |
| Works for one account but not another. | The two accounts use different field status groups. | Compare the groups in FS00. |
| Group changed but field still required. | The posting key requires the field. | Check the field status of the posting key in OB41. |
| Group is not offered in FS00. | It is not part of the field status variant of the company code. | Check the variant assignment and the group in OBC4. |
| Due date looks wrong after posting. | A wrong baseline date or payment terms were used. | Review the Payment tab of the document. |
| Cannot save the setting. | No open customizing request or missing authorization. | Create or choose an open request or ask for the right role. |
Field status groups remain part of G/L account master data in SAP S/4HANA, and the baseline date still drives the due date calculation. Menu paths, Fiori apps for G/L account master data and some settings can differ from the classic examples used here. Confirm the exact path and fields in your own release before you plan the work. The principle does not change: when the field status marks the baseline date as required, it must be filled before posting.
Once the message is gone, finish the job. Post a vendor invoice, a customer invoice and a general ledger document with the finance team, and confirm that the due dates and discount dates behave as expected. Update your configuration documentation with the final setting and the transport number.
If your company later opens another G/L account of the same type, repeat the same pattern: choose the right field status group, check its Payment Transactions section, test a posting and record the result. Treating the setup as a standard checklist item keeps this message from returning.
Finally, share the finished setting with the accounts payable and receivable teams. When everyone knows when the baseline date is required and which date to enter, questions at month end are answered in minutes.
| Check | Done When |
|---|---|
| Payment tab | The baseline date and payment terms are filled in the test document. |
| Field status group | The G/L account carries the agreed group in FS00. |
| OBC4 setting | Baseline date has the agreed status, required or optional. |
| Other accounts | Accounts sharing the group were reviewed. |
| Posting key | The posting key field status does not conflict. |
| Test posting | A document was posted to the account without the error. |
| Transport | The request is released and imported in the right order. |
Walking through this list takes only a few minutes, and it often catches a second setting that would have caused another message after go-live.
Q: What is the baseline date?
The date from which SAP counts the payment term days to calculate the due date.
Q: Why does SAP ask for it on a G/L account?
Because the field status group of the account marks it as a required entry.
Q: Where is the field status group of an account maintained?
In FS00, on the Create/bank/interest tab.
Q: Where do you change the status of a field inside a group?
In OBC4, for example the Payment Transactions section.
Q: What is the risk of changing a group in OBC4?
It affects every G/L account that uses the group.
The error "Baseline Date is a required field" for G/L account 500061 has a simple cause: the field status group makes the baseline date a required entry and the field was empty. Fill in the date under the Payment tab, or, if the account is set up wrongly, assign a suitable group in FS00, or make the field optional in OBC4 if the business process allows. Then post a test document and record the setting. If you run into any errors while following along, feel free to send a screenshot to pramod@learntosap.com for help.