Vendor invoice based billing experience (VIBBE) architecture system and method

Abstract

20 26 20 47 01 17 J un 2 02 6 2 0 2 6 A B S T R A C T 2 0 2 6 2 0 4 7 0 1 1 7 J u n 2 0 2 6 A B S T R A C T 2 0 2 6 2 0 4 7 0 1 1 7 J u n

Description

BACKGROUND

[0001] Billing and invoicing for partners in conventional cloud architecture hosting Software as a Service (SaaS) models involve numerous manual operations and complex processes. Typically, these platforms must handle various billing schemes from different vendors, such as subscription-based, usage-based, or hybrid models. Managing these billing schemes requires multiple operations to calculate final invoice data, which is then supplied to resellers' Enterprise Resource Planning (ERP) systems for further processing.

[0002] Conventional processes encounter several challenges. Many tasks related to invoice data management, such as verification and reconciliation, are performed manually. This manual intervention is time-consuming and prone to errors. Additionally, managing the billing for various vendors, each with their own unique pricing models and contract terms, adds a layer of complexity that further increases the likelihood of inaccuracies. The manual handling of these processes often requires significant time and resources, especially when dealing with large volumes of transactions and multiple currencies.

[0003] Moreover, there is a lack of integration between the different systems used for billing, provisioning, and subscription management. This lack of integration results in fragmented workflows, where data must be manually transferred and reconciled between systems. Such fragmentation leads to inefficiencies and delays in the billing cycle. It also hinders the ability to provide real-time can update on subscription statuses and accurate billing information to partners and resellers. 2026204701   17 Jun 2026

[0004] Moreover, conventional processes are challenged in accommodating changes in subscriptions, such as upgrades, downgrades, or cancellations, within the billing cycle. Manual adjustments are often required to reflect these changes, which can result in delayed or incorrect billing. Additionally, the absence of automated tools to handle complex billing rules, such as prorations and discounts, further complicates the billing process.

[0005] These issues highlight the need for an automated solution that can address the complexities of vendor billing, reduce manual intervention, and enhance the overall efficiency of the billing process. BRIEF SUMMARY OF THE INVENTION

[0006] Embodiments described herein provide systems and methods for automating vendor invoice-based billing experiences (VIBBE) in a cloud architecture, enhancing the efficiency and accuracy of billing processes. The described solution relates to the subscription business only, such as through integration with, for example, the XVS XVANTAGE subscription engine or similar subscription architectures. These embodiments address the complexities and inefficiencies of conventional billing systems by integrating automated processes and advanced computational methodologies.

[0007] In some embodiments, the system can include a vendor product onboarding module configured to receive and integrate vendor product catalogs into the cloud architecture. This module can support various file formats and converts them into a standardized format for integration into the product catalog system. The product catalog system consolidates vendor and sales catalog information, ensuring a comprehensive overview of available products. 2026204701   17 Jun 2026

[0008] A pricing engine can manage and applies pricing rules, margins, and discounts to the products. The pricing engine dynamically adjusts pricing based on real-time data inputs, such as currency conversions and regional pricing variations. It can support different types of margins, including default program margins, custom item-specific margins, reseller-specific margins, and deal-specific margins.

[0009] The system also can include an ordering system that can process sales orders from resellers. This system is designed to handle high volumes of concurrent order submissions, ensuring efficient processing and accurate order management. Orders can be placed through the cloud architecture’s UI or via custom API integrations.

[0010] A subscription management system can manage subscription data and provisioning requests. This system synchronizes subscription states with the vendor’s system, reflecting changes such as renewals, cancellations, and upgrades. It can manage the entire lifecycle of a subscription, from creation to termination, and ensures that all can update are accurately reflected across the platform.

[0011] The vendor connector interfaces with vendor systems to parse vendor invoices and generate usage data records. It can employ advanced parsing algorithms to extract relevant data fields from vendor invoices and format them into vendor-rated data (VRD). The vendor connector enables integration and communication between the cloud architecture and the vendor systems.

[0012] The guiding system can process the VRD to create detailed usage data records (UDRs). These records are essential for accurate billing calculations and are sent to the subscription management system for further processing. The guiding system can provide a mechanism for supporting data integrity and availability for subsequent billing calculations. 2026204701   17 Jun 2026

[0013] A rating engine calculates total contract value (TCV) and total contract cost (TCC) based on subscription data and usage records. It applies sophisticated algorithms to perform these calculations, considering various billing models and forecasting methods. The rating engine interfaces with the subscription management system for subscription history and the pricing engine for pricing details.

[0014] The finance / ERP system can generate and issues reseller invoices based on the calculated charges. It can generate detailed financial reports and invoices, ensuring that all charges reflect the latest usage and pricing information. This system can support multiple accounting standards and can provide customizable reporting templates to meet diverse business requirements.

[0015] For example, the vendor product onboarding module can receive and integrate various file formats into a standardized product catalog. The pricing engine can dynamically adjust pricing and discounts based on real-time data inputs, ensuring accurate and up-to-date pricing information. The ordering system can handle high volumes of concurrent order submissions, providing efficient and reliable order processing.

