Melio

1.1 Company Identity, Architecture, and Business Model

Melio Payments Inc. was founded in 2018 and is headquartered in New York City, with Bessemer Venture Partners describing a team assembled in New York and Tel Aviv [CO001, CO002]. The company was created to address small-business cash-flow friction: suppliers may demand ACH or checks while buyers seek flexibility over payment method and timing [CO003]. Melio's workflow allows an SMB to fund an eligible vendor payment by card even when the vendor receives another supported payment type [CO004]. Third-party 2026 pricing sources describe a free entry tier plus Core at $25 per month and Boost at $55 per month; one profile also reports a 2.9% card-payment fee, but live terms require confirmation [CO005]. In June 2026, a company-issued release announced an agent-powered network intended to execute buyer payments through supplier accounts-receivable systems without requiring suppliers to join a new portal [CO009].

1.2 Founders, Governance, and Operational Leadership

The company was co-founded by Matan Bar, Ilan Atias, and Ziv Paz [CO001]. A 2026 third-party profile identifies Bar as CEO, Atias as CTO, and Paz as CPO; it also reports that Bar previously led consumer peer-to-peer products at PayPal, Atias previously held an engineering leadership role at AppsFlyer, and Paz has payments-product experience [CO002]. Bessemer's account corroborates Bar's prior PayPal product role and emphasizes the three founders' complementary backgrounds, but the assigned pool does not independently verify the complete post-acquisition reporting structure [CO002, CO003]. A June 2026 company release quotes Aharon Levine as vice president of payments strategy, providing one additional current leadership datapoint [CO009]. Founder continuity supports domain knowledge, yet the absence of a complete Xero-era governance roster leaves key-person dependence and decision rights as diligence questions rather than established conclusions.

1.3 Capitalization History, Ownership, and the Strategic Xero Acquisition

A third-party profile reports approximately $706 million of venture funding across five rounds through the late-2021 Series D, including a $501 million Series D at a $4.0 billion valuation; these figures are not supported here by an audited filing and should remain reported, historical metrics [CO006]. Bessemer separately stated in September 2020 that Melio had raised $144 million across several rounds and identified itself as an investor, corroborating the earlier financing trajectory without validating the later cumulative total [CO003]. Competitor Cleo Pay reports that Xero announced the acquisition in June 2025 and completed it on October 15, 2025 for roughly $2.5 billion of consideration, described as about $2.15 billion in cash and approximately $360 million in Xero shares, plus up to $500 million in employee incentives over three years [CO007]. The $2.5 billion figure is transaction consideration, not a reusable standalone valuation or proof of cash available to Melio.

1.4 Operational Scale, Network Reach, and Key Milestones

Melio's current scale is disclosed through a mixture of company claims and secondary reporting rather than audited standalone statements. The official homepage claims more than 100,000 business owners, 40 million bills paid, over $100 billion processed, and more than two million vendors paid [CO013]. A June 2026 company release separately claims more than $30 billion in annual payment volume and nearly 100,000 businesses, while naming Capital One, Shopify, and Fiserv as examples in its syndication model [CO009]. Fintech.TV reports that Xero's acquisition announcement cited 80,000 SMB customers, more than $30 billion in payout volume, and $153 million in FY25 revenue; the assigned evidence does not include the underlying Xero disclosure, so the metric remains secondhand [CO008]. Trustpilot reviews show both favorable support experiences and specific adverse reports of account closure and weak approval workflows, indicating operational variance rather than a measured incident rate [CO010]. Melio says it remains a standalone Xero platform, while competitor Cleo Pay reports Xero embedding by March 2026 [CO014, CO015].

1.5 Exhibits

2.1 Market Definition, Boundary Logic, and Status-Quo Substitutes

The business-to-business payments landscape in the United States represents an aggregate annual transaction volume of approximately $25 trillion, of which small and medium-sized businesses account for roughly $10 trillion in payments to external vendors, suppliers, and contractors. Melio's primary addressable market boundary encompasses non-payroll operational vendor disbursements, utility payments, inventory procurement, and commercial services for micro and small enterprises. We explicitly exclude enterprise treasury operations, high-frequency supply chain electronic data interchange transactions, consumer peer-to-peer transfers, and internal employee payroll from this core scope. The dominant status-quo substitute is not incumbent enterprise software, but manual paper checks—which historically account for roughly 40% of SMB commercial disbursements—and basic bank portal automated clearing house transfers. Small business owners rely on these legacy rails because traditional accounts payable automation platforms enforce rigid setup overhead, complex chart-of-accounts mapping, and high monthly subscription minimums that over-serve single-operator shops and micro-businesses.[CM001, CM002, CM003, CM004, CM005]

