Payment term TCode in SAP defines how and when a company pays its vendors or customers. Understanding the related configuration and execution tools helps finance teams control cash flow and compliance.
Use the overview below to quickly compare key tools and transactions that support payment terms. This table focuses on practical use rather than exhaustive technical detail.
| Transaction Code (TCode) | Primary Purpose | Related Master Data | Typical User Role |
|---|---|---|---|
| OB08 | Maintain payment terms code | Payment terms key, currency, days or percentage basis | Configurer, Finance Specialist |
| FTXP | Process outgoing payment proposals | Vendor master, bank data, payment terms baseline | Accounts Payable Clerk |
| F110 | Execute payment run | Payment program settings, bank connectors, payment terms | Financial Controlling, Treasury |
| FK03 | Display vendor master data | Payment terms, purchasing organization, company code | Procurement, Finance |
| FBL5N | Display line items for customer account | Customer master, aging, payment terms application | Account Receivables, Auditor |
Configuring Payment Terms TCode OB08
OB08 is the central TCode for maintaining payment terms codes in SAP. Each code represents conditions such as net days, discount periods, or mixed percentage and day structures. Accurate setup in OB08 ensures that downstream documents like invoices and payment proposals reference the correct terms.
When you open OB08, you specify the key, valid from and to dates, and the basis of the terms. You can define fixed days, percent-based milestones, or a combination. It is important to align these settings with contract terms and local regulations to avoid mismatches during payment proposal runs.
Testing new or changed payment terms codes in a sandboxed environment is strongly recommended. Use sample vendors or customers and run parallel checks in F110 or FBL5N to confirm that the system calculates due dates and discounts as expected before going live.
Executing Payment Runs with F110
F110 is the workhorse transaction for payment run execution in SAP. It evaluates open items, applies the payment terms from vendor or customer master records, and proposes payment dates based on bank country and holiday calendars. The program respects the defined payment terms such as early payment discounts and net due days.
Payment proposals generated by F110 show the proposed payment date and the payment term code used for each item. You can manually adjust proposals within defined limits, but it is best to resolve discrepancies in master data or contract terms upstream. Consistent use of payment term TCode entries helps prevent manual overrides and reduces treasury exceptions.
Scheduling F110 as part of standard closing or treasury routines ensures predictable cash flow forecasting. Integration with bank connectivity and SWIFT interfaces further automates execution, while logs and output documents provide audit trails for each payment term decision.
Maintaining Vendor and Customer Master Data Impacting Payment Terms
Vendor master data via FK03 and customer via FD03 store the default payment term code. These codes flow into billing, invoicing, and reconciliation processes. If the term code is missing or incorrect, payment proposals and dunning activities may not reflect contractual obligations.
Integrating purchasing documents and sales orders with the finance side ensures that negotiated payment terms are reflected in the master. Any changes in payment conditions should trigger master data reviews and, where required, automated updates to keep the system aligned with legal and operational requirements.
Cross-checking the payment term TCode between contract documents and SAP master data reduces disputes and supports stronger internal control. Regular data quality checks using transaction tools and reports help identify inactive or inconsistent entries.
Monitoring and Reporting on Payment Terms Usage
Use F110 logs, payment program documents, and reconciliation reports to monitor how often each payment term TCode is applied. Trend analysis on usage of discount versus net terms supports working capital decisions and supplier negotiation strategies. Reports combining OB08 definitions with actual payment execution highlight deviations that may require investigation or process updates. Key metrics like early payment uptake, days payable outstanding, and payment batching efficiency become more reliable when linked to consistent use of payment term codes.
Best Practices for Payment Term Configuration and Execution
- Review payment term TCode entries in OB08 regularly to align with contract changes.
- Test changes in a sandbox before promoting to production to avoid disruptions in F110 and supplier communication.
- Ensure vendor and customer master data consistently reference the correct payment term code for each company code.
- Integrate payment term usage with treasury and cash forecasting to optimize working capital and discount capture.
- Set up automated monitoring and exception reporting to detect incorrect or inconsistent application of payment terms across open items.
FAQ
Reader questions
How does changing payment term TCode OB08 affect existing open items in F110?
Changing a payment term code in OB08 does not automatically update open items. Existing items continue with the term version valid at the time of entry. To apply new terms, you need to rerun payment proposals in F110 or use manual correction tools, ensuring proper authorization and testing first.
Can a single vendor use multiple payment term TCode entries across different company codes?
Yes, a vendor can have different payment term codes in different company codes within the same client. The system determines the active term based on the combination of vendor account, company code, and the effective validity dates defined in OB08.
What happens if the payment term TCode has an invalid bank country key during a payment run in F110?
The payment run may reject items or skip discount calculations if the bank country key linked to the payment term is missing or incorrect. Maintaining the correct bank country in both the payment term definition and vendor master prevents processing errors and ensures compliance with local payment regulations.
How can I audit which payment term TCode was applied to each line item in a cleared document?
Use transaction F110 audit logs, payment program history, and reconciliation reports that display the payment term code at item level. Cross-reference these logs with the payment proposal and master data to trace how each line item was processed and which term version was applied.