Beyond Artificial Intelligence: The SAP Capital Twin, the Evidence Economy, and the Architecture of Capital Optimization

From enterprise data to capital intelligence: why the next frontier of financial innovation is the economic interpretation of operational reality 1. The Artificial Intelligence Paradox: More Intelligence, Not Necessarily More Value Artificial intelligence has become one of the most prominent investment priorities in enterprise technology. Organizations are integrating large language models, predictive analytics, machine learning and autonomous agents into their operations, expecting improvements in productivity, decision-making, risk management and financial performance. The technological progress is real. Machine learning can identify patterns across enormous datasets, classification algorithms can distinguish between complex categories, clustering can reveal previously unrecognized relationships, decision trees can support structured decisions, and regression models can estimate relationships between variables. Modern generative systems extend these capabilities by processing unstructured information, interpreting natural language and coordinating increasingly sophisticated tasks. Yet technological capability and economic value are not the same thing. The enterprise AI investment cycle is revealing a fundamental distinction between what a system can do and what an organization can economically justify doing with it. The total cost of an AI implementation extends beyond the price of a model or a computing service. It includes infrastructure, energy consumption, data preparation, integration, security, governance, human supervision, maintenance, error correction and the organizational changes required to turn an experimental capability into a dependable business process. Some applications produce substantial benefits. Others struggle to generate returns commensurate with their costs. The outcome depends on the problem being addressed, the quality of the available information, the consequences of an incorrect result and the extent to which the technology changes an economically meaningful decision. This distinction is especially important in corporate finance. A model can produce an accurate prediction without knowing whether that prediction is financially relevant. It can identify a relationship between two variables without understanding the contractual obligations that connect them. It can summarize an invoice, forecast a delay or classify a transaction while remaining unaware of how the result affects liquidity, credit exposure, collateral eligibility or regulatory capital. The model may be functioning correctly. The architecture surrounding it may nevertheless be economically inadequate. This is not an argument against artificial intelligence. It is an argument for placing artificial intelligence inside a more rigorous economic and financial architecture. The central question should not be how many processes can incorporate AI, how many agents an enterprise can deploy or how much data a model can consume. It should be how effectively intelligence can transform operational information into decisions that improve economic performance. The next frontier of enterprise finance is not moving money faster. It is making every unit of capital more productive. Achieving that objective requires more than computational power. It requires a representation of economic reality that connects operational events, contractual commitments, financial consequences and capital-market requirements. This is the purpose of the Capital Twin. 2. The Information Problem Behind Enterprise AI Discussions about artificial intelligence frequently focus on model architecture, parameter counts, inference performance and the availability of computing resources. These are legitimate technical considerations, but they address only part of the problem. An enterprise does not operate on data alone. It operates through relationships between objects, events, commitments, decisions and constraints. A purchase order has a commercial meaning. A delivery date has an operational meaning. A payment term establishes a contractual expectation. Inventory in transit represents goods whose location, ownership, financing requirements and delivery risks may differ from those of inventory held in a warehouse. A supplier's promise to deliver is not equivalent to the physical receipt of the goods. An invoice does not necessarily mean that cash has been collected, and a recorded receivable does not automatically imply that the corresponding exposure has the same economic characteristics as every other receivable. These distinctions are elementary to experienced supply chain and finance professionals. They are also essential to the intelligent interpretation of enterprise data. Consider an AI agent asked to evaluate a company's short-term liquidity position. If the agent receives only accounting balances, historical payments and general financial indicators, it may produce a reasonable assessment based on the information available. However, it could miss a significant concentration of supplier payments falling due before customer collections arrive. It might not recognize that a contractual change has accelerated a payment obligation, that a shipment has been delayed, or that a customer has accepted a delivery but disputes the corresponding invoice. The problem is not necessarily a lack of computational intelligence. It is a lack of contextual information. The same limitation appears in credit risk. Historical financial statements can provide important evidence about a company's ability to meet its obligations, but they offer an incomplete view of the evolving contractual and operational conditions that determine future exposures. A company's financial position is partly the outcome of processes already executed and transactions already recognized. Its future liquidity position is also shaped by commitments that have not yet become accounting entries, deliveries that have not yet occurred, invoices that have not yet been issued and payments that have not yet been settled. An AI system that cannot distinguish between these states risks confusing historical evidence with future obligations. The implication is straightforward: improving model performance cannot compensate indefinitely for an inadequate representation of the business environment. Better models can extract more information from available data. They cannot reliably recover every missing contractual relationship, establish the legal enforceability of an obligation from an ambiguous record or infer a financial meaning that the surrounding architecture has never defined. This is why the quality of AI depends on more than data accuracy. It depends on the meaning of the data, the relationships between the underlying business objects, the time at which the information becomes relevant and the decision for which the information is being used. Data quality determines whether information is represented correctly. Semantic quality determines whether its meaning is understood correctly. Economic relevance determines whether that understanding can improve a decision. The Capital Twin is designed around this distinction. 3. From Digital Twins and Financial Twins to the Capital Twin The term digital twin has become familiar across manufacturing, engineering and industrial operations. In its established applications, a digital twin provides a digital representation of a physical asset, system or process, often updated through sensors, telemetry and operational data. Its purpose is to improve the understanding, monitoring, simulation and management of physical reality. Enterprise finance has developed its own digital representations of economic activity. In SAP environments, S/4HANA and the Universal Journal, represented by the ACDOCA table, provide an important foundation for recording and analyzing accounting information. The exact scope depends on the implemented configuration and surrounding applications, but the underlying principle is familiar: financial events are represented through structured accounting objects and records. For the purposes of the Capital Optimization framework, this accounting-centered representation can be understood as a Financial Twin: a structured view of the financial state reflected in the enterprise's accounting records. The Financial Twin and the Digital Twin answer different questions. The Digital Twin helps establish what is happening, or is expected to happen, in the physical or operational environment. The Financial Twin records the financial consequences recognized through accounting processes. Neither representation, by itself, necessarily provides the complete forward-looking interpretation required to optimize capital across an extended commercial relationship. The Capital Twin addresses this gap. It is conceived as a living representation of economic reality expressed in the language of capital markets. It connects operational events, contractual commitments, accounting information, risk parameters and financing requirements to provide a continuously evolving view of the financial implications of business activity. Its purpose is not to replace the underlying operational or accounting systems. It is to establish a financial interpretation of their information that supports decisions about liquidity, risk, collateral, financing capacity and capital efficiency. The distinction is fundamental. A Digital Twin represents physical or operational reality. A Financial Twin represents the financial state captured through accounting. A Capital Twin seeks to connect these representations with the economic obligations, uncertainties and financial consequences that determine how capital is committed, exposed, recovered and reused. This makes the Capital Twin more than another dashboard, data warehouse or predictive model. It is a proposed semantic and analytical architecture in which enterprise activity becomes interpretable as capital-market information. The word semantic is particularly important. A semantic layer does not merely move data between systems. It defines what business objects mean, how they relate to one another, which events change their status and how their attributes contribute to a particular financial interpretation. For example, a delivery date is an operational attribute. Its financial significance depends on the associated contract, the payment conditions, the customer's acceptance requirements, the supplier's obligations, the inventory position, the financing arrangement and the consequences of delay. The Capital Twin connects these elements so that an AI system can analyze the financial significance of the delivery date rather than treating it as an isolated field. The same principle applies to inventory in transit, consignment stock, purchase commitments, receivables, payment obligations and contractual milestones. The objective is to make the economic meaning of operational information explicit, structured and available to financial decision-making. 4. Contractual Gravity: Why Capital Is Committed Before Accounting Recognition One of the central concepts within this framework is Contractual Gravity. The concept starts from a simple observation: economic commitments can create future financial consequences before those consequences appear as recognized accounting balances. A company may enter into a supply agreement, reserve production capacity, commit to purchase materials, agree to payment terms or undertake a delivery obligation well before the associated invoice is issued or the transaction is recognized in the relevant financial statements. These commitments are not all equivalent. Their enforceability, cancellation rights, conditions precedent, contingencies, probability of execution and potential financial consequences vary considerably. Nevertheless, many of them influence future liquidity and risk from the moment the underlying obligation becomes economically meaningful. Contractual Gravity describes the capacity of enforceable commitments and economically significant contractual obligations to shape future liquidity requirements, exposures and capital allocation. The concept challenges an overly static interpretation of corporate finance in which attention is concentrated on recognized balances while the contractual processes generating future cash flows are treated as secondary operational information. Consider a manufacturing company that agrees to purchase a substantial volume of components for delivery over the following three months. The company may not yet have received the components, and the corresponding invoices may not yet exist. Its accounting position therefore does not necessarily show the entire future cash requirement as a recognized liability. However, the contract may already constrain the company's choices. The company may need to reserve liquidity, arrange financing, maintain production capacity, manage foreign-exchange exposure or negotiate changes to delivery schedules. If the market price of the components changes, if the supplier experiences financial difficulties or if customer demand deteriorates, the economic consequences may emerge before the corresponding accounting entries. A similar situation arises when a supplier reserves production capacity for a major customer, when a buyer commits to a minimum purchase volume or when a logistics agreement imposes financial consequences for failing to meet a delivery window. Contractual Gravity directs attention toward the economic force of these commitments. It does not imply that every purchase order is automatically a debt, that every commercial promise is legally enforceable or that every future obligation should be treated as a current credit exposure. Those conclusions require contractual interpretation, accounting analysis and, where applicable, regulatory assessment. The point is more precise: the absence of a recognized accounting liability does not necessarily mean the absence of an economically relevant commitment. For AI, this distinction matters enormously. An agent that evaluates only recognized accounting balances may overlook obligations that materially affect future liquidity. A predictive model may forecast payment behavior accurately while failing to incorporate the contractual events that determine when payments become due. A financing platform may identify available cash while ignoring commitments that make part of that cash economically unavailable. Contractual Gravity provides a conceptual basis for bringing these commitments into the analytical field of capital optimization. Within the Capital Twin, contracts, orders and operational milestones can be evaluated according to their legal status, expected execution, financial implications and associated uncertainty. Their economic significance can then be connected to the relevant risk and liquidity models. The result is a more forward-looking representation of capital requirements. Instead of waiting exclusively for accounting recognition or a payment request, the enterprise can begin assessing the financial consequences of commitments as the evidence surrounding them develops. This is particularly valuable in complex supply chains, where thousands of interdependent contractual relationships determine the timing and distribution of future cash flows. Contractual Gravity therefore establishes one of the foundations for a more dynamic understanding of capital: the recognition that commitments influence economic reality before all their consequences become visible in accounting. 5. The Evidence Economy: From Assertions to Verifiable Economic Events Contractual commitments establish expectations. Operational evidence helps determine what has actually happened. This distinction leads to the second central concept: the Evidence Economy. In conventional corporate finance, financing decisions frequently rely on a combination of financial statements, credit ratings, historical payment behavior, guarantees, collateral, contractual documentation and other forms of evidence. These mechanisms remain essential. The Evidence Economy does not propose abandoning financial statements, credit analysis or prudential safeguards. It proposes expanding the evidence available to evaluate economic activity. Modern enterprise systems capture a growing sequence of operational events. Purchase orders are created and confirmed. Production orders progress through defined stages. Goods are dispatched, transported and delivered. Customers accept or reject deliveries. Invoices are issued. Disputes are raised and resolved. Payments become due and are settled. When appropriately controlled and linked to the underlying contractual relationships, these events provide evidence about the execution of commercial obligations. The economic value of that evidence depends on its reliability. A purchase order demonstrates that an order has been recorded; it does not necessarily establish that the goods will be delivered. A shipping notification provides information about dispatch; it does not by itself prove delivery or acceptance. A proof of delivery may support a contractual claim, but its legal and financial significance depends on the applicable agreement and the quality of the evidence. An invoice may be validly issued without being undisputed, payable or immediately financeable. The Evidence Economy requires these distinctions to be preserved rather than obscured. Its objective is to connect evidence to the specific economic proposition it supports. A verified delivery, for example, may reduce uncertainty about the physical execution of a contract. Customer acceptance may strengthen the evidence that a performance obligation has been fulfilled. A consistent history of on-time payments may inform the assessment of a counterparty's behavior. The resolution of a dispute may change the expected timing or collectability of a receivable. Each event changes the information available to evaluate the underlying economic relationship. The resulting evidence can improve risk assessment, provided that its provenance, integrity, timing, completeness and relevance are established. It can also help distinguish between transactions that may look similar in accounting terms but have materially different operational characteristics. Two receivables of equal nominal value may differ in the strength of the supporting evidence, the existence of disputes, the contractual payment terms, the concentration of counterparty risk and the expected time to collection. A static accounting view may record both as receivables. A more granular financial interpretation can identify the differences that matter for financing and risk management. The Evidence Economy therefore seeks to make verified operational information an economically useful input into capital allocation. This is not simply the digitization of documentation. It is the systematic association of evidence with commitments, performance obligations, financial exposures and decisions. The distinction becomes particularly important when AI is introduced. An AI model can process large volumes of documentation, identify anomalies, compare actual events with contractual expectations and estimate the likelihood of delays or disputes. However, the reliability of these outputs depends on whether the model receives evidence that is appropriately classified, linked to the correct economic object and interpreted within a controlled framework. Without that structure, an AI agent may confuse an assertion with a verified event, a forecast with an obligation or a document with proof of performance. With it, the model can operate on a more coherent representation of economic reality. The Evidence Economy thus provides the informational foundation on which the Capital Twin can evaluate changing risk, liquidity and financing conditions. It also creates a possible path toward reducing information asymmetry between companies, suppliers, customers, financiers and other participants in a commercial network. The proposition is not that evidence eliminates risk. It is that better evidence can make risk more visible, more differentiated and, where the relevant institutions and rules permit, more accurately priced. 6. The Capital Twin as a Semantic Bridge to Capital Markets Contractual Gravity identifies the economic significance of commitments. The Evidence Economy establishes the importance of verifying how those commitments develop and are executed. The Capital Twin connects these dimensions to the financial language required for capital allocation. This translation is not merely a matter of attaching financial labels to operational data. Capital markets and regulated financial institutions use specific concepts to evaluate exposures, expected losses, capital requirements, collateral and returns. These concepts have established definitions and depend on particular assumptions, methodologies and regulatory rules. Among the relevant measures are Probability of Default (PD), Loss Given Default (LGD), Exposure at Default (EAD), Credit Conversion Factors (CCFs), risk-weighted assets (RWA), collateral haircuts and risk-adjusted return measures such as RAROC. These measures are related, but they are not interchangeable. Their application depends on the exposure, the counterparty, the contractual structure, the applicable risk framework and the methodology adopted by the financial institution. The Capital Twin does not eliminate the need for these models. It seeks to provide them with better contextual information about the economic activity underlying an exposure. Consider a purchase commitment that may result in a future payment obligation. Its financial significance cannot be determined solely from the nominal amount of the order. The analysis may require an understanding of cancellation rights, delivery conditions, the probability of execution, the counterparty relationship, payment terms and the applicable treatment of the commitment. Similarly, inventory in transit cannot automatically be treated as eligible collateral merely because the goods exist or their location is known. Ownership, control, valuation, competing claims, insurance, jurisdiction, enforceability and the relevant financing agreement may all matter. The Capital Twin can connect the operational evidence associated with these objects to the financial assessment required for a particular decision. Whether that evidence changes a regulatory exposure, qualifies an asset as collateral or reduces a capital requirement remains a separate question governed by the applicable accounting, legal, prudential and contractual framework. This distinction is essential to the credibility of the architecture. The objective is not to declare that operational data automatically becomes bankable collateral. It is to establish a structured way of identifying which operational and contractual facts may support a financing decision, which uncertainties remain unresolved and which conditions must be satisfied before a financial institution can act on the information. The same principle applies to liquidity. A confirmed customer payment may improve the forecast of future cash availability, but it is not equivalent to cash already received. A purchase commitment may indicate a future cash requirement, but its timing and amount may depend on subsequent events. A receivable may be commercially well supported but still expose the holder to counterparty, concentration, dispute or settlement risk. A Capital Twin should preserve these distinctions while connecting them into a coherent financial view. Its contribution is to make the relationship between operational reality and financial consequences explicit. That creates an environment in which AI can assist with forecasting, anomaly detection, risk differentiation, scenario analysis and the identification of financing opportunities without being asked to invent the underlying financial semantics. The model can estimate the probability of a delay. The contractual framework determines the consequences of that delay. The evidence layer establishes what is known about the actual event. The financial architecture evaluates the resulting exposure under the relevant methodology. Each component performs a distinct function. Together, they can support a more reliable and economically meaningful form of enterprise intelligence. 7. Why SAP Matters: The Operational Foundation Already Exists A central strategic consideration is that much of the information required for this architecture is already generated by enterprise resource planning and supply chain systems. SAP has a substantial presence in large enterprises and supports business processes across procurement, production, inventory management, sales, logistics, invoicing, financial accounting and treasury. Its ecosystem includes products and capabilities such as S/4HANA, SAP Ariba, SAP Integrated Business Planning, SAP Business Network and logistics-related solutions, alongside financial risk and planning capabilities. These systems do not constitute one universal data model shared identically by every customer. Implementations differ in configuration, customization, master-data quality, process design, integration and governance. Information may also be distributed across SAP and non-SAP applications. Nevertheless, the existence of structured business objects and established transactional relationships provides a significant starting point. A purchase order is not an abstract data point. It belongs to a business process. It has relationships with suppliers, materials, delivery schedules, contractual conditions and subsequent transactions. A goods receipt is not merely a timestamp. It records an event whose significance depends on the associated order, the quantities received, the applicable conditions and the subsequent financial treatment. Likewise, a sales order, outbound delivery, proof of delivery, billing document and customer payment can be understood as related stages in a commercial process. The challenge is to connect these objects into a financial interpretation that extends beyond the boundaries of individual applications. SAP's potential advantage is not simply that it stores large quantities of enterprise data. Many platforms do that. Its strategic relevance lies in the breadth of the operational and financial processes represented within its ecosystem and the possibility of connecting their information through governed business semantics. The Capital Twin builds on this possibility. It seeks to interpret the relationships between procurement, production, logistics, sales, contractual obligations and financial accounting in terms that can be consumed by risk models, financial planning systems and AI agents. For example, information from procurement and inventory management may help explain future supplier payment requirements. Logistics events may provide evidence about delivery progress. Sales and billing records may support analysis of expected collections. Treasury and financial accounting information may establish existing exposures, cash positions and recorded obligations. Integrated appropriately, these sources can support a more comprehensive view of the commercial process that generates a future financial outcome. The objective is not to assume that all relevant information already exists in a clean or immediately usable form. Data quality, master-data consistency, event linkage, access controls, integration and process discipline remain critical implementation challenges. Nor does the presence of SAP automatically establish a common semantic layer across customers, suppliers and banks. Intercompany and interorganizational integration requires explicit agreements about data definitions, evidence exchange, permissions, identifiers, contractual interpretation and responsibilities. The strategic opportunity is to build on the operational structures that already exist rather than attempting to reconstruct the entire economy from disconnected documents and generic AI prompts. This is particularly relevant as enterprise software evolves toward increasingly autonomous processes. An autonomous enterprise needs more than agents capable of executing tasks. It needs a reliable representation of the economic consequences of those tasks. An agent that can create a purchase order should also operate within defined authority limits, procurement policies, liquidity constraints and contractual rules. An agent that recommends accelerating a payment should understand the potential effect on working capital and supplier relationships. An agent that identifies a financing opportunity should distinguish between an economically attractive proposal and one that satisfies the relevant legal, risk and regulatory requirements. The Capital Twin provides a conceptual architecture for connecting operational autonomy with capital discipline. 8. AI Agents Need Financial Semantics, Not Just Access to Data The emergence of AI agents makes the need for this architecture more urgent. Traditional enterprise automation generally executes predefined rules against structured information. AI agents introduce greater flexibility. They can interpret natural-language requests, coordinate tasks across applications, retrieve information from different sources and recommend or execute actions within their permitted scope. This creates opportunities for more adaptive business processes. It also creates a risk: an agent may be capable of taking an action without having a sufficiently complete understanding of its financial consequences. Giving an agent access to enterprise applications does not automatically provide it with an accurate representation of economic reality. An agent may retrieve an inventory balance without understanding the contractual restrictions affecting the stock. It may identify an overdue receivable without distinguishing between a genuine payment delay and a formally documented dispute. It may recommend delaying a supplier payment without accounting for the contractual consequences or the operational importance of that supplier. These are not merely language-model limitations. They are architecture and information-model limitations. A more capable model may improve interpretation, but it cannot replace authoritative records, contractual logic, access controls, validated risk models or the controls required for regulated financial decisions. The Capital Twin offers a way to separate these responsibilities. Operational systems record transactions and events. Contractual structures establish the relevant obligations and conditions. Evidence mechanisms determine what has been verified. Financial models translate the resulting information into exposure, risk and capital assessments. AI agents can then use those outputs to support decisions within explicitly defined permissions. This separation allows AI to operate on a richer information foundation while preserving the distinction between prediction, interpretation and authorization. For example, an AI agent could identify a potential liquidity shortfall arising from the timing difference between supplier payments and customer collections. It could analyze contractual terms, assess the status of relevant deliveries, retrieve available financing conditions and present alternative actions. A further analytical layer could compare the expected financial consequences of accelerating collections, negotiating payment terms, adjusting inventory policies or arranging financing. The final decision would still depend on the applicable commercial, financial, risk and governance requirements. In another scenario, an agent could identify a receivable supported by strong delivery evidence and a consistent payment history. It might flag the receivable for financing review. The financing institution would still need to determine eligibility, legal enforceability, counterparty exposure, pricing and any relevant capital treatment. The value lies in improving the quality and timeliness of the information entering the decision process. The model does not need to reconstruct the meaning of every transaction from scratch. It can work with a financial representation that already connects operational events to contractual obligations and recognized risk concepts. This is how AI can move from generic assistance toward economically relevant enterprise intelligence. The key is not to make the agent appear more autonomous. It is to make its operating environment sufficiently coherent that its actions can be evaluated, constrained and justified. 9. The Energy and Economics of Intelligence Any serious discussion of enterprise AI must consider its resource consumption. AI workloads require computing infrastructure, and computing requires energy. The scale of consumption varies considerably according to the model, hardware, workload, utilization, data-center efficiency, cooling requirements and the frequency with which the system is used. Energy is only one component of the total cost, but it is an increasingly important one when organizations deploy AI across thousands of processes or operate agents continuously. The relevant question is not whether AI consumes energy. It is whether the economic benefit generated by a particular application justifies its complete resource requirements. A sophisticated model may be appropriate for a high-value, complex decision where the cost of an error is substantial. A simpler predictive model, deterministic rule or conventional optimization algorithm may be more appropriate for a routine task with clearly defined conditions. A well-designed architecture should allow organizations to choose the appropriate technique for each problem rather than assuming that every decision requires a large generative model. This is particularly important in financial applications, where reliability, explainability, latency, auditability and regulatory requirements can matter as much as raw model capability. Some tasks are best handled by deterministic business rules. Others benefit from statistical models, optimization methods, anomaly detection or machine learning. Generative AI can be valuable for interpreting documents, synthesizing information and coordinating complex workflows. In many cases, the strongest solution combines several methods. The Capital Twin supports this differentiated approach by providing a common financial context across different analytical techniques. A forecast may be generated by one model, a credit assessment by another, and a contractual interpretation by a controlled legal or business-rule process. Their outputs can be connected through shared definitions of the underlying commercial objects and financial exposures. This avoids making the generative model the sole authority on every aspect of the decision. It also improves the ability to evaluate economic performance. An AI initiative should be assessed not merely by the number of interactions it handles or the volume of tasks it automates, but by its contribution to measurable business outcomes: lower operating costs, fewer errors, improved forecasting, reduced processing delays, better working-capital management, more informed risk decisions or increased productivity. In capital-intensive processes, those outcomes should be evaluated alongside the financing costs, implementation effort, operational risk and resource consumption required to achieve them. The objective is not maximum intelligence at any price. It is the most economically effective combination of information, analytical capability and execution. 10. From Corporate Solvency to the Financial Characteristics of Processes One of the most important implications of the Capital Twin is the possibility of evaluating the financial characteristics of commercial processes with greater granularity. Corporate finance traditionally places substantial emphasis on the creditworthiness of the legal entity seeking financing. This is entirely understandable. A bank must assess repayment capacity, leverage, cash generation, existing obligations, business risk, collateral and the other factors relevant to its credit decision. The Capital Twin does not eliminate the importance of corporate solvency. It introduces an additional analytical perspective: the financial characteristics of the individual process, contract or commercial exposure that generates a financing requirement. Consider two companies with different credit profiles participating in comparable supply chain processes. The underlying transactions may differ in contractual enforceability, delivery evidence, payment conditions, buyer concentration, operational performance and expected cash-flow timing. A purely entity-centered analysis may not fully distinguish between the financial characteristics of these individual transactions. A process-centered analysis can add relevant information, while retaining the counterparty risk that remains essential to the decision. The same principle applies to two transactions undertaken by the same company. They may have identical nominal values but different delivery risks, payment terms, evidence quality, dispute exposure and financing requirements. Their economic characteristics are not necessarily identical. The Capital Twin seeks to represent these differences systematically. This creates the possibility of evaluating financing opportunities at a more granular level, based on the relationship between contractual obligations, verified performance, expected cash flows and the relevant risk framework. However, process-level information must not be confused with the elimination of corporate risk. A well-documented transaction can still be affected by the insolvency of a buyer, seller, guarantor or other relevant counterparty. A strong delivery record does not guarantee payment, and a commercially attractive process does not automatically qualify for a lower risk weight or a reduced capital requirement. The purpose is to improve the evidence available for the decision, not to bypass its constraints. A bank may determine that additional transaction-level information improves underwriting, monitoring or pricing. Another institution may require further evidence or may be unable to recognize certain features under its applicable methodology. The economic benefit depends on the quality of the evidence, the structure of the transaction and the rules governing the relevant financial product. Nevertheless, the strategic direction is significant. When operational processes are represented in a financial language, their characteristics become easier to compare, monitor and evaluate across organizational boundaries. This creates a foundation for more differentiated risk assessment and potentially more efficient allocation of capital. 11. Financial Airbnb: Connecting Capital Capacity with Evidenced Demand The concept of the Financial Airbnb extends the Capital Twin into the domain of financial networks. The analogy is not intended to suggest that corporate liquidity is identical to residential accommodation, or that financing can be organized without credit analysis, contractual controls or regulation. Its purpose is to illustrate a potential economic mechanism: a platform can identify underused capacity, match it with a relevant demand and facilitate a transaction between parties that might otherwise remain disconnected. In the corporate environment, liquidity is distributed across companies, subsidiaries, suppliers, customers and commercial networks. Some organizations hold cash or possess financing capacity while others face temporary funding requirements arising from inventory, production cycles, delivery schedules or differences between payment and collection dates. These positions are not automatically compatible. Currency, maturity, creditworthiness, legal restrictions, operational requirements and risk appetite can prevent a straightforward match. Nevertheless, the underlying opportunity is worth examining. A company may have a financing requirement associated with a well-documented commercial transaction. Another participant may have available liquidity or a mandate to finance exposures meeting specified criteria. A network that can identify the opportunity, establish the relevant evidence and facilitate a compliant transaction could potentially improve the connection between capital supply and capital demand. The Capital Twin provides the financial representation needed to assess the underlying process. The Evidence Economy provides the operational information needed to evaluate its status and supporting documentation. Contractual Gravity helps identify the commitments and future cash-flow requirements that create the demand for capital. The Financial Airbnb brings these elements into a potential matching mechanism. Its purpose would be to identify opportunities in which the characteristics of a financing need correspond to the capabilities and constraints of a potential capital provider. This could involve financing associated with receivables, confirmed commercial obligations, inventory or other eligible exposures, depending on the legal and financial structure. The platform might help participants discover opportunities, exchange authorized evidence, compare financing conditions, coordinate transaction execution and monitor the relevant operational events. The precise business model would depend on the design. A platform could act as a technology provider, marketplace operator, arranger or intermediary. Whether it would require a particular license or be subject to financial-services regulation would depend on the activities it actually performs and the jurisdictions involved. Calling a service a platform rather than a bank does not determine its regulatory status. Similarly, the availability of operational evidence does not automatically make a transaction eligible for financing. Legal enforceability, transferability, ownership, debtor acknowledgment where required, fraud controls, counterparty exposure, servicing arrangements and applicable prudential rules remain relevant. The proposition is therefore not that every company can lend directly to every other company without constraints. It is that better information and more effective matching mechanisms may reveal financing opportunities that remain difficult to identify or evaluate within fragmented corporate processes. The Financial Airbnb is a conceptual extension of capital optimization: making the characteristics of financing demand more visible and connecting them with appropriate capital supply. Its ultimate value would have to be demonstrated through measurable outcomes, including transaction costs, funding availability, risk-adjusted returns, execution times and the resilience of the resulting arrangements. 12. From Evidence to Financing Capacity The relationship between evidence and financing is central to this architecture. In many commercial processes, financing decisions are delayed because information is fragmented across multiple organizations and systems. The buyer holds one set of records, the supplier holds another, the logistics provider records transport events, and the bank receives a subset of the available information through documents, integrations or manual processes. Reconciling these records can require time and operational effort. Discrepancies must be resolved. The authenticity of documents may need to be checked. The status of delivery, acceptance, invoicing and payment must be established. The parties may need to confirm whether an obligation is disputed, assigned, already financed or subject to competing claims. These requirements cannot simply be removed. They are part of the work needed to establish whether a financing transaction is acceptable. However, the process can become more efficient if relevant evidence is generated, linked and made available in a consistent form from the beginning. Imagine a commercial transaction whose contractual conditions are clearly represented, whose delivery milestones are recorded, whose evidence of performance can be verified and whose invoice status is connected to the underlying obligation. A financing institution could receive a more structured information package for its assessment. Its own policies and models would determine whether the exposure qualifies, how it should be priced and which controls remain necessary. The improvement would not come from treating the transaction as risk-free. It would come from reducing avoidable uncertainty and the cost of reconstructing information that already exists. This is where the Evidence Economy and the Capital Twin reinforce one another. Evidence becomes more useful when it is linked to a financial interpretation. Financial interpretation becomes more reliable when it is supported by verifiable evidence. The combination can make certain exposures easier to assess, monitor and potentially finance. Over time, a well-governed network could also support continuous updates as the commercial process evolves. A delivery delay could change the expected timing of a cash flow. Customer acceptance could strengthen the evidence supporting a receivable. A dispute could trigger a review of eligibility. A payment could close an exposure and release capacity for another transaction. Such updates would need to be reflected in the relevant financial models and transaction controls. They should not automatically alter regulatory classifications or financing terms without the required validation and authorization. The broader principle remains powerful: financing information need not be assembled exclusively at the moment a company requests credit. Some of the relevant evidence can be created and maintained throughout the commercial process. That creates the possibility of moving from episodic information collection toward a more continuous assessment of financing opportunities. The economic value would depend on whether the improvement in information and execution translates into better access to capital, lower administrative costs, more appropriate pricing or more productive use of available liquidity. 13. Capital Optimization Is Not the Same as Maximizing Leverage A framework designed to make capital more productive must distinguish capital optimization from indiscriminate financial leverage. The objective is not to finance every transaction, maximize borrowing or transform every operational object into a financial instrument. Some commitments should not be financed. Some exposures are too uncertain. Some transactions create risks that exceed their expected returns. Some assets cannot be pledged or transferred effectively. Some companies need to preserve liquidity rather than use it to fund additional activity. A credible Capital Twin must make these constraints visible. Capital optimization means allocating financial resources according to their expected economic contribution, associated risk, liquidity requirements and alternative uses. It includes identifying opportunities to release unnecessary working capital, reduce avoidable financing costs and improve the timing of cash flows. It also includes recognizing when a proposed transaction should not proceed. The distinction is important because additional data can reveal both opportunities and risks. More precise information about inventory may identify stock that can be reduced, but it may also reveal that a safety-stock level is necessary to protect production continuity. Better visibility into payment terms may reveal an opportunity to extend supplier financing, but it may also show that doing so would damage a strategically important relationship or violate contractual obligations. A model that optimizes a single financial metric without representing operational consequences may produce recommendations that are locally attractive and globally harmful. The Capital Twin should therefore support decisions that consider financial performance alongside operational resilience, contractual commitments and risk limits. This is particularly relevant when autonomous agents are involved. An agent tasked with reducing working capital could recommend inventory reductions that increase the risk of production interruptions. An agent instructed to maximize short-term liquidity might delay payments in ways that create contractual penalties or disrupt the supply chain. The appropriate objective is not to maximize one metric in isolation. It is to improve economic outcomes subject to explicit operational, contractual, financial and regulatory constraints. Capital optimization is a discipline of allocation, not simply a strategy of extracting liquidity. 14. The Role of Basel and Prudential Discipline The relationship between operational information and capital markets requires particular care when banking regulation is involved. Basel standards provide internationally developed prudential frameworks that inform the regulation of banking institutions, subject to implementation through national and regional rules. They establish approaches for measuring credit risk, capital requirements and related supervisory considerations. The Capital Twin is not a replacement for these frameworks. Its role is to improve the information available to the systems and professionals responsible for applying the relevant methodologies. Operational evidence may help a bank understand a transaction more accurately. Contractual information may clarify the nature of an obligation. Delivery and payment histories may inform internal estimates of risk. Information about guarantees or collateral may support an assessment of the relevant legal and economic protections. However, the existence of more detailed data does not itself authorize a change in regulatory treatment. PD, LGD, EAD, credit conversion factors and risk-weighted assets have specific meanings under the applicable framework. Their calculation depends on the exposure category, methodology, regulatory requirements and, where relevant, supervisory approval. Collateral recognition depends on eligibility conditions and enforceability, not merely on the availability of operational information. The Capital Twin should therefore distinguish between three questions. First, what does the operational evidence tell us about the underlying economic event? Second, how does that information affect the institution's assessment of risk, liquidity or expected financial performance? Third, what treatment is permitted under the applicable accounting, contractual and prudential rules? These questions are connected but not identical. An AI model might identify that a transaction has a lower predicted probability of delay than comparable transactions. That finding may be useful for operational planning and internal risk assessment. It does not automatically establish a lower Probability of Default under a regulatory model. Similarly, strong evidence that goods have been delivered may support a commercial claim, but it does not necessarily establish that the goods qualify as eligible collateral for a particular bank. Maintaining these distinctions is essential to regulatory credibility. The long-term opportunity is to improve the quality of the information entering financial decisions, reduce unnecessary information gaps and provide a more granular understanding of economic activity. If the resulting evidence supports improved underwriting or monitoring within the permitted framework, financial institutions may be able to make better-informed decisions. Any resulting improvement in pricing, capital efficiency or financing availability must be established through the applicable methodology and measured in practice. This is a more demanding proposition than claiming that operational data automatically reduces capital requirements. It is also a more credible foundation for innovation. 15. A New Relationship Between Supply Chain Management and Finance Supply chain management and corporate finance have traditionally developed distinct operational priorities. Supply chain teams focus on service levels, production continuity, procurement performance, inventory, delivery reliability and network resilience. Finance teams focus on cash flow, working capital, profitability, credit exposure, liquidity, funding costs and financial controls. These objectives are interdependent, but their systems, metrics and decision processes do not always provide a unified representation of their relationship. A procurement decision affects payment obligations. An inventory policy influences working capital and operational resilience. A production delay may affect delivery commitments, customer acceptance, invoicing and collection. A change in payment terms can alter the distribution of liquidity across suppliers and buyers. The Capital Twin offers a framework for making these relationships explicit. It connects operational events with the financial consequences they may produce, enabling decisions to be assessed across organizational boundaries. For example, a company considering an increase in safety stock could evaluate not only the operational benefit of improved service continuity but also the resulting cash commitment, storage costs, financing requirements and potential exposure to obsolescence. A procurement team negotiating payment terms could evaluate the effect on supplier liquidity, buyer working capital, contractual risk and the resilience of the wider commercial relationship. A treasury team could use operational forecasts to improve the timing of funding requirements, while recognizing that forecast cash flows remain subject to uncertainty and must not be treated as guaranteed receipts. These are not entirely new management disciplines. Working-capital optimization, integrated business planning, supply chain finance and cash-flow forecasting already address many of these issues. The proposed contribution of the Capital Twin is to connect them through a common financial interpretation of the underlying operational and contractual reality. That interpretation could make it easier to compare alternatives using consistent definitions and to expose the trade-offs between operational performance, liquidity, risk and capital efficiency. It also creates a more coherent foundation for AI applications that cross traditional functional boundaries. Rather than asking each department to optimize its own metrics independently, organizations could evaluate how local decisions affect the economic performance of the broader commercial process. This does not remove the need for specialized systems or functional expertise. It provides a way to connect their outputs to a shared economic objective. 16. The Network Opportunity: From Internal Coordination to Intercompany Capital Enterprise systems have historically focused on coordinating activities within the organization. Modern business networks extend this coordination to suppliers, customers, logistics providers and other external participants. This evolution is strategically important for capital optimization because many financial constraints emerge between companies rather than exclusively within them. A supplier may need liquidity to purchase raw materials before receiving payment from a buyer. A buyer may hold cash but lack visibility into the supplier's immediate funding needs. A logistics provider may possess evidence about the status of goods but not be connected to the financial assessment of the underlying transaction. Each participant holds part of the information needed to understand the economic relationship. A network that connects these participants can potentially improve the availability and consistency of that information, provided that the relevant parties authorize its use and that the architecture protects confidentiality, commercial sensitivity and data ownership. The Capital Twin could serve as the financial interpretation layer across such relationships. The objective would not be to create one unrestricted repository containing every company's commercial information. It would be to establish controlled mechanisms through which relevant information can be shared, verified and interpreted for specific purposes. A buyer might authorize the sharing of delivery and acceptance evidence with a financing institution. A supplier might provide information about an eligible receivable. A logistics provider might contribute authenticated shipment events. The financial institution would evaluate the combined information within its own risk and compliance framework. The scope of access, the legal basis for sharing, the permitted purposes and the retention requirements would need to be explicitly governed. Such a model could help reduce the fragmentation that makes some commercial exposures difficult or costly to assess. It could also create opportunities for more targeted financing, particularly where transaction-level evidence is stronger or more informative than the information available through conventional documentation alone. The potential benefits should not be confused with guaranteed outcomes. Network participation, data quality, transaction volume, interoperability, fraud controls, legal enforceability and the economics of intermediation would determine whether the model succeeds. Nevertheless, the strategic logic is clear: when operational processes extend across companies, the information needed to optimize capital often extends across companies as well. A capital architecture confined to the internal boundaries of a single enterprise may therefore capture only part of the opportunity. 17. Building the Architecture: Governance Before Autonomy The transition from concept to implementation requires disciplined architecture and governance. The first requirement is a reliable mapping between operational objects and their economic meaning. Contracts, orders, deliveries, invoices, receivables, payment obligations and inventory records must be linked in a way that preserves their relationships and lifecycle states. The second requirement is evidence governance. The architecture must distinguish between recorded events, externally verified facts, predictions, assumptions and unresolved disputes. It must also retain sufficient information about provenance, timing, permissions and the process by which evidence was validated. The third requirement is financial semantics. Operational attributes must be connected to clearly defined financial concepts without confusing internal analytical indicators with regulatory measures or legally recognized claims. The fourth requirement is model governance. Predictive systems must be evaluated for performance, stability, bias where relevant, limitations and suitability for their intended use. Their outputs must be distinguishable from authoritative transaction records and validated financial calculations. The fifth requirement is execution governance. An AI recommendation should not automatically become a financial commitment merely because the model expresses high confidence. Authority limits, segregation of duties, approval requirements, contractual controls and audit trails remain essential. The sixth requirement is interoperability. The architecture must accommodate different enterprise systems, data standards, legal environments and institutional risk frameworks without assuming that all participants use identical processes or definitions. Finally, the implementation must be measured against explicit economic objectives. A pilot should identify the problem it intends to solve, establish a baseline and define the expected improvement. It might focus on reducing the time required to verify commercial evidence, improving cash-flow forecasts, identifying avoidable working capital, reducing reconciliation effort or accelerating financing decisions for eligible transactions. The results should be evaluated against the full cost of implementation and operation, including the AI infrastructure where applicable. This is the practical test of the Capital Twin. A compelling conceptual architecture becomes strategically relevant when it can demonstrate measurable improvements under real operating conditions. The implementation should therefore progress from clearly defined use cases toward broader integration, rather than attempting to transform every enterprise process simultaneously. Autonomy should follow reliable information, validated models and effective controls. It should not be used as a substitute for them. 18. Measuring Success: From Model Performance to Capital Productivity The success of an AI system is often measured through technical indicators such as accuracy, latency, throughput and the rate of task completion. These indicators are useful, but they do not fully establish business value. In financial and supply chain applications, the relevant question is whether improved information changes decisions in ways that create measurable economic benefits without introducing unacceptable risks. For a Capital Twin implementation, useful measures may include the accuracy of cash-flow forecasts, the time required to verify transaction evidence, the cost of reconciling commercial records, the duration of financing assessments, the incidence of disputes, inventory-related financing costs and the quality of risk differentiation. Other measures may examine the proportion of eligible transactions that can be assessed through standardized processes, the speed with which material operational changes become visible to financial decision-makers and the extent to which capital is allocated to activities with an appropriate risk-adjusted return. No single indicator is sufficient. A faster financing process is not necessarily better if it increases fraud exposure or weakens credit controls. Lower inventory is not necessarily an improvement if it increases disruption risk. More accurate forecasts do not automatically create value unless the organization can act on them. A lower estimated risk does not necessarily justify a lower financing price unless the evidence supports that conclusion under the relevant methodology. The architecture should therefore be evaluated through a combination of operational, financial, risk and governance measures. The cost side must be equally comprehensive. Integration, data remediation, security, model maintenance, human review, computing resources, energy consumption and ongoing compliance all contribute to the economic equation. The objective is to determine whether the combined architecture produces a better outcome than the available alternatives. In some cases, a simple rule-based system may be sufficient. In others, predictive models or AI agents may create substantial value. The Capital Twin should enable the organization to select the appropriate tools according to the characteristics of the decision rather than prescribe a single technology for every problem. This is an important principle for long-term adoption. Capital productivity is not improved by introducing more technology indiscriminately. It is improved by allocating technology, information and financial resources where they produce the greatest defensible economic benefit. 19. From Payment Orchestration to Capital Orchestration The development of enterprise-embedded payment services illustrates the broader evolution of corporate financial technology. Integrating payment initiation, transaction processing, reconciliation and financial workflows into enterprise systems can reduce friction between business operations and the movement of money. It can improve visibility, simplify execution and connect payment activity more closely to the commercial events that generate it. These are meaningful capabilities. However, payment orchestration and capital orchestration address different levels of the economic process. Payment orchestration focuses on executing and coordinating payments through the relevant channels, institutions and controls. Capital orchestration asks a broader question: how should financial resources be allocated across operational commitments, expected cash flows, risk exposures and competing financing opportunities? The distinction is not that one is necessary and the other is optional. Efficient payment execution is an important component of a well-functioning financial architecture. But moving money efficiently does not, by itself, establish whether the underlying allocation of capital is economically optimal. A company can execute every payment correctly while maintaining excessive inventory, financing poorly performing activities or overlooking opportunities to improve the relationship between contractual commitments and available liquidity. Conversely, an organization can identify a valuable financing opportunity but fail to realize it because payment systems, data exchange or execution processes are fragmented. The Capital Twin is intended to address the broader allocation problem. It connects the information required to understand why capital is needed, when it may be needed, what economic activity it supports, which risks accompany it and how alternative uses of capital should be evaluated. In this sense, payment orchestration can contribute to the execution layer of a broader capital architecture, while the Capital Twin provides a proposed framework for the financial interpretation and optimization of the underlying economic activity. The distinction matters as enterprise software evolves toward integrated financial services and autonomous business processes. The long-term opportunity is not merely to embed more financial transactions into operational software. It is to connect those transactions to a more comprehensive understanding of the economic commitments and processes they serve. 20. The Strategic Thesis: Making the Real Economy Legible to Capital The four concepts described here form a coherent architecture. Contractual Gravity highlights the economic significance of commitments before all their consequences appear in accounting records. The Evidence Economy emphasizes the role of verifiable operational events in reducing information gaps and improving the assessment of commercial obligations. The Capital Twin connects operational and contractual reality to the language of financial risk, liquidity, collateral and capital allocation. The Financial Airbnb extends this logic toward a network model in which evidenced financing needs can potentially be matched with appropriate capital supply. Together, these concepts propose a different way of thinking about the relationship between enterprise technology and financial services. The objective is not to turn every operational event into a financial product. It is to make the economic characteristics of business activity more visible, more interpretable and more useful for decisions about capital. This distinction becomes increasingly important as AI capabilities expand. When operational information remains fragmented, artificial intelligence can help search, summarize and analyze it, but the resulting intelligence may remain disconnected from the financial decisions that matter most. When the information is linked to contractual obligations, verified events and governed financial semantics, AI can operate within a more coherent representation of economic reality. The difference is between asking a model to discover meaning from disconnected records and providing it with an architecture that establishes how those records relate to economic commitments, risk and financial outcomes. The latter does not remove uncertainty. It makes uncertainty easier to identify, measure and manage. Nor does it eliminate the need for professional judgment, financial regulation or institutional controls. It provides a stronger information foundation on which those disciplines can operate. SAP's enterprise footprint creates a potential foundation for this development because many of the relevant operational processes are already represented within enterprise systems. Realizing that potential, however, requires deliberate semantic design, interoperability, governance and demonstrable economic value. The existence of a large installed base does not automatically create a functioning capital network. The opportunity lies in connecting established operational capabilities with a financial architecture that can interpret their outputs consistently and make them useful across corporate and financial boundaries. If successful, such an architecture could support better working-capital decisions, more timely risk assessment, improved financing processes and more productive use of available capital. The extent of those benefits would depend on the quality of implementation, the participation of relevant institutions, the legal structure of transactions and the evidence generated in practice. These are substantial requirements. They are also the right requirements against which to evaluate the proposition. 21. The Next Frontier Is Economic Intelligence Artificial intelligence is becoming more capable, but capability alone does not determine its contribution to enterprise performance. The value of AI depends on the problems it addresses, the quality of the information it receives, the context in which its outputs are interpreted and the decisions those outputs support. In corporate finance, this means connecting models to the operational processes and contractual obligations that generate financial consequences. It means distinguishing between an accounting balance and a future commitment, between a recorded event and verified evidence, between a prediction and an authorized financial decision. It means recognizing that a transaction's economic characteristics cannot always be understood from a single data point or from the overall financial position of the company involved. And it means evaluating technology according to its contribution to risk-adjusted economic outcomes rather than assuming that greater computational sophistication necessarily creates greater value. The Capital Twin provides a framework for addressing these requirements by connecting operational reality with financial semantics. Contractual Gravity brings commitments into focus. The Evidence Economy provides a foundation for verifiable information. The Financial Airbnb explores how that information could help connect financing demand with available capital. The architecture is ambitious, but its underlying principle is practical: capital allocation improves when the economic reality behind a financial decision is better represented. For enterprises, this creates an opportunity to connect supply chain performance, working capital and financial strategy more closely. For financial institutions, it offers a way to investigate whether richer operational evidence can improve the assessment and monitoring of eligible exposures. For AI developers, it highlights the importance of providing models with reliable, contextualized and economically meaningful information. For technology platforms, it raises a strategic question about the next stage of enterprise integration: whether they can move beyond recording and executing transactions toward supporting a governed, evidence-based understanding of how those transactions consume, release and create economic value. None of these outcomes should be assumed in advance. They must be designed, tested, governed and measured. The standard of success should be clear. The architecture must improve decisions, produce measurable economic benefits, preserve appropriate risk controls and justify its total cost. That is the test of any serious innovation in enterprise finance. The next financial revolution will not come from creating more capital. It will come from unlocking more value from the capital already committed to the real economy. The central challenge is therefore not simply to build more intelligent models. It is to build a more intelligent economic architecture in which data acquires meaning, evidence supports trust, contracts reveal future commitments and financial decisions reflect the reality of the processes they are intended to finance. That is the proposition of the Capital Twin. And it is a proposition that should ultimately be judged not by the sophistication of its terminology, the number of AI agents it can accommodate or the scale of the technology behind it, but by the quality of the decisions it enables and the economic value those decisions demonstrably create. Connect and Stay Informed: Join the Conversation: Connect with fellow professionals in the SAP Banking Group on LinkedIn. https://www.linkedin.com/groups/92860/ Stay Updated: Subscribe to the SAP Banking Newsletter for the latest insights. https://www.linkedin.com/newsletters/sap-banking-6893665983048081409/ Explore More: Visit the SAP Banking Blog for in-depth articles and analyses. https://sapbank.blogspot.com/ Connect Personally: Feel free to send a LinkedIn invitation; I'm always open to connecting with like-minded individuals. ferran.frances@gmail.com I look forward to hearing your perspectives. Kindest Regards, Ferran Frances-Gil. #SAPPay #SAPBN4L #ContractualGravity #CapitalTwin #SAP #IFRS9 #CapitalOptimization #PredictiveFinance #SAPIFRA #AutonomousEnterprise #FerranFrances

