IP Library › Granted Patent US 12,327,290
Granted Patent B2
US 12,327,290 · App. 18/433,608 · Granted Jun 10, 2025

Net settlement of subrogation claims using a distributed ledger

Inventors: Ryan Maurer (Phoenix, AZ); Nolan White (Chandler, AZ); Kyle D. Weber (Gilbert, AZ); Edward Austin (Scottsdale, AZ); William Guthrie (Mesa, AZ); Dustin Helland (Morton, IL); Bharat Prasad (San Antonio, TX); Sharon Kay Haverlah (Bulverde, TX); Karen Marie Shackelford-George (San Antonio, TX)
Assignees: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY; United Services Automobile Association (USAA)
G06Q50/18G06F16/2365H04L9/3236
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,327,290
App. No.
18/433,608
Filed
Feb 6, 2024
Granted
Jun 10, 2025
Kind
B2
Art Unit
2161
USPC
705/311
Abstract

Aspects of distributed ledger technology are leveraged to verify subrogation settlements. In particular, two parties to a subrogation claim provide cryptographic hashes to a subrogation demand smart contract stored at an address on a blockchain. The subrogation demand smart contract determines that the parties have reached an agreement by determining that the cryptographic hashes match. A settlement amount from the subrogation claim may be appended to a set of settlement amounts to determine a net settlement amount to facilitate a single payment between the parties on a periodic basis, such as daily, to alleviate the need for the parties to send or receive a payment for each individual settlement amount.

Claims (51)

1. A computer-implemented method for generating a subrogation demand smart contract using a distributed ledger, the method comprising, via one or more processors, servers, and/or associated transceivers:

generating the subrogation demand smart contract for the distributed ledger in a distributed ledger network maintained by a plurality of participants each executing code in the subrogation demand smart contract to reach a distributed consensus on a state of the subrogation demand smart contract, the subrogation demand smart contract configured to:

determine a proof of agreement regarding a settlement between a first party and a second party to a subrogation claim by comparing a first cryptographic hash value provided by the first party to a second cryptographic hash value provided by the second party, and determining that there is proof of agreement in response to determining that the first and second cryptographic hash values match, wherein each of the first and second cryptographic hash values are determined based upon a same set of one or more characteristics of the settlement between the first and second parties; and

record the proof of agreement regarding the settlement in the distributed ledger to allow the first and second parties to verify terms of the settlement; and

deploying the subrogation demand smart contract to the distributed ledger maintained by the plurality of participants in the distributed ledger network.

2. The computer-implemented method of claim 1 , wherein the one or more characteristics of the settlement include at least one of: a demand identifier, a demand type, a settlement amount, or a company code of one of the first and second parties providing the settlement.

3. The computer-implemented method of claim 1 , wherein the subrogation demand smart contract is further configured to:

determine that there is no proof of agreement in response to determining that the first and second cryptographic hash values do not match; and

transmit notifications to the parties indicating that there is no proof of agreement regarding the settlement.

4. A computer-implemented method of verifying a settlement of a subrogation claim between a first party and a second party using a distributed ledger, the method comprising, via one or more processors, servers, and/or associated transceivers:

determining, by the first party, a settlement amount for the settlement of the subrogation claim between the first party and the second party;

generating a first cryptographic hash value based upon one or more characteristics of the settlement between the first party and the second party;

broadcasting the first cryptographic hash value to a subrogation demand smart contract deployed to the distributed ledger and maintained by a plurality of participants in a distributed ledger network as a proof of agreement of the settlement between the first and second party, each of the plurality of participants executing code in the subrogation demand smart contract to reach a distributed consensus on a state of the subrogation demand smart contract, wherein the subrogation demand smart contract compares the first cryptographic hash value submitted by the first party to a second cryptographic hash value submitted by the second party to determine if there is a match;

obtaining an indication from the subrogation demand smart contract that the first and second cryptographic hash values match indicating there is proof of agreement between the first party and second party; and

appending the settlement amount to a set of settlement amounts between the first party and the second party agreed upon over a threshold time period to determine a net settlement amount with the second party over the threshold time period.

5. The computer-implemented method of claim 4 , wherein the first party and the second party determine the first cryptographic hash value and the second cryptographic hash value, respectively, using a same set of one or more characteristics of the settlement.

