US20050075960A1 - System and method for automated incoming payment and invoice reconciliation - Google Patents

System and method for automated incoming payment and invoice reconciliation Download PDF

Info

Publication number
US20050075960A1
US20050075960A1 US10/866,015 US86601504A US2005075960A1 US 20050075960 A1 US20050075960 A1 US 20050075960A1 US 86601504 A US86601504 A US 86601504A US 2005075960 A1 US2005075960 A1 US 2005075960A1
Authority
US
United States
Prior art keywords
payment
data
seller
matching
invoices
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/866,015
Other languages
English (en)
Inventor
Stacy Leavitt
Stephen Malloy
Robert Rogoff
Brian Schweigel
William Steiner
Alan Walters
Xiang Kong
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
OLD WORLD INDUSTRIES Inc
Original Assignee
OLD WORLD INDUSTRIES Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by OLD WORLD INDUSTRIES Inc filed Critical OLD WORLD INDUSTRIES Inc
Priority to US10/866,015 priority Critical patent/US20050075960A1/en
Assigned to OLD WORLD INDUSTRIES, INC. reassignment OLD WORLD INDUSTRIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KONG, XIANG, LEAVITT, STACY A., MALLOY, STEPHEN LOUIS, ROGOFF, ROBERT, SCHWEIGEL, BRIAN R., STEINER, WILLIAM M., WALTERS, ALAN J.
Publication of US20050075960A1 publication Critical patent/US20050075960A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/045—Payment circuits using payment protocols involving tickets
    • G06Q20/0457—Payment circuits using payment protocols involving tickets the tickets being sent electronically
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102—Bill distribution or payments
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/42—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for ticket printing or like apparatus, e.g. apparatus for dispensing of printed paper tickets or payment cards
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F9/00—Details other than those peculiar to special kinds or types of apparatus
    • G07F9/04—Means for returning surplus or unused coins
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07G—REGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS
    • G07G1/00—Cash registers
    • G07G1/01—Details for indicating
    • G07G1/06—Details for indicating with provision for the noting of the money to be paid
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07G—REGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS
    • G07G5/00—Receipt-giving machines

