Different customers, they confidently hand over the order to overseas Chinese, how can overseas Chinese make them feel at ease? For different businesses, which nodes do customers care about, and how do we feed them back quickly and accurately? Did the inspection pass? When will the ship lean? The free cabinet period is coming tomorrow. Can it be lucky today? And so on, did you mention the customer concerns?

In 2016, our company will fully implement the accrual basis. Finance staff receive piles of payment requests every day, and constantly review them back to the source. The workload of the finance department and the business department in checking the application can be imagined. Then, can we sort out all the nodes that generate costs according to the accrual basis and discuss whether the rules of this node are applicable to automatic billing? If automatic billing is realized, is it necessary to check business data and payment application documents continuously? In addition, to open a "reconciliation bill" to the customer, the customer needs to reconcile according to the business format, the disputed point to put forward the voucher requirements, the bank pays the "water bill" and "reconciliation bill" bundled, in the customer information system to achieve payment cancellation. Imagine a scenario in which our company regularly publishes "reconciliation bills" in customer format on the Internet. Customers can download electronic versions and import automated reconciliation of customer information systems. And transfer payment. Win win benefits, everything is possible

LFS is based on all types of business, all stakeholders, and all regional offshore companies to set up the relevant basic data and system architecture. For the same entity relationship, different departments have different opinions. How to identify the system? In addition, the contract rates and business processes of foreign companies are slightly different from those of Guangzhou. Should we consider the system requirements as a whole? Based on the same set of basic codes and rates, does it need bilateral billing, reconciliation and cancellation? How to realize unilateral billing and unilateral cancellation?

Professionals recommend that when it comes to system requirements, think about how you can be "lazy" while meeting regulatory requirements. The field department can imagine "running outside in the daytime and returning to the recording system in the evening, so can you enter relevant information in the field through the mobile phone and send it back to the PC side of the system?" The staff in the office can think, "If different leaders ask me to give different reports, can I submit templates for different reports to the developers, and then generate different reports with only one total entry?" The dispatcher can imagine that "customer service, warehouse, fleet and operator have been asking the same thing, can the system have an interface to display the required shared information, so that people do not have to communicate information back and forth?"