[0016] In some embodiments, the vendor product onboarding module can support multiple file formats, including CSV, XML, and JSON, and converts them into a standardized format for integration into the product catalog. The pricing engine dynamically adjusts pricing and discounts based on real-time data inputs, including currency conversions and regional pricing variations, and can manage various types of margins, such as program, item-specific, resellerspecific, and deal-specific margins. The ordering system can process high volumes of concurrent orders, ensuring efficient and reliable order management. The subscription management system synchronizes subscription states with vendor systems in real-time, Page 4 of 34 2026204701   17 Jun 2026 managing the entire lifecycle of a subscription from creation to termination. The vendor connector can employ advanced parsing algorithms to extract relevant data fields from vendor invoices and format them into vendor-rated data (VRD). The guiding system can process VRD to create detailed usage data records (UDRs), ensuring data integrity and availability for billing calculations. The rating engine applies sophisticated algorithms to calculate TCV and TCC, considering various billing models and forecasting methods. The finance / ERP system can generate detailed financial reports and invoices, supporting multiple accounting standards and customizable reporting templates.

[0017] In some embodiments, a computing device can execute instructions to manage and apply pricing rules, margins, and discounts, process sales orders, manage subscription data, and handle provisioning requests. The computing device can also interface with vendor systems to parse vendor invoices, generate usage data records, and calculate TCV and TCC. The finance / ERP system can then generate and issue reseller invoices based on these calculations.

[0018] In some embodiments, the computing device can dynamically adjust pricing based on real-time data inputs, such as currency conversions and regional pricing variations. It can handle high volumes of concurrent order submissions and synchronize subscription states with the vendor’s system, reflecting changes such as renewals, cancellations, and upgrades.

[0019] In some embodiments, a computerized methodology can interface with vendor systems to parse vendor invoices, generate usage data records, and calculate TCV and TCC. The finance / ERP system can then generate and issue reseller invoices based on the calculated charges, significantly reducing manual intervention and improving overall billing accuracy. 2026204701   17 Jun 2026

[0020] Overall, these embodiments provide a comprehensive solution for automating vendor invoice-based billing experiences, addressing the complexities of conventional billing systems, and enhancing the efficiency and accuracy of billing processes within cloud-based SaaS platforms. BRIEF DESCRIPTION OF THE DRAWINGS / FIGURES

[0021] FIG. 1A is an illustration of a system and operational environment for automating vendor invoice-based billing experiences (VIBBE), according to some embodiments.

[0022] FIG. 1B is an illustration of a system for automating VIBBE, according to some embodiments.

[0023] FIG. 2 is an illustration of a system for calculating Total Contract Value (TCV) and associated billing details for VIBBE, according to some embodiments.

[0024] FIG. 3 is an illustration of a system for automating Vendor Invoice Processing and Integration module within the VIBBE system, according to some embodiments.

[0025] FIG. 4 is an illustration of embodiments of a system for the synchronization and update process of subscription states within the VIBBE system, according to some embodiments.

[0026] FIG. 5 is a flow diagram of a method for automating vendor invoice-based billing experiences (VIBBE) in a cloud architecture, according to some embodiments.

[0027] FIG. 6 is a block diagram of the example components of a device, illustrating the processor, memory, and communication interfaces used to implement the system, according to some embodiments. 2026204701   17 Jun 2026 DETAILED DESCRIPTION OF THE INVENTION

[0028] Embodiments may be implemented in hardware, firmware, software, or any combination thereof. Embodiments may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a machine-readable medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices, and others. Further, firmware, software, routines, instructions may be described herein as performing certain actions. However, it should be appreciated that such descriptions are merely for convenience and that such actions in fact result from computing devices, processors, controllers, or other devices executing the firmware, software, routines, instructions, etc.

[0029] It should be understood that the operations shown in the exemplary methods are not exhaustive and that other operations can be performed as well before, after, or between any of the illustrated operations. In some embodiments of the present disclosure, the operations can be performed in a different order and / or vary.

[0030] FIG. 1A depicts a conceptual architecture of the VIBBE system, a cloud-based architecture designed to automate vendor invoice-based billing, order management, and subscription processing. The system enables resellers to place and manage orders, vendors to onboard and distribute products, and the platform to handle pricing, provisioning, and financial transactions efficiently. 2026204701   17 Jun 2026

[0031] In some embodiments, the system workflow begins The VIBBE system is a cloud-based platform designed to streamline vendor invoice-based billing, order management, and subscription processing. The process begins with Vendor 1 submitting a Vendor Catalog, which includes vendor costs and MSRP details. The Vendor Product Onboarding Experience 2 standardizes and integrates this catalog, pulling data from external sources such as the Ingram Micro Sales Catalog. Once the catalog is processed, it is supplied to the Product Catalogue 3, ensuring all product details remain consistent across the system. The catalog data is then passed to the Pricing and Costs 4 module, which manages sales margin, markup, and optional price terms. The vendor-defined costs and MSRPs are automatically transferred to the pricing system to enable automated pricing adjustments.

[0032] Resellers interact with the system through the Reseller Ordering Experience 6, where they can create new reseller orders or modify existing subscriptions. These orders are processed by the Ordering System 7, which receives the reseller’s request and communicates with Subscription Management 8 to manage the associated subscription. The Provisioning System 9 receives provisioning requests and forwards them to the Vendor Connector 10, which is responsible for interfacing with the vendor’s system. The Vendor Connector 10 submits provisioning requests to the vendor and retrieves subscription details and subscription status changes, which are then transmitted back to Subscription Management 8 for real-time updates.