2.2 Market Sizing Lenses and Constrained TAM/SAM/SOM Boundaries

Evaluating the addressable market for SMB bill payment requires dissecting aggregate transaction volume into realizable software and payment fee revenue. While the top-line US B2B payments volume reaches $25 trillion, the serviceable addressable market contracts to the estimated $10 trillion transacted annually by the 31 million US small businesses, of which 81% are non-employer sole proprietorships or micro-firms. Melio's serviceable obtainable market reflects the monetizable gross processing volume flowing across flexible payment rails—specifically credit card transactions, accelerated same-day transfers, and international disbursements—rather than non-monetized free ACH transfers. Because Melio provides standard ACH processing and check mailing without subscription fees on entry tiers, the software monetization pool is structurally narrower than gross payment flow. Achieving commercial scale requires processing double-digit billions in gross volume across tens of thousands of active business endpoints to generate meaningful fee income.[CM001, CM002, CM006, CM007, CM008]

2.3 Buyer Segmentation, Budget Ownership, and Workflow Adoption Paths

Purchasing decisions in Melio's core target market differ fundamentally from mid-market corporate accounts payable. In micro-enterprises and small retail operators, such as independent wine merchants, specialty craft producers, and local trade contractors, the business owner or general manager personally directs bill approvals and controls the operating bank account. Cash flow volatility rather than back-office labor reduction serves as the primary adoption catalyst: business owners face acute working capital timing mismatches, needing to hold cash until vendor due dates while suppliers demand rapid settlement. Melio captures this workflow by enabling business payers to fund bills with commercial credit cards—extending float up to the card billing cycle—even when the recipient vendor only accepts bank ACH or physical paper checks. Conversely, as businesses scale beyond twenty employees, workflow ownership migrates to dedicated bookkeepers and finance controllers who prioritize multi-level approval hierarchies, automated tax compliance, and fraud underwriting over consumerized simplicity.[CM003, CM009, CM010, CM011, CM012]

2.4 Growth Drivers, Adoption Constraints, and Sizing Diligence Gaps

Market expansion is propelled by two compounding tailwinds: the ongoing secular migration away from physical paper checks toward digital payment rails, and the rapid adoption of embedded accounting workflows powered by integrations with platforms like QuickBooks. Furthermore, unilateral two-sided network virality accelerates merchant acquisition: when an active Melio user issues a payment, the recipient vendor is introduced to the platform to specify delivery preferences, frequently converting into an active payer. However, adoption encounters significant structural constraints. First, Melio does not underwrite buyer credit risk or offer net-terms working capital financing, leaving B2B sellers exposed to customer invoice default risks. Second, scaling businesses encounter operational ceilings when approval hierarchies and complex enterprise resource planning integrations prove insufficient compared to mature enterprise solutions. Finally, critical diligence gaps remain regarding the precise proportion of gross payment volume that elects fee-bearing payment methods versus zero-margin free ACH rails.[CM004, CM009, CM013, CM014, CM015, CM016]

2.5 Exhibits

3.1 Competitive Landscape & Market Segmentation

The small and medium business (SMB) accounts payable (AP) automation market divides across four distinct competitive categories: dedicated AP and bill-pay platforms, spend-management and corporate card disruptors, B2B net terms and seller-financing specialists, and native accounting ledgers. Melio's core value proposition centers on eliminating manual check writing and administrative payment burdens for small teams without mandating upfront software subscription fees or counterparty enrollment. However, enterprise competitors such as BILL dominate mid-market procurement with comprehensive ERP integrations and sophisticated compliance controls, while platforms like Ramp bundle bill payment into zero-subscription corporate card architectures. Furthermore, niche players like ResolvePay focus on seller-side credit risk and net terms financing rather than buyer-side invoice disbursement, establishing clear functional boundaries across B2B transaction management.[CP001, CP002, CP003, CP004]

3.2 Capability Architecture, Pricing Mechanics, and Lock-In Dynamics

