# US 2019/0378183 A1 · Systems and methods for improving invoice management using enhanced analytical insight > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0378183 A1 - Document ID: US20190378183A1 - Status: Published application - Kind: A1 - Application number: 16/547,101 - Filed: 2019-08-21 - Published: 2019-12-12 - Earliest claimed: 2018-04-30 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Eric Lowell; Brandon Walsh; Meredith Van Voorhis; Paola Thurlow; Sehyoung Myung; Qiang Xue; Heather Aller; Kristofer Johnson; Michael Baird Beers; Chad Fisher; Mark Lareau; Karthik Kaimal; Victor Mayaki - Web page: https://patentgrep.com/patent/US20190378183A1 ## CPC - G06Q 30/04: Billing or invoicing - G06Q 10/06316: {Sequencing of tasks or work} - G06F 16/26: Visual data mining; Browsing structured data - G06Q 40/03: Credit; Loans; Processing thereof - 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 - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An improved invoice management product may include an invoice hub server and an invoice database, and may receive data including one or more invoices, transmit one or more invoice records to an invoice database, identify one or more invoice records for expedited processing, transmit a request to issue an advance payment to a supplier associated with one or more supplier identifiers associated with the one or more invoice records, and transmit a notice to a customer. An Invoice Hub server may receive data comprising one or more invoices, create one or more invoice records based on the one or more invoices, transmit the one or more invoice records to an invoice database, identify one or more invoice records for expedited processing, transmit a request to issue an advance payment to a supplier, and transmit a notice to a customer associated with the one or more invoice records. ## Claims ### Claim 1 A method comprising: receiving, at an invoice hub server through an invoice interface accessible to a third party invoice system, a plurality of open invoices directly from the third party invoice system, wherein each of the plurality of open invoices is associated with a transaction between a supplier and a buyer, and wherein each of the plurality of invoices comprises at least a buyer identifier, a supplier identifier associated with the supplier, and an invoice amount; identifying one or more supplier invoices from the plurality of open invoices, the supplier invoices relating to the same supplier; receiving, at the invoice hub server, a supplier preference associated with at least one of the supplier invoices, the supplier preference designating at least one or more supplier invoices for advance processing; analyzing, by machine-learning (ML) logic at the invoice hub server, the designated one or more supplier invoices for advance processing, the analyzing further comprising: generating an invoice score for each of the designated one or more supplier invoices, each invoice score based on at least a supplier score, a buyer score, or a payment schedule of a respective invoice; and comparing each of the generated invoice scores to an invoice score threshold to identify one or more invoices eligible for advance processing, wherein the one or more eligible invoices have an invoice score that exceeds the invoice score threshold; generating, by the invoice hub server, an indication identifying the one or more eligible invoices available for advance processing; and responsive to receiving selection of one or more of the eligible invoices, automatically transmitting an advance payment to the supplier based on the selected eligible invoices. ### Claim 2 (depends on 1) The method of claim 1, wherein the invoice score is further based on an available amount of a credit line associated with the supplier. ### Claim 3 (depends on 1) The method of claim 1, wherein the advance payment for the one or more selected eligible invoices matches the invoice amount corresponding to at least one of the plurality of open invoices. ### Claim 4 (depends on 1) The method of claim 1, wherein the advance payment for the one or more selected eligible invoices is less than the invoice amount corresponding to at least one of the plurality of open invoices. ### Claim 5 (depends on 4) The method of claim 4, further comprising automatically transmitting an additional advance payment to the supplier based on the selected eligible invoices, the combination of the advance payment and the additional advance payment matching the invoice amount corresponding to the at least one of the plurality of open invoices. ### Claim 6 (depends on 1) The method of claim 1, wherein the supplier preference comprises a payment type preference relating to the one or more supplier invoices for advance processing, the payment type preference further comprising at least the options of complete payment, partial payment, and installment payment. ### Claim 7 (depends on 1) The method of claim 1, further comprising calculating, by the ML logic, the invoice score threshold based on an advanced amount value relating to a total amount advanced for the one or more supplier invoices from the plurality of open invoices. ### Claim 8 (depends on 1) The method of claim 1, wherein the invoice score is generated based on each of the supplier score, the buyer score, and the payment schedule of the respective invoice. ### Claim 9 (depends on 1) The method of claim 1, wherein generating the invoice score further comprises: assigning a weighting score to the supplier score, the buyer score, or the payment schedule of a respective invoice; analyzing at least one of a historical supplier score over a defined time period, a historical buyer score over the defined time period, or a historical payment history of the supplier over the defined time period; assigning a weighting score to the one of the historical supplier score, the historical buyer score, or the historical payment history; and generating the invoice score based on the weighted supplier score, the weighted buyer score, or the weighted payment schedule, and the weighted historical supplier score, the weighted historical buyer score, or the weighted historical payment history. ### Claim 10 A method comprising: receiving, at an invoice hub server through an invoice interface accessible to a third party invoice system, a plurality of open invoices directly from the third party invoice system, wherein each of the plurality of open invoices is associated with a transaction between a supplier and a buyer, and wherein each of the plurality of invoices comprises at least a buyer identifier, a supplier identifier associated with the supplier, and an invoice amount; identifying one or more supplier invoices from the plurality of open invoices, the supplier invoices relating to the same supplier; analyzing, by a machine-learning (ML) server in communication with the invoice hub server, the one or more supplier invoices relating to the same supplier, the analyzing further comprising: generating an invoice score for each of the one or more supplier invoices relating to the same supplier, each invoice score being based on at least a supplier score, a buyer score, or a payment schedule of a respective invoice; and automatically determining an advance payment amount for each of the one or more supplier invoices relating to the same supplier based on one or more of the respective invoice scores, wherein the advance payment amount correlates directly to one or more of the one or more invoice scores; generating, by the invoice hub server, an indication identifying each of the one or more supplier invoices relating to the same supplier and the respective advance payment amounts; receiving selection of one or more of the supplier invoices relating to the same supplier after generating the indication; and automatically transmitting an advance payment to the supplier based on the selected invoices. ### Claim 11 (depends on 10) The method of claim 10, further comprising receiving at the invoice hub server a supplier preference associated with at least one of the supplier invoices, the supplier preference designating at least one or more supplier invoices for advance processing, wherein the ML server analyzes the one or more supplier invoices based on the one or more supplier invoices designated for advanced processing. ### Claim 12 (depends on 10) The method of claim 10, wherein the advance payment for at least one respective supplier invoice matches the invoice amount corresponding to the respective supplier invoice. ### Claim 13 (depends on 10) The method of claim 10, wherein each invoice score is generated based on each of the supplier score, the buyer score, and the payment schedule of the respective invoice. ### Claim 14 (depends on 10) The method of claim 10, further comprising: responsive to receiving information relating to the supplier, analyzing the received information, by the ML server; automatically adjusting the invoice score for each of the one or more supplier invoices relating to the same supplier; and responsive to adjusting the invoice score, automatically adjusting the advance payment amount for each of the one or more supplier invoices relating to the same supplier based the respective adjusted invoice score. ### Claim 15 (depends on 14) The method of claim 14, further comprising transmitting a notification to the supplier associated with the selected one or more supplier invoices, the notification indicating the respective adjusted advance payment amounts. ### Claim 16 A system comprising: an invoice hub server comprising machine-learning (ML) logic, one or more processors, and a non-transitory memory, the memory storing instructions that, when executed by the processor, cause the processor to perform processing comprising: receive, from an invoice interface accessible to a third party invoice system, a plurality of open invoices directly from the third party invoice system, wherein each of the plurality of open invoices is associated with a transaction between a supplier and a buyer, and wherein each of the plurality of invoices comprises at least a buyer identifier, a supplier identifier associated with the supplier, and an invoice amount; identify one or more supplier invoices from the plurality of open invoices, the supplier invoices relating to the same supplier; receive a supplier preference associated with at least one of the supplier invoices, the supplier preference designating at least one or more supplier invoices for advance processing; analyzing, by instructions associated with the ML logic, the designated one or more supplier invoices for advance processing, the analyzing further comprising: generating an invoice score for each of the designated one or more supplier invoices, each invoice score based on at least a supplier score, a buyer score, or a payment schedule of a respective invoice; and comparing each of the generated invoice scores to an invoice score threshold to identify one or more invoices eligible for advance processing, wherein the one or more eligible invoices have an invoice score that exceeds the invoice score threshold; generate an indication identifying the one or more eligible invoices available for advance processing; and automatically transmit an advance payment to the supplier based on the one or more eligible invoices, wherein the advance payment is transmitted to the supplier responsive to a selection of one or more of the eligible invoices. ### Claim 17 (depends on 16) The system of claim 16, wherein the advance payment for the one or more selected eligible invoices matches the invoice amount corresponding to at least one of the plurality of open invoices. ### Claim 18 (depends on 16) The system of claim 16, wherein the instructions further cause the processor to perform processing comprising calculate the invoice score threshold based on an advanced amount value relating to a total amount advanced for the one or more supplier invoices from the plurality of open invoices. ### Claim 19 (depends on 16) The system of claim 16, wherein the invoice score is generated based on each of the supplier score, the buyer score, and the payment schedule of the respective invoice. ### Claim 20 (depends on 16) The system of claim 16, wherein the invoice score threshold is dynamically determined by the ML logic during analyzing of the designated one or more supplier invoices for advance processing.