[0033] Once the vendor completes an order, the Vendor Connector 10 processes the Vendor Invoice, which is parsed into Itemized Vendor Invoice Data and forwarded to the Guiding System 13. The Guiding System 13 creates and stores Usage Data Records (UDRs), which are transmitted to Subscription Management 8. Upon receiving the usage records, Page 8 of 34 2026204701   17 Jun 2026 Subscription Management 8 triggers the Rating Engine 11 to process the updated data and calculate charges. The Rating Engine 11 retrieves subscription history from Subscription Management 8, processes usage data records, and calculates Total Contract Value (TCV) and Total Contract Cost (TCC). It also applies sales margin and markup calculations to determine final pricing adjustments.

[0034] Once the pricing calculations are completed, Rating Engine 11 transmits invoice AP / AR (accounts payable / accounts receivable) BITs (billing information) to Finance / ERP System 12, which generates the corresponding reseller invoices. The Finance / ERP System 12 issues reseller invoices based on the finalized charges, ensuring that reseller payments reflect usage-based adjustments and pricing markups. The invoice is then sent to the Reseller 5, completing the transaction.

[0035] Throughout this process, Subscription Management 8 continuously updates subscription details, ensuring that the reseller has real-time access to order changes. The Vendor Connector 10 facilitates vendor-specific integrations, ensuring that provisioning requests and invoice processing remain seamless. The Guiding System 13 processes vendor invoices into structured usage data, allowing the Rating Engine 11 to recalculate pricing dynamically. The Finance / ERP System 12 ensures that financial reconciliation remains accurate by aligning reseller invoices with vendor invoice data.

[0036] The VIBBE system is designed to support dynamic pricing models, automated subscription tracking, and real-time order adjustments. The architecture ensures seamless financial reconciliation, reducing manual intervention and increasing operational efficiency for vendors, resellers, and platform administrators. By integrating pricing automation, real- 2026204701   17 Jun 2026 time subscription management, and vendor invoice processing, the system provides a scalable and accurate billing solution for cloud-based subscription services.

[0037] FIG. 1B illustrates system 100 for automating VIBBE. System 100 builds upon the above VIBBE architecture to streamline the billing process for cloud-based SaaS platforms by automating the integration and processing of vendor invoices.

[0038] System 100 can include Vendor 110, which initiates the process by onboarding the Vendor Catalog to the cloud architecture. This catalog comprises a list of vendor products and their attributes, which are supplied to Vendor Product Onboarding Module 120 via platform API or UI. Vendor Product Onboarding Module 120 allows vendors to manage their products within the cloud architecture’s product catalog.

[0039] The Vendor Product Onboarding Module 120 automatically processes various file formats containing vendor catalog data, converting them into a standardized format compatible with the cloud architecture. This integration ensures that all product attributes, such as pricing, descriptions, and metadata, are accurately captured and updated in the Product Catalog 130. Vendor Product Onboarding Module 120 can process file formats including one or more of CSV, XML, and JSON file formats and wherein convert the multiple file formats into a standardized format for integration into the product catalog such that all product attributes are captured and updated.

[0040] The integrated product catalog information is processed by Pricing and Costs module 140 to manage pricing and discount configurations. Product Catalog 130 consolidates vendor and sales catalog information, providing a comprehensive overview of products available on the platform. In some embodiments, Pricing and Costs module 140 automatically can receive vendor-defined costs and MSRPs. It can manage pricing and discounts based on Page 10 of 34 2026204701   17 Jun 2026 pre-configured rules and algorithms, ensuring up-to-date pricing information for all products. Pricing and Costs module 140 can automatically calculate TCV and TCC by interfacing with the Subscription Management Module for subscription history and the Product Catalog for pricing details. These calculations are performed without manual input to ensure accurate billing. Pricing and Costs module 140 dynamically adjusts pricing and discounts based on realtime data inputs. This module is programmed to handle complex pricing rules, including currency conversions, regional pricing variations, and time-based promotional discounts.

[0041] Pricing and Costs module 140 can receive vendor-defined costs and MSRPs, enabling automated price and discount management. Reseller 150 interacts with system 100 by creating sales orders through Ordering System 170 via the cloud architecture’s UI or a custom API integration. Ordering System 170 can provide a real-time interface for resellers to place orders, view subscription statuses, and apply changes. Reseller orders are created and processed automatically through the Ordering System 170. Orders are submitted via the cloud architecture’s UI or API and are managed by the Ordering System. The Ordering System 170 is designed to handle high volumes of concurrent order submissions, ensuring efficient and error-free processing. Orders are automatically processed and submitted to Ordering System 170.

[0042] Ordering System 170 processes the sales orders, interfacing with Subscription Management System 180 to manage subscription-related information. Subscription Management System 180 continuously synchronizes subscription states with the vendor's system via Vendor Connector 195. This synchronization ensures that any changes in subscription status, such as renewals, cancellations, or upgrades, are accurately reflected in both the vendor and cloud architecture systems. This system can manage provisioning requests Page 11 of 34 2026204701   17 Jun 2026 by communicating with Provisioning System 190. In some embodiments, Subscription Management Module 180 can manage all subscription-related information, including creation, modification, and cancellation of subscriptions. It also processes provisioning requests and maintains subscription history.