Evaluating AP software requires balancing base subscription overhead, per-seat licensing, and transaction-level fees against workflow depth. Melio's Go plan provides a free entry tier with five monthly ACH payments, but caps user access at a single seat, forcing growing organizations onto paid tiers such as Core ($25/month plus $10/user) or Unlimited ($80/month) once multi-user approval routing is introduced. In contrast, BILL operates on a per-user pricing model starting at $49 per user monthly, offering bidirectional sync across diverse ERP environments including Sage Intacct, NetSuite, and Microsoft Dynamics 365, alongside automated OCR invoice extraction and complex multi-step approvals. For leaner teams, spend platforms like Ramp offer free software models monetized through interchange on corporate card volume, whereas native accounting bill-pay add-ons (such as QuickBooks Bill Pay and Zoho Books) keep transaction execution directly inside existing ledgers, avoiding secondary software reconciliation.[CP005, CP006, CP007, CP008, CP009]

3.3 Moat Durability, Platform Vulnerabilities, and Adverse Risk

Melio's competitive moat rests primarily on user experience simplicity, decoupled payment rail mechanics (enabling payers to use credit cards even when vendors accept only checks or bank transfers), and deep accounting sync into QuickBooks and Xero. However, this defensive moat exhibits vulnerabilities in pre-payment workflow automation, customer support accessibility, and cross-border payment reliability. Independent user evaluations and review data highlight operational friction points, including unexpected payment holds triggered by automated compliance algorithms, limited phone support on lower-tier plans, and manual invoice data entry requirements due to the absence of native AI extraction tools. Furthermore, following Xero's acquisition of Melio, prospective buyers using competing general ledgers must weigh whether product roadmap investments will increasingly prioritize Xero-native workflows over neutral cross-platform parity.[CP010, CP011, CP012, CP013, CP014]

3.4 Exhibits

4.1 Revenue Model and Monetization Mechanisms

Melio operates an atypical hybrid monetization architecture within the business-to-business accounts payable software sector. Rather than imposing mandatory upfront per-seat licensing fees or fixed monthly subscription hurdles on small business accounts, Melio maintains a basic plan providing free standard automated clearing house bill payments to lower customer acquisition friction and expand top-of-funnel reach across commercial operators. Monetization activates dynamically when business users opt into value-added transaction capabilities, including card-funded vendor disbursements, expedited payment rails, and international transfers. Alongside direct self-serve monetization, Melio generates commercial revenue via embedded software and white-label distribution agreements across financial institutions, vertical SaaS platforms, and enterprise business partner networks.[CI001, CI002, CI003, CI004, CI005]

4.2 GTM Channel Economics and Cost Structure

Distribution efficiency has historically relied on two complementary go-to-market motions: direct small business digital acquisition and syndicated partner-led distribution. Syndicated channels through core banking platforms, software ecosystems, and accounting integrations target an addressable pool of approximately 3,500 financial institutions and up to 18 million small businesses across partner networks. However, partner-led distribution introduces structural volatility and counterparty roadmaps risks, exemplified by the wind-down of the embedded QuickBooks Bill Pay powered by Melio integration. Service delivery costs encompass interchange expenses on card transactions, payment gateway fees, banking partner clearing charges, verification operations, customer support overhead, and cloud infrastructure requirements.[CI006, CI007, CI008, CI009]

4.3 Public Scale Traction and Capital Adequacy Under Xero

Publicly confirmed operational milestones demonstrate substantial platform scale, with over $100 billion in total processed volume, more than 40 million bills paid, over 2 million receiving vendors, and an active business base exceeding 100,000 operators. Prior to its acquisition by Xero announced in June 2025 and finalized later that year, Melio raised substantial venture capital, including $144 million across early funding rounds to scale its payments infrastructure and partner integrations. The corporate integration into Xero eliminates independent private venture financing dependency, but creates an analytical opacity barrier for external underwriters evaluating standalone cash burn, rail gross margins, and customer acquisition payback periods.[CI010, CI011, CI012, CI013, CI014, CI015]

4.4 Exhibits

5.1 Product Definition and SMB Workflow Integration

