DCT
2:17-cv-00239
Finnavations LLC v. Wave Accounting Inc
Key Events
Complaint
Table of Contents
complaint
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Finnavations, LLC (Texas)
- Defendant: Wave Accounting Inc. (Canada)
- Plaintiff’s Counsel: Kizzia & Johnson PLLC
- Case Identification: 2:17-cv-00239, E.D. Tex., 03/29/2017
- Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant is deemed to reside in the district and has committed acts of infringement there.
- Core Dispute: Plaintiff alleges that Defendant’s accounting and invoicing software platform infringes a patent related to a system for capturing and enhancing financial transaction data.
- Technical Context: The technology addresses the process of capturing detailed, item-level data from online commercial transactions for use in personal financial management software.
- Key Procedural History: The complaint notes that the patent-in-suit issued after overcoming an examiner's rejection under 35 U.S.C. § 101, which pertains to patent-eligible subject matter. This history suggests that the patent's eligibility, particularly the abstractness of the claimed software method, was a point of contention during prosecution and may re-emerge as a focus of the litigation.
Case Timeline
| Date | Event |
|---|---|
| 1999-09-22 | ’755 Patent Priority Date |
| 2016-06-14 | Non-final rejection of '755 Patent application under 35 U.S.C. § 101 |
| 2017-02-14 | U.S. Patent No. 9,569,755 Issues |
| 2017-03-29 | Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 9,569,755 - “Financial Management System”
- Patent Identification: U.S. Patent No. 9,569,755, “Financial Management System,” issued February 14, 2017.
The Invention Explained
- Problem Addressed: The patent's background section describes a drawback of early financial management systems where data from online credit card transactions was limited to the total purchase amount, payee, and date, failing to capture information about the specific items purchased ('755 Patent, col. 1:52-62). This made detailed expense tracking and reconciliation difficult for users.
- The Patented Solution: The invention proposes a "Financial Assistant," a software application that operates on a user's network device or an associated server ('755 Patent, col. 3:12-26). This assistant searches data being transmitted during an online transaction, identifies it as transaction data, copies it into a "first data structure," and then creates a "second data structure" by combining the copied data with additional information (e.g., user-entered categories or notes) not present in the original transmission ('755 Patent, col. 8:1-12; FIG. 1). This enriched data is then sent to a personal financial management program, providing a more detailed record of the purchase.
- Technical Importance: This approach aimed to bridge the information gap between merchant transaction systems and personal finance software, automating the capture of item-level detail that previously required manual entry. ('755 Patent, col. 1:49-58).
Key Claims at a Glance
- The complaint asserts independent Claim 9 and dependent Claim 17.
- Independent Claim 9 recites a method with the following essential elements:
- Using a network device to conduct an online financial transaction with a commercial web server.
- A "financial assistant" on the network device searching a set of transmitted data.
- The financial assistant determining if the searched data comprises transaction data.
- When it does, the financial assistant copies the transaction data (from a "first data structure") and stores it along with "additional transaction data not included in the transmitted transaction data" into a "second data structure."
- The second data structure must differ from the first data structure.
- The complaint does not explicitly reserve the right to assert other claims.
III. The Accused Instrumentality
Product Identification
The "Wave accounting and invoicing software and platform" (“Product”) (Compl. ¶13).
Functionality and Market Context
- The complaint describes the Product as a platform that allows users to send invoices and receive payments from customers (Compl. ¶14). The system involves a user's network device (e.g., laptop, smartphone), a cloud server where the Wave platform resides, and a separate commercial web server for credit card processing (Compl. ¶¶13-14).
- Functionally, the platform analyzes data from an invoice payment to determine and display the invoice's status on a user dashboard (Compl. ¶15). It is alleged to correlate specific payment data to a specific invoice to ensure accuracy (Compl. ¶16).
IV. Analysis of Infringement Allegations
No probative visual evidence provided in complaint.
Claim Chart Summary
| Claim Element (from Independent Claim 9) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| using a network device to conduct an online financial transaction with a commercial web server; | The Product uses a network device (e.g., laptop, smartphone) to send invoices and receive payment via a commercial web server, such as a credit card processing server. | ¶14 | col. 3:5-11 |
| searching, by a financial assistant on the network device, a set of transmitted data related to the online financial transaction; | The Wave invoice application, acting as the "financial assistant," analyzes data transmitted during an invoice payment to determine the status of the invoice for a user dashboard. | ¶15 | col. 4:25-28 |
| determining, by the financial assistant on the network device, whether the searched data comprises transaction data for the online financial transaction; | The Wave invoice application determines if particular invoice payment data is related to a particular invoice to correlate the payment and display the status accurately. | ¶16 | col. 4:26-28 |
| when the searched data comprises transaction data in a first data structure...copying and storing...the transaction data and additional transaction data not included in the transmitted transaction data into in a second data structure...wherein the second data structure differs from the first data structure. | When invoice payment data exists in a "first data structure" (for credit card payment), the Wave application copies it and combines it with "additional transaction data" (e.g., client name, invoice status) to create a "second data structure" for the Wave platform. | ¶17 | col. 8:1-12 |
Identified Points of Contention
- Scope Questions: The patent describes a "Financial Assistant" that appears to intercept data flowing between a user's device and a separate commercial website ('755 Patent, col. 4:42-45). The complaint alleges Wave's own integrated invoicing application is the "financial assistant." This raises the question of whether the accused architecture, where the application is the primary service rather than an intermediary tool, falls within the scope of the claims.
- Technical Questions: The infringement theory hinges on the existence of distinct "first" and "second" data structures. A key question will be whether the accused Product's process of combining payment data with existing invoice data constitutes the creation of a "second data structure" containing "additional transaction data not included in the transmitted transaction data" as required by the claim, or if it is merely a reformatting or aggregation of data already present within the Wave system.
V. Key Claim Terms for Construction
The Term: "financial assistant"
- Context and Importance: This term defines the active agent performing the core steps of the claimed method. Its construction will be critical to determining if the accused Wave application, which is the primary platform for the transaction itself, can be considered a "financial assistant" in the manner contemplated by the patent. Practitioners may focus on this term to dispute whether the accused product's architecture matches the claimed invention.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification states the Financial Assistant could be "an application running on the terminal device or on a server associated with the commercial web site" ('755 Patent, col. 3:24-26), which could support an argument that it covers software integrated with the service.
- Evidence for a Narrower Interpretation: The patent repeatedly describes the assistant as "intercept[ing]" data transmitted from a terminal device to a commercial web server, with a preferred embodiment residing on an Internet Service Provider (ISP) server, separate from both the user and merchant ('755 Patent, col. 3:19-21; col. 4:42-45). This may support a narrower construction requiring a distinct, intermediary component.
The Term: "additional transaction data not included in the transmitted transaction data"
- Context and Importance: This limitation is central to the invention's purported improvement over the prior art—the enrichment of raw transaction data. The case may turn on whether the data the Wave platform allegedly adds (e.g., "client name and status of the invoice") (Compl. ¶17) meets this definition.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The claim language itself is open-ended and does not specify the source or type of "additional transaction data."
- Evidence for a Narrower Interpretation: The specification provides examples of such additional data as user-entered information, such as a "category" or "remarks" ('755 Patent, col. 4:63-65), or data from a user's profile ('755 Patent, col. 2:15-17). This could support a narrower construction requiring the addition of information external to the transaction's core data set, potentially from direct user input.
VI. Analyst’s Conclusion: Key Questions for the Case
- A core issue will be one of architectural scope: Can the term "financial assistant," described in the patent as an intermediary tool that intercepts and enriches data, be construed to read on an integrated software platform like Wave's, where the application is the primary service managing the transaction from end to end?
- A key evidentiary question will be one of data transformation: Does the accused Wave platform create a "second data structure" by adding new information "not included in the transmitted transaction data" as the claim requires, or does it merely aggregate and re-organize data already existing within its own system? The answer will likely depend on a detailed, technical analysis of the data flows within the accused product.
- The patent's prosecution history, specifically its successful navigation of a § 101 rejection (Compl. ¶12), suggests the patentability rests on the specific, concrete steps of creating a new, enriched data structure. This places significant weight on Plaintiff's ability to prove that the accused system performs these exact technical steps, making the aforementioned architectural and data transformation questions central to the dispute.
Analysis metadata