[0043] Provisioning System 190 can send provisioning requests to Vendor Connector 195, which interacts with the vendor's system to confirm the provisioning process. Provisioning System 190 automates the entire provisioning workflow, from receiving requests to confirming service activation. The system uses predefined workflows and API integrations with the Vendor Connector 195 to perform service provisioning. Once confirmed, Vendor Connector 195 can update the Provisioning System 190. Vendor Connector 195 can interface with the vendor’s system to process provisioning requests, receive vendor invoices, and parse invoice data. It enables integration and communication between the cloud architecture and the vendor. Vendor invoices can be processed by Vendor Connector 195, which parses and itemizes the invoice data. This data is converted into Usage Data Records and sent to the Subscription Management System.

[0044] Vendor Connector 195 ensures the communication and integration of vendor specific processes, enabling can update to the Provisioning System 190 and Subscription Management System 180. Subscription Management System 180 can update Ordering System 170 with sales order completion confirmation, triggering Pricing and Costs module 140 to calculate Total Contract Value (TCV) and Total Contract Cost (TCC). Vendor Connector 195 can employ advanced parsing algorithms to break down vendor invoices into individual line items. These items are then converted into Usage Data Records, which are processed and stored in the Subscription Management Module 180. Subscription Management Module 180 can Page 12 of 34 2026204701   17 Jun 2026 automatically process usage data records and trigger Pricing and Costs module 140 to recalculate charges based on the latest vendor usage data.

[0045] Pricing and Costs module 140 performs these calculations by interfacing with Subscription Management System 180 for subscription history and Product Catalog 130 for pricing details. The calculated TCV / TCC values are returned to Ordering System 170, which then can update the cloud architecture’s UI for display to the reseller. Pricing and Costs module 140 can employ sophisticated algorithms to calculate TCV and TCC. These calculations consider various billing models, including usage-based and subscription-based schemes, ensuring accurate financial projections and revenue recognition.

[0046] Vendor 110 invoices the cloud architecture, sending the Vendor Invoice to Vendor Connector 195. Vendor Connector 195 processes the invoice, parsing and itemizing the invoice data, and providing Usage Data Records to Subscription Management System 180.

[0047] Subscription Management Module 180 processes these records and can trigger Pricing and Costs module 140 to recalculate charges based on vendor usage data. These recalculations are sent to Ordering System 170, which can update the reseller invoices accordingly. The system automatically can generate reseller invoices based on the recalculated charges and can send them to the resellers.

[0048] This automation significantly reduces manual intervention, enhances accuracy, and can support various billing models, providing a scalable solution for managing complex cloudbased billing operations. VIBBE system 100 automatically can manage adjustments resulting from vendor-initiated changes, such as invoice corrections or subscription modifications. These adjustments are processed in real-time, ensuring that all stakeholders have up-to-date information. 2026204701   17 Jun 2026

[0049] VIBBE System 100 can be connected operatively to CRM / ERP and other finance systems to generate detailed financial reports, including reseller invoices and vendor payments. The system can support multiple accounting standards and can provide customizable reporting templates to meet diverse business requirements.

[0050] In some embodiments, the VIBBE system may include configurable logic for selecting among different billing and pricing calculation strategies based on vendor capabilities, system configuration, or business requirements. For example, a subscription engine may expose a configurable control, such as a “Use External Pricing” setting, that enables dynamic selection between internal pricing algorithms and vendor-supplied pricing inputs. The system may implement multiple techniques for calculating or estimating Total Contract Value (TCV) and Total Contract Cost (TCC), including direct application of markup to vendor-provided costs or MSRPs, predictive modeling based on historical usage patterns, or real-time derivation of pricing based on order metadata or invoice records. In some implementations, the system may also support hybrid strategies that combine order- and invoice-based data to reconcile pricing inputs across asynchronous billing events. These capabilities enable the platform to support a wide range of billing models—such as subscription-based, usage-based (e.g., PAYG), or mixed-mode billing—without structural changes to the core architecture.

[0051] VIBBE system 100 is configured with a scalable architecture, supporting horizontal scaling to accommodate increasing transaction volumes and expanding vendor integrations. The architecture leverages cloud-native technologies to ensure high availability and fault tolerance. The system incorporates robust security measures, including data encryption, access controls, and compliance with industry standards (e.g., GDPR, HIPAA). These measures Page 14 of 34 2026204701   17 Jun 2026 ensure that sensitive financial and subscription data is protected against unauthorized access and breaches. System 100 facilitates customization of business rules and workflows to meet specific vendor and reseller requirements. This flexibility ensures that the platform can adapt to diverse business models and operational processes.

[0052] FIG. 2 illustrates System 200 for calculating Total Contract Value (TCV) and associated billing details for vendor invoice-based billing experiences (VIBBE). System 200 is designed to automate the pricing, margin application, and total cost calculations for subscriptions managed within a cloud architecture.

[0053] System 200, as described in FIG. 2, can be an embodiment of Pricing and Costs module 140 described above. Module 200 can be configured to calculate Total Contract Value (TCV), Total Contract Cost (TCC), and other pricing details essential for billing and financial management within the VIBBE system.

[0054] As described above, Pricing and Costs module 140 can receive vendor-defined costs and MSRPs, manage pricing and discounts, and interface with other components such as Product Catalog 130, Ordering System 170, and Subscription Management System 180to ensure accurate and dynamic pricing.

[0055] As shown in FIG. 2, System 200 further elaborates on these functionalities by detailing the specific processes and sub-components involved in calculating TCV and associated billing details, including Cost Calculation Module 220, Pricing Engine 230, Margin Management Module 240, TCV Calculation Engine 250, Billing Period Alignment Module 260, Contract Value Estimator 270, Total Price Calculation Module 280, and Reporting Engine 290. System 200 is configured to automate and optimize the pricing and billing processes, ensuring precise cost calculations and financial reporting. 2026204701   17 Jun 2026