Melio provides an integrated accounts payable (AP) and accounts receivable (AR) platform engineered to simplify business disbursements and collections for US small and mid-sized enterprises. Built originally to resolve the structural inflexibility confronting small business operators—who lack dedicated internal finance departments and often operate at the mercy of vendor payment terms—Melio consolidates bill capture, approval routing, payment execution, and accounting reconciliation into a unified cloud interface CE001 CE006. In standard SMB workflows, incoming vendor bills are ingested digitally or uploaded manually, triggering automated optical character recognition (OCR) and AI data extraction that parses vendor details, invoice amounts, line items, and due dates CE002 CE007. Once validated, invoices pass through customizable approval workflows before disbursement across bank transfers, credit cards, or physical checks CE008. On the receivables side, businesses issue payment requests and payment links with automated tracking and overdue reminders, accelerating collections and reducing manual administrative drag CE009. By integrating consumer-grade design principles into financial operations, Melio enables small businesses to separate business disbursements from personal accounts while maintaining cash-flow control CE006.[CE001, CE002, CE006, CE007, CE008, CE009]

5.2 System Architecture, Processing Engine, and Rail Execution

Melio's operating architecture is organized into four core functional layers: an ingestion and document extraction layer, a workflow and business-logic engine, a payment orchestration and disbursement rail, and an accounting integration framework FE001. A critical technological and economic differentiator is Melio's decoupled funding and delivery rail architecture: small business payers can fund disbursements using credit cards (bearing a 2.9% fee) or bank ACH transfers even when the recipient vendor only accepts conventional paper checks or direct bank deposits CE003 CE005. When a payer selects paper check delivery, Melio prints and physically mails the check on their behalf within standard (5–7 days) or expedited delivery windows CE004 CE008. However, independent benchmark analyses indicate that Melio's architecture is optimized primarily for single-entity domestic SMB workflows; it lacks native multi-location automated splitting, automated general ledger (GL) predictive coding, and advanced enterprise procurement controls such as automated three-way purchase-order matching CE002 CE010 CE011. While Melio supports payouts to 88 countries in 15 currencies, it lacks integrated foreign exchange (FX) hedging tools and deep enterprise tax engines like automated 1099/W-9 filing wizards found in mid-market alternatives CE012 CE013.[CE002, CE003, CE004, CE005, CE008, CE010, CE011, CE012, CE013]

5.3 Security, Compliance, and Technical Operating Risks

Operating at significant financial scale—having processed over $100 billion securely across more than 40 million on-time bill disbursements for over 100,000 business customers—Melio enforces strict financial data encryption and banking compliance standards to prevent digital fraud CE014 CE015. Platform safeguards incorporate automated transaction screening and backend fraud prevention monitoring designed to protect businesses against payment diversion and unauthorized account takeovers CE009. However, rigorous backend risk controls introduce operational friction: customer evidence and support logs demonstrate that internal fraud verification reviews can trigger abrupt account suspensions or scheduled payment cancellations with limited advance notice or explanation, exposing users to vendor relationship strain and urgent cash disbursements CE016. Furthermore, technical integration dependencies represent an ongoing maintenance risk; while Melio maintains direct bi-directional synchronization with QuickBooks Online, QuickBooks Desktop, Xero, and NetSuite (on higher subscription tiers), synchronization errors require periodic manual reconciliation CE001 CE007 CE011. Additionally, developer community signaling and public API surface visibility remain constrained, as Melio's embedded finance capabilities primarily deploy through strategic bilateral partnerships—such as Intuit's QuickBooks 'pay now' integration—rather than open developer registries CE014.[CE001, CE007, CE009, CE011, CE014, CE015, CE016]

5.4 Exhibits

6.1 Customer Segmentation and Buyer Personas

Melio's customer base is concentrated among small and midsize businesses, independent makers, wine merchants, construction operators, and professional service firms that lack formal internal finance departments. Unlike enterprise-grade accounts payable automation platforms designed for corporate treasurers, Melio targets non-technical business owners and their external bookkeepers. Core user motivation centers on cash flow flexibility—specifically the ability to defer payments by funding vendor disbursements via commercial credit cards even when suppliers accept only bank transfers or paper checks. With approximately 90% of Melio's user base actively utilizing business credit cards for expenses, the product acts as a consumer-grade bridge to traditional banking rails and cloud ledgers like QuickBooks and Xero. However, enterprise suppliers requiring advanced buyer underwriting and non-recourse net terms frequently look beyond Melio toward specialized accounts receivable solutions such as Resolve Pay.[CU001, CU002, CU003, CU004, CU005, CU006]

6.2 Adoption Trajectory and Named Deployment Proof

Melio's commercial adoption trajectory expanded from a localized NYC pilot with wine merchants into a nationwide payments network processing over $100 billion in cumulative volume. The platform has settled more than 40 million on-time bills across more than 2 million recipient vendors, saving active business owners an estimated average of 15 hours monthly on manual accounts payable operations. Product distribution benefits from a two-sided network dynamic: when a business pays an un-enrolled supplier, Melio disburses via paper check or invites the vendor to enter banking details for faster settlement. Customer feedback collected by Info-Tech Research Group confirms strong user satisfaction, highlighting an 8.4/10 overall product score, 86% likeliness to recommend, and 93% plan to renew, supported by seamless QuickBooks synchronization and automated payment scheduling.[CU007, CU008, CU009, CU010, CU011, CU012]

6.3 Retention Durability, Workflow Friction, and Churn Signals

Independent sentiment across Info-Tech Research Group and Trustpilot reflects a bifurcated customer experience. While 91% of user sentiment on Info-Tech is positive with an 83 Net Emotional Footprint, customer reviews reveal acute operational friction points that elevate mid-market churn risk. Small business users migrating from BILL frequently report that Melio's multi-step bill approval workflows are insufficiently granular, leading to delayed payment routing and strained customer support turnaround. Furthermore, transaction fees for credit card payments accumulate rapidly for high-volume payers, prompting finance teams to compare Melio against all-inclusive flat-rate alternatives. Finally, uncommunicated account closures and payment freezes enacted by Melio's internal compliance and risk verification teams present critical operational disruptions for small businesses dependent on reliable vendor disbursements.[CU013, CU014, CU015, CU016]

6.4 Exhibits

7.1 Ranked residual risk view

The most consequential public-evidence risks are data and security exposure, opaque account-verification outcomes, approval-workflow reliability, and dependence on external payment and data infrastructure. Melio says it handles sensitive banking credentials, uses partners and specialized service providers, transfers some information across jurisdictions, and cannot guarantee internet transmission security. A customer review also reports an account cancellation after a payment was scheduled; Melio's reply says an internal verification team handles such closures while support cannot disclose details. These observations show exposure, not a proven breach or a measured systemic failure. Residual severity remains high because the assigned public evidence does not establish incident frequency, closure-error rates, processor concentration, or tested recovery performance.[CR001, CR002, CR003, CR004, CR009, CR010, CR015]

7.2 Legal, regulatory, and data risk

The privacy policy is the strongest direct source for the present legal and data posture. It documents collection of financial-account credentials, disclosures to partners and service providers, cross-border transfers, contractual safeguards, and privacy-rights processes. It also expressly states that internet transmission cannot be guaranteed secure. Current pricing separately notes card-network limitations, while customer evidence raises questions about the transparency of verification-led closures. The source set contains no regulator order, licensing inventory, court docket, independent control audit, or incident register, so absence of those records here is not evidence that no enforcement, litigation, or security event exists. Investment diligence should obtain the complete license map, regulator correspondence, data-flow inventory, DPA set, and recent control reports.[CR001, CR002, CR003, CR004, CR006, CR009, CR010]

7.3 Operational, quality, and support risk

Melio company-claims more than $100 billion of processed volume, which increases the impact of payment, fraud, security, or support-control failures even though the figure is not independently verified here. The adverse customer evidence is specific but not statistically representative: one reviewer describes an unusable approval workflow and unanswered tickets, while another describes a transfer affected by wrong bank details that support ultimately helped resolve. Official materials advertise simple small-business UX, custom approval workflows, user controls, and tiered support, creating a direct execution test rather than proving those controls work at scale. A thesis break would be an undisclosed material incident, repeated settlement failures, or an inability to provide twelve months of payment-failure, closure, support, and recovery metrics.[CR005, CR011, CR012, CR013, CR015]

7.4 Partner, rail, and economic dependencies

Melio's policy identifies platform partners, accounting-software connections, payment processors, fraud providers, hosting, and cybersecurity vendors as parts of service delivery. Pricing says card-funded payments remain subject to card-network limits. Historical investor reporting adds that fee economics depended on customers choosing paid payment types across high aggregate transaction volume, and that API distribution and an Intuit integration were strategic growth paths. Because the public pool does not quantify processor, platform, or embedded channel concentration, the durability of these relationships and their margin effects remain open. Kill criteria should include a single processor or platform without tested failover, contractual change that impairs access or economics, or payment-mix deterioration that prevents contribution-margin improvement. Current plan complexity and premium-data deletion on downgrade add customer-friction and switching-risk questions.[CR002, CR006, CR007, CR008, CR014, CR015]