Definitions

  • the present application generally relates to systems and methods for automatically matching and processing an incoming payment from a buyer with an invoice that has been previously sent to the buyer. More specifically, the present application presents an automated electronic system and method for matching incoming payments with a previously sent invoice, processing the transaction at the seller's side in conjunction with the seller's financial institution, closing out the transaction, and updating the seller's accounting system.
  • FIG. 1 illustrates a typical transaction 100 for the purchase of goods according to the prior art.
  • the transaction involves a buyer 110 , a seller 130 , and a financial institution 120 .
  • the buyer 110 sends a purchase request 102 or purchase order to the seller 130 .
  • the purchase request 102 identifies the goods the buyer 110 desires.
  • the seller 130 receives the buyer's purchase request and then ships the goods to the buyer 110 .
  • the seller 130 may send a statement or invoice 105 .
  • the invoice 105 typically lists the goods being shipped and may include other information such as price, quantity, a seller coding or identification such as a SKU number and/or other order information.
  • a statement reflecting multiple shipments may be employed in situations where multiple shipments are sent to the same buyer.
  • the buyer 110 Once the buyer 110 has received the seller's goods and invoice 105 , the buyer 110 must pay for the goods. Presently, buyers pay for goods using any of a variety of methods including checks, Automated Clearing House (ACH) or other electronic/wire transfer or cash. Regardless of the method of payment, the buyer's payment is remitted to the financial institution 120 as payment 115 . In some cases the payment and/or information is sent initially to the seller 130 , who then passes it along to the financial institution 120 .
  • ACH Automated Clearing House
  • the financial institution 120 receives the buyer's payment 115 and deposits the funds into seller's account at the financial institution 120 . T The financial institution 120 then alerts the seller 130 that a payment has been received by sending payment data 125 to the seller 130 .
  • the payment data 125 may take the form of a monthly, weekly, or typically a daily account summary. In the most preferable configuration, the account summary is updated several times a day.
  • the payment data may also be electronically sent to the seller 130 or may be provided to the seller 130 by allowing the seller to electronically access the financial institution's records or photocopies may be mailed to the seller 130 .
  • the buyer's payment may be received in any of a variety of methods.
  • the payment is typically converted to an electronic expression by the financial institution.
  • a paper check that is received by the financial institution may be scanned or imaged and the payment data on the face of the check may be converted into an electronic expression by a data entry person at the financial institution 120 .
  • ACH or wire transfers are already in an electronic form, but the financial institution's record of the transaction may also reflect the originator of the ACH, and the date of the ACH, for example.
  • most of the bank's electronic data is sent to the seller 130 as the payment data 125 .
  • the seller 130 must typically then begin the laborious task of matching each received payment with the corresponding invoice. That is, in order to confirm that the buyer 110 has paid for the goods that were shipped, the seller 130 matches the payment data 125 received from the financial institution 120 to the invoice data 105 that was sent to the buyer 110 . Once the seller 130 has matched the invoice data 105 to the payment data 125 , the transaction is said to be closed-out, provided that the invoice data matches the payment data exactly. For a seller with a large number of invoices, this process may be very time consuming.
  • the seller 130 does not know whether the correct payment has been received from the buyer 110 .
  • the buyer 110 may have over or underpaid, for example. Consequently, until the transaction has been closed out, the seller 130 cannot be sure whether the current balance reflected in the seller's account at the financial institution 120 represents available cash or whether some amount is due back to the buyer 110 as an overpayment, for example.
  • FIG. 2 illustrates a typical work flow 200 for a processing a transaction for selling goods.
  • the sell side 201 sends an invoice to the buy side 202 .
  • the invoice is initially reviewed by the buyer. Any disputes are handled in step 230 , for example by making an adjustment.
  • any dispute or adjustment is reviewed and approved by the buyer. As discussed further below and indicated in FIG. 2 , the dispute and adjustment process may be quite time and labor consuming for the seller.
  • payment is sent from the buyer to the seller.
  • step 240 the payment received from the buyer is often manually matched to an invoice at the seller, which is quite time consuming. Even if some data is electronically provided, the buyer's payment systems are typically not equipped to process the received data without substantial human interaction.
  • the embodiments of the present invention provide a system and method for automating the reconciliation of incoming payment data with invoice data and automatically updating the seller's accounting system and the seller's financial institution.
  • the seller ships goods and sends one or more invoices to the buyer.
  • the buyer pays for the goods by sending a payment and remittance to the seller's financial institution.
  • the seller's financial institution processes the buyer's payment and payment information for payment data.
  • the payment data is supplied to an invoice and payment matching application.
  • the payment matching application preferably retrieves an identification of the buyer's invoice from the payment data and then queries the seller's accounting system for all outstanding invoices for the particular buyer.
  • the payment matching application attempts to match the invoice from the payment data with one or more of the buyer's outstanding invoices.
  • the payment matching application finds a full match, the invoiced payment is processed and the payment matching application sends posting data to the seller's accounting system and updates the seller's financial institution. If no full match is found, then the payment data is flagged for further processing by the seller.
  • the present system may preferably be directly integrated with the seller's financial institution.
  • FIG. 1 illustrates a typical transaction for the purchase of goods according to the prior art.
  • FIG. 2 illustrates a typical work flow for a processing a transaction for selling goods.
  • FIG. 3 illustrates an invoice and payment matching application according to an embodiment of the present invention.
  • FIG. 4 illustrates a flowchart of the operation of the automated incoming payment and invoice reconciliation system of FIG. 3 in greater detail.
  • FIG. 5 illustrates an example of some of the types of informational sources that may be included in the payment data.
  • FIG. 3 illustrates an automated incoming payment and invoice reconciliation system 300 according to an embodiment of the present invention.
  • the payment reconciliation system 300 includes a buyer 310 , a financial institution 320 , a seller 330 , an invoice and payment matching application 340 , and a payment management application 350 .
  • the payment management application 350 includes the financial institution 320 and the invoice and payment matching application 340 .
  • a purchase request 302 travels from buyer 310 to the seller 330 .
  • Invoice information 305 travels from the seller 330 to buyer 310 .
  • the invoice information 305 may travel separate from the goods and/or services provided by the seller 330 , or may travel along with the goods and/ore services.
  • Payment information 315 is sent from buyer 310 to the seller's financial institution 320 .
  • Payment data 325 is sent from the financial institution 320 to the invoice and payment matching application 340 .
  • Order data 335 is sent from the seller to the invoice and payment matching application 340 .
  • the order data 335 may be sent to the payment matching application 340 when the underlying goods are invoiced to the buyer or may be sent to the payment matching application at some later time.
  • the posting data 345 is sent from the invoice and payment matching 340 to the seller 330 .
  • the reconciliation system 300 proceeds generally as follows. First, the buyer 310 may decide to purchase goods, for example, from the seller 330 . Typically, the buyer 310 then notifies the seller 330 that the buyer 310 wishes to make a purchase by sending a purchase request 302 to the seller 330 . The seller 330 then receives the buyer's purchase request 302 . The seller 330 then ships the desired goods to the buyer 310 and also sends invoice information 305 to the buyer 310 .
  • the invoice information 305 preferably includes information relating to the goods that were shipped from the seller 330 to the buyer 310 .
  • the invoice information 305 preferably includes a seller coding identifying the goods being shipped, the price, quantity, and/or other order information.
  • the buyer receives the invoice information 305 and the goods.
  • the buyer 310 then reviews the received goods.
  • the buyer 310 preferably then pays for the received goods.
  • the amount of the buyer's payment may differ from the payment amount invoiced by the seller 330 for a variety of reasons.
  • the buyer's payment may differ from the invoice total. Additionally, for example, some or all of the goods may be damaged or destroyed. Alternatively, the price or quantity of the actual goods received may not match the agreed price or quantity of the goods appearing in the invoice information. Additionally, the seller 330 may have shipped goods other then the goods desired by the buyer 340 . These are merely a few examples of the myriad difficulties that may be encountered in shipping the goods to the buyer that may result in a discrepancy from the invoice information 305 .
  • the buyer 310 once the buyer 310 has received the goods, the buyer then pays for the goods by submitting payment information 315 to the financial institution 320 .
  • the present embodiment operates to transform the financial institution 320 into an payment management application 350 by integrating the financial institution 320 with the invoice and payment matching application 340 .
  • the buyer's payment information 315 is sent to the financial institution 320 .
  • the payment information 315 may be any of a variety of forms ranging from cash or check to electronic fund transfers such as Electronic Data Interchange (EDI), for example.
  • the financial institution 320 receives the payment information 315 and generates the payment data and remittance info 325 .
  • the payment data and remittance info 325 preferably includes all of the remittance data and may include additional information such as scanned images of received checks, the date of receipt of the buyer's remittance, or an invoice number included by the buyer on the check, for example.
  • the payment data 325 is then sent to the invoice and payment matching application 340 .
  • the invoice and payment matching application 340 also receives order data 335 from the seller 330 .
  • the order data 335 preferably includes three types of information, invoice-related information, buyer-related information and seller-related information.
  • the order data 335 preferably includes all of the information that was included in the invoice information 305 that was sent to the buyer 310 , and may also include information relating to the transfer of the goods such as a bill of lading or electronic images of the invoice information 305 .
  • one element of the payment data 325 preferably identifies the buyer making the payment.
  • the outstanding invoices have been previously sentor pre-delivered to the payment matching application 340 , for example at the time the invoice was originally sent to the buyer. If the payment matching application 340 is unable to find a particular invoice for a particular seller, then the payment matching 340 may send the payment data to the seller for further processing, as further described below. Alternatively, the payment matching application 340 may then query the seller 330 and retrieve a listing of all outstanding invoices for the indicated buyer as order data 335 . If no buyer is indicated in the payment data 325 , the payment matching application 340 may preferably retrieve all outstanding invoices for all buyers.
  • the payment and remittance data 325 preferably indicates the buyer.
  • the payment matching application 340 may then query the seller 330 for any information related to that buyer. Additionally, the payment matching application 340 may retrieve the data from the seller 330 in any of a variety of ways. For example, order data 335 may be received by the payment matching application 340 as a batch of information representing several invoices for one or more buyers as opposed to information for a single invoice of a buyer. Additionally, the payment information 315 received from the buyer 310 may represent a batch of several invoices instead of a single invoice.
  • the order data 335 also preferably includes information relating to the buyer itself, such as the number of previous orders by the buyer, any negotiated discounts that apply to the buyer or other incentives, for example, as further described below.
  • the order data 335 may include information with regard to the seller such as the salesperson that originated the order or internal routing information for adjustment approval, for example, as further described below.
  • the invoice and payment matching application 340 receives the payment data 325 and the order data 335 , the invoice and payment matching application 340 then proceeds to attempt to match the received payment data to one or more of the outstanding invoices retrieved as part of the order data.
  • the invoice and payment matching application 340 displays or sends an indication of the successful match to the seller 330 as posting data 345 .
  • the posting data 345 preferably indicates which invoice or invoices are being paid by the payment data.
  • the seller 330 receives the posting data 345 and the accounting system records at the seller 330 are then updated to reflect that the invoices(s) have been paid in order to close the transaction.
  • the payment matching application may also operate on a batch basis. For example, a batch of invoices may be processed at one time. The batch of invoices may be sent to the seller at one time as batch after all invoices have been matched. A reviewer at the seller may then further review, modify and/or approve/reject the matches.
  • the invoice and payment matching application 340 may then flag the payment data for further processing.
  • the additional processing is further described in U.S. patent application Ser. No. ______ filed ______, entitled “System and Method For Automated Payment And Adjustment Processing” and U.S. patent application Ser. No. ______ filed ______, entitled “System and Method For Seller-Assisted Automated Payment Processing and Exception Management”, both of which are incorporated herein by reference in their entirety.
  • the invoice information 305 may take any of several forms.
  • the invoice information 305 may be a paper document or an electronic document such as an e-mail, web-enabled form, or other EDI information exchange.
  • the buyer may instead be interested in securing services. Similar considerations arise in the context of procuring services with regard to invoice and payment matching. Although the current description focuses on goods, the present invoice and payment matching system applies equally well to services and is not limited to goods. Additionally, the applicability of the present system is not limited to any specific industry or sector.
  • the invoice information may include a great deal of information as further described below. However, not all of the items of information listed below need be present in the invoice information.
  • the inclusion of an item as part of the invoice information may be configured by the seller.
  • the invoice information may include information concerning the quantity and price of goods and/or services sold by the seller 330 to buyer 310 .
  • the invoice information 305 may also include information such as the delivery date, buyer's 310 name and address, the seller's 330 name and address, any amount of money that is past due from buyer 310 to the seller 330 , or any available credit buyer 310 has with the seller 330 .
  • the invoice information 305 preferably includes an invoice number to be used by the seller 330 for identification and tracking purposes.
  • the payment information may take any of a wide number of forms as chosen by the buyer.
  • the payment information 315 may therefore include a check, a financial institution draft, a cashier's check, a money order, an order to charge a credit line, a promissory note, or any other document that shows payment for goods and/or services received.
  • the payment information 315 may also include an electronic image of the form of payment.
  • the payment information 315 may include an electronic image of a check used to pay for the goods and/or services.
  • the payment data and remittance information are preferably constructed by the financial institution 320 to the extent that the payment data and/or remittance info are not already available from the buyer in electronic form. That is, the financial institution 320 may review incoming payment information, such as a check for example, and then develop a set of remittance data relating to the check. For example, the financial institution 320 may electronically note the date of receipt, payor, payee, and any account or invoice numbers on the check. The financial institution may also electronically image the received check. The notations made by the financial institution 320 may then be passed to the invoice and payment matching application as part of the payment data and remittance info 325 .
  • incoming payment information such as a check for example
  • the financial institution 320 may electronically note the date of receipt, payor, payee, and any account or invoice numbers on the check.
  • the financial institution may also electronically image the received check.
  • the notations made by the financial institution 320 may then be passed to the invoice and payment matching application as part
  • the payment information may take any of a wide variety of forms.
  • the financial institution 320 typically processes the received payment information and re-expresses or re-formats the payment information to be in accordance with the financial institution's internal processing desires.
  • the reprocessed electronically received payment information is preferably then passed to the invoice and payment matching application 340 as part of the payment data
  • the payment data itself may take any of a wide variety of forms as selected by the financial institution 320 .
  • the payment data 325 may alternatively be comprised of XML documents, EDI documents, information from internet-based financial services, or any other form of electronic data relating to the payment of goods or services.
  • the order data 335 and posting data 345 may also take any of wide variety of forms such as e-mail, XML documents, HTML documents, or EDI, for example.
  • the invoice and payment matching application 340 may be implemented, for example, as a package software application or installed at a financial institution or other third party as an application service provider (ASP).
  • ASP application service provider
  • the invoice and payment matching application 340 may be directly hosted by the financial institution 320 , the seller 330 or a third party.
  • the actual physical location of the invoice and payment matching application 340 is not relevant as long as it remains in communication with the financial institution 320 and the seller 330 .
  • the payment matching application 340 may be hosted or installed at a third party or may be otherwise outsourced.
  • FIG. 4 illustrates a flowchart 400 of the operation of the automated incoming payment and invoice reconciliation system of FIG. 3 in greater detail.
  • the payment data and the order data are received at steps 401 - 402 .
  • the payment data is received and batched by the financial institution. That is, preferably the financial institution may accumulate a number of payments in a queue to form a batch. Then, a person at the seller may access the financial institution's records to process the batch of payments as a whole. While the accumulation of a number of payments into batches is preferred, the system may process individual payments if desired by the seller.
  • each payment in the batch of payments is evaluated.
  • the payment data 325 includes invoice information for linking a payment made by the buyer with a specific invoice number sent to the buyer by the seller.
  • the listing of invoice numbers is preferably retrieved from the seller as part of the order data 335 .
  • the matching of the payment data to the order data described above is performed on the basis of invoice number
  • other elements of the payment and/or remittance information may be used to match the buyer's payment.
  • payments may be matched based on a purchase order number or remitter or seller's name, for example.
  • step 420 additional processing, such as further automated or human interaction by the seller may be required to match the received payment data with one or more invoices retrieved in the order data.
  • additional processing such as further automated or human interaction by the seller may be required to match the received payment data with one or more invoices retrieved in the order data.
  • step 430 the received payment has been matched to a specific invoice number.
  • step 432 the invoiced payment amount included in the invoice is compared to the received payment. If the received payment matches the invoiced payment, the process proceeds to step 435 .
  • step 435 the payment is marked for posting to the seller's accounting system.
  • step 420 the process proceeds to step 420 and further automated or human interaction by the seller may be required to match the payment to one or more invoices.
  • the received payment and its respective invoice are market for posting on the seller's system.
  • the posting data is transmitted to the seller to update the seller's accounting system.
  • the buyer's payment has been automatically matched with the seller's outstanding invoice and the seller's accounting system has been updated to reflect an accurate indication or available cash.
  • the requirement for human interaction to process the seller's payment by matching the payment to an invoice has been minimized.
  • the seller's assistance may be required when the received payment does not match an outstanding invoice, the seller's direct interaction is no longer necessary in the typical case of a payment exactly matching an invoice.
  • the present description recites that data is received directly from the buyer and seller, the actual data may be retrieved from a third part intermediary, agent, hosting service, or other party on behalf of the respective buyer and seller. Additionally, the payment need not be sent directly from the original buyer and may instead originate with the buyer's distributor, corporate parent, agent, or other third party.
  • invoice and payment matching application is preferably integrated as part of the financial institution, the invoice and payment matching application may be implemented as a third party or even at the seller's site.
  • FIG. 5 illustrates an example of some of the types of informational sources that may be included in the payment data 325 .
  • the payment data 325 may include data derived from XML documents 510 , EDI documents 520 , electronic data 540 , and/or data from web services 530 .
  • the electronic data 540 may include electronic images of the payment information 315 , as described in FIG. 3 .
  • the payment data 325 may be configured in any internal format desired by the financial institution that is capable of being received and processed by the invoice and payment matching application 340 .
  • the automated incoming payment and invoice reconciliation system provides an automated solution to review and verify payment for the transaction between buyer and seller. That is, each payment may be automatically evaluated and matched with an outstanding invoice, preferably using the invoice number. If the payment amount of the transaction matches, the buyer's payment may be directly posted to the seller's account at the financial institution and the seller's accounting system may be updated by the posting data. Preferably, most of the transactions occurring between buyers and sellers proceed as expected and consequently have matching invoice numbers and payment amounts. Consequently, a large percentage of the matching operations that previously may have required human interaction at the seller may now be accomplished automatically. Conversely, if the transaction does not match, then further processing at the seller may be required.
  • the present embodiment serves to automatically match payment data with invoice data.
  • the prior art methodologies for matching payment data with invoice data involved a great deal of manual effort and were quite slow.
  • most incoming payments may be matched and processed automatically. Thus reducing effort and cost and providing a more accurate assessment of available cash.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