[0056] System 200 interacts with Vendor System 110, which can provide the initial input data for TCV calculation. This data can include items (SKUs), cost per item, subscription period, and billing period. These inputs are essential for accurately determining the financial metrics associated with each subscription.

[0057] Cost Calculation Module 220 can receive input data from Vendor System 110 and calculates the cost per item based on the specified billing period and subscription period. This module can support various billing models, such as per billing period, per subscription period, or custom billing cycles, ensuring flexibility in cost calculations.

[0058] Pricing Engine 230 integrates the calculated costs with predefined pricing rules. It applies margins, markups, and discounts to the base costs to determine the final price per item. This engine can handle default program margins, custom item-specific margins, resellerspecific margins, and deal-specific margins, ensuring accurate pricing across different scenarios. The pricing engine can dynamically adjust pricing and discounts based on real-time data inputs, including currency conversions and regional pricing variations. It can support different types of margins, including default program margins, custom item-specific margins, reseller-specific margins, and deal-specific margins, ensuring accurate and up-to-date pricing information

[0059] Margin Management Module 240 is responsible for managing the different types of margins that can be applied to the costs. In some non-limiting examples, Margin Management Module 240 determines one or more margin types, such as: Margin per program (default), Margin per item (custom), Margin per reseller, Margin per deal, etc.

[0060] TCV Calculation Engine 250 consolidates the pricing information and applies the relevant margins to calculate the Total Contract Value for each subscription. In some nonPage 16 of 34 2026204701   17 Jun 2026 limiting examples, TCV Calculation engine 250 can support various TCV calculation methods, including: Simple cost multiplication for fixed-term contracts, Forecasting based on historical usage data, Estimation using product tiers and remaining contract terms, etc.

[0061] Billing Period Alignment Module 260 ensures that all cost calculations are aligned with the appropriate billing periods. It can manage proration based on different denominators, such as the number of days in the start month, end month, or entire billing period, ensuring precise cost distribution across billing cycles.

[0062] Contract Value Estimator 270 uses the output from the TCV Calculation Engine 250 to provide a comprehensive estimate of the total contract value. This estimator can support different forecasting methods, such as moving averages and linear regression, to predict future costs and revenues based on past usage trends.

[0063] Total Price Calculation Module 280 consolidates all the calculated values to provide the final total price per deal. This module integrates the calculated TCV, applied margins, and any additional costs or discounts to present a complete financial overview of each subscription deal.

[0064] Reporting Engine 290 can generate detailed financial reports, including total price per deal and overall TCV for all active subscriptions. These reports are used for revenue recognition, financial planning, and analytics, providing valuable insights into the financial performance of the cloud architecture.

[0065] System 200 is thereby configured to perform automated processes involved in calculating TCV and associated billing details within the VIBBE system, highlighting the system's capability to manage complex billing scenarios and provide accurate financial metrics. 2026204701   17 Jun 2026

[0066] FIG. 3 illustrates system 300 for automating Vendor Invoice Processing and Integration module within the VIBBE system. System 300 automates end-to-end processes for handling vendor invoices, parsing involved data, and integrating this information into the cloud architecture for accurate billing and subscription management. System 300 can include components 310 to 390.

[0067] System 300 can include Vendor System 110, which issues invoices to the cloud architecture. These invoices contain detailed information about the services provided, including item descriptions, quantities, prices, and usage data.

[0068] Vendor Invoice 320 may be an actual document or digital file sent by Vendor System 110. This invoice is received by Vendor Connector 330, which serves as the interface between the vendor and the cloud architecture.

[0069] Vendor Connector 330 parses the Vendor Invoice 320 using advanced parsing algorithms to extract relevant data fields such as itemized charges, service periods, and quantities. This data is then formatted into a standardized structure known as Vendor Rated Data (VRD).

[0070] System 300 can receive the parsed VRD from Vendor Connector 330, which can be an embodiment of Vendor Connector 195. Invoice Processing Module 340 processes this data to create Usage Data Records (UDRs), which detail the consumption of each service item listed in the invoice. Usage Data Records (UDRs) 350 are generated by Guiding System 340 and can contain comprehensive information about service usage. These records are communicated to Subscription Management System 360 and support subsequent billing calculations. 2026204701   17 Jun 2026

[0071] Subscription Management System 360 can update the subscription records based on the UDRs received. Subscription Management System 360, which can be an embodiment of Subscription Management System 180, ensures that the subscription details reflect the most current usage data, enabling accurate billing and reporting.

[0072] Rating Engine 370 interfaces with Subscription Management System 360 to obtain updated subscription and usage data. Rating Engine 370 can be an embodiment of Rating Engine 190, configured to recalculate charges based on the latest UDRs and apply the appropriate pricing rules, margins, and discounts.

[0073] Billing Recalculation Module 380, part of Rating Engine 370, ensures that any changes in usage data trigger a recalculation of the Total Contract Value (TCV) and Total Contract Cost (TCC). This module can dynamically adjust the billing amounts based on realtime data inputs.

[0074] CRM / ERP System 390 can receive the recalculated billing data from Rating Engine 370. It can generate and can send updated reseller invoices, ensuring that all charges reflect the latest usage and pricing information.