6. The computer-implemented method of claim 4 , wherein the one or more characteristics of the settlement include at least one of: a demand identifier, a demand type, a settlement amount, or a company code of one of the first and second parties providing the settlement.

7. The computer-implemented method of claim 4 , further comprising:

determining a supplemental settlement amount for a supplement settlement of the subrogation claim between the first party and a second party based upon additional items or expenses which were not included in the settlement;

generating a third cryptographic hash value based upon one or more characteristics of the supplement settlement between the first party and the second party;

broadcasting the third cryptographic hash value to the subrogation demand smart contract deployed to the distributed ledger and maintained by the plurality of participants in the distributed ledger network as a proof of agreement of the supplemental settlement between the first and second party, wherein the subrogation demand smart contract compares the third cryptographic hash value submitted by the first party to a fourth cryptographic hash value submitted by the second party to determine if there is a match;

obtaining an indication from the subrogation demand smart contract that the third and fourth cryptographic hash values match indicating there is proof of agreement between the first party and second party; and

appending the supplemental settlement amount to the set of settlement amounts between the first party and the second party agreed upon over the threshold time period to determine the net settlement amount with the second party over the threshold time period.

8. The computer-implemented method of claim 7 , wherein determining a settlement amount includes determining a partial settlement amount based upon a subset of items or expenses in the subrogation claim.

9. The computer-implemented method of claim 8 , wherein:

generating a first cryptographic hash value includes generating the first cryptographic hash value based upon one or more characteristics of the partial settlement between the first party and the second party; and

appending the settlement amount includes appending the partial settlement amount to the set of settlement amounts between the first party and the second party agreed upon over the threshold time period.

10. The computer-implemented method of claim 8 , wherein the subset of items or expenses in the subrogation claim are a first subset of items or expenses in the subrogation claim and wherein the additional items or expenses are a second subset of items or expenses in the subrogation claim which were not agreed upon in the settlement.

11. The computer-implemented method of claim 7 , wherein the additional items or expenses are submitted by the first or second party after the settlement has been agreed upon.

12. The computer-implemented method of claim 4 , wherein the subrogation claim further includes at least a third party, and the subrogation demand smart contract compares the first cryptographic hash value submitted by the first party, the second cryptographic hash value submitted by the second party, and at least a third cryptographic hash value submitted by the at least third party to determine if there is a match.

13. The computer-implemented method of claim 4 , wherein the first cryptographic hash value is generated by a third-party aggregator or service provider.

14. The computer-implemented method of claim 4 , further comprising:

transmitting a message to a messaging smart contract deployed to the distributed ledger and maintained by the plurality of participants in the distributed ledger network, wherein the message is viewable by the second party.

15. A computer system for verifying a settlement of a subrogation claim between a first party and a second party using a distributed ledger, the computer system comprising:

a network interface;

one or more processors; and

a non-transitory computer-readable memory storing instructions thereon, that when executed by the one or more processors, cause the one or more processors to:

determine, by the first party, a settlement amount for the settlement of the subrogation claim between the first party and the second party;

generate a first cryptographic hash value based upon one or more characteristics of the settlement between the first party and the second party;

broadcast, via the network interface, the first cryptographic hash value to a subrogation demand smart contract deployed to the distributed ledger and maintained by a plurality of participants in a distributed ledger network as a proof of agreement of the settlement between the first and second party, each of the plurality of participants executing code in the subrogation demand smart contract to reach a distributed consensus on a state of the subrogation demand smart contract, wherein the subrogation demand smart contract compares the first cryptographic hash value submitted by the first party to a second cryptographic hash value submitted by the second party to determine if there is a match;

obtain an indication from the subrogation demand smart contract that the first and second cryptographic hash values match indicating there is proof of agreement between the first party and second party; and

append the settlement amount to a set of settlement amounts between the first party and the second party agreed upon over a threshold time period to determine a net settlement amount with the second party over the threshold time period.

16. The computer system of claim 15 , wherein the first party and the second party determine the first cryptographic hash value and the second cryptographic hash value, respectively, using a same set of one or more characteristics of the settlement.

17. The computer system of claim 15 , wherein the one or more characteristics of the settlement include at least one of: a demand identifier, a demand type, a settlement amount, or a company code of one of the first and second parties providing the settlement.

