ediation system has to collect data from multiple network elements and on the business modules side the mediation system has to interact with multiple billing and business support solutions. The mediation system should be designed to provide easy integration with its interacting modules. Use of standard and published inter- faces can reduce the implementation overhead, however in most cases there will be multiple interfaces defined by standardizing bodies and the mediation system, and hence may have to support multiple interface standards or have adapters to work with different solutions. Heterogeneous infrastructure: The scale and diversity of network elements is continuously increasing with new technical innovations. The mediations systems have to support aggregation and correlation of billing records on the new elements in the network. Most next generation networks have a new billing defined by standardizing bodies, which the mediation system has to adapt while formatting the records. Complex validation checks: There can be scenarios where correction is required for inconsistent formats, access, and semantics. Identification of these issues and fixing them are not straight forward and will require intelli- gent algorithms. The mediation system should be designed to handle multiple records in parallel to ensure that maximum processing is performed to sup- port real-time billing. Rich information records: The information content in the records is quite huge compared to the actual billable usage information. The additional information is mainly for debugging and validation purposes. The media- tion systems should filter out relevant data based on predefined rules. When new record formats are introduced, the filtering logic needs to be updated to ensure that these records are not omitted as error records. The validation, filtering, and formatting logic is usually implemented to work together to ensure that there are minimum iterations performed on the records there by increasing performance and decreasing processi