[0075] System 300 thereby automates processes involved in handling and integrating vendor invoices within the VIBBE system. It highlights the system's ability to automate the parsing, processing, and updating of subscription and billing information based on vendor-supplied data, ensuring accuracy and efficiency in financial management. System 300 automatically processes vendor invoices and integrates with billing and subscription management workflows of the VIBBE system.

[0076] It should be understood that the operations shown in the exemplary methods are not exhaustive and that other operations can be performed as well before, after, or between any of Page 19 of 34 2026204701   17 Jun 2026 the illustrated operations. In some embodiments of the present disclosure, the operations can be performed in a different order and / or vary.

[0077] FIG. 4 illustrates an arrangement of a System 400 for the synchronization and update process of subscription states within the VIBBE system, according to some embodiments. System 400 is configured to ensure that subscription records on both the vendor's side and the cloud architecture’s side remain consistent, reflecting any can update or changes accurately and in real-time.

[0078] System 400 can include Vendor System 410, which maintains the original subscription records (A). These records include details such as subscription start and end dates, renewal flags, billing periods, and any changes made by the vendor. Vendor Connector 430 interfaces with Vendor System 410 to detect any can update or changes to subscription records. Upon detecting a change, Vendor Connector 420 can generate an Adjustment Request 440 in Connect Platform 420.

[0079] Connect Platform 420 can process Adjustment Request 440 to update the mirrored subscription record (B2) on the cloud architecture. This involves applying changes such as new subscription dates, modified renewal flags, and adjusted billing periods to Subscription Management Module 450. Subscription Management Module 450, which maintains the subscription record (B1) matching the reseller’s expectations, can receive can update from Connect Platform 420. It ensures that any changes are accurately reflected, maintaining consistency between the reseller's view and the vendor's records.

[0080] Billing Event Notification 460 is triggered by Connect Platform 420 to inform Subscription Engine 470 about the can update. Subscription Engine 470 can update the subscription record (B1) accordingly, ensuring synchronization with the vendor’s system. 2026204701   17 Jun 2026 For changes initiated by Subscription Engine 470 as part of the Ordering / Provisioning process, the flow can include creating an Order for changes, updating pending requested changes, creating a provisioning request, and provisioning the changes through Vendor Connector 430.

[0081] FIG. 5 illustrates a method 500 for automating vendor invoice-based billing experiences (VIBBE) in a cloud architecture. The method comprises several key steps to streamline the integration and processing of vendor invoices, ensuring accurate and efficient billing and subscription management. Based on the disclosure herein, operations in method 100 can be performed in a different order and / or vary.

[0082] The method begins at operation 510, where vendor product catalogs are received and integrated into the product catalog system. This operation involves using a vendor product onboarding module to support multiple file formats and convert the vendor catalog data into a standardized format for integration.

[0083] At operation 520, the method proceeds to managing and applying pricing rules, margins, and discounts using a pricing engine. The pricing engine dynamically adjusts the pricing based on real-time data inputs, such as currency conversions and regional pricing variations.

[0084] In operation 530, the method involves processing sales orders from resellers through an ordering system. The ordering system is designed to handle high volumes of concurrent order submissions, ensuring efficient processing and accurate order management.

[0085] Operation 540 focuses on managing subscription data and provisioning requests via a subscription management system. This system synchronizes subscription states with the vendor’s system, reflecting changes such as renewals, cancellations, and upgrades in real-time. Page 21 of 34 2026204701   17 Jun 2026

[0086] At operation 550, the method interfaces with vendor systems to parse vendor invoices and generate usage data records using a vendor connector. The vendor connector can employ advanced parsing algorithms to extract relevant data fields from vendor invoices and format them into vendor-rated data (VRD).

[0087] Operation 560 involves processing usage data records with a guiding system. The guiding system can process the VRD to create detailed usage data records (UDRs) that are essential for accurate billing calculations.

[0088] In operation 570, the method calculates total contract value (TCV) and total contract cost (TCC) based on subscription data and usage records using a rating engine. The rating engine applies programmed computational routines to determine TCV and TCC based on predefined billing models and configurable forecasting parameters. In some examples, these routines may include multi-variable pricing formulas and estimation logic that are tailored to reflect vendor-specific pricing schemes and usage trends. Forecasting may be performed using algorithmic approaches such as rule-based extrapolation, regression analysis, analog-based estimation, or other programmable statistical or optimization techniques. In some embodiments, the forecasting module may include adaptive logic for selecting or weighting different models based on historical performance or parameter thresholds.

[0089] Finally, operation 580 encompasses generating and issuing reseller invoices based on the calculated charges through a finance / ERP system. The finance / ERP system can generate detailed financial reports and invoices, ensuring that all charges reflect the latest usage and pricing information. 2026204701   17 Jun 2026

[0090] Method 500 automates the vendor invoice-based billing process providing integration and processing mechanisms that ensure accurate, efficient, and scalable billing operations within a cloud architecture.

[0091] FIG. 6 is a block diagram of example components of device 600. One or more computer systems 600 may be used, for example, to implement any of the embodiments discussed herein, as well as combinations and sub-combinations thereof. Computer system 600 may include one or more processors (also called central processing units, or CPUs), such as a processor 604. Processor 604 may be connected to a communication infrastructure or bus 606.

[0092] Computer system 600 may also include user input / output device(s) 603, such as monitors, keyboards, pointing devices, etc., which may communicate with communication infrastructure 606 through user input / output interface(s) 602.

