Helping PingCAP to reconstruct the middle and back office business integration and revenue recognition process for five major online/offline business models.

1. The business and finance systems are not connected: PingCAP has many business front-end systems, whose main function is to monitor the implementation of sales contracts and the actual usage of customer accounts. However, these business front-office systems have not yet been interfaced with the back-office financial Kingdee system (Kingdee system is currently only used for bookkeeping and adopts the cash basis). In addition, Salesforce is responsible for customer development and management, and although it interacts with the business front office in terms of customers and contracts, it also does not interface with the financial system;

2.Lack of business and financial integration master data: customer master data and account numbers (Orgs) are managed by Salesforce, and all kinds of service goods are managed in the business frontend, which only has business attributes without financial attributes, and Kingdee system is only responsible for bookkeeping and payment collection;

3. Huge manual workload:

    - Receivable invoicing: customer invoicing is handled offline, and specific charge items and amounts need to be exported from the business frontend, then manually merged or split and invoiced, and sent to the customer by manual mail;

    - Revenue recognition: Revenue recognition for the two offline and three online business models is completely manual and lacks business and financial integration and automation;

4. Challenges in business front-end transformation and business middle-end construction: there was no corresponding order before in the On Demand mode of business front-end, only RevRec records, which led to the need to create orders based on RevRec records in Salesforce, putting the cart before the horse. In addition, the data generated by the business frontend lacks version control, and the new version will cover the old version, which is not conducive to statistical analysis;

1.Assist customers to transform the front and middle office:

   - Establish the business management and analysis middle office to ensure that CP mode and On Demand mode orders are all generated in the middle office and distributed to NetSuite according to the billing cycle; Salesforce inquires about order execution through the interface;

   - Add customer Credit and points management modules to the Business Middle Office;

2.Synchronisation between Business Middle Office and NetSuite:

   - Offline customer master data is synchronised by Salesforce to the business middle office; online customer and account master data is generated by the business frontend and managed in the business middle office; all customer master data and account (Org) information in the middle office is regularly synchronised to NetSuite for subsequent invoicing, collection and other financial processing;

   - The middle office creates and maintains service goods, and new or modified service goods are synchronised to NetSuite;

   - The middle office customer pre-charge records and customer Credit points records are synchronised to NetSuite in a timely manner;

   - The actual consumption (RevRec) of CP orders corresponding to a customer or Org in the Middle Office and the data of one or more On Demand orders during the bookkeeping cycle are synchronised to NetSuite for subsequent invoicing and revenue recognition;

3.Set up the master data of business and financial integration service goods uniformly in NetSuite:

   - Including offline SaaS mode of local deployment services, offline milestone mode of professional services, online actual usage corresponding to a variety of services and combinations;

4. Unified invoicing management:

   - According to the orders, milestones, and actual usage of various modes of online/offline, configure the corresponding separate invoicing and combined invoicing functions and processes, and send them to customers via email, while docking with Docusign electronic signatures for applications on Invoice;

5.NetSuite and business front-end Portal docking:

   - The PDF version of customer invoices is transmitted to the front-end Portal through the interface, and customers can download it on their own as needed;

6.Remodeling of the five major business processes of receivables closed-loop write-off and revenue recognition process:

   - Deferred revenue and automated revenue recognition management for offline SaaS local deployment services;

   - Revenue recognition for offline professional services model milestones;

   - Personalised revenue recognition process design for online CP, On Demand and pre-charge models;

1.NetSuite's leadership and practice in SaaS: NetSuite's SaaS business model management provides the best practice, and its PaaS development platform lays the foundation for PingCAP's seamless interaction between the business middle-office and the front-office's large data volume;

2. Hitpoint's professional support and implementation services: Hitpoint, with rich experience in Internet technology and SaaS, provided full consulting support for PingCAP's pre-sales phase of the project in terms of discussing the through solution, transforming the middle-office, confirming the revenues of the five models, and reaching a consensus among various departments, and ensured professional implementation and landing services in the later phase.