KA Pricing is a process to setup pricing to charge our key accounts (corporates). There are many types of fees, many rules to define what unit to charge and calculation formulas. You can take a look at t
to understand existing Pricing Structure, but there are some key points:
The current human flow: KA team deal pricing with customers, then update pricing into a data table, with confirmation from FA team on 1Office → Effect: Unable to track/control pricing change in database, unable to adit/verify logic
The data flow: each KA invoice is calculated via metabase query based on some common template, but the formula is hard coded in SQL query. While the sql and pricing configuration is somehow transparent, it is still hard to understand logic from external view except the author.
Human process: We suggest a new one-way flow: KA deal with external customers and inform FA team via 1Office with defined template & provided data → FA verify logic, update database (via admin page) and confirm on 1Office with defined response template to end the process.
Data flow: OpsTech team will build a standard data structure + standard query template + standard processing flow. KA will build custom query, FA will control pricing configuration, and OpsTech will do data processing