[0093] One or more processors 604 may be a graphics processing unit (GPU). In an embodiment, a GPU may be a processor that can be a specialized electronic circuit configured to process mathematically intensive applications. The GPU may have a parallel structure that can be efficient for parallel processing of large blocks of data, such as mathematically intensive data common to computer graphics applications, images, videos, etc.

[0094] Computer system 600 may also include a main or primary memory 608, such as random access memory (RAM). Main memory 608 may include one or more levels of cache. Main memory 608 may have stored therein control logic (i.e., computer software) and / or data.

[0095] Computer system 600 may also include one or more secondary storage devices or memory 610. Secondary memory 610 may include, for example, a hard disk drive 612 and / or a removable storage device or drive 614. 2026204701   17 Jun 2026

[0096] Removable storage drive 614 may interact with a removable storage unit 618. Removable storage unit 618 may include a computer-usable or readable storage device having stored thereon computer software (control logic) and / or data. Removable storage unit 618 may be program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface. Removable storage drive 614 may read from and / or write to removable storage unit 618.

[0097] Secondary memory 610 may include other means, devices, components, instrumentalities or other approaches for allowing computer programs and / or other instructions and / or data to be accessed by computer system 600. Such means, devices, components, instrumentalities or other approaches may include, for example, a removable storage unit 622 and an interface 620. Examples of the removable storage unit 622 and the interface 620 may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0098] Computer system 600 may further include a communication or network interface 624. Communication interface 624 may enable computer system 600 to communicate and interact with any combination of external devices, external networks, external entities, etc. (individually and collectively referenced by reference number 628). For example, communication interface 624 may allow computer system 600 to communicate with external or remote devices 628 over communications path 626, which may be wired and / or wireless (or a combination Page 24 of 34 2026204701   17 Jun 2026 thereof), and which may include any combination of LANs, WANs, the Internet, etc. Control logic and / or data may be transmitted to and from computer system 600 via communication path 626.

[0099] Computer system 600 may also be any of a personal digital assistant (PDA), desktop workstation, laptop or notebook computer, netbook, tablet, smartphone, smartwatch or other wearables, appliance, part of the Internet-of-Things, and / or embedded system, to name a few non-limiting examples, or any combination thereof.

[0100] Computer system 600 may be a client or server, accessing or hosting any applications and / or data through any delivery paradigm, including but not limited to remote or distributed cloud computing solutions; local or on-premises software (“on-premise” cloud-based solutions); “as a service” models (e.g., content as a service (CaaS), digital content as a service (DCaaS), software as a service (SaaS), managed software as a service (MSaaS), platform as a service (PaaS), desktop as a service (DaaS), framework as a service (FaaS), backend as a service (BaaS), mobile backend as a service (MBaaS), infrastructure as a service (IaaS), etc.); and / or a hybrid model including any combination of the foregoing examples or other services or delivery paradigms.

[0101] Any applicable data structures, file formats, and schemas in computer system 600 may be derived from standards including but not limited to JavaScript Object Notation (JSON), Extensible Markup Language (XML), Yet Another Markup Language (YAML), Extensible Hypertext Markup Language (XHTML), Wireless Markup Language (WML), MessagePack, XML User Interface Language (XUL), or any other functionally similar representations alone or in combination. Alternatively, proprietary data structures, formats or schemas may be used, either exclusively or in combination with known or open standards. 2026204701   17 Jun 2026

[0102] In a non-limiting example, system components and database models can be programmed with C++, Python, Java and any other programming languages. The systems and methods described herein can support different file formats exchange capabilities.

[0103] In some embodiments, a tangible, non-transitory apparatus or article of manufacture comprising a tangible, non-transitory computer useable or readable medium having control logic (software) stored thereon may also be referred to herein as a computer program product or program storage device. This can include, but is not limited to, computer system 600, main memory 608, secondary memory 610, and removable storage units 618 and 622, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system 600), may cause such data processing devices to operate as described herein.

[0104] It is to be appreciated that the Detailed Description section, and not the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary embodiments of the present invention as contemplated by the inventor(s), and thus, are not intended to limit the present invention and the appended claims in any way.

[0105] The present invention has been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed.

[0106] The foregoing description of the specific embodiments will so fully reveal the general nature of the invention that others can, by applying knowledge within the skill of the Page 26 of 34 2026204701   17 Jun 2026 art, readily modify and / or adapt for various applications such specific embodiments, without undue experimentation, without departing from the general concept of the present invention. Therefore, such adaptations and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by the skilled artisan in light of the teachings and guidance.

[0107] The breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

1. A system for automating vendor invoice-based billing experiences (VIBBE) in a cloud architecture, comprising a server, coupled to a processor, and configured to execute instructions that:receive and integrate vendor product catalogs into a product catalog system;apply pricing rules, margins, and discounts using a pricing engine;process sales orders from resellers through an ordering system;manage subscription data and provisioning requests via a subscription management system; interface with vendor systems using a vendor connector, wherein the vendor connector parses a vendor invoice into itemized vendor invoice data and formats the itemized vendor invoice data into vendor-rated data (VRD);process the VRD with a guiding system to create usage data records (UDRs) and transmit the UDRs to the subscription management system;update, by the subscription management system, subscription records based on the UDRs and trigger a rating engine in response to the UDRs;calculate total contract value (TCV) and total contract cost (TCC) based on the updated subscription records and the UDRs with the rating engine; andgenerate reseller invoices through a finance / ERP system based on billing data generated after calculating the TCV and TCC from the updated subscription records and the UDRs.