US10/866,015 2003-10-02 2004-06-10 System and method for automated incoming payment and invoice reconciliation Abandoned US20050075960A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/866,015 US20050075960A1 (en) 2003-10-02 2004-06-10 System and method for automated incoming payment and invoice reconciliation

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US50822103P 2003-10-02 2003-10-02
US10/866,015 US20050075960A1 (en) 2003-10-02 2004-06-10 System and method for automated incoming payment and invoice reconciliation

Publications (1)

Publication Number Publication Date
US20050075960A1 true US20050075960A1 (en) 2005-04-07

Family

ID=34465079

Family Applications (6)

Application Number Title Priority Date Filing Date
US10/866,015 Abandoned US20050075960A1 (en) 2003-10-02 2004-06-10 System and method for automated incoming payment and invoice reconciliation
US10/865,997 Abandoned US20050075979A1 (en) 2003-10-02 2004-06-10 System and method for seller-assisted automated payment processing and exception management
US10/865,076 Abandoned US20050075978A1 (en) 2003-10-02 2004-06-10 System and method for automated payment and adjustment processing
US11/326,950 Abandoned US20060116956A1 (en) 2003-10-02 2006-01-06 System and method for automated payment and adjustment processing
US11/327,802 Abandoned US20060112010A1 (en) 2003-10-02 2006-01-06 System and method for automated payment and adjustment processing
US11/544,353 Expired - Fee Related US8498935B2 (en) 2003-10-02 2006-10-04 System and method for automated payment and adjustment processing

