A global telecommunications company headquartered in Finland had to post more than 300,000 journal entries every quarter under IFRS 16, within five days and with a team of three. With Automate Studio the team now does this without outside help, and saves about 500 working hours per quarter.
300k+
journal entries per quarter
5 days
closing window
3 people
in the asset management team
99.9%
posting accuracy
The challenge300,000 journal entries, five days, three people
IFRS 16 changed how leases are accounted for. For this client it meant more than 300,000 journal entries every quarter, all to be posted within a five-day window during quarter-end closing, by a team of three.
The data came from the facility management software and could not be posted directly. It had to be enriched and validated with additional data from SAP first.
Project facts
- Client: global telecommunications company, headquartered in Finland
- Process: IFRS 16 journal entries at quarter-end closing
- Systems: three SAP systems: two SAP ECC and one SAP S/4HANA
- Product: Automate Studio
- Time to value: 1 week
The solutionFrom raw extract to posted entries in one chain
We translated the business requirements and the raw data extract into an Automate Studio upload template through more than 40 business rules. Studio then posts two types of journal entries in three SAP systems.
Key functionalities
Chain of Studio scripts
Cost centre extraction (KS03), foreign-exchange revaluation posting (FBB1) and revenue posting (FB01) run in one chain, with no manual intervention.
Semi-automatic data preparation
Data is enriched and validated with Excel functions and the Studio simulation function, so data quality is checked before the mass upload.
Self-service, full control
The asset management team does not depend on IT or data migration teams for mass data extraction or journal entry posting.
Business valueWhat changed for the team
- About 500 working hours saved per quarter. In the five-day window this equals the work of 12 people.
- 99.9% accuracy of journal entries. Minimal rework is needed.
- Time for other closing tasks. While Studio processes the entries, the team works on the rest of the closing.
- No dependency on other teams. Mass execution needs no support from data migration or IT.
- Audit-proof postings. Journal entries are posted on behalf of the asset management team members, with full SAP control.
Behind this storyThe solution, the product and the service
SolutionSAP Automation
ProductAutomate Studio
ServiceSolution Design & Implementation
Want results like these? Talk to an expert.
ContactTalk to an expert
Tell us which SAP process or product you are looking at. One of our consultants will get back to you.
- We read your message and pass it to the consultant who knows the topic.
- We contact you to agree on a short call.
- If you wish, we show a demo on a process like yours.
Prefer to write directly?
info@novacon.hu
