Case Study of AutoHome’s Financial Information System Evolution (2014‑2019)

Business Background – After AutoHome’s NASDAQ listing in late 2013, rapid business growth highlighted the need for a robust financial information system to improve efficiency, risk control, and group‑wide financial management.

2014 System Status – The finance system was low‑automation, manual‑heavy, and unable to support fast‑changing business needs, lacking integrated data flows and group‑level control.

2014 Architecture – The early architecture consisted of a few isolated systems with limited data exchange, relying on manual import/export and file‑server sharing.

Phase 1 (2014‑2016): From Offline to Online – The finance R&D team aimed to fully online‑enable business processes, introduce new online financial controls, and boost efficiency while reducing risk. Six core finance systems (Billing Center, SO, E‑commerce Finance, Business Settlement, Procurement, EBS) were built, creating a closed‑loop data environment and dramatically improving operational efficiency.

Key Projects in Phase 1 – Billing Center + SO system unified revenue collection, invoicing, and logistics; Procurement system digitized contracts, PR, payments, and reimbursements with mobile approval; EBS replaced legacy NC, supporting multi‑organization and flexible data integration; Business Settlement system consolidated over 60 settlement rules for e‑commerce and finance.

Phase 2 (2017‑2018): Finance‑Business Fusion & Management Upgrade – With online processes established, focus shifted to stronger group‑level financial governance and risk control. New systems introduced included a comprehensive Budget Management system, a Finance Settlement system integrating business revenue details, and a Tax Management system offering visual tax indicators and automated filing via a rule engine.

Phase 3 (2019‑Future): Platformization – The proliferation of over a dozen finance subsystems created data silos and inconsistent interfaces. The strategy moved toward a unified finance middle‑platform, data warehouse, and master‑data service layer to achieve finance‑business integration, standardized data services, and streamlined analytics.

Technical Transformation of the Finance R&D Team – Over five years the team evolved from a .NET‑centric stack (2014‑2015) to Java (starting 2016), adopted modern front‑end frameworks (2018), and introduced data‑warehouse capabilities (2019) to support analytics, all while meeting tight delivery schedules and serving as a model for other IS teams.

Conclusion – The finance information system modernization at AutoHome illustrates how coordinated technical upgrades, platform‑centric architecture, and proactive R&D management can drive enterprise‑wide financial efficiency, risk mitigation, and strategic support for rapid business growth.