Suing Accenture over a failed core-systems project, seeking ¥12.4 billion (2023)
Where responsibility divides — an old question, freshly asked
The heart of this dispute is an old and recurring question: when a large systems development collapses, how much of the responsibility falls on the vendor and how much on the user. The vendor is held to a “project management duty” that covers not only tracking progress but explaining whether cost and schedule need to be revised; the user is held to a “duty of cooperation” — providing information, putting the right organisation in place. On the standing of keystroke testing and on whether requirements were properly presented, the two sides’ accounts remain at odds.
In past case law, there are almost no examples of responsibility for a failed development being assigned to the vendor or the user alone. The dispute between Nippon Express and Accenture likewise turns on how the court judges whether both parties exhausted their dialogue and discharged their duties, and as of this writing it remains pending. Beyond the loss of an investment on the order of ¥12.4 billion, the case can be read as a mirror held up to the relationship between client companies and their vendors.
Revenue and net margin, FY2018–FY2025
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2023 onwards — after it was taken.
Source: securities reports
Read the full dossier in Japanese →
The Japanese edition carries the complete record of this decision — the situation that forced it, the options weighed, what actually followed, and the sources behind every claim.
Other key decisions at Nippon Express Holdings
- 2000 The parcel alliance with the postal service, and a shared brand (2000)
- 2022 Moving to a holding-company structure — the founding of NIPPON EXPRESS HOLDINGS (2022)
- 2023 Acquiring cargo-partner of Austria to buy a European and Central-Eastern European base (2023)
- 2026 Buying Metro Supply Chain Group of Canada while shrinking the balance sheet (2026)
Yen amounts are converted at the average rate of each figure’s own year — not today’s rate; the revenue chart is shown in yen. Exchange rates & sources — the full ¥/US$ table →
Disclaimer
- This page is provided for general information only and is not investment advice, nor a recommendation to buy or sell any security.
- Figures are compiled independently and include our own estimates, approximations and machine-processed data; we make no warranty as to their accuracy or completeness.
- Sources are primarily each company’s securities reports and other public filings, but errors and omissions may remain.
- Any use of this information is at the reader’s own risk. Past performance does not indicate future results.
- Company names, logos and other marks belong to their respective owners.
Data API
Nippon Express Holdings’s history, financials, executives and
shareholders are published as static JSON — no key, plain GET.
Full specification →
| Method | Endpoint | Returns |
|---|---|---|
| GET | /api/companies.json | All companies |
| GET | /api/9147/manifest.json | Resource index |
| GET | /api/9147/history.json | History overview |
| GET | /api/9147/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/9147/decisions.json | Management decisions (index) |
| GET | /api/9147/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/9147/executives.json | Executives |
| GET | /api/9147/shareholders.json | Major shareholders |
| GET | /api/9147/financials.json | Financial statements |
| GET | /api/9147/financials-longterm.json | Long-term results |
| GET | /api/9147/segments.json | Business segments |
| GET | /api/9147/regions.json | Sales by region |
| GET | /api/9147/workforce.json | Workforce |