2. The system of claim 1, further comprising a vendor product onboarding module configured to support multiple file formats and convert them into a standardized format for integration into the product catalog, wherein the multiple file formats comprise one or more of CSV, XML, and JSON file formats and wherein the vendor product onboarding module is configured to convert the multiple file formats into a standardized format for integration into the product catalog such that all product attributes are captured and updated.

3. The system of claim 1, wherein the pricing engine dynamically adjusts pricing and discounts based on real-time data inputs, including currency conversions and regional pricing variations.

4. The system of claim 1, wherein the ordering system is configured to handle high volumes of concurrent order submissions and ensure efficient processing.

5. The system of claim 1, wherein the subscription management system synchronizes subscription states with the vendor’s system, reflecting changes such as renewals, cancellations, and upgrades.

6. The system of claim 1, wherein the vendor connector can employ advanced parsing algorithms to extract relevant data fields from vendor invoices and format them into vendor-rated data (VRD).

7. The system of claim 1, wherein the rating engine applies sophisticated algorithms to perform TCV and TCC calculations, considering various billing models and forecasting methods.

8. A computerized method for automating vendor invoice-based billing experiences (VIBBE) in a cloud architecture, comprising:receiving and integrating vendor product catalogs into a product catalog system; managing and applying pricing rules, margins, and discounts using a pricing engine;2026204701   07 Sep 2026processing sales orders from resellers through an ordering system;managing subscription data and provisioning requests via a subscription management system; interfacing with vendor systems using a vendor connector, including parsing a vendor invoice into itemized vendor invoice data and formatting the itemized vendor invoice data into vendor-rated data (VRD);processing the VRD with a guiding system to create usage data records (UDRs) and transmitting the UDRs to the subscription management system;updating, by the subscription management system, subscription records based on the UDRs and triggering a rating engine in response to the UDRs;calculating total contract value (TCV) and total contract cost (TCC) based on the updated subscription records and the UDRs with the rating engine; andgenerating and issuing reseller invoices through a finance / ERP system based on billing data generated after calculating the TCV and TCC from the updated subscription records and the UDRs.

9. The method of claim 8, further comprising supporting multiple file formats for vendor product catalogs and converting them into a standardized format for integration, wherein the multiple file formats comprise one or more of CSV, XML, and JSON file formats and wherein a vendor product onboarding module is configured to convert the multiple file formats into a standardized format for integration into the product catalog such that all product attributes are captured and updated.

10. The method of claim 8, further comprising dynamically adjusting pricing and discounts based on real-time data inputs, including currency conversions and regional pricing variations.

11. The method of claim 8, further comprising handling high volumes of concurrent order submissions to ensure efficient processing.

12. The method of claim 8, further comprising synchronizing subscription states with the vendor’s system to reflect changes such as renewals, cancellations, and upgrades.

13. The method of claim 8, further comprising employing advanced parsing algorithms to extract relevant data fields from vendor invoices and format them into vendor-rated data (VRD).

14. The method of claim 8, further comprising applying sophisticated algorithms to perform TCV and TCC calculations, considering various billing models and forecasting methods.

15. A non-transitory computer-readable medium containing instructions that, when executed by a processor, cause the computing device to perform automated vendor invoice-based billing experiences (VIBBE) operations comprising:receiving and integrating vendor product catalogs into a product catalog system;managing and applying pricing rules, margins, and discounts using a pricing engine; processing sales orders from resellers through an ordering system;managing subscription data and provisioning requests via a subscription management system; interfacing with vendor systems using a vendor connector, including parsing a vendor invoice into itemized vendor invoice data and formatting the itemized vendor invoice data into vendor-rated data (VRD);processing the VRD with a guiding system to create usage data records (UDRs) and transmitting the UDRs to the subscription management system;updating, by the subscription management system, subscription records based on the UDRs2026204701   07 Sep 2026and triggering a rating engine in response to the UDRs;calculating total contract value (TCV) and total contract cost (TCC) based on the updated subscription records and the UDRs with the rating engine; andgenerating and issuing reseller invoices through a finance / ERP system based on billing data generated after calculating the TCV and TCC from the updated subscription records and the UDRs.

16. The non-transitory computer-readable medium of claim 15, wherein the instructions further comprise supporting multiple file formats for vendor product catalogs and converting them into a standardized format for integration, wherein the multiple file formats comprise one or more of CSV, XML, and JSON file formats and wherein a vendor product onboarding module is configured to convert the multiple file formats into a standardized format for integration into the product catalog such that all product attributes are captured and updated.

17. The non-transitory computer-readable medium of claim 15, wherein the instructions further comprise dynamically adjusting pricing and discounts based on real-time data inputs, including currency conversions and regional pricing variations.

18. The non-transitory computer-readable medium of claim 15, wherein the instructions further comprise handling high volumes of concurrent order submissions to ensure efficient processing.

19. The non-transitory computer-readable medium of claim 15, wherein the instructions further comprise synchronizing subscription states with the vendor’s system to reflect changes such as renewals, cancellations, and upgrades.

20. The non-transitory computer-readable medium of claim 15, wherein the instructions further comprise employing advanced parsing algorithms to extract relevant data fields from vendor invoices and format them into vendor-rated data (VRD).

Images