18. The computer system of claim 15 , wherein the instructions further cause the one or more processors to:

determine a supplemental settlement amount for a supplement settlement of the subrogation claim between the first party and a second party based upon additional items or expenses which were not included in the settlement;

generate a third cryptographic hash value based upon one or more characteristics of the supplement settlement between the first party and the second party;

broadcast, via the network interface, the third cryptographic hash value to a subrogation demand smart contract deployed to a distributed ledger and maintained by a plurality of participants in a distributed ledger network as a proof of agreement of the supplemental settlement between the first and second party, wherein the subrogation demand smart contract compares the third cryptographic hash value submitted by the first party to a fourth cryptographic hash value submitted by the second party to determine if there is a match;

obtain an indication from the subrogation demand smart contract that the third and fourth cryptographic hash values match indicating there is proof of agreement between the first party and second party; and

append the supplemental settlement amount to the set of settlement amounts between the first party and the second party agreed upon over the threshold time period to determine the net settlement amount with the second party over the threshold time period.

19. The computer system of claim 18 , wherein the settlement amount is a partial settlement amount based upon a subset of items or expenses in the subrogation claim.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 14, 2024
From: MAURER, RYAN; WHITE, NOLAN; WEBER, KYLE D.; AUSTIN, EDWARD; GUTHRIE, WILLIAM; HELLAND, DUSTIN
To: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Reel/Frame 066457/0023 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 14, 2024
From: PRASAD, BHARAT; HAVERLAH, SHARON KAY; SHACKELFORD-GEORGE, KAREN MARIE
To: UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA)
Reel/Frame 066457/0146 →
Continuity (5)
Continuation 17896617 · Aug 26, 2022
Continuation 17530030 · Nov 18, 2021
Provisional Application 63196516 · Jun 3, 2021
Provisional Application 63196544 · Jun 3, 2021
Related Publication 20240212078A1 · Jun 27, 2024
References Cited (86)
US 6029146A · Hawkins et al. · 2000 [cited by applicant]
US 7249114B2 · Burchetta et al. · 2007 [cited by applicant]
US 7574596B2 · Chen et al. · 2009 [cited by applicant]
US 7962385B2 · Falk et al. · 2011 [cited by applicant]
US 10454878B2 · Khan et al. · 2019 [cited by applicant]
US 10600009B1 · Augustine et al. · 2020 [cited by applicant]
US 10606669B2 · Jacobs et al. · 2020 [cited by applicant]
US 10796393B2 · Messerges et al. · 2020 [cited by applicant]
US 10824746B1 · Magerkurth et al. · 2020 [cited by applicant]
US 10872381B1 · Leise · 2020 [cited by examiner]
US 10885590B2 · Sivakumar et al. · 2021 [cited by applicant]
US 10891694B1 · Leise et al. · 2021 [cited by applicant]
US 10929931B1 · Bryant et al. · 2021 [cited by applicant]
US 10949926B1 · Call et al. · 2021 [cited by applicant]
US 10963966B1 · Brandmaier et al. · 2021 [cited by applicant]
US 11037246B1 · Leise et al. · 2021 [cited by applicant]
US 11100477B1 · Kemper et al. · 2021 [cited by applicant]
US 11170388B1 · Violette et al. · 2021 [cited by applicant]
US 11216813B1 · Delong et al. · 2022 [cited by applicant]
US 11245534B2 · Brownlee et al. · 2022 [cited by applicant]
US 11250466B2 · Soundararajan et al. · 2022 [cited by applicant]
US 11374739B2 · Huang · 2022 [cited by examiner]
US 11829961B1 · Wood · 2023 [cited by examiner]
US 20010037204A1 · Horn et al. · 2001 [cited by applicant]
US 20050138429A1 · Miura · 2005 [cited by applicant]
US 20070245159A1 · Youn · 2007 [cited by applicant]
US 20080071664A1 · Silverman et al. · 2008 [cited by applicant]
US 20160292672A1 · Fay et al. · 2016 [cited by applicant]
US 20170186057A1 · Metnick · 2017 [cited by applicant]
US 20170308893A1 · Saraniecki · 2017 [cited by applicant]
US 20170357921A1 · Glucroft · 2017 [cited by applicant]
US 20170372432A1 · McKown · 2017 [cited by applicant]
US 20180025442A1 · Isaacson et al. · 2018 [cited by applicant]
US 20180046992A1 · Hanrahan et al. · 2018 [cited by applicant]
US 20180091316A1 · Stradling et al. · 2018 [cited by applicant]
US 20180218455A1 · Kolb et al. · 2018 [cited by applicant]
US 20180365684A1 · Reilly et al. · 2018 [cited by applicant]
US 20190019186A1 · Falah et al. · 2019 [cited by applicant]
US 20190026821A1 · Bathen et al. · 2019 [cited by applicant]
US 20190102736A1 · Hudson · 2019 [cited by applicant]
US 20190149864A1 · Britt et al. · 2019 [cited by applicant]
US 20190197620A1 · Jayaram et al. · 2019 [cited by applicant]
US 20190354966A1 · Himura et al. · 2019 [cited by applicant]
US 20190392437A1 · Castagna et al. · 2019 [cited by applicant]
US 20190392438A1 · Rice · 2019 [cited by applicant]
US 20200058071A1 · Yang · 2020 [cited by applicant]
US 20200065763A1 · Rosinzonsky et al. · 2020 [cited by applicant]
US 20200065802A1 · Mathieson et al. · 2020 [cited by applicant]
US 20200177373A1 · Komandur et al. · 2020 [cited by applicant]
US 20200226677A1 · Dhawan et al. · 2020 [cited by applicant]
US 20200250753A1 · Blount · 2020 [cited by applicant]
US 20200272966A1 · Kirkegaard · 2020 [cited by applicant]
US 20200273027A1 · Gordon et al. · 2020 [cited by applicant]
US 20200279328A1 · Zhiri et al. · 2020 [cited by applicant]
US 20200320638A1 · Erickson · 2020 [cited by examiner]
US 20200341971A1 · Krishnaswamy et al. · 2020 [cited by applicant]
US 20200394321A1 · Ramos et al. · 2020 [cited by applicant]
US 20200394322A1 · Ramos et al. · 2020 [cited by applicant]
US 20200409937A1 · Wang et al. · 2020 [cited by applicant]
US 20210049265A1 · Pescatore et al. · 2021 [cited by applicant]
US 20210065070A1 · Augustine et al. · 2021 [cited by applicant]
US 20210065293A1 · Sigler et al. · 2021 [cited by applicant]
US 20210090037A1 · Dowding · 2021 [cited by applicant]
US 20210099295A1 · Li et al. · 2021 [cited by applicant]
US 20210118060A1 · Floyd et al. · 2021 [cited by applicant]
US 20210174442A1 · Trudeau et al. · 2021 [cited by applicant]
US 20210216525A1 · Leise et al. · 2021 [cited by applicant]
US 20210217084A1 · Diamond · 2021 [cited by applicant]
US 20210225499A1 · Takayama · 2021 [cited by applicant]
US 20210304317A1 · Leise et al. · 2021 [cited by applicant]
US 20210326992A1 · Leise et al. · 2021 [cited by applicant]
US 20210328804A1 · Snow et al. · 2021 [cited by applicant]
US 20210328995A1 · Albero et al. · 2021 [cited by applicant]
US 20210342828A1 · Magerkurth et al. · 2021 [cited by applicant]
US 20210342946A1 · Leise et al. · 2021 [cited by applicant]
US 20220058623A1 · Snow et al. · 2022 [cited by applicant]
US 20220058732A1 · Reses · 2022 [cited by examiner]
AU 2009212995A1 · 2010 [cited by applicant]
WO WO2004044696A2 · 2004 [cited by applicant]
WO WO2018232493A1 · 2018 [cited by applicant]
WO WO2021046494A1 · 2021 [cited by applicant]
U.S. Appl. No. 17/530,030, Notice of Allowance, mailed Jun. 3, 2022. [cited by applicant]
U.S. Appl. No. 17/530,030, Nonfinall Office Action, dated Mar. 2, 2022. [cited by applicant]
U.S. Appl. No. 17/529,983, Nonfinal Office Action, dated Mar. 4, 2022. [cited by applicant]
U.S. Appl. No. 17/529,983, Final Office Action, dated Jun. 15, 2022. [cited by applicant]
U.S. Appl. No. 17/896,617, Non-Final Office Action, dated Jul. 13, 2023. [cited by applicant]