Family Applications After (5)

Application Number Title Priority Date Filing Date
US10/865,997 Abandoned US20050075979A1 (en) 2003-10-02 2004-06-10 System and method for seller-assisted automated payment processing and exception management
US10/865,076 Abandoned US20050075978A1 (en) 2003-10-02 2004-06-10 System and method for automated payment and adjustment processing
US11/326,950 Abandoned US20060116956A1 (en) 2003-10-02 2006-01-06 System and method for automated payment and adjustment processing
US11/327,802 Abandoned US20060112010A1 (en) 2003-10-02 2006-01-06 System and method for automated payment and adjustment processing
US11/544,353 Expired - Fee Related US8498935B2 (en) 2003-10-02 2006-10-04 System and method for automated payment and adjustment processing

Country Status (6)

Country Link
US (6) US20050075960A1 (https=)
EP (2) EP1668452A4 (https=)
JP (2) JP2007507799A (https=)
CN (2) CN1926568A (https=)
CA (2) CA2540654A1 (https=)
WO (3) WO2005038557A2 (https=)

Cited By (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040153384A1 (en) * 2002-12-30 2004-08-05 Fannie Mae System and method for creating financial assets
US20070156583A1 (en) * 2005-12-30 2007-07-05 Volker Ripp Clearing receivables with improved search
US20070255648A1 (en) * 2002-12-30 2007-11-01 Whipple F S Cash flow system and method
US20070255654A1 (en) * 2002-12-30 2007-11-01 Whipple F S Servicer compensation system and method
US20080015982A1 (en) * 2000-09-20 2008-01-17 Jeremy Sokolic Funds transfer method and system including payment enabled invoices
US20080133388A1 (en) * 2006-12-01 2008-06-05 Sergey Alekseev Invoice exception management
US20090248518A1 (en) * 2008-03-28 2009-10-01 Fujitsu Limited Sales support apparatus, computer-readable recording medium having recorded therein sales support program, and sales support method
US7797213B2 (en) 2002-12-30 2010-09-14 Fannie Mae Cash flow aggregation system and method
US7885891B1 (en) 2006-03-22 2011-02-08 Fannie Mae Portal tool and method for securitizing excess servicing fees
CN102368341A (zh) * 2011-10-31 2012-03-07 浪潮齐鲁软件产业有限公司 一种增值税发票自助代开的方法
US8595134B2 (en) 2010-02-12 2013-11-26 Mastercard International Incorporated Apparatus and method for bill presentment and payment
US8620782B2 (en) 2001-06-28 2013-12-31 Checkfree Services Corporation Inter-network electronic billing
WO2013173664A3 (en) * 2012-05-16 2014-01-23 Inttra Inc. Invoice and freight statement matching and dispute resolution
US8732044B2 (en) 2006-05-23 2014-05-20 Mastercard International Incorporated Electronic transaction apparatus and method
US8874480B2 (en) 2007-04-27 2014-10-28 Fiserv, Inc. Centralized payment method and system for online and offline transactions
WO2015158628A1 (en) * 2014-04-14 2015-10-22 Mastercard International Incorporated Transaction identification and recognition
CN105630785A (zh) * 2014-10-27 2016-06-01 航天信息股份有限公司 一种发票使用异常预警方法和系统
CN106651396A (zh) * 2016-12-21 2017-05-10 世纪禾光科技发展（北京）有限公司 客户识别方法及装置
US9749391B2 (en) 2000-03-29 2017-08-29 Mastercard International Incorporated Method and system for processing messages in a bill payment and presentment system over a communications network
WO2019022716A1 (en) * 2017-07-25 2019-01-31 Visa International Service Association REAL TIME CROSSING MATCH DATA
US10417622B2 (en) * 2013-11-19 2019-09-17 Oracle International Corporation Configurable invoice matching optimization system
US10970777B2 (en) 2008-09-15 2021-04-06 Mastercard International Incorporated Apparatus and method for bill payment card enrollment
LU101595B1 (en) * 2020-01-07 2021-07-07 Creopay S A R L System and method for managing unpaid debts
US20210365905A1 (en) * 2016-09-06 2021-11-25 Wells Fargo Bank, N.A. Automated, history-based correction of electronic remittances for programmatic reconciliation of electronic receivables
US11341547B1 (en) * 2019-06-19 2022-05-24 Amazon Technologies, Inc. Real-time detection of duplicate data records
US20230035551A1 (en) * 2021-07-29 2023-02-02 Intuit Inc. Multiple source audit log generation
US11616744B2 (en) 2021-07-29 2023-03-28 Intuit Inc. Context-dependent message extraction and transformation
US11645686B2 (en) 2018-12-05 2023-05-09 Sap Se Graphical approach to multi-matching
US11748368B1 (en) 2015-10-06 2023-09-05 Wells Fargo Bank, N.A. Data field transaction repair interface
US11809390B2 (en) 2021-07-29 2023-11-07 Intuit Inc. Context-dependent event cleaning and publication
US12400247B2 (en) 2018-12-04 2025-08-26 Sap Se Representing sets of entities for matching problems

Families Citing this family (75)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050049964A1 (en) * 2003-01-14 2005-03-03 Winterer Mary Jo Financial transaction card with automatic payment feature
US6315193B1 (en) * 1998-08-31 2001-11-13 Mastercard International Incorporated Financial transaction card with installment loan feature
US8799153B2 (en) 1998-08-31 2014-08-05 Mastercard International Incorporated Systems and methods for appending supplemental payment data to a transaction message
US8266028B2 (en) 2002-12-06 2012-09-11 Altisource Solutions S.à r.l. Expense tracking, electronic ordering, invoice presentment, and payment system and method
US7412418B2 (en) 2002-12-06 2008-08-12 Ocwen Financial Corporation Expense tracking, electronic ordering, invoice presentment, and payment system and method
US10127558B2 (en) * 2002-12-06 2018-11-13 Altisource S.À R.L. Expense tracking, electronic ordering, invoice presentment, and payment system and method
US20050075960A1 (en) * 2003-10-02 2005-04-07 Leavitt Stacy A. System and method for automated incoming payment and invoice reconciliation
US8175938B2 (en) * 2004-04-13 2012-05-08 Ebay Inc. Method and system for facilitating merchant-initiated online payments
WO2008157458A1 (en) * 2007-06-16 2008-12-24 Ronald Ronald Rosenberger Bill payment using portional crediting from additional available cash and credit balances
US8682784B2 (en) * 2004-07-16 2014-03-25 Ebay, Inc. Method and system to process credit card payment transactions initiated by a merchant
US20060059026A1 (en) * 2004-08-24 2006-03-16 Oracle International Corporation Compliance workbench
US7904386B2 (en) * 2005-09-30 2011-03-08 American Express Travel Related Services Company, Inc. System, method, and computer program product for saving and investing through use of transaction cards
US20070094136A1 (en) * 2005-10-24 2007-04-26 Robert Reiner Method of selecting line item kind for invoice database
US7596519B2 (en) * 2005-11-14 2009-09-29 Sap Ag System and method for facilitating open item clearance
DE102006009733B4 (de) * 2006-03-02 2011-02-24 Odu-Steckverbindungssysteme Gmbh & Co. Kg Teil einer elektronischen Kuppelvorrichtung
US7680737B2 (en) 2006-07-06 2010-03-16 Moneygram International, Inc. Systems and methods for processing payments with payment review features
US20080021822A1 (en) * 2006-07-18 2008-01-24 Jpmorgan Chase Bank, N.A. Method and system for receivables management
US10453029B2 (en) * 2006-08-03 2019-10-22 Oracle International Corporation Business process for ultra transactions
US20100094735A1 (en) * 2006-11-15 2010-04-15 Charles Reynolds Methods and systems for automated payments
US20090083179A1 (en) * 2007-04-18 2009-03-26 Jonathan Gustave Web-accessible payment processing system
US20080294551A1 (en) * 2007-01-29 2008-11-27 Ernesto Degenhart Cross-Border Remittance
US20080255972A1 (en) * 2007-04-10 2008-10-16 Invoice Compliance Experts Legal billing enhancement method and apparatus
US7974922B1 (en) 2007-09-24 2011-07-05 Wells Fargo Bank, N.A. Computer-driven exception processing system
US8285573B1 (en) 2008-01-15 2012-10-09 SciQuest Inc. Prioritizing orders/receipt of items between users
US8065202B1 (en) 2008-01-15 2011-11-22 SciQuest Inc. Form management in an electronic procurement system
US8359245B1 (en) 2008-01-15 2013-01-22 SciQuest Inc. Taxonomy and data structure for an electronic procurement system
US12299732B2 (en) 2008-01-15 2025-05-13 Sciquest, Inc. User-specific rule-based database querying
US8065189B1 (en) 2008-01-15 2011-11-22 SciQuest Inc. Method, medium, and system for automatically moving items from a first shopping cart to a second shopping cart
US8112317B1 (en) 2008-01-15 2012-02-07 SciQuest Inc. Providing substitute items when ordered item is unavailable
US8930244B2 (en) * 2008-01-15 2015-01-06 Sciquest, Inc. Method, medium, and system for processing requisitions
US8694429B1 (en) 2008-01-15 2014-04-08 Sciquest, Inc. Identifying and resolving discrepancies between purchase documents and invoices
US20140129431A1 (en) * 2008-01-31 2014-05-08 Bill.Com, Inc. Enhanced System and Method For Private Interbank Clearing System
US20110184843A1 (en) * 2008-01-31 2011-07-28 Bill.Com, Inc. Enhanced electronic anonymous payment system
US9141991B2 (en) 2008-01-31 2015-09-22 Bill.Com, Inc. Enhanced electronic data and metadata interchange system and process for electronic billing and payment system
US10769686B2 (en) 2008-01-31 2020-09-08 Bill.Com Llc Enhanced invitation process for electronic billing and payment system
US10043201B2 (en) * 2008-01-31 2018-08-07 Bill.Com, Inc. Enhanced invitation process for electronic billing and payment system
US20110196786A1 (en) * 2008-01-31 2011-08-11 Rene Lacerte Determining trustworthiness and familiarity of users of an electronic billing and payment system
US8756117B1 (en) 2008-05-27 2014-06-17 Sciquest, Inc. Sku based contract management in an electronic procurement system
US8069096B1 (en) 2008-05-27 2011-11-29 SciQuest Inc. Multi-constituent attribution of a vendor's product catalog
US9245291B1 (en) 2008-05-27 2016-01-26 SciQuest Inc. Method, medium, and system for purchase requisition importation
US20110270749A1 (en) * 2010-04-30 2011-11-03 Robert Bennett Electronic invoice presentation and payment system
US8819789B2 (en) 2012-03-07 2014-08-26 Bill.Com, Inc. Method and system for using social networks to verify entity affiliations and identities
US10482396B2 (en) * 2012-03-16 2019-11-19 Refinitiv Us Organization Llc System and method for automated compliance verification
US8660866B1 (en) * 2012-06-08 2014-02-25 Atlas Financial Partners LLC Methods and systems for administering life insurance products through classifying insured lives to allocate costs
CN103595613B (zh) * 2012-08-13 2017-06-06 阿里巴巴集团控股有限公司 即时通讯客户端、即时通讯服务器和即时通讯方法
US10387858B2 (en) * 2013-02-07 2019-08-20 Jpmorgan Chase Bank, N.A. Integrated electronic cash flow management system and method
US10282712B2 (en) * 2013-02-07 2019-05-07 Jpmorgan Chase Bank, N.A. Integrated electronic disbursement and cash flow management system and method
US10417674B2 (en) 2013-03-14 2019-09-17 Bill.Com, Llc System and method for sharing transaction information by object tracking of inter-entity transactions and news streams
US10115137B2 (en) 2013-03-14 2018-10-30 Bill.Com, Inc. System and method for enhanced access and control for connecting entities and effecting payments in a commercially oriented entity network
US20150012442A1 (en) 2013-03-14 2015-01-08 Bill.Com, Inc. Enhanced system and method for scanning and processing of payment documentation
US10572921B2 (en) 2013-07-03 2020-02-25 Bill.Com, Llc System and method for enhanced access and control for connecting entities and effecting payments in a commercially oriented entity network
EP3072095A4 (en) 2013-11-20 2017-07-05 Mastercard International, Inc. Method and system for processing a discount
US20150324872A1 (en) * 2014-05-09 2015-11-12 Bank Of America Corporation Matching Data From Various Channels
US10241989B2 (en) * 2014-05-21 2019-03-26 Adobe Inc. Displaying document modifications using a timeline
US10019743B1 (en) 2014-09-19 2018-07-10 Altisource S.á r.l. Methods and systems for auto expanding vendor selection
US10319025B2 (en) 2015-11-24 2019-06-11 Bank Of America Corporation Executing terms of physical trade documents
US10127209B2 (en) 2015-11-24 2018-11-13 Bank Of America Corporation Transforming unstructured documents
US10430760B2 (en) 2015-11-24 2019-10-01 Bank Of America Corporation Enhancing communications based on physical trade documents
US10410168B2 (en) 2015-11-24 2019-09-10 Bank Of America Corporation Preventing restricted trades using physical documents
US20180047076A1 (en) * 2016-08-09 2018-02-15 Kathlynn Fekete Sale service process assistance
US11646114B2 (en) * 2016-08-26 2023-05-09 Sap Se Method and system for processing of electronic medical invoices
CN108830664A (zh) * 2017-05-05 2018-11-16 平安科技（深圳）有限公司 差额电子蓝票生成方法、设备以及计算机可读存储介质
FR3069083A1 (fr) * 2017-07-12 2019-01-18 Compagnie De L'arc Atlantique Procede pour augmenter la robustesse d'un paiement
CN107180345A (zh) * 2017-07-20 2017-09-19 东莞市盟大塑化科技有限公司 一种线上交易线下支付的交易方法
US20190095915A1 (en) * 2017-09-28 2019-03-28 Mastercard International Incorporated System and method for managing recurring payments
CN110019967B (zh) * 2017-12-07 2022-04-29 航天信息股份有限公司 一种获取企业异常发票信息的方法及系统
JP7075142B2 (ja) * 2018-03-29 2022-05-25 Ｂａｎｋ Ｉｎｖｏｉｃｅ株式会社 情報処理装置、情報処理方法およびプログラム
JP7056930B2 (ja) * 2018-12-21 2022-04-19 株式会社アライ 業務管理システム
US11100409B2 (en) * 2019-02-15 2021-08-24 Highradius Corporation Machine learning assisted transaction component settlement
US11521249B2 (en) * 2019-03-13 2022-12-06 Stripe, Inc. Auto-reconciliation
US11587093B2 (en) * 2019-03-13 2023-02-21 Stripe, Inc. Optimized dunning using machine-learned model
US11410246B2 (en) * 2019-06-06 2022-08-09 Salus Finance, LLC System and method for consolidation, reconciliation and payment management
CN110969408B (zh) * 2019-11-08 2024-04-05 国网辽宁省电力有限公司 物资结算全流程一体化管理平台生成系统及方法
CA3209072A1 (en) * 2021-02-18 2022-08-25 Xero Limited Systems and method for generating labelled datasets
US11704669B1 (en) 2022-01-03 2023-07-18 Bank Of America Corporation Dynamic contactless payment processing based on real-time contextual information

Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3363362A (en) * 1965-07-09 1968-01-16 Paul L. Jolley Self-loading transporter for composite toy vehicles
US5121945A (en) * 1988-04-20 1992-06-16 Remittance Technology Corporation Financial data processing system
US5920847A (en) * 1993-11-01 1999-07-06 Visa International Service Association Electronic bill pay system
US5940813A (en) * 1996-07-26 1999-08-17 Citibank, N.A. Process facility management matrix and system and method for performing batch, processing in an on-line environment
US6070150A (en) * 1996-10-18 2000-05-30 Microsoft Corporation Electronic bill presentment and payment system
US6223168B1 (en) * 1995-07-25 2001-04-24 Bottomline Technologies, Inc. Automatic remittance delivery system
US20020007302A1 (en) * 2000-03-06 2002-01-17 Work Bruce V. Method and apparatus for tracking vendor compliance with purchaser guidelines and related method for the commercial distribution of software and hardware implementing same
US6363362B1 (en) * 1999-04-07 2002-03-26 Checkfree Services Corporation Technique for integrating electronic accounting systems with an electronic payment system
US20020038305A1 (en) * 2000-08-04 2002-03-28 Bottomline Technologies (De) Inc. Automated invoice receipt and management system
US20020052846A1 (en) * 2000-10-18 2002-05-02 Webmoney Corporation Electronic account settlement apparatus electronic settlement method, storage medium and computer data signal
US20020107794A1 (en) * 2001-02-05 2002-08-08 Furphy Thomas W. Method and system for processing transactions
US20020111906A1 (en) * 1997-12-19 2002-08-15 Checkfree Corporation Remittance payment processing with account scheming and/or validation
US20020116334A1 (en) * 2001-02-22 2002-08-22 International Business Machines Corporation Invoice processing system
US20020138426A1 (en) * 2001-03-26 2002-09-26 Streamtrans, Inc. Concentration of electronic payments
US20020166334A1 (en) * 2001-05-14 2002-11-14 Houk Thomas I Modular liquid-cooled air conditioning system
US20020194125A1 (en) * 1998-07-01 2002-12-19 Michael F.Krieger Method and software article for selecting electronic payment of vendors in an automated payment environment
US20030018550A1 (en) * 2000-02-22 2003-01-23 Rotman Frank Lewis Methods and systems for providing transaction data
US20030158811A1 (en) * 2001-07-18 2003-08-21 Ventanex System and method for rules based electronic funds transaction processing
US20040010465A1 (en) * 2002-05-20 2004-01-15 Cliff Michalski Method and apparatus for exception based payment posting
US20040034596A1 (en) * 2002-08-19 2004-02-19 Jeremy Light Electronic payment management
US20040093278A1 (en) * 1998-08-06 2004-05-13 Burchetta James D. Computerized dispute resolution system and method
US20040148324A1 (en) * 2003-01-29 2004-07-29 Garg Rajat P Block-partitioned technique for solving a system of linear equations represented by a matrix with static and dynamic entries
US20040148234A1 (en) * 2000-02-18 2004-07-29 Oracle Corporation Methods and systems for online self-service receivables management and automated online receivables dispute resolution
US6832212B1 (en) * 1997-09-30 2004-12-14 Ncr Corporation Method and apparatus for manipulating billing and payment information within a browser interface system
US6856970B1 (en) * 2000-09-26 2005-02-15 Bottomline Technologies Electronic financial transaction system
US20050125340A1 (en) * 2003-06-06 2005-06-09 Huey Lin Automatic dispute resolution

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0880749A4 (en) * 1996-02-09 2003-05-28 Citibank Na STATEMENT ORDER SYSTEM
US7340433B1 (en) * 1999-07-30 2008-03-04 Orbian Management Limited System and method of transaction settlement using trade credit
CA2310589A1 (en) * 2000-02-06 2001-12-02 Jason Frank Saxon System and method for ordering products or services
US7181422B1 (en) * 2000-10-20 2007-02-20 Tranquilmoney, Inc. Segregation and management of financial assets by rules
US8326754B2 (en) * 2001-02-05 2012-12-04 Oracle International Corporation Method and system for processing transactions
US7229811B2 (en) * 2001-08-03 2007-06-12 Genencor International, Inc. 2,5-diketo-D-gluconic acid (2,5-DKG) permeases
US20060010016A1 (en) * 2003-05-01 2006-01-12 Kossol Joyce L System and method for reconciling an insurance payment with an insurance claim
US20050075960A1 (en) * 2003-10-02 2005-04-07 Leavitt Stacy A. System and method for automated incoming payment and invoice reconciliation

Patent Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3363362A (en) * 1965-07-09 1968-01-16 Paul L. Jolley Self-loading transporter for composite toy vehicles
US5121945A (en) * 1988-04-20 1992-06-16 Remittance Technology Corporation Financial data processing system
US5920847A (en) * 1993-11-01 1999-07-06 Visa International Service Association Electronic bill pay system
US6223168B1 (en) * 1995-07-25 2001-04-24 Bottomline Technologies, Inc. Automatic remittance delivery system
US5940813A (en) * 1996-07-26 1999-08-17 Citibank, N.A. Process facility management matrix and system and method for performing batch, processing in an on-line environment
US6070150A (en) * 1996-10-18 2000-05-30 Microsoft Corporation Electronic bill presentment and payment system
US6832212B1 (en) * 1997-09-30 2004-12-14 Ncr Corporation Method and apparatus for manipulating billing and payment information within a browser interface system
US20020111906A1 (en) * 1997-12-19 2002-08-15 Checkfree Corporation Remittance payment processing with account scheming and/or validation
US20020194125A1 (en) * 1998-07-01 2002-12-19 Michael F.Krieger Method and software article for selecting electronic payment of vendors in an automated payment environment
US20040093278A1 (en) * 1998-08-06 2004-05-13 Burchetta James D. Computerized dispute resolution system and method
US6363362B1 (en) * 1999-04-07 2002-03-26 Checkfree Services Corporation Technique for integrating electronic accounting systems with an electronic payment system
US20040148234A1 (en) * 2000-02-18 2004-07-29 Oracle Corporation Methods and systems for online self-service receivables management and automated online receivables dispute resolution
US20030018550A1 (en) * 2000-02-22 2003-01-23 Rotman Frank Lewis Methods and systems for providing transaction data
US20020007302A1 (en) * 2000-03-06 2002-01-17 Work Bruce V. Method and apparatus for tracking vendor compliance with purchaser guidelines and related method for the commercial distribution of software and hardware implementing same
US20020038305A1 (en) * 2000-08-04 2002-03-28 Bottomline Technologies (De) Inc. Automated invoice receipt and management system
US6856970B1 (en) * 2000-09-26 2005-02-15 Bottomline Technologies Electronic financial transaction system
US20020052846A1 (en) * 2000-10-18 2002-05-02 Webmoney Corporation Electronic account settlement apparatus electronic settlement method, storage medium and computer data signal
US20020107794A1 (en) * 2001-02-05 2002-08-08 Furphy Thomas W. Method and system for processing transactions
US20020116334A1 (en) * 2001-02-22 2002-08-22 International Business Machines Corporation Invoice processing system
US20020138426A1 (en) * 2001-03-26 2002-09-26 Streamtrans, Inc. Concentration of electronic payments
US20020166334A1 (en) * 2001-05-14 2002-11-14 Houk Thomas I Modular liquid-cooled air conditioning system
US20030158811A1 (en) * 2001-07-18 2003-08-21 Ventanex System and method for rules based electronic funds transaction processing
US20040010465A1 (en) * 2002-05-20 2004-01-15 Cliff Michalski Method and apparatus for exception based payment posting
US20040034596A1 (en) * 2002-08-19 2004-02-19 Jeremy Light Electronic payment management
US20040148324A1 (en) * 2003-01-29 2004-07-29 Garg Rajat P Block-partitioned technique for solving a system of linear equations represented by a matrix with static and dynamic entries
US20050125340A1 (en) * 2003-06-06 2005-06-09 Huey Lin Automatic dispute resolution

Cited By (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9749391B2 (en) 2000-03-29 2017-08-29 Mastercard International Incorporated Method and system for processing messages in a bill payment and presentment system over a communications network
US20080015982A1 (en) * 2000-09-20 2008-01-17 Jeremy Sokolic Funds transfer method and system including payment enabled invoices
US8620782B2 (en) 2001-06-28 2013-12-31 Checkfree Services Corporation Inter-network electronic billing
US10210488B2 (en) 2001-06-28 2019-02-19 Checkfree Services Corporation Inter-network financial service
US20110131116A1 (en) * 2002-12-30 2011-06-02 Fannie Mae System and method for creating financial assets
US20040153384A1 (en) * 2002-12-30 2004-08-05 Fannie Mae System and method for creating financial assets
US7533057B2 (en) 2002-12-30 2009-05-12 Fannie Mae Servicer compensation system and method
US20070255648A1 (en) * 2002-12-30 2007-11-01 Whipple F S Cash flow system and method
US8195564B2 (en) 2002-12-30 2012-06-05 Fannie Mae System and method for creating financial assets
US7797213B2 (en) 2002-12-30 2010-09-14 Fannie Mae Cash flow aggregation system and method
US7856397B2 (en) 2002-12-30 2010-12-21 Fannie Mae System and method for creating financial assets
US20070255654A1 (en) * 2002-12-30 2007-11-01 Whipple F S Servicer compensation system and method
US20070156583A1 (en) * 2005-12-30 2007-07-05 Volker Ripp Clearing receivables with improved search
US7664704B2 (en) * 2005-12-30 2010-02-16 Sap Ag Clearing receivables with improved search
US7885891B1 (en) 2006-03-22 2011-02-08 Fannie Mae Portal tool and method for securitizing excess servicing fees
US8732044B2 (en) 2006-05-23 2014-05-20 Mastercard International Incorporated Electronic transaction apparatus and method
US20080133388A1 (en) * 2006-12-01 2008-06-05 Sergey Alekseev Invoice exception management
US8874480B2 (en) 2007-04-27 2014-10-28 Fiserv, Inc. Centralized payment method and system for online and offline transactions
US20090248518A1 (en) * 2008-03-28 2009-10-01 Fujitsu Limited Sales support apparatus, computer-readable recording medium having recorded therein sales support program, and sales support method
US10970777B2 (en) 2008-09-15 2021-04-06 Mastercard International Incorporated Apparatus and method for bill payment card enrollment
US8595134B2 (en) 2010-02-12 2013-11-26 Mastercard International Incorporated Apparatus and method for bill presentment and payment
US9824342B2 (en) 2010-02-12 2017-11-21 Mastercard International Incorporated Apparatus and method for bill presentment and payment
CN102368341A (zh) * 2011-10-31 2012-03-07 浪潮齐鲁软件产业有限公司 一种增值税发票自助代开的方法
WO2013173664A3 (en) * 2012-05-16 2014-01-23 Inttra Inc. Invoice and freight statement matching and dispute resolution
US10417622B2 (en) * 2013-11-19 2019-09-17 Oracle International Corporation Configurable invoice matching optimization system
WO2015158628A1 (en) * 2014-04-14 2015-10-22 Mastercard International Incorporated Transaction identification and recognition
CN105630785A (zh) * 2014-10-27 2016-06-01 航天信息股份有限公司 一种发票使用异常预警方法和系统
US11748368B1 (en) 2015-10-06 2023-09-05 Wells Fargo Bank, N.A. Data field transaction repair interface
US20210365905A1 (en) * 2016-09-06 2021-11-25 Wells Fargo Bank, N.A. Automated, history-based correction of electronic remittances for programmatic reconciliation of electronic receivables
US11720867B2 (en) * 2016-09-06 2023-08-08 Wells Fargo Bank, N.A. Automated, history-based correction of electronic remittances for programmatic reconciliation of electronic receivables
CN106651396A (zh) * 2016-12-21 2017-05-10 世纪禾光科技发展（北京）有限公司 客户识别方法及装置
US11810084B2 (en) * 2017-07-25 2023-11-07 Visa International Service Association Real time cross-matching data
US20210150495A1 (en) * 2017-07-25 2021-05-20 Visa International Service Association Real time cross-matching data
WO2019022716A1 (en) * 2017-07-25 2019-01-31 Visa International Service Association REAL TIME CROSSING MATCH DATA
US20240037521A1 (en) * 2017-07-25 2024-02-01 Visa International Service Association Real time cross-matching data
US12400247B2 (en) 2018-12-04 2025-08-26 Sap Se Representing sets of entities for matching problems
US11645686B2 (en) 2018-12-05 2023-05-09 Sap Se Graphical approach to multi-matching
US11341547B1 (en) * 2019-06-19 2022-05-24 Amazon Technologies, Inc. Real-time detection of duplicate data records
LU101595B1 (en) * 2020-01-07 2021-07-07 Creopay S A R L System and method for managing unpaid debts
US11809390B2 (en) 2021-07-29 2023-11-07 Intuit Inc. Context-dependent event cleaning and publication
US11616744B2 (en) 2021-07-29 2023-03-28 Intuit Inc. Context-dependent message extraction and transformation
US20230035551A1 (en) * 2021-07-29 2023-02-02 Intuit Inc. Multiple source audit log generation

Also Published As

Publication number Publication date
CA2540654A1 (en) 2005-04-28
CN1926568A (zh) 2007-03-07
WO2005038557A2 (en) 2005-04-28
JP2007507799A (ja) 2007-03-29
US20060112010A1 (en) 2006-05-25
WO2005038556A9 (en) 2005-08-11
WO2005040973A2 (en) 2005-05-06
US20070038564A1 (en) 2007-02-15
EP1668452A4 (en) 2007-02-28
CN1942890A (zh) 2007-04-04
CA2540702A1 (en) 2005-05-06
US20050075978A1 (en) 2005-04-07
JP2007507800A (ja) 2007-03-29
US20060116956A1 (en) 2006-06-01
US8498935B2 (en) 2013-07-30
EP1668453A2 (en) 2006-06-14
EP1668452A2 (en) 2006-06-14
WO2005040973A3 (en) 2006-09-14
WO2005038556A3 (en) 2006-08-10
US20050075979A1 (en) 2005-04-07
WO2005038556A2 (en) 2005-04-28
WO2005038557A3 (en) 2006-08-10

Similar Documents

Publication Publication Date Title
US20050075960A1 (en) System and method for automated incoming payment and invoice reconciliation
US10115098B2 (en) Invoiceless trading and settlement method and system
US7805365B1 (en) Automated statement presentation, adjustment and payment system and method therefor
US7437327B2 (en) Method and system for buyer centric dispute resolution in electronic payment system
US6151588A (en) Full service trade system
US20160267449A1 (en) Internet payment system and method
US20040181493A1 (en) Method and system for real-time transactional information processing
US20080208723A1 (en) System and method for settling trades in a digital merchant exchange
JP2005501326A (ja) 国際代金引換配送システム及び方法
WO2001013216A1 (en) Improved business systems
KR100407397B1 (ko) 무역서식 전자문서 및 전자문서교환방식에 의한무역자동화시스템
KR100836874B1 (ko) 국제무역서비스 제공시스템 및 그 방법
US20030004864A1 (en) Receivables management method
Ameredes Procurement model analysis
KR20020025546A (ko) 구매정보통합 시스템

Legal Events

Date Code Title Description
AS Assignment

Owner name: OLD WORLD INDUSTRIES, INC., ILLINOIS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KONG, XIANG;LEAVITT, STACY A.;MALLOY, STEPHEN LOUIS;AND OTHERS;REEL/FRAME:015467/0651;SIGNING DATES FROM 20040609 TO 20040610

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION