Real-time ERP Billing Processing via Virtual Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
ERP platforms face inefficiencies in processing billing records at scale, particularly when dealing with large volumes of data or reprocessing requirements, leading to prolonged processing times and wastage of computing resources due to the resource-related billing method.
Innovation Solution
The introduction of a real-time billing application that processes ERP transaction records in real-time, allowing users to configure trigger events for processing transactions, creating virtual tables, and generating editable billing items, which can be reviewed and updated as needed, thereby distributing processing over the billing period.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If resource-related billing (RRB) method is used to process billing records, then billing data can be stored and processed systematically, but processing time increases significantly and system performance degrades when handling large volumes of records
Solution Approach 1:
The patent segments the billing processing task by introducing a trigger event mechanism that divides processing into multiple small transactions throughout the billing cycle rather than processing all records at once. Each trigger event processes only the necessary subset of records, breaking the monolithic processing task into manageable segments that reduce system overload and processing time.
Solution Approach 2:
The patent implements preliminary action by creating virtual tables and pre-processing billing data as transactions occur during the billing cycle. Trigger events activate processing in advance of the final billing deadline, allowing the system to prepare billing records incrementally rather than facing a sudden processing burden at cycle end.
2Manufacturing precision
If all billing data is reprocessed when pricing modifications are needed, then data accuracy is maintained, but computing resources are wasted on duplicative operations
Solution Approach 1:
The patent extracts only the necessary subset of billing records that require reprocessing when pricing modifications occur. The trigger event mechanism identifies and isolates specific transactions affected by pricing changes, allowing the system to reprocess only those records rather than redundantly processing entire billing datasets, thus maintaining accuracy while conserving computing resources.
Solution Approach 2:
The patent applies local quality by implementing selective reprocessing based on transaction-specific criteria. Different portions of the billing data receive different treatment - only those records matching the pricing modification criteria are reprocessed, while other records remain unchanged. This localized approach maintains data accuracy where needed without wasting resources on unnecessary duplicative operations elsewhere.
3Extent of automation
If ERP platforms process billing records individually at cycle end, then systematic processing is achieved, but system bottleneck occurs and performance deteriorates with large record volumes
Solution Approach 1:
The patent implements continuity of useful action by distributing billing processing continuously throughout the billing cycle via trigger events rather than concentrating it at cycle end. Automated processing occurs incrementally as transactions are posted and trigger events are activated, maintaining steady system throughput and preventing bottlenecks while preserving automation benefits.
Data Source
AI summary
Systems and methods are described for processing billing transactions from an Enterprise Resource Planning (“ERP”) system. In an example, when a new transaction posts to an ERP database, the ERP system creates a first virtual table with data related to the transaction. An application queries the ERP's database to create a second virtual table based on the first virtual table based on preconfigured criteria. Using the second virtual table, the application creates an editable billing item with all the data for billing the particular transaction type of the transaction. The editable billing items can be stored until the end of the billing period. At final billing, the application aggregates data from the editable billing items of each transaction type and sends the aggregated data to the ERP system for final billing. Prior to final billing, the editable billing items can be edited or changed as needed.