# US 2024/0005331 A1 · Multi-Party Payment Distribution Automation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0005331 A1
- Document ID: US20240005331A1
- Status: Published application
- Kind: A1
- Application number: 18/061,545
- Filed: 2022-12-05
- Published: 2024-01-04
- Earliest claimed: 2022-06-30
- Assignees: Fidelity Information Services, LLC
- Applicants: Fidelity Information Services, LLC
- Inventors: SUSHEEL NESARGI; George S. Durant; Joel Dake; Glen M. Casey; Prashant Gupta; Cary Jeffers; Karsten Propper
- Web page: https://patentgrep.com/patent/US20240005331A1

## CPC

- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 20/023: {the neutral party being a clearing house}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Disclosed embodiments relate to systems and methods for automatic payment distribution. Techniques include validating, based on user-specified rules that the received file form data fields match user requirements, determining whether to authenticate a form based on the validation, calculating payment eligibility and payment amount, authorizing recipient payments, and notifying the recipient.

## Claims

### Claim 1

An automatic payment distribution system, comprising:
a database,
a memory storing instructions; and
at least one processor configured to execute the instructions to:
receive, from a user device, a request to authenticate a recipient file template, wherein the recipient file template contains data fields for a recipient;
validate, based on user-specified rules, that the data fields match user requirements;
determine whether to authenticate the recipient file template based on the validation;
calculate, based on the data fields, at least one of payment eligibility and payment amount;
authorize an automatic payment to a recipient; and
send the payment to a payment disbursement system.

### Claim 2 (depends on 1)

The system of claim 1, wherein the operations further comprise logging each authorized payment to a recipient as a transaction.

### Claim 3 (depends on 1)

The system of claim 1, wherein the payment to a recipient further comprises a payment method of at least one of a check, ACH payment, or debit to a bank account.

### Claim 4 (depends on 3)

The system of claim 3, the operations further comprising:
logging each payment method in a positive pay file; and
generating a notification if a payment is attempted more than once.

### Claim 5 (depends on 1)

The system of claim 1, wherein the recipient is selected from a database of eligible recipients.

### Claim 6 (depends on 1)

The system of claim 1, wherein the operations further comprise:
denying authorization of payment to a recipient; and
logging the denied authorization of payment to a recipient.

### Claim 7 (depends on 1)

The system of claim 1, wherein the user-specified rules are configuration-based.

### Claim 8 (depends on 1)

The system of claim 1, wherein the operations further comprise sending a notification of at least one of an email, text message, phone call, or system alert, based on the user-specified rules when a payment is sent to a payment disbursement system.

### Claim 9 (depends on 1)

The system of claim 1, wherein each payment is an encrypted transaction.

### Claim 10

A non-transitory computer readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for automatic payment distribution, comprising:
receive, from a user device, a request to authenticate a recipient file template, wherein the recipient file template contains data fields for a recipient;
validate, based on user-specified rules, that the data fields match user requirements;
determine whether to authenticate the recipient file template based on the validation;
calculate, based on the data fields, at least one of payment eligibility and payment amount;
authorize a payment to a recipient; and
notify the recipient of a status of the payment.

### Claim 11 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein the operations further comprise determining a user's authorization or status, wherein the user includes at least one of a read-only user, an upload-only user, a call center agent, or an administrator;

### Claim 12 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein the administrator has full permissions within the user-specified rules including changing the payment recipient's address, re-issuing check payments, or flagging payments for review.

### Claim 13 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein the operations further comprise the call center agent performing at least one of:
searching for a payment recipient;
reporting a payment recipient;
searching a database;
reviewing payment history; or
viewing payment status.

### Claim 14 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein the data fields include personal identifiable information.

### Claim 15 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein authorizing a payment further comprises:
validating the payment recipient's address; and
confirming financial information with a financial institution.

### Claim 16 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein the operations further comprise the payment recipient receiving multiple payments.

### Claim 17 (depends on 10)

The non-transitory computer-readable medium of claim 10, wherein the payment amount has a limit based on user-specified rules.

### Claim 18

A computer-implemented method for automatic payment distribution, comprising:
receiving, from a user device, a request to authenticate a recipient file template, wherein the recipient file template contains data fields for a recipient;
validating, based on user-specified rules, that the data fields match user requirements;
determining whether to authenticate the recipient file template based on the validation;
calculating, based on the data fields, at least one of payment eligibility and payment amount;
authorizing a payment to a recipient; and
notifying the recipient of a status of the payment.

### Claim 19 (depends on 18)

The computer-implemented method of claim 18, wherein the user-specified rules are determined by an employing entity.

### Claim 20 (depends on 18)

The computer-implemented method of claim 18, wherein the operations further comprise an administrator changing the user requirements.
