Komori
bBreak Systems (3986) · FactRestated

Combination of flow and recurring revenue

First written in FY2017. 23 of 24 entries say "Restated". Latest entry: FY2024.

24entries
8years
0from disclosures
Share on X
How it moved
ProgressHeldSoftenedWorseRestatedFY2017 – FY20242017: 22018: 420182019: 420192020: 320202021: 420212022: 220222023: 320232024: 22024
Same theme, other companies
A flow-and-stock revenue model combining one-off project revenue with recurring monthly and maintenance revenueA theme 53 companies write about · 1 as a headwind · 52 as a tailwind

16 other companies' latest entry also says "Restated".

Ridges = years it wrote progress, valleys = years it wrote worse. Most hopeful companies at the back. Drag to turn, scroll to zoom, right-drag to pan. On a phone, two fingers turn and pinch to zoom; one finger scrolls the page.
Showing 14 of the 53 companies compared. The sentences above are computed from all 53.
Full recordFilings, disclosures and news, newest first
  1. FY2024RestatedAnnual report

    「Revenue from this business consists of consideration received when implementing core business systems (project-based revenue) and consideration generated by customers' continued use of our services after implementation (recurring revenue).」

    Reiterates the revenue structure combining implementation revenue and revenue from continued use.
  2. FY2024-Q3RestatedAnnual report

    「This was mainly due to increases in the provision for bonuses and in deferred revenue (contract liabilities) related to new orders for the package business and to maintenance and SaaS version usage fees.」

    Implementation revenue from new orders for the package business and recurring revenue from maintenance and SaaS version usage fees continue to be shown as factors behind the increase in contract liabilities.
  3. FY2024-Q1RestatedAnnual report

    「This was mainly due to an increase in contract liabilities related to new orders for the package business and to maintenance and SaaS version usage fees.」

    The revenue structure, including implementation revenue from new orders and recurring revenue from maintenance and SaaS version usage fees, continues to be shown as a factor behind the increase in contract liabilities.
  4. FY2023RestatedAnnual report

    「In addition, revenue from this business consists of consideration received when implementing core business systems (project-based revenue) and consideration generated by customers' continued use of our services after implementation (recurring revenue).」

    Reiterates the revenue structure combining implementation revenue and revenue from continued use.
  5. FY2023-Q3RestatedAnnual report

    「This was mainly due to increases in the provision for bonuses and in deferred revenue (contract liabilities) related to new orders for the package business and to maintenance and SaaS version usage fees.」

    Implementation revenue from new orders for the package business and recurring revenue from maintenance and SaaS version usage fees continue to be shown as factors behind the increase in contract liabilities.
  6. FY2022-Q3RestatedAnnual report

    「This was mainly due to increases in the provision for bonuses and in deferred revenue (contract liabilities) related to new orders for the package business and to maintenance and SaaS version usage fees.」

    The combination of implementation revenue from new orders for the package business and recurring revenue from maintenance and SaaS version usage fees continues to be shown as a factor behind the increase in contract liabilities.
  7. FY2022-Q2RestatedAnnual report

    「This was mainly due to increases in the provision for bonuses and in deferred revenue (contract liabilities) related to new orders for the package business and to maintenance and SaaS version usage fees.」

    The combination of implementation revenue from new orders and recurring revenue from maintenance and SaaS version usage fees continues to be shown as a factor behind the increase in contract liabilities.
  8. FY2022-Q1RestatedAnnual report

    「This was mainly due to an increase in deferred revenue (contract liabilities) related to new orders for the package business and to maintenance and SaaS version usage fees.」

    The combination of implementation revenue from new orders and recurring revenue from maintenance and SaaS usage fees continues to be shown as a factor behind the increase in contract liabilities.
  9. FY2021RestatedAnnual report

    「In addition, revenue from this business consists of consideration received when implementing core business systems (project-based revenue) and consideration generated by customers' continued use of our services after implementation (recurring revenue).」

    Reiterates the revenue structure combining implementation revenue and revenue from continued use.
  10. FY2021-Q3RestatedAnnual report

    「Total liabilities at the end of the third quarter stood at ¥408 million, an increase of ¥78 million from the end of the previous fiscal year. This was mainly due to increases in the provision for bonuses and deferred revenue related to orders for the package business.」

    The increase in deferred revenue related to orders for the package business is cited as a factor behind the increase in liabilities, continuing to show a revenue structure that includes implementation revenue and other sources.
  11. FY2021-Q2RestatedAnnual report

    「This was mainly due to an increase in cash and deposits resulting from the recording of quarterly net income.」

    In addition to explaining the revenue structure itself, the disclosure notes an increase in deferred revenue related to orders for the package business, continuing to show a business structure that includes implementation and recurring revenue.
  12. FY2020RestatedAnnual report

    「In addition, revenue from this business consists of consideration received when implementing core business systems (project-based revenue) and consideration generated by customers' continued use of our services after implementation (recurring revenue).」

    Reiterates the revenue structure combining implementation revenue and revenue from continued use.
  13. FY2020-Q3RestatedAnnual report

    「Total liabilities at the end of the third quarter stood at ¥356 million, an increase of ¥56 million from the end of the previous fiscal year. This was mainly due to increases in the provision for bonuses and deferred revenue related to maintenance and SaaS version usage fees in the package business.」

    The combination of implementation revenue from new orders and recurring revenue from maintenance and SaaS usage fees continues to be shown as a factor behind the increase in deferred revenue.
  14. FY2020-Q2RestatedAnnual report

    「For MA-EYES, the company's flagship cloud ERP product, new orders and orders for additional development from existing users remained firm, while maintenance fees and SaaS version usage fees increased as projects ordered in the previous fiscal year went live.」

    The combination of implementation revenue from new orders and recurring revenue from maintenance fees and SaaS usage fees after systems go live continues to be shown.
  15. FY2020-Q1RestatedAnnual report

    「For MA-EYES, the company's flagship cloud ERP product, new orders and orders for additional development from existing users remained firm, while maintenance fees and SaaS version usage fees increased as projects ordered in the previous fiscal year went live.」

    Continues to describe the combination of implementation revenue from new orders and recurring revenue from maintenance fees and SaaS usage fees after systems go live.
  16. FY2019RestatedAnnual report

    「In addition, revenue from this business consists of consideration received when implementing core business systems (project-based revenue) and consideration generated by customers' continued use of our services after implementation (recurring revenue).」

    Reiterates the revenue structure combining implementation revenue and revenue from continued use.
  17. FY2019-Q3RestatedAnnual report

    「Total liabilities at the end of the third quarter stood at ¥316 million, an increase of ¥52 million from the end of the previous fiscal year. This was mainly due to increases in deferred revenue related to new orders for the package business and to maintenance and SaaS version usage fees.」

    The combination of implementation revenue from new orders and recurring revenue from maintenance and SaaS version usage fees continues to be shown as a factor behind the increase in deferred revenue.
  18. FY2019-Q2RestatedAnnual report

    「This was mainly due to increases in new orders for the package business and deferred revenue related to maintenance and SaaS version usage fees.」

    The combination of implementation revenue from new orders and recurring revenue from maintenance and SaaS version usage fees continues to be shown as a factor behind the increase in deferred revenue.
  19. FY2019-Q1RestatedAnnual report

    「For MA-EYES, the company's flagship cloud ERP product, new orders increased substantially, while maintenance fees and other revenue increased as projects ordered in the previous fiscal year went live.」

    The combination of revenue from new orders at implementation and recurring revenue from maintenance fees and other charges after systems go live continues to be shown.
  20. FY2018RestatedAnnual report

    「In addition, revenue from this business consists of consideration received when implementing core business systems (project-based revenue) and consideration generated by customers' continued use of our services after implementation (recurring revenue).」

    Reiterates the revenue structure combining implementation revenue and revenue from continued use.
  21. FY2018-Q3RestatedAnnual report

    「This was mainly due to increases in new orders for the package business and deferred revenue related to maintenance and SaaS version usage fees.」

    The combination of implementation revenue from new orders and recurring revenue from maintenance and SaaS version usage fees continues to be shown.
  22. FY2018-Q2RestatedAnnual report

    「This was mainly due to increases in new orders for the package business and deferred revenue related to maintenance and SaaS version usage fees.」

    The combination of implementation revenue from new orders and recurring revenue from maintenance and SaaS usage fees continues to be shown.
  23. FY2018-Q1RestatedAnnual report

    「For the cloud ERP "MA-EYES," the company's flagship product, new orders remained solid, while revenue from maintenance fees for the packaged version and usage fees for the SaaS version increased. As a result, net sales were ¥129 million and segment profit was ¥60 million.」

    Describes the increase in recurring revenue from maintenance fees and SaaS usage fees in addition to new orders received at implementation.
  24. FY2017First statedAnnual report

    「Revenue from this business consists of consideration received when implementing core business systems (project-based revenue) and consideration generated by customers' continued use of our services after implementation (recurring revenue).」

    Shows a revenue structure combining implementation revenue and revenue from continued use.
Moved together

None of this company's other threads moved the same way in the same document twice or more.

When this could move next
No upcoming earnings preview for bBreak Systems yet.
News
No news is linked to this thread yet. When an article touches it, it will appear here by date.