
SAP practices
SAP Record to Report: Universal Journal, Close, and the Factory Behind the Pack
- SAP Record to Report
- RTR
- Universal Journal
- Close
- S/4HANA Finance

Record to Report is the process, not a module: capture, reconcile, close, report. On S/4 it runs through the Universal Journal (ACDOCA), entity close, GR/IR, tax (often Vertex), allocations, overhead, and group reporting. Fortune 500 finance programs fail RTR when they staff “an FI consultant” and leave close as a tribal checklist in someone’s head.
The unique challenge is interlock. T&E (Concur), intercompany, GR/IR, asset under construction, and tax extracts all have to finish before the pack. If any one is late, close is a hero weekend. SR Soft staffs RTR as a factory: tasks, owners, SLAs, and the systems that feed them.
The challenges that actually break the program
- Close tasks with no system owner — “accounting will know”
- GR/IR that never clears and is dumped into a suspense P&L
- Tax and T&E arriving after the entity is “closed”
- Allocations that change the story the board already saw
- No distinction between entity close and group close
How SR Soft LLC staffs and delivers it
We put an RTR process lead with FICO, Concur, and (when in scope) Group Reporting and Central Finance. We publish a close calendar that names systems, not just people. We treat Vertex, Concur, and GR/IR as RTR objects. That is how the pack stops depending on one controller’s weekend.
- 01
Task inventory
Every close task, system, and owner.
- 02
Feeders
Concur, Vertex, GR/IR, IC — in the calendar.
- 03
Entity then group
Two clocks. Do not pretend they are one.
- 04
Hypercare as factory
The first three closes are designed, not survived.