SAP-RPT and the Evidence Economy: How Tabular AI Can Give the Capital Twin a Structural Competitive Advantage

1. The Missing Link Between Enterprise Data and Financial Intelligence The global economy generates an enormous volume of structured business information every day. Purchase orders, production records, inventory movements, transportation milestones, delivery confirmations, invoices, payment commitments and contractual obligations collectively describe how economic activity actually unfolds. Enterprise resource planning systems have spent decades organizing this information into relational structures. Yet a significant gap remains between managing the real economy and translating its operational reality into the financial language used to assess risk, allocate capital and determine financing costs. The Capital Twin is an architectural framework designed to bridge that gap. Its purpose is to connect the operational processes managed by enterprise systems with the financial models used by banks, insurers, investors and capital markets. Instead of relying exclusively on aggregated corporate financial statements and conventional credit assessments, the Capital Twin seeks to establish a more granular representation of the economic characteristics of individual assets, transactions and contractual commitments. The central principle is that the financing conditions of an economic asset should reflect not only its accounting value or the creditworthiness of its owner, but also its traceability, contractual protection, operational status, expected performance and recoverability. Achieving this requires more than integrating databases. It requires a mechanism capable of transforming structured operational information into reliable predictions, verifiable evidence and financially meaningful conclusions. This is where SAP's tabular artificial intelligence capabilities become strategically important. SAP-RPT, supported by Tabular AI on SAP and the SAP AI Core runtime, offers a technological foundation for making the Evidence Economy more scalable, predictive and economically actionable. The competitive opportunity lies in connecting this capability to the semantic and relational structure of enterprise processes and then translating its outputs into the language of capital markets. 2. Why Structured Business Data Requires a Different Kind of AI Most enterprise information is not originally created as free-form text. It exists in tables, transactions, master data, reference data and relationships among business objects. A purchase order has a supplier, purchasing organization, material, quantity, price, delivery schedule and contractual context. A goods movement references a material, plant, storage location and movement type. An invoice refers to commercial obligations, tax classifications, payment terms and accounting records. These relationships determine the meaning of the information. A conventional relational database can retrieve and combine records using SQL joins. Such joins remain essential for deterministic processing, reporting and data integration. But a join does not, by itself, predict whether a delivery will be late, whether a supplier is likely to fulfil a commitment or whether a particular combination of operational conditions indicates elevated financial risk. Those questions require analytical models that can identify patterns across structured observations. Large language models are powerful tools for interpreting language, generating content and coordinating complex workflows. However, converting structured business records into text and asking a language model to reason over them is not necessarily the most efficient approach for every numerical prediction or classification task. Tabular foundation models are designed specifically for this different problem. They work natively with structured data, learning patterns across rows and columns and using the relationships represented in the data to produce predictions. SAP-RPT stands for Relational Pretrained Transformer. SAP describes it as a fully managed, table-native foundation model that supports predictive tasks such as classification and regression through in-context learning, without requiring a separate training or fine-tuning cycle for every use case. SAP also describes explainability capabilities that help users identify which input columns and contextual records influenced a prediction. SAP-RPT product information. This design is particularly relevant to enterprise environments, where many business decisions depend on structured data that changes continuously. Rather than building and maintaining an independent predictive model for every narrowly defined business problem, an organization can evaluate whether a pretrained tabular model can support multiple use cases through appropriately designed prediction requests and contextual examples. That does not eliminate the need for data preparation, model evaluation, business-rule implementation or validation. It can, however, reduce the amount of task-specific model development required. For the Capital Twin, this distinction has strategic significance. The objective is not simply to analyze enterprise data faster. It is to make predictive analysis economically practical across a much broader universe of assets and business processes. 3. From Relational Tables to Economic Meaning The competitive potential of SAP's tabular AI becomes clearer when we examine the structure of SAP enterprise data. SAP systems do not merely store isolated business facts. They organize them through business objects, identifiers, document relationships, master data, organizational structures, domains, permitted values and application-level validation rules. These elements help define what a record represents and how it relates to other records. Consider a shipment of industrial components. Its economic significance may depend on a network of related information: The purchase order establishes the commercial requirement. The supplier and material master data identify the parties and goods. Production records indicate whether the goods have been manufactured. Warehouse and transportation records describe their location and movement. Delivery milestones indicate whether contractual dates are being met. Inspection records provide evidence about quality status. Customer orders and contractual commitments establish the expected commercial outcome. Invoices and payment terms describe the associated financial obligations. A conventional query can join these records to construct a consistent view of the transaction. A tabular predictive model can then use relevant structured features to estimate outcomes such as transportation lead time, delivery delay, payment lateness or other defined business variables. The distinction is important: relational integration establishes what the records say; predictive modelling estimates what is likely to happen; evidence validation establishes what can be relied upon financially or contractually. These are complementary functions, not interchangeable ones. A domain value or reference-table entry can establish that a field contains an allowed value. It does not automatically prove that the underlying event occurred as reported. Likewise, a prediction can indicate a high probability of successful delivery without establishing legal ownership of the goods or the enforceability of a customer commitment. The Capital Twin needs all three dimensions. First, the operational information must be assembled and interpreted correctly. Second, predictive models must evaluate relevant uncertainties. Third, deterministic controls, contractual validation and audit mechanisms must establish which conclusions can legitimately support a financial decision. This is the foundation of the Evidence Economy. 4. The Evidence Economy: Making Operational Reality Financially Usable The Evidence Economy is the principle through which the Capital Twin seeks to transform verifiable business events into information that can support financial decisions. Traditional credit assessment often begins with the company requesting financing. Its financial statements, debt levels, credit history, available collateral and repayment capacity provide the basis for determining its risk profile. These factors remain essential. Nevertheless, they may not fully capture the changing characteristics of every asset or transaction within a complex supply chain. Two companies with similar financial profiles may have very different operational exposures. Equally, two transactions involving the same company may have different risk characteristics because their contractual protection, traceability, delivery reliability, payment arrangements and recovery prospects differ. The Evidence Economy seeks to make these differences visible. Its analytical sequence is: Operational events → Relational context → Predictive intelligence → Verified evidence → Financial risk assessment → Potential capital-cost improvement. For example, an inventory position supported by a confirmed customer order, traceable transportation records, valid insurance and a strong delivery history may offer a different risk profile from inventory whose destination, contractual status or recoverability is uncertain. The model does not assume that the first position automatically deserves cheaper financing. It provides a basis for investigating whether the difference is material, measurable and acceptable to a financing institution. Evidence becomes economically useful when it changes a decision. That decision might concern whether an asset is eligible for financing, how much exposure should be recognized, what additional protection is needed, whether a transaction should receive enhanced monitoring or what pricing conditions are appropriate. The resulting framework could support a shift from evaluating only the financial condition of a company to assessing the economic characteristics of the specific transactions being financed. For this to work, the system must process evidence at a frequency and cost consistent with the economics of the underlying activity. Manual investigation may be reasonable for a small number of high-value transactions. It becomes less practical when the objective is to evaluate millions of interdependent business events across international supply chains. This is the point at which tabular AI becomes strategically relevant: it can help make the predictive component of the Evidence Economy repeatable across large numbers of structured transactions. 5. The Correct Technological Architecture: SAP-RPT, Tabular AI and SAP AI Core The technology should be understood as a combination of distinct capabilities rather than a single product performing every function. SAP-RPT is the predictive model. It is designed to make predictions from structured relational business data through classification, regression and in-context learning. Tabular AI on SAP is the broader capability for operationalizing tabular intelligence. It brings together tabular foundation models, orchestration, contextualization and governance to support predictive workflows across enterprise use cases. SAP AI Core provides the managed runtime and deployment environment through which models and tabular workflows can be operated at enterprise scale within the SAP Business AI Platform. SAP's architecture guidance recommends using Tabular AI orchestration for most production scenarios because it can manage contextual data selection and prediction requests. Direct model API access remains available for evaluation and specialized integrations. SAP architecture guidance. This architecture matters because enterprise prediction is not simply a matter of sending a table to a model. A production workflow must identify the prediction target, select appropriate input features, retrieve relevant historical examples, manage contextual information, execute the prediction, record the result and evaluate whether the model performs adequately on representative data. It must also deal with changing business conditions, incomplete records, data access permissions, monitoring and model governance. Tabular orchestration can help standardize these tasks and reduce the need to implement every element separately for each use case. For the Capital Twin, this creates the possibility of a reusable predictive layer supporting several economic functions. The same general architecture could be evaluated for delivery reliability, payment-delay estimation, supplier performance, inventory realization, operational disruption and other variables relevant to financing decisions. Each use case would still require its own definition, validation and assessment of predictive performance. A common platform does not mean that one prediction model automatically solves every financial problem. The strategic benefit is the potential to reuse the infrastructure and modelling approach across multiple processes rather than treating each predictive problem as an isolated technology project. 6. Why SAP's Enterprise Context Can Create a Competitive Advantage The potential differentiation of SAP's tabular AI is not based solely on the existence of a pretrained model. Other organizations can develop or deploy models for structured data. The more significant opportunity lies in the combination of table-native predictive technology with enterprise process knowledge, structured business information and an established environment for operationalizing AI. SAP systems contain extensive representations of how organizations purchase, manufacture, transport, sell, invoice and account for economic activity. This context can help developers identify relevant business variables, understand how operational records relate to each other and formulate predictive questions grounded in actual enterprise workflows. SAP's tabular AI offering also supports data beyond SAP systems, so the opportunity is not necessarily limited to transactions originating in a single ERP environment. Tabular AI on SAP. For the Capital Twin, three potential advantages follow. 6.1 Reusable predictive capability If a pretrained tabular model can deliver acceptable results without requiring a separately trained model for every narrowly defined use case, development and maintenance effort may be reduced. This matters because the Evidence Economy requires more than one prediction. It potentially requires many different predictions across procurement, manufacturing, logistics, contractual performance and financial risk. The economics of the architecture improve if predictive capabilities can be reused without compromising accuracy or reliability. 6.2 Operational integration Predictions become more valuable when they can be integrated into existing business workflows rather than remaining isolated analytical outputs. A delivery-risk prediction, for example, could inform inventory planning, exception management or a Capital Twin assessment of an asset's financing characteristics. Tabular AI on SAP is designed to make predictive insights available through business workflows, custom applications and Joule-related capabilities. The specific integration required for the Capital Twin would need to be designed and validated. 6.3 Traceability and governance Financial decisions require more than a prediction score. They require an explanation of which data was used, what the model estimated, which controls were applied and how the output affected the final decision. SAP documents features for tracing predictions to influential rows and columns. These explanations are useful diagnostic signals, although they should not be treated as proof of causality or as a substitute for independent validation. The Capital Twin could build on this foundation by retaining the source evidence, prediction outputs, applicable financial rules and resulting decisions in an auditable chain. The competitive opportunity therefore lies in the integration of predictive capability, business context, workflow execution and financial governance. 7. Business Case: Financing Inventory and Goods in Transit Consider a hypothetical international manufacturer with annual revenue of €2.4 billion. The company has €150 million tied up in work in progress, inventory, consignment stock and goods in transit. It also has substantial contractual commitments and foreign-exchange exposures associated with its international supply chain. The company finances part of its working capital through banks. Financing conditions depend on its credit profile, the nature of the assets, the available guarantees and the lender's risk assessment. The manufacturer wants to determine whether a more granular evaluation of its operational evidence could improve financing terms. The objective is not to assume that SAP-RPT automatically reduces borrowing costs. It is to test whether structured operational evidence can identify meaningful differences in transaction risk that conventional assessments do not fully capture. 7.1 The initial problem The company faces several sources of uncertainty: Some shipments arrive later than expected. Production delays affect the timing of customer deliveries. Inventory positions have different levels of traceability and contractual protection. Payment delays create uncertainty about the timing of cash inflows. Financing assessments do not always incorporate the latest operational evidence. The company has information relevant to these issues across its ERP, warehouse, logistics, order-management and financial systems. However, that information is distributed across related business objects and is not necessarily translated into a unified, continuously updated financial assessment. 7.2 Building the evidence model The Capital Twin establishes a structured representation of the relevant assets and transactions. For each financing candidate, it assembles the applicable evidence, potentially including: Purchase-order and sales-order references. Material and inventory characteristics. Production and inspection milestones. Shipment identifiers and transportation status. Contractual delivery dates and customer commitments. Insurance and collateral documentation. Historical delivery and payment performance. Relevant invoice, collection and foreign-exchange information. Deterministic validation rules check the consistency of the records, identify missing evidence and detect conflicting or duplicated claims. Where necessary, additional controls verify that contractual rights, ownership, insurance coverage and other legal or financial requirements are satisfied. The result is a structured dataset representing the current operational and contractual state of the assets under consideration. 7.3 Applying SAP-RPT SAP-RPT can then be evaluated for selected prediction tasks. For example, one task might estimate the expected transportation lead time for a shipment using structured variables such as material, origin, destination and goods-issue date. SAP itself uses transportation lead-time prediction as an example of a tabular AI use case. Other candidate tasks could include payment-delay classification or delivery-performance estimation, provided that suitable historical examples and reliable target variables are available. The model is evaluated against representative holdout data that was not used as contextual examples for the corresponding prediction. The assessment should compare its performance with relevant baselines, including existing operational forecasts and appropriately chosen alternative models. The organization should measure not only average prediction accuracy but also performance across different suppliers, routes, product classes and operating conditions. A model that performs well on average but fails on a high-risk subset may be unsuitable for a financing decision. Where results are acceptable, the prediction workflow can be integrated into the Capital Twin's evidence and risk-assessment processes. 7.4 From operational predictions to financial decisions Suppose the model estimates that a particular shipment is likely to arrive later than its contractual delivery date. That prediction does not itself establish a financial loss. The Capital Twin must evaluate the potential consequences. Would the delay postpone customer payment? Could it trigger contractual penalties? Is substitute inventory available? Does insurance cover the relevant event? Would the delay materially affect the lender's recovery prospects? The financial model then assesses how these factors affect the transaction's risk profile. A different shipment might have a stronger delivery record, better contractual protection and more reliable payment arrangements. Its financing assessment could therefore differ, provided that the relevant evidence is verified and the lender's methodology recognizes the difference. The purpose is to enable financing decisions to reflect the characteristics of individual assets and transactions rather than relying exclusively on a company-level credit classification. 7.5 Illustrative financial assumptions Assume the following hypothetical figures for the manufacturer: Business-case parameterIllustrative assumptionAnnual revenue€2.4 billionRelevant inventory and goods-in-transit pipeline€150 millionAverage financing balance potentially affected€100 millionBaseline annual financing rate on that balance6.0%Hypothetical rate improvement after lender validation0.20 percentage pointsAnnual implementation and operating cost€250,000 The €100 million financing balance is an assumption for the example, not the entire €150 million operational pipeline. The 20-basis-point improvement is also hypothetical; it is not an expected or guaranteed result of SAP-RPT. At the assumed baseline rate, annual financing expense on the relevant balance would be: €100 million × 6.0% = €6 million. If a lender independently verified the evidence, accepted the resulting risk assessment and agreed to reduce the rate by 20 basis points, the annual financing benefit would be: €100 million × 0.20% = €200,000. After the assumed €250,000 annual operating cost, the net annual benefit would be negative €50,000. This first scenario demonstrates an important point: even a technically successful predictive system does not necessarily produce an attractive business case. The benefit must exceed the full cost of data integration, technology, validation, governance and operation. Now consider a second scenario in which the accepted financing improvement is 40 basis points on the same €100 million balance. The annual financing benefit would be €400,000. After the €250,000 operating cost, the net annual benefit would be €150,000, before implementation costs, taxes and any additional effects. The business case becomes more attractive if the architecture also reduces operational losses, improves working-capital utilization or supports additional financing opportunities. Those benefits should be measured independently to avoid double counting. The example does not establish that SAP-RPT will generate a 20- or 40-basis-point reduction. It demonstrates how the Capital Twin could connect a measurable financing outcome to the economic value of verified evidence. 7.6 What must be proven in a pilot? A credible pilot should answer five questions. First: Does the model predict better? Compare SAP-RPT with existing forecasting methods and relevant alternative models using representative holdout data. Second: Is the evidence reliable? Test the completeness, consistency, provenance and contractual validity of the operational records. Third: Does the prediction improve a financial decision? Demonstrate that the output changes a defined risk assessment, eligibility decision, monitoring requirement or pricing recommendation. Fourth: Will a financing institution recognize the improvement? Obtain an explicit assessment from the relevant lender or funding partner. A lower predicted operational risk does not automatically imply a lower regulatory capital requirement or borrowing rate. Fifth: Does the economics justify the system? Calculate total integration, model-operation, governance and financing costs against verified benefits. Only after these questions have been answered should the organization consider scaling the approach across additional assets and processes. 8. Scaling the Evidence Economy Across the Enterprise The previous example involves inventory and goods in transit. The same broad architecture could be evaluated in other areas of the enterprise. In manufacturing, predictions of production completion and quality-related delays could support better assessments of contractual performance. In logistics, shipment reliability and exception detection could help identify assets whose delivery or recovery prospects differ materially. In procurement, supplier-performance predictions could inform operational resilience assessments and the evaluation of contractual dependencies. In receivables management, payment-delay predictions could improve cash-flow forecasting and the identification of exposures requiring additional monitoring. In insurance, structured asset, maintenance and incident information could support selected risk-assessment workflows, subject to the requirements of the specific insurance model. Each application would require its own evidence definitions, model evaluation and financial interpretation. The objective is not to use one universal prediction as a substitute for domain-specific analysis. Instead, the architecture could provide a common mechanism for converting structured business information into validated predictive outputs and then connecting those outputs to defined financial decisions. This creates a potential network effect within the enterprise: once the data relationships, governance mechanisms and integration patterns are established, additional use cases may become less expensive to implement. That effect is not automatic. It depends on data quality, reuse of existing components, model performance and the degree to which the use cases share meaningful structures. Nevertheless, the possibility of reusing predictive infrastructure across multiple business processes is strategically important. The Evidence Economy requires breadth as well as depth. Its potential value comes from evaluating many different kinds of economic activity, not from optimizing a single isolated prediction. 9. The Capital Twin: Translating Evidence into Capital-Markets Language The final step is the one that differentiates the Capital Twin from a conventional predictive analytics initiative. SAP-RPT can estimate outcomes from structured business data. Tabular AI on SAP can help operationalize those predictions. Neither component independently determines the correct cost of capital for an asset. That requires a financial architecture. The Capital Twin must translate verified operational and contractual evidence into the variables and concepts used by financial institutions. Depending on the transaction, these may include: Probability of default (PD). Loss given default (LGD). Exposure at default (EAD). Expected credit loss. Collateral eligibility and valuation. Liquidity and funding requirements. Regulatory capital treatment. Return on risk-adjusted capital (RAROC). Contractual protection and recovery expectations. Market-based financing spreads. The relationships among these variables must be defined through appropriate financial models, contractual structures and regulatory rules. For example, a better delivery forecast might reduce uncertainty about the timing of customer payment. But the impact on credit risk depends on the contract, counterparties, recovery rights and other relevant factors. The effect on regulatory capital depends on the applicable framework and whether the relevant requirements are satisfied. The Capital Twin therefore acts as the bridge between predictive operational intelligence and financial interpretation. Its objective is to establish a more granular financial representation of economic assets, one in which the cost and availability of capital can reflect their measurable characteristics rather than being determined exclusively by aggregated company-level assessments. The word Twin is important in this context. The ambition is not merely to produce a report or a risk score. It is to maintain a representation of the economic and financial state of assets and transactions as their operational, contractual and predictive characteristics change. This representation can then inform financing decisions as new evidence becomes available. The architecture would need to preserve the distinction between observed facts, model estimates, contractual conclusions and financial decisions. That distinction is essential for auditability, responsible use and acceptance by external financial institutions. 10. Why This Could Become a Structural Competitive Advantage The competitive proposition rests on the combination of four capabilities. First, enterprise process structure. SAP environments already organize large volumes of business activity into relational records and interconnected operational processes. Second, table-native predictive intelligence. SAP-RPT is designed to generate predictions from structured data without requiring a separate training cycle for every use case. Third, operational orchestration. Tabular AI on SAP and SAP AI Core can help integrate prediction workflows, contextual data selection, execution and governance. Fourth, financial interpretation. The Capital Twin adds the architecture required to translate operational evidence into risk, collateral, liquidity and capital-market concepts. No individual capability is sufficient by itself. A relational database can store and connect business records but cannot automatically establish their financial implications. A predictive model can estimate outcomes but cannot independently verify legal rights or determine regulatory treatment. A financial model can price risk but may lack sufficiently granular operational evidence. The opportunity arises when these capabilities are connected. The potential competitive advantage is therefore not that SAP-RPT makes every query faster or that it replaces all existing financial models. It is that the broader architecture could make the systematic evaluation of operational evidence more economically viable across a large number of transactions. If this can be demonstrated in practice, the Capital Twin could move beyond isolated predictive use cases toward a reusable framework for evidence-based capital allocation. 11. The Validation Agenda: From Architecture to Demonstrable Value A strong strategic proposition must ultimately be supported by measurable results. The first requirement is a technical benchmark. The organization should measure prediction quality, latency, throughput, stability and operating cost for representative enterprise datasets. The second requirement is an evidence benchmark. It should measure how frequently records are incomplete, contradictory, duplicated or insufficiently supported, and how effectively the controls identify these issues. The third requirement is a financial benchmark. It should establish whether the evidence and predictions materially improve a defined decision compared with the existing process. The fourth requirement is external validation. Lenders, insurers or other financial counterparties must confirm which outputs they can incorporate into their own decisions and under what conditions. Finally, the complete business case must account for technology costs, integration effort, governance, ongoing maintenance, financing benefits and any independently verified operational savings. The model's explainability features can help analysts understand which rows and columns influenced a prediction, but those signals must be interpreted carefully. They do not by themselves establish causation, legal validity or financial materiality. Likewise, an accurate prediction is not necessarily economically valuable. The relevant question is whether it improves a decision enough to justify the cost of obtaining and acting on it. This validation agenda is not a weakness in the Capital Twin proposition. It is the mechanism through which the proposition can become credible to enterprise customers and financial institutions. Conclusion: Making the Evidence Economy Computationally and Financially Viable The next frontier in enterprise AI is not simply generating more information. It is using the structure of business data to make better decisions about the economic activity that information represents. SAP-RPT offers a model designed specifically for structured relational data. Tabular AI on SAP provides capabilities for operationalizing tabular predictions, while SAP AI Core supplies the managed runtime and orchestration environment. Together, these technologies can provide important building blocks for the Capital Twin. Their strategic relevance lies in making it more practical to interpret operational events, predict business outcomes and produce repeatable analytical outputs across multiple enterprise processes. The Evidence Economy supplies the next step: establishing which outputs are supported by reliable evidence and how that evidence changes the assessment of an asset or transaction. The Capital Twin then translates those assessments into the language of financial institutions and capital markets, connecting operational characteristics with risk, collateral, liquidity, capital requirements and potential financing costs. The result would not be a system in which AI automatically declares every asset financeable or assigns a definitive price to every transaction. It would be an architecture in which verified evidence can support more granular, timely and economically grounded financial decisions. The distinction is fundamental. SAP-RPT helps turn structured enterprise data into predictive intelligence. The Evidence Economy turns that intelligence, together with verified business facts, into financially usable evidence. The Capital Twin translates that evidence into capital-markets language. If validated at scale, this combination could create a meaningful competitive advantage: enabling financial institutions to assess the economic reality behind assets and transactions with greater precision, and potentially to allocate and price capital in a way that more closely reflects the risks and opportunities of the real economy. The ultimate measure of success will not be the number of tables processed or predictions generated. It will be whether the architecture produces demonstrably better decisions and measurable economic value. Connect and Stay Informed: Join the Conversation: Connect with fellow professionals in the SAP Banking Group on LinkedIn. https://www.linkedin.com/groups/92860/ Stay Updated: Subscribe to the SAP Banking Newsletter for the latest insights. https://www.linkedin.com/newsletters/sap-banking-6893665983048081409/ Join my readers on Medium where I explore Capital Optimization in depth. Follow for actionable insights and fresh perspectives https://medium.com/@ferran.frances Explore More: Visit the SAP Banking Blog for in-depth articles and analyses. https://sapbank.blogspot.com/ Connect Personally: Feel free to send a LinkedIn invitation; I’m always open to connecting with like-minded individuals. ferran.frances@gmail.com I look forward to hearing your perspectives. Kindest Regards, Ferran Frances-Gil. #SAPBusinessAIPlatform #ContractualGravity #CapitalTwin #DigitalTransformation #FinancialTwin #SAPPay #CorporateTreasury #BusinessBackbone #FutureOfFinance #CapitalOptimization #FerranFrances