Payment and Invoice Systems Integration

Abstract

A method is described to display an end-to-end view of multiple post-payment stages of a single invoice. A status of the invoice is obtained from an accounting data repository. A visualization of an interface is generated showing the status for the invoice. The method also includes obtaining, from different computer payment systems, and based on the status indicating a payment on the invoice, monetary transaction records that match the invoice. The monetary transaction records received from the different payment systems in different formats are aggregated to update the status of the invoice after the status indicates the payment on the invoice. The visualization of the interface is updated to show the end-to-end view of the invoice. The end-to-end view includes at least a summary of the invoice and also a graphical depiction of a series of visually interconnected payment categories including a post-payment category indicating that the payment to a vendor is incomplete.

1 . A method for displaying, on a computer display, an end-to-end view of multiple post-payment stages of a single invoice, the method comprising:
 obtaining a status of the single invoice from an accounting data repository;   generating a visualization of an interface showing the status for the single invoice;   obtaining, from a plurality of different computer payment systems, and based on the status indicating a payment on the single invoice, a plurality of monetary transaction records that match the single invoice;   aggregating the plurality of monetary transaction records received from the plurality of different payment systems in a plurality of different formats to update the status of the single invoice after the status indicates the payment on the single invoice; and   updating the visualization of the interface to show the end-to-end view of the single invoice, wherein the end-to-end view comprises at least a summary of the single invoice and also a graphical depiction of a series of visually interconnected payment categories including a post-payment category indicating that the payment on the single invoice to a vendor is incomplete.   
     
     
         2 . The method of  claim 1 , further comprising:
 receiving, subsequent to generating the visualization, a view request to view the status of the single invoice;   obtaining the status of the single invoice from the invoice data repository; and   determining that the payment on the single invoice is performed based on the invoice data repository, wherein obtaining the plurality of monetary transaction records is in response to the view request and the determining that the payment on the single invoice is performed.   
     
     
         3 . The method of  claim 1 , further comprising:
 sending, in response to the status indicating the payment, a monetary transaction request to a payment system, the monetary transaction request identifying the single invoice.   
     
     
         4 . The method of  claim 1 , further comprising:
 obtaining the plurality of monetary transaction records from a financial institution of the vendor; and   storing the plurality of monetary transaction records in the payment repository.   
     
     
         5 . The method of  claim 1 , further comprising:
 matching the plurality of monetary transaction records to the single invoice based on a payment identifier of the payment.   
     
     
         6 . The method of  claim 1 ,
 wherein the plurality of monetary transaction records comprises a single monetary transaction record corresponding to the single invoice and at least one other invoice and   wherein aggregating the plurality of monetary transaction records comprises apportioning a portion of the single monetary transaction to each of the single invoice and the at least one other invoice.   
     
     
         7 . The method of  claim 1 , wherein the visualization comprises a list of a plurality of invoices, including the single invoice. 
     
     
         8 . A system comprising:
 a computer processor; and   an invoice accounting system configured to execute on the computer processor and comprising:
 an accounting data repository for storing a plurality of invoices; and 
   an invoice manager executing on the computer processor and configured to:
 obtaining a status of the single invoice from an accounting data repository; 
 generating a visualization of an interface showing the status for the single invoice; 
 obtaining, from a plurality of different computer payment systems, and based on the status indicating a payment on the single invoice, a plurality of monetary transaction records that match the single invoice; 
 aggregating the plurality of monetary transaction records received from the plurality of different payment systems in a plurality of different formats to update the status of the single invoice after the status indicates the payment on the invoice; and 
 updating the visualization of the interface to show the end-to-end view of the single invoice, wherein the end-to-end view comprises at least a summary of the single invoice and also a graphical depiction of a series of visually interconnected payment categories including a post-payment category indicating that the payment on the single invoice to a vendor is incomplete. 
   
     
     
         9 . The system of  claim 8 , further comprising:
 a customer system comprising:
 a customer data repository for storing a plurality of customer interactions with the single invoice, and 
 a customer manager executing on the computer processor, the customer manager configured for receiving a payment for the single invoice and processing the payment via the payment system, wherein the payment is recorded as a matched transaction record in the plurality of matched transaction records. 
   
     
     
         10 . The system of  claim 9 , wherein the payment system further comprises a payment manager, the payment manager configured to obtain the plurality of monetary transaction records from a financial institution. 
     
     
         11 . The system of  claim 8 , further comprising:
 a payment system comprising a payment data repository for storing the plurality of monetary transaction records.   
     
     
         12 . The system of  claim 11 , wherein the payment system further comprises a payment manager, the payment manager configured to match the plurality of monetary transaction records from a financial institution. 
     
     
         13 . The system of  claim 8 , wherein the invoice manager is further configured to:
 receive, subsequent to generating the visualization, a view request to view the status of the single invoice;   obtain the status of the single invoice from the invoice data repository; and   determine that that the payment on the single invoice is performed based on the invoice data repository,   wherein obtaining the plurality of monetary transaction records is in response to the view request and the determining that the payment on the single invoice is performed.   
     
     
         14 . The system of  claim 8 , wherein the invoice manager is further configured to:
 send, in response to the status indicating the payment, a monetary transaction request to a payment system, the monetary transaction request identifying the single invoice.   
     
     
         15 . The system of  claim 8 ,
 wherein the plurality of monetary transaction records comprises a single monetary transaction record corresponding to the single invoice and at least one other invoice, and   wherein aggregating the plurality of monetary transaction records comprises apportioning a portion of the single monetary transaction to each of the single invoice and the at least one other invoice.   
     
     
         16 . A non-transitory computer readable medium for displaying, on a computer display, an end-to-end view of multiple post-payment stages of a single invoice, the non-transitory computer readable medium comprising computer readable program code for:
 obtaining a status of the single invoice from an accounting data repository;   generating a visualization of a interface showing the status for the single invoice;   obtaining, from a plurality of different computer payment systems, and based on the status indicating a payment on the single invoice, a plurality of monetary transaction records that match the single invoice;   aggregating the plurality of monetary transaction records received from the plurality of different payment systems in a plurality of different formats to update the status of the single invoice after the status indicates the payment on the single invoice; and   updating the visualization of the interface to show the end-to-end view of the single invoice, wherein the end-to-end view comprises at least a summary of the single invoice and also a graphical depiction of a series of visually interconnected payment categories including a post-payment category indicating that the payment on the single invoice to a vendor is incomplete.   
     
     
         17 . The non-transitory computer readable medium of  claim 16 , wherein the computer readable program code is further for:
 receiving, subsequent to generating the visualization, a view request to view the status of the single invoice;   obtaining the status of the single invoice from the invoice data repository; and   determining that the payment on the single invoice is performed based on the invoice data repository,   wherein obtaining the plurality of monetary transaction records is in response to the view request and the determining that the payment on the single invoice is performed.   
     
     
         18 . The non-transitory computer readable medium of  claim 16 , wherein the computer readable program code is further for:
 sending, in response to the status indicating the payment, a monetary transaction request to a payment system, the monetary transaction request identifying the single invoice.   
     
     
         19 . The non-transitory computer readable medium of  claim 16 , wherein the computer readable program code is further for:
 obtaining the plurality of monetary transaction records from a financial institution of the vendor; and   storing the plurality of monetary transaction records in the payment repository.   
     
     
         20 . The non-transitory computer readable medium of  claim 16 , wherein the plurality of monetary transaction records comprises a single monetary transaction record corresponding to the single invoice and at least one other invoice and
 wherein aggregating the plurality of monetary transaction records comprises apportioning a portion of the single monetary transaction to each of the single invoice and the at least one other invoice.