S4F55 – Revenue Accounting and Reporting – Assisting with IFRS 15/US-GAAP ASC 606 — Lesson 2: Transaction Price, Allocation, Fulfillment, and Contract Changes

Learning Objectives

• Explain how Transaction Price, Allocation, Fulfillment, and Contract Changes supports compliant revenue recognition.
• Complete the workflow and produce a reviewable allocation and modification evidence pack.
• Evaluate the condition where a contract modification reallocates revenue using an outdated standalone selling price and select a supported response.

Detailed Topics

• transaction price determination: business purpose, responsible roles, and SAP objects that establish the operating scope.
• standalone selling prices: configuration choices, master-data dependencies, and determination logic shaping the result.
• allocation rules: transaction flow, status behavior, integration effects, and reviewable operational evidence.
• contract modifications: control points, exception paths, testing needs, and release criteria protecting the outcome.

Instructor Demonstration

Using the scenario, the instructor demonstrates transaction price determination, standalone selling prices, allocation rules, contract modifications and highlights object relationships, determination behavior, integration effects, and approval evidence. The demonstration deliberately introduces the exception where a contract modification reallocates revenue using an outdated standalone selling price.

Hands-On Exercise

Complete a controlled activity covering transaction price determination, standalone selling prices, allocation rules, contract modifications and preserve the result in allocation and modification evidence pack.

1. Review prerequisites, dependencies, authorizations, and acceptance criteria before starting the activity.
2. Complete the configured or transactional scenario and preserve the resulting document and status trail.
3. Compare the normal result with the controlled exception and identify the strongest root-cause evidence.
4. Document the selected response, retest result, residual risk, and future review trigger.

Scenario Analysis

• Which SAP object, rule, record, or process step most strongly influences Transaction Price, Allocation, Fulfillment, and Contract Changes?
• What evidence separates configuration, data, authorization, integration, and timing causes in this scenario?
• How should the allocation and modification evidence pack be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected behavior differs from the observed result. Review process sequence, relevant data, configuration, authorization, integration, and timing as separate hypotheses. Treat “a contract modification reallocates revenue using an outdated standalone selling price” as unconfirmed until settings, documents, logs, reports, and focused retesting support the cause.

Validation Checklist

• Required roles, structures, data, settings, and dependencies for Transaction Price, Allocation, Fulfillment, and Contract Changes are present.
• The allocation and modification evidence pack links each conclusion to objective and reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, monitoring, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Transaction Price, Allocation, Fulfillment, and Contract Changes, explain the resulting SAP behavior, and defend the outcome through allocation and modification evidence pack.