7.5 Evidence boundaries and diligence priorities

The risk conclusion is constrained by the assigned pool. It contains company policies and product pages, historical investor commentary, an independent software overview, a customer-review page, and one unrelated namesake result. The namesake result is retained only to document entity-resolution noise and does not support any claim about Melio Payments' controls or operations. Customer reviews supply concrete failure modes but not prevalence; company pages describe mitigations but not their effectiveness. Priority diligence is therefore quantitative: request security incidents and losses, KYC closure and appeal rates, payment failure and recovery times, support SLAs, processor and partner concentration, network-fee sensitivity, and evidence that approval workflows perform under representative customer loads.[CR011, CR012, CR013, CR015, CR016]

7.6 Exhibits

8.1 Recommendation and investment frame

The recommendation is research-more rather than buy: Melio's own website reports more than 100,000 business owners and more than $100 billion processed, which supports product relevance and scale, while Bessemer's earlier account explains why the model needs a high aggregate payment volume to monetize fee-bearing payment choices. Those are real thesis inputs, but neither source establishes current standalone revenue quality, margins, cash generation, retention, or an investable security. A current customer review also describes an unusable approval workflow and slow support, providing a concrete anti-thesis signal rather than a quantified churn conclusion. With no executable private-market price and no audited operating bridge in the assigned evidence, confidence is medium on the decision to wait but low on any intrinsic-value estimate. Risk is high and the valuation stance is unsupported-to-stretched for a hypothetical standalone entry.[CV005, CV007, CV008, CV009, CV010, CV012, CV013]

8.2 Financing history and price context

Public price references are not comparable enough to form a valuation anchor. Tracxn reports a $150 million Series E at a $2 billion post-money valuation in October 2024 and separately lists a $4.5 billion last-known valuation in July 2025. Netfigo compares Xero's reported $2.5 billion upfront acquisition consideration with the $4 billion Series D mark, while Forge displays a $2 billion last-known valuation for May 2026. These values describe different events, definitions, and vintages; Forge also says price is unavailable and market activity is limited. The range therefore signals uncertainty rather than a defensible current fair value. Funding raised is historical financing, not cash available, and the strategic acquisition price should not be reused as a standalone entry mark without deal terms, liabilities, preferences, contingent consideration, and current economics.[CV001, CV002, CV003, CV004, CV005, CV006, CV007]

8.3 Scenario and return discipline

Scenario analysis must remain directional because the evidence lacks a revenue base, growth rate, gross margin, free-cash-flow profile, retention, and share-count or preference stack. In the bull case, company-reported processing scale converts into durable fee-bearing volume and Xero distribution while product quality holds; historical multi-billion-dollar marks then become context, not a target. The base case treats the acquisition as proof of strategic value but assigns no reusable standalone price until audited economics and integration results are available. The bear case is triggered by weak monetization of free bank-transfer volume, persistent workflow or support friction, or evidence that the strategic buyer cannot convert scale into margin. No probability or return percentage is assigned because doing so would create false precision.[CV003, CV005, CV007, CV008, CV009, CV010, CV012, CV013]

8.4 Exit readiness and final diligence

Traditional exit-readiness analysis is largely superseded by the completed transaction: Forge lists the M&A announcement in June 2025 and closing in October 2025, and Seedtable marks Melio acquired. The still-live careers page is only a weak signal of continuing employer presence; it does not establish headcount, retention, autonomy, or integration success. The final diligence path is therefore post-close and evidence-led: obtain the purchase agreement and contingent-consideration terms, a standalone revenue and margin bridge, cohort retention and payment-mix data, partner concentration, and integration scorecards. Thesis-break triggers are measurable deterioration in fee-bearing mix, retention, workflow reliability, support outcomes, partner distribution, or the buyer's ability to realize revenue and cost synergies. Until those data exist, neither a target return nor a hold period is supportable.[CV014, CV015, CV016, CV007, CV010, CV012, CV013]

8.5 Exhibits