Real Estate Contracts in RE-FX: Conditions, Terms, and Periodic Posting

In SAP RE-FX, the real estate contract is where commercial terms turn into accounting entries. If the contract is set up well, periodic posting runs quietly every month. If it is not, finance teams spend the close chasing missing receivables, wrong accounts, and unexplained reversals.

This article walks through the three building blocks that determine what RE-FX posts: conditions, terms, and the periodic posting run, plus the account determination that connects them to the general ledger.

Contract Types Set the Frame

Every real estate contract has a contract type, for example a lease-out or lease-in contract. The contract type controls important defaults and, through its condition group, which condition types users can enter. Only one condition group can be assigned to a contract type.

This design is deliberate. By limiting the condition types available per contract type, you limit the ways a user can produce an unexpected posting. When defining contract types, involve accounting early. A new contract type is not just a label; it is a decision about which conditions, valuation rules, and account determination paths apply.

Conditions: What Is Owed

Conditions represent the amounts in a contract: base rent, parking, service charge advance payments, and similar items. Each condition has a condition type that describes its nature, plus an amount, a validity period, and assignment to the contract or to specific objects.

Practical points to consider:

• Granularity. Separate condition types for separate economic items make reporting and account determination easier. Bundling everything into a single "rent" condition saves effort up front and costs much more later.

• Time dependency. Conditions are time-dependent. A rent increase should be entered as a new validity period, not by overwriting the existing amount.

• Condition adjustments. RE-FX supports adjustments such as index-based adjustments and graduated rent. If these apply, define them as part of the contract design rather than as manual changes.

Terms: How and When It Is Posted

RE-FX groups posting-relevant settings into time-dependent terms on the contract's posting parameters. A standard term exists for each category, and additional numbered terms can be created where needed.

Posting terms hold the data required to create a receivable or payable:

• Payment method, payment terms, and payment block

• Dunning area and dunning block

• Bank details and house bank

• Tax type and tax group

• The contract partner the term applies to

A single contract can carry several posting terms, for example one for direct debit and one for another payment method.

Frequency terms control timing:

• Frequency and frequency unit, such as monthly or quarterly

• How the condition amount relates to time

• Calculation method, such as 30 days per month or exact days

• Payment form: in advance, mid-period, or in arrears

• Due date correction rules, for example shifting due dates to a specific business day

Organizational assignment terms carry assignments such as profit center or business area. These drive the account assignment on the documents created during periodic posting.

Conditions are assigned to the relevant terms automatically. When a posting looks wrong, checking which term the condition is linked to is usually one of the first diagnostic steps.

Account Determination: Where It Lands

RE-FX derives G/L accounts through a chain:

1. The condition type is assigned to flow types, which classify cash flows. Separate flow types typically exist for the base posting, increases and decreases in the condition amount, and transfer postings.

2. Reference flow types link follow-up postings, such as retroactive changes, to the correct flow type.

3. Flow types map to account symbols, an intermediate layer between flow types and G/L accounts.

4. Account symbols resolve to G/L accounts. The customer or vendor reconciliation symbol takes the business partner from the contract.

Optional account determination values on the contract allow a different G/L account for specific contracts. Use this sparingly and document the reason, since it creates exceptions auditors will ask about.

The Periodic Posting Run

Periodic posting posts or reverses receivables and payables to the contract partner for each contract, based on conditions and frequency terms. In practice:

• Run it as a scheduled background job.

• Simulate first. The simulation shows what will be posted and surfaces errors before any document is created.

• Review the log. The posting log lists created documents and errors. Typical causes for missing postings include inactive contracts, blocked business partners or account assignments, no items due in the selected period, and incomplete Customizing.

• Watch retroactive changes. When a condition is changed for a past period, RE-FX generates follow-up postings through the reference flow types. These should be expected and explainable, not a surprise during close.

Each contract also offers a partner-related and an object-related cash flow. These views are the most direct way to see what RE-FX plans to post before it posts.

Controls Worth Building in

• Approval of new contracts and material condition changes before activation

• Review of the periodic posting simulation and error log as a standard close step

• Periodic review of contract-specific account determination values

• Restricted authorization for changing condition types, flow types, and account determination in Customizing

These controls also support SOX documentation, because each posting can be traced back to an approved contract and a controlled configuration.

Related Articles

• What Is SAP RE-FX? Real Estate Management in SAP Explained

• ASC 842 and IFRS 16 Lease Accounting in RE-FX

• Right-of-Use Assets: How RE-FX and Asset Accounting Work Together

The Bottom Line

RE-FX contracts combine conditions (what is owed), terms (how and when it is posted), and account determination (where it lands). Clean contract types, granular condition types, and a disciplined simulate-review-post routine make periodic posting reliable. At Revident, we favor human-governed automation here: let the system prepare simulations and flag anomalies, and keep an accountable reviewer in the loop before documents post.

Planning to redesign your RE-FX contract setup? Talk to our experts.