US20080172314A1 - Financial institution-based transaction processing system and approach - Google Patents

Financial institution-based transaction processing system and approach Download PDF

Info

Publication number
US20080172314A1
US20080172314A1 US11/151,747 US15174705A US2008172314A1 US 20080172314 A1 US20080172314 A1 US 20080172314A1 US 15174705 A US15174705 A US 15174705A US 2008172314 A1 US2008172314 A1 US 2008172314A1
Authority
US
United States
Prior art keywords
transaction
seller
buyer
sponsoring
financial institution
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
US11/151,747
Inventor
Dean W. Hahn-Carlson
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.)
Syncada LLC
Original Assignee
US Bank NA
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
Priority claimed from US08/748,243 external-priority patent/US5910896A/en
Priority claimed from US10/437,405 external-priority patent/US20040010463A1/en
Application filed by US Bank NA filed Critical US Bank NA
Priority to US11/151,747 priority Critical patent/US20080172314A1/en
Assigned to U.S. BANCORP LICENSING, INC. reassignment U.S. BANCORP LICENSING, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HAHN-CARLSON, DEAN W.
Assigned to U.S. BANK NATIONAL ASSOCIATION reassignment U.S. BANK NATIONAL ASSOCIATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: U.S. BANCORP LICENSING, INC.
Publication of US20080172314A1 publication Critical patent/US20080172314A1/en
Priority to US12/492,986 priority patent/US8589268B2/en
Priority to US12/492,965 priority patent/US8595099B2/en
Assigned to SYNCADA LLC reassignment SYNCADA LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: U.S. BANK NATIONAL ASSOCIATION
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Commerce
    • G06Q30/04Billing or invoicing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03Credit; Loans; Processing thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12Accounting

Definitions

  • the present invention is directed to communications and data processing and, more specifically, to communications and data processing involving transaction-related financial processing.
  • Financial institutions employ transaction processing parameters that are unique to each institution. In addition, these transaction processing parameters typically need to be kept separate (and confidential), relative to other financial institutions. Often, transaction processing is dependent upon these parameters, which are specific to a particular financial institution involved in financing the transaction. In this regard, transaction processing for portions of a transaction that are related to a financial institution has generally been limited to implementation by a processing engine or system employed by the financial institution participating in the transaction.
  • the present invention is directed to overcoming the above-mentioned challenges and others related to the types of devices and applications discussed above and in other applications.
  • the present invention is exemplified in a number of implementations and applications, some of which are summarized below.
  • financial transactions involving financial institutions are managed using an approach generally involving the use of rules for processing payment-related aspects of the financial transactions.
  • a transaction management system is configured for using sets of rules associated with financial institutions for processing transactions.
  • transaction information When transaction information is received, it is associated with a particular sponsoring financial institution. Rules for the sponsoring institution are used to process the transaction. In some instances, the rules are further selected and implemented as a function of one or more of the sponsored transaction parties (e.g., a buyer or seller).
  • an automated transaction processing system is adapted for processing transactions involving a plurality of financial institutions.
  • the system includes a central processing node adapted to audit (e.g., validate or otherwise approve) transactions between contracting parties according to different sets of transaction rules.
  • Each of the respective sets of transaction rules are defined as a function of a unique one of the plurality of financial institutions and a relationship between the unique financial institution and at least one of the contracting parties.
  • an automated transaction processing system audits transactions between contracting parties on behalf of a plurality of financial institutions.
  • the automated transaction processing system includes a central processing node adapted, for different transactions involving various financial institutions, to associate each transaction with a unique one of the plurality of financial institutions and to audit each associated transaction according to a set of transaction rules.
  • These transaction rules are defined as a function of the unique financial institution and a business relationship between the unique financial institution and at least one of the contracting parties.
  • the audit involves using information in the rules, upon which payment can be authorized, and comparing or otherwise processing information for a particular transaction (e.g., receipt of goods, issuance of an invoice) to approve payment for the transaction (or deny payment where transaction information fails to satisfy payment-type conditions).
  • the central processing node facilitates payment for each transaction as a function of the audit.
  • FIG. 1 shows a transaction processing arrangement, according to an example embodiment of the present invention
  • FIG. 2 shows an arrangement and approach for transaction management, according to another example embodiment of the present invention.
  • FIG. 3 shows a flow diagram for transaction processing, according to another example embodiment of the present invention.
  • the present invention is believed to be applicable to a variety of different types of communications and financial process management approaches, and has been found to be particularly useful for applications involving the operational implementation and application of financial institution rules and processes with transactions, payments, tracking and related aspects thereof. While the present invention is not necessarily limited to such approaches, various aspects of the invention may be appreciated through a discussion of various examples using these and other contexts.
  • a financial rules-based transaction approach is implemented with multiple sponsoring financial institutions for automatically processing financial transactions.
  • the sponsoring financial institutions sponsor transaction parties (e.g., buyers and sellers); financial aspects of transactions between two or more of the sponsored transaction parties are carried out as a function of business rules for the financial institution sponsoring each party.
  • a central transaction management system uses business rules (e.g., included in profile information) associated with financial institutions to process financial transactions between parties sponsored by the financial institutions.
  • the central transaction management system receives transaction information, the information is parsed for identifying characteristics that can be associated with sponsoring financial institutions. When these identifying characteristics match a particular financial institution, the central transaction management system uses business rules for the financial institution to process the financial transaction.
  • financial aspects of the transaction that are specific to each party are processed according to the each party's corresponding sponsoring financial institution. Funds relating to the financial transaction are thus transferred according to the business rules associated with sponsoring financial institutions for each party and to the particular characteristics of the financial transaction.
  • the central transaction management system audits data for transactions between the different parties as a function of business rules for one or more of the transaction parties. For example, where a particular party specifies conditions, in its business rules, upon which payment can be authorized, the central transaction management system implements those conditions in connection with the audit and determines therefrom a condition of payment for the transaction (e.g., whether some or all of a particular invoice can be paid). As another example, different parties to a contract may specify rules upon which transaction data is to be audited to indicate that the transaction is valid and/or ripe for payment.
  • This auditing may include, for example, setting a price for a particular transaction, such as setting the price for a shipment involving bill of lading (BOL) rating or setting the price for a transaction based on characteristics of the transaction such as quantity of goods and/or receipt of the goods.
  • the auditing involves comparing terms in transaction data from an electronic invoice to previously agreed upon contract terms; where the invoice matches the terms, or is within a tolerance where specified, the auditing results in an approval (i.e., validation of the transaction) for payment of the invoice.
  • a multitude of such auditing approaches can selectively be implemented, based on various terms set by different transaction parties, by sponsoring financial institutions or other related entities.
  • the central transaction management system further uses business rules associated with individual parties to a transaction in processing financial transactions involving the individual parties. For instance, when the central transaction management system receives transaction information, the information is parsed (as discussed above) to identify sponsoring financial institutions as well as the parties to the transaction. The transaction is then process according to the business rules of the sponsoring financial institutions as well as the business rules of the parties to the transaction. These party-specific business rules may be stored, for example, in a user profile that is accessible by the central transaction management system. The user profiles may include identifiers used to identify buyer or seller transaction parties and/or sponsoring financial institutions.
  • the sponsoring financial institution for a particular party is identified as a function of the identity of the party and corresponding business rules for the party. For example, when a party sets business rules to identify a particular sponsoring financial institution, these business rules are implemented in selecting the sponsoring financial institution. Correspondingly, the business rules for the financial institution identified by the party's business rules are used to process the financial transaction.
  • two or more financial institutions can be specified by a particular party, including sponsoring and/or non-sponsoring financial institutions.
  • Business rules for the particular party may include financial institution selection criteria that is implemented as a function of the particular transaction. For instance, selection criteria may be configured to indicate that payment for transactions under a certain value be processed (financed) using a first financial institution, while payment for transactions at or over the certain value be processed using a second financial institution.
  • This approach may be implemented, for example, where large value transactions that may involve a longer payment period are desirably financed through a financial institution offering terms that are practicable for maintaining a longer payment term (i.e., lower rates). Small value transactions typically involving a shorter (or no) payment term may preferably be serviced using a financial institution offering desirable services or low service fees, but higher rates.
  • Sponsoring financial institutions may implement criteria similar to that discussed in the paragraph above for selecting a particular institution via which to process transactions, with selected criteria being implemented for making such selections. This approach may be useful, for example, where parties to the transaction agree to use a financial institution selected by the sponsoring financial institution that sponsors the party into the automated transaction process.
  • the financial institution selected for providing payment for a particular transaction is selectively different than the sponsoring financial institution.
  • Such a financial institution may be selected by the sponsoring financial institution using, for example, a geographical location of a seller to which payment is to be made.
  • the central transaction management system works to keep separate the transaction rules for each financial institution (and transaction parties, where appropriate). Access to the transaction rules is restricted to the institution (or party) to which the rules belong. This restricted access approach may be implemented using, for example, encryption, passwords, tracking and other security-type measures typically implemented for data access and protection.
  • a data access controller facilitates the restriction of access to transaction information by providing access to each financial institution for data relating to their clients.
  • the data access controller selectively facilitates access via an overview type of data presentation that shows a financial overview for each customer to whom the financial institution issues credit. For example, for buyer customers, the data access controller selectively implements an overview showing each buyer's net position between payments due from the buyer and payments due to sellers (suppliers) through the transaction processing system.
  • the data access controller discussed above is further configured and arranged, for each sponsoring financial institution, to perform customer service functions related to transaction processing for the financial institution's customers within the transaction processing system.
  • customer service functions are defined in the sponsoring financial institution's business rules in association with each customer.
  • the data access controller implements the business rules in performing the customer service functions.
  • Business rules used by the central transaction management system may be stored using one or more of a variety of approaches.
  • a database accessible by the central transaction management system and having labels or other identifying characteristics that associate the business rules with a particular financial institution can be used.
  • This database can be physically local or remote to the central transaction management system, as long as the central transaction management system can access the database and control access to the database by other entities.
  • the central transaction management system is further configured to interface with financial institutions for a particular transaction party, in addition to a sponsoring financial institution for the transaction party. For instance, where a transaction party has primary banking functions with a non-sponsoring financial institution, the sponsoring financial institution, via the central transaction management system, facilitates the transaction by exchanging funds via the non-sponsoring financial institution.
  • the sponsoring financial institution may further implement processing type fees via the central transaction management system, charged for facilitating the financial transaction.
  • the central transaction management system interfaces directly with financial institutions that, from a hierarchical perspective, pass-through information received from one or more parties to the transaction.
  • the central transaction management system uses transaction rules based on the transaction information received from a financial institution. Effectively, the financial institutions use the central transaction management system to execute transaction-processing functions that are carried out using transaction-based rules specific to the particular financial institution providing the transaction information.
  • the central transaction management system is adapted to interface directly with parties to a transaction and to use transaction rules based on information received from one or more of the parties (i.e., without a sponsoring financial institution).
  • parties i.e., without a sponsoring financial institution.
  • a buyer or seller can interface with the central transaction management system using rules, implemented with the system, which are based on profile information for the particular buyer or seller.
  • rules implemented with the system, which are based on profile information for the particular buyer or seller.
  • These parties may contract with a system administration entity, effectively acting as a sponsoring financial institution in some regards, relative to the above discussion, to facilitate transactions in this manner.
  • a central transaction management system uses transaction information for buyers and sellers of products and/or services to automatically derive pricing and/or payment options for individual transactions.
  • These products and services may include, for example, tangible goods, shipment services, consulting services and financial services (e.g., where the seller may be a financial institution selling a financing package for a transaction between a buyer and another seller).
  • the transaction information may include, for example, the identities of the buyer and seller, the products and/or services being purchased, the date of the purchase and the specific contract under the terms of which the transaction is being executed.
  • specific contracts under the terms of which a transaction is being prosecuted may include prices agreed upon between a buyer and seller for a particular product and/or service.
  • Transaction-related contracts facilitated by the central transaction management system may also (or in the alternative) include rules agreed upon for setting certain financial and/or price terms between a buyer and seller.
  • terms associated with a particular transaction are automatically set by the central transaction management system to correspond to transaction information assigned to a particular buyer. The terms may be set, for example, using predetermined terms agreed to by the buyer and seller involved in the transaction.
  • pricing arrangements such as quantity discounts, group discounts and conditional price variances (e.g., an acceptable percentage of variance in cost associated with for fluctuating shipping costs, product prices, financing costs and others) are further automatically implemented in response to the transaction information and the approved contract details in the central transaction management system.
  • financing terms such as processing fees for facilitating a transaction, interest-related fees, credit-extension fees and others are automatically set as a function of such a transaction-related contract.
  • a rating engine is optionally implemented to assign an interest rate to an applicable transaction, for extending credit on behalf of a contracting party to the transaction.
  • a transaction processing arrangement 100 includes a central transaction processor 110 programmed to automatically process transaction information according to business rules corresponding to particular financial institutions, according to another example embodiment of the present invention.
  • the central transaction processor 110 When transaction information is received at the central transaction processor 110 , the information is associated with sponsoring financial institutions for each party to the transaction and processed according to business rules for the sponsoring financial institutions.
  • the central transaction processor 110 may be implemented, for example, in connection with the above-discussed approaches including those involving the discussion of a central transaction management system and/or with a central transaction node in a network node-based arrangement.
  • Business rules are supplied by a multitude of financial institutions employing the central transaction node 110 , represented here by financial institution nodes 120 and 128 . In some instances, parties involved in transactions facilitated by the central transaction node also supply business rules.
  • the central transaction processor 110 is in communication with a database 112 where transaction-related information including the above-discussed financial institution rules is stored.
  • the database 112 is optionally coupled to (or part of) the central transaction processor 110 and further may include a plurality of data storage arrangements at different locations.
  • the central transaction node 110 maintains separate (and secure) storage for these business rules by restricting access to the rules by the financial institutions (or others such as transaction parties).
  • the central transaction node 110 is further adapted to communicate with a variety of different parties to a transaction, represented by transaction parties 122 , 124 and 126 . These transaction parties and the financial institutions represented by user nodes 120 , 122 , 124 , 126 and 128 are communicatively coupled with the central transaction processor 110 .
  • the user nodes 120 - 128 may, for example, include one or more of a buyer, seller, distributor, shipper, carrier, government agency, financial institution or other type of individual, group or agency that would be involved in a transaction, with parties shown in the figure by way of example.
  • the nodes 120 - 128 interact with the central transaction processor 110 for providing transaction-related information, such as financial processing rules, accounting rules, orders, invoices, shipping documents, payment authorization data, payment execution data, customs documents, security documents and others.
  • this transaction-related information may include information for relating the application of rules to transaction data, such as payment processes, credit extension and finance charges.
  • financial institution nodes provide rules that are stored in the database 112 , with other party nodes simply interacting with the central transaction node 110 (e.g., without providing any information for storage in the database 112 ). Transactions are thus processed as a function of stored rules for a particular financial institution (or institutions) with which the transactions are associated.
  • the database 112 is also implemented for maintaining transaction party-type information, such as user preferences (e.g., reporting, billing, credit extension) and financial institution preferences (e.g., which institution to use).
  • the transaction parties 122 , 124 and 126 may be implemented via sponsoring financial institutions, with nodes 122 , 124 and 126 representing this combination of transaction parties with a particular sponsoring financial institution. This combinatorial representation may also maintain direct interaction between transaction parties and the central transaction node 110 for facilitating party-specific communications, such as for setting business rules or profile information for individual parties.
  • one or more of the nodes 120 - 128 are used as interfaces to the central transaction processor 110 , with users at the nodes being able to provide transaction-related information such as classification rules.
  • the central transaction processor 110 automatically accesses information from the user nodes for a variety of purposes, such as retrieving classification rules (e.g., accounting codes and/or business rules) or updating related accounting fields. This interaction between the nodes and the central transaction processor 110 is controlled using, for example, access authorization such as those involving password-protected authorization and others.
  • the central transaction node 110 parses the data and automatically associates the transaction data with a particular financial institution sponsoring the transaction to which the data applies. This automatic association is implemented using business rules in the database 112 and/or as a function of the node sending the transaction data. In some instances, profile information for various sponsoring financial institutions (and/or transaction parties) is stored in the database 112 and used in connection with identifiers in received transaction information to automatically associate the transaction information with sponsoring financial institutions.
  • the central transaction node 110 processes the associated data according to applicable business rules that may be tailored, for example, to a particular type of transaction or to particular transaction characteristics.
  • the central transaction processor 110 selectively assigns an interest rate to the extension of credit, either directly wherein an administrator of the central transaction processor extends credit, or in connection with an interest rate offered by a financial institution extending the credit.
  • the central transaction processor 110 implements a rating engine to assign an interest rate to an applicable transaction, for extending credit on behalf of a contracting party to the transaction.
  • the rating engine uses information about the contracting party in order to establish such an interest rate.
  • the central transaction processor 110 is further adapted to grant and control information exchange with the database 112 as a function of inputs received from the nodes 120 - 128 , such as authorization inputs and transaction-specific inputs.
  • authorization information may include, for example, access-type information (e.g., a password or user ID) or simply document information that the central transaction processor 110 recognizes.
  • the central transaction processor 110 maintains data for business rules and processed transactions over time for a variety of purposes, such as for generating reports, tracking compliance and for taking appropriate action where errors or non-compliance occurs. For example, when a particular transaction is processed or when business rules are changed, the central processor monitors associated information and stores and/or processes the monitored information for these purposes.
  • a typical such profile may include one or more of the following data: general ledger charts of accounts, identification of computer systems submitting contract or transaction data, customer lists, vendor lists, financial institution lists, contract and price approval policies, transactional approval policies, business rules, operational roles (e.g., defining what functions a user associated with that role can perform), organizational hierarchy (e.g., defining how much of a company's data a user associated with a particular organizational node can access), and individual users.
  • Financial institution profiles may also include information further defining the business relationship with selected customers or other financial institutions and financial processing organizations from the financial institution's perspective.
  • FIG. 2 shows an arrangement and approach for transaction management in an automated transaction network, according to another example embodiment of the present invention.
  • a transaction processing system 210 interfaces with a plurality of financial institutions for facilitating transactions, using data stored in a database 220 for implementing rules for the transactions. These rules are used to process financial aspects of the transactions, relative to information received via sponsoring financial institutions.
  • Two sponsoring financial institutions are shown, with multiple such institutions being contemplated but not shown for brevity.
  • Each sponsoring financial institution 230 and 240 works with multiple users, represented as users 1 -N for institution 230 , and users A-i for institution 240 .
  • Communications between the sponsoring financial institutions and the transaction processing system 210 may be implemented directly from the sponsoring financial institutions.
  • the shown communication links may represent a direct communication from a sponsored user, the user including in the communication sufficient information (and security type information, where appropriate) to designate the appropriate sponsoring financial institution.
  • the transaction processing system 210 also interfaces with a variety of funds processing originators.
  • automatic clearing house (ACH) originators 250 and 270 and SWIFT (a European-based, straight through processing (STP) transaction system) originators 260 and 280 are shown.
  • These funds processing originators are typically implemented as financial institutions having appropriate funds processing capabilities for implementing, for example, ACH or SWIFT-type functions.
  • the transaction processing system 210 interfaces with financial transaction processing entities for obtaining authorization to proceed with a transaction and to coordinate fund transfer using the respective originators (i.e., as conventional).
  • the transaction processing system's interface with ACH and other providers is selectively specified by business rules used in processing a particular transaction for payment and facilitation functions.
  • the business rules in database 220 typically include user-specified rules that are provided by the financial institutions using the transaction processing system 210 for processing financial transactions.
  • user profile information for each sponsoring financial institution can be stored in the database 220 for use by the transaction processing system 210 .
  • This profile information may include, for example, business rules specifying one or more various conditions or approaches related to financial transaction processing, as discussed herein.
  • the database 220 is accessed to retrieve profile information (and corresponding business rules) for processing the transaction data.
  • the business rules are used to determine a variety of transaction-related characteristics, such as fees to be charged for different parties to the transaction, including buyer, seller and their respective financial institutions. Additional rules-based processing examples are discussed further below.
  • the storage of information in the database 220 may involve the use of a single database, or may involve multiple databases, either in a single or at multiple locations, communicatively coupled with the transaction management system 210 .
  • all transaction data for all buyers and sellers sponsored by all financial institutions is stored in one centralized database.
  • the transaction management system 210 manages the centralized database such that information in the database that has a common relationship with other information in the database can be cross-referenced and updated. For instance, where information for a buyer and seller for a single transaction is stored in the centralized database, updates made to the buyer's information can be appropriately made to similar seller's information. This approach can be implemented to ensure that any buyer and any seller can do business with each other and see up-to-date status and documents without latencies typically involved attempting to replicate and synchronize data across multiple databases.
  • Business rules stored in the database 220 are optionally tailored to particular users that are being sponsored by the financial institution.
  • the business rules pertaining to a particular sponsoring financial institution, as well as the user being sponsored for a particular transaction are retrieved from the database 220 and used accordingly.
  • sponsored users also store profile information in the database 220 , such as preferred banking institution (i.e., with the sponsoring financial institution simply sponsoring the transaction for a fee and not funding the transaction).
  • the transaction processing system 210 includes two or more system implementations, represented by system implementations 1 and 2-N. These system implementations may involve virtually separate implementations at a single location to facilitate data security and continuity for particular sponsoring financial institutions. For instance, each system implementation may be implemented for a particular financial institution, with communication between each system implementation and other system implementations being facilitated within the transaction processing system 210 . In this regard, each user (sponsoring financial institution) may tailor it's specific system implementation to its own needs.
  • the system implementations with transaction processing system 210 may also be implemented at physically separate locations, with virtual ties to the transaction processing system 210 .
  • the implementation of various aspects of the transaction processing system may be appropriate for applications in different countries or for point-of-use type applications (e.g., to reduce long distance data communications).
  • This physically separate approach may also be implemented, for example, to address laws associated with transactions, including taxation and other processing rules.
  • various business rules stored at the database 220 are implemented by the transaction processing system 210 for a variety of transaction characteristics.
  • One such characteristic involves the determination of fees to be charged to users (buyers and sellers), to sponsoring financial institutions and, where applicable, to other financial institutions involved in the transaction.
  • the database 220 stores business rules characterizing these fees, and the transaction processing system 210 uses these characterizing business rules to process financial transactions.
  • the database 220 may store party-identifying information for use by the fee-based rules in characterizing the fees to be assessed for a particular transaction.
  • the business rules are implemented to arrive at a collaborative transaction term, such as a price or other term automatically implemented as an agreed-upon term by using previously agreed-upon business rules for generating such a term.
  • Fee-based rules implemented in connection with these approaches may involve, for example, information for determining the amount of fees to assess for one or more of the following:
  • an association processor 212 identifies a particular sponsoring bank for each buyer and seller as a function of stored identifiers.
  • the association identifies respective business rules, set in accordance with the particular sponsoring bank and the particular buyer or seller for which the rules are set, for respectively processing transactions on behalf of the buyer and on behalf of the seller for a particular transaction.
  • association processor 212 functions can be implemented separately from or in connection with (e.g., as a software-implemented function) the transaction processing system 210 .
  • the association processor facilitates the identification of business rules using a geographic location of a party to the transaction, for example where transaction payment characteristics are affected by such a location (e.g., where tariffs and/or taxes are involved).
  • the association processor identifies business rules for a sponsoring financial institution using historical information for a particular transaction party. For example, where a financial institution implements different sets of business rules based on payment characteristics, credit rating, business volume or other historical-type information pertaining to a transaction party, that information is used to select a set of business rules to use in facilitating a transaction involving the transaction party.
  • a collaborative contracts processor uses the identified business rules and a business agreement between the buyer and seller to determine the amount of fees assessed in accordance with one or more of the above fees discussed in connection with the fee-based rules. Other approaches involving a collaborative contracts approach are discussed further below.
  • the transaction processing system 210 uses information in profiles for facilitating the transfer of funds from, or the extension of credit on behalf of, the entity to which fees are assessed. For instance, where a particular fee is to be assessed against sponsoring financial institution 230 and/or one of the users 1 -N, funds from that institution are provided directly (e.g., funds transfer) or indirectly (e.g., extension of credit), from the sponsoring financial institution 230 or from another financial institution specified by the user, where applicable.
  • the user (e.g., buyer, seller and financial institution) profiles discussed herein and implemented with collaborative-type approaches may include a variety of information for use in transaction management and otherwise.
  • typical profiles include one or more of the following data: a general ledger chart of accounts, identification of a computer system authorized for submitting contract or transaction data, customer and/or vendor lists, policies for contract, price or transactional approval and business rules.
  • operational roles for such users are defined and include, e.g., access authorization for the users as well as individual access tracking.
  • Seller customer list profiles may also include information further defining the business relationship with the customer from the Seller's perspective, for example, such as a retail buyer relationship or a wholesale buyer relationship.
  • List profiles for buyers who act as vendors may also include information further defining the business relationship with the vendor from the Buyer's perspective.
  • profile information such as business rules, operational roles, authorization levels and/or other attributes are specific to particular levels and/or individuals within a particular entity.
  • This profile information is stored for access by the transaction processing system 210 and used for implementing transactions. For example, when a particular financial institution or sponsored user includes different subsidiaries, divisions or locations, profile information can be tailored for the particular source. Certain profile information can also be implemented to supersede other profile information, for example, when a particular subsidiary is assigned different specific pricing terms, relevant to another subsidiary of a common entity.
  • the transaction processing system 210 stores information for transaction parties including one or more of financial institutions and sponsored users (e.g., buyers and sellers), and communicates therewith using an identification approach for users at the buyer and/or seller level.
  • the transaction processing system 210 controls access to the stored information as a function of user identification (ID), with access parameters controlled for processes such as contract modification, price modification, display configuration, access to the stored information for that particular user and others.
  • ID user identification
  • the seller offerings are automatically configured for usage by the individual users.
  • seller offerings may involve real goods and/or services, as well as or in the alternative to financial offerings, such as the extension of credit and/or financial processing services.
  • the automatic configuration may, for example, include price, delivery and payment options.
  • the transaction processing system 210 is adapted for accepting requests from buyers and communicating the requests to the seller.
  • the transaction processing system 210 is further adapted for accepting acknowledgment of receipt by the buyer either manually (e.g., an individual buyer logs into the system with a user ID and confirms receipt) or electronically (e.g., buyer's inventory receiving systems automatically generate and transmit a detailed notice of receipt or acceptance). Once receipt or acceptance is acknowledged, the system communicates that acknowledgment to the seller. In one implementation, the system is further adapted for automatically paying the seller in response to the receipt/acceptance acknowledgment. In another implementation, the system is further adapted to invoice the buyer for the offerings. Further, “payment” in this context may involve the drawdown of a credit line, or extension of credit in manners as appropriate for the particular transaction.
  • the transaction processing system 210 implements a settlement processor 214 in connection with facilitating payment for a particular transaction between a buyer and a seller.
  • the settlement processor 212 performs inter-bank settlement by calculating the amount of funds to be collected from a sponsoring bank for the buyer and remitted to a sponsoring bank for the seller.
  • the settlement is used to fund a payment that the seller's sponsoring bank will make to the seller for all transactions that achieve payable status, e.g., within a payment period defined as a function of the business rules.
  • the settlement processor 214 is implemented to facilitate payment/settlement in a variety of manners, depending upon the application and appropriate contract terms and other information relative to the truncation parties and/or sponsoring financial institutions involved in a particular transaction. In this regard, some applications involve one or more of the following electronic payment approaches as facilitated by the settlement processor 214 for a transaction involving a buyer and a seller, with sponsoring banks for each. In one approach, the settlement processor 214 facilitates the submission of an electronic payment demand at a defined period to the buyer's sponsoring bank for all net monies due to at least one of the transaction processing system and the seller's sponsoring bank, when the buyer's sponsoring bank is in a net funds due (to the transaction processing system) position.
  • the settlement processor 214 facilitates the submission of an electronic payment demand at a defined period to the seller's sponsoring bank for all net monies due to at least one of the transaction processing system and the buyer's sponsoring bank, when the seller's sponsoring bank is in a net funds due position.
  • the settlement processor 214 facilitates the submission of an electronic payment notice at a defined period to the buyer's sponsoring bank for all net monies due to the buyer's sponsoring bank, after subtraction of funds due to at least one of the transaction processing system and the seller's sponsoring bank, when the buyer's sponsoring bank is in a net funds due to processor position.
  • the settlement processor 214 facilitates the submission of an electronic payment demand at a defined payment period to the seller's sponsoring bank for all net monies due to the seller's sponsoring bank after subtraction of funds due to at least one of the transaction processing system and the buyer's sponsoring bank, when the seller's sponsoring bank is in a net funds due to processor position.
  • the net funds due to processor position selectively characterizes funds due, and in certain applications, characterizes funds due to an administrator of the transaction processing system 210 for transaction payment (e.g., from a buyer to a seller) and/or for fees associated with the processing of the transaction payment.
  • the transaction management system discussed in the preceding paragraph is further adapted for accepting a receipt of purchase acknowledgment including receipt characteristics.
  • characteristics such as total acceptance of goods, partial acceptance of goods and rejection of goods at the invoice or receipt line item level can be included in the acknowledgment. These characteristics are tied to transaction levels involving users sponsored by the financial institutions (e.g., 230 or 240 , shown by way of example). Where compliance before payment for a transaction is executed is to be ensured, this information is required to be verified a priori. An invoice or invoices for a particular transaction are updated with this and other transaction-fulfillment-related information. Using this approach, problems with received purchases, such as damaged goods, improper goods and improper financial terms are readily addressed. The various invoicing and payment-related characteristics are correspondingly modified (e.g., payment is only made for accepted portions of goods, or credit for the cost of returning goods is granted, or payment is made using only accepted terms such as those relating to an accepted credit-related interest rate).
  • financial institutions approve financial contracts using a collaborative contract manager and submit order and invoice quantities for executing the contracts to the transaction processing system 210 (e.g., implementing a collaborative contract manager).
  • the transaction processing system 210 uses the terms from the collaborative contracts manager to establish financial processing terms (e.g., credit rate or other cost) between a user of financial services and the corresponding financial service provider.
  • financial service providers use the collaborative contracts manager as the central repository called by various provider systems.
  • the financial service user implements the collaborative contracts manager as the central repository called by various procurement systems.
  • the transaction processing system 210 is configured for settling inter-bank issues relating to fees and/or other transaction characteristics.
  • the transaction processing system 210 calculates the amount of funds to be collected from the buyer's sponsoring bank and remitted to the seller's sponsoring bank. These funds are used to fund the payment that the seller's sponsoring bank will make to the seller for all transactions that achieve payable status within a particular payment period (e.g., a network day) for the transaction processing system's.
  • the transaction processing system 210 further acts to facilitate the collection of these funds in one or more of a variety of manners. For instance, the transaction processing system 210 may simply make the amount of funds known to parties to the transaction using conventional communications methods. In other instances, the transaction processing system 210 actively facilitates collection of these funds.
  • an electronic payment demand is submitted on an interval (e.g., at least daily) to the buyer's sponsoring bank for all net monies due either to the transaction processing system or to the seller's sponsoring bank when the buyer's sponsoring bank has net funds due.
  • An electronic payment demand is also submitted on an interval to the seller's sponsoring bank for all net monies due either to the transaction processing system or to the buyer's sponsoring bank when the seller's sponsoring bank has net finds due.
  • an electronic payment notice is submitted on an interval (e.g., at least daily) to the buyer's sponsoring bank for all net monies due to the buyer's sponsoring bank.
  • the net monies due are contemplated after subtraction of funds due to either the transaction processing system or the seller's sponsoring bank when the buyer's sponsoring bank has net funds due.
  • An electronic payment notice is also submitted to the seller's sponsoring bank for all net monies due to the seller's sponsoring bank.
  • these net monies due are contemplated after subtraction of funds due to either the transaction processing system or the buyer's sponsoring bank when the seller's sponsoring bank has net funds due.
  • a fee engine is selectively implemented to facilitate the assessment of transaction processing fees.
  • the fee engine is implemented with a transaction processor (e.g., with transaction processing system 210 ), as a software-implemented engine.
  • fees such as those assessed in accordance with a business relationship between a financial institution and a buyer or seller party contracting therewith, or with a business relationship between a financial institution and an administrative transaction processor auditor, can be assessed using the fee engine. That is, the fee engine applies a fee appropriate for each transaction, and either directly or indirectly facilitates payment of that fee.
  • Access to information at the database 220 is controlled in one or more of a variety of manners, with information made available to users selectively and in a variety of formats, depending upon the implementation.
  • Various examples using this general approach are discussed below. These examples are selectively implemented with a data access controller 216 and may involve approaches discussed above in connection with similar data access controller functions.
  • each buyer-sponsoring financial institution and each seller-sponsoring institution has access to the transactions naming their sponsored buyer or seller organization.
  • each financial institution is granted access to perform customer service functions related to transaction processing for their customers within the transaction processing system.
  • customer service functions may, for example, include the provision of accounting-related data in an appropriate format and at a selected interval, or include providing a notification to the customer upon certain predefined events related to transaction processing and/or financial status of transactions or accounts.
  • each financial institution can maintain an overview of their net position with each of their customers to whom they are issuing credit. The financial institution is presented a view into the transaction processing system that shows their customers' net position between payments due from customer and payments due to suppliers (through the transaction processing system).
  • each buyer-sponsoring financial institution has the capability, as enabled by user profiles stored at the database 220 , to specify a variety of bank-specific operating characteristics.
  • each buyer-sponsoring financial institution may specify the financial institution that is to perform foreign currency translation on its sponsored buyer's behalf. This approach may be implemented, for example, where the seller desires to be paid in currency local to the seller and the buyer desires to be billed in currency local to the buyer.
  • Each buyer-sponsoring financial institution may also specify a currency translation markup amount to add to translation services being provided to its buyers.
  • the buyer-sponsoring financial institution may also specify the financial institution to use for remittance collection from its buyers.
  • Seller-sponsoring institutions may also specify the financial institution(s) to use for delivering payments to the seller. For instance, one institution may be used for ACH origination for sellers holding US-domiciled bank accounts and another institution (e.g., a SWIFT institution) for European-based sellers, and another for Latin American-based sellers.
  • a SWIFT institution e.g., a SWIFT institution
  • Financial institutions issuing credit to either the buyer or the seller can also specify where credit-related information is retrieved from for use in the transaction. For example, the location from which credit drawdown advice (e.g., relative to available credit in an appropriate credit account) is to be delivered can be specified.
  • credit-issuing financial institutions can specify whether the drawdown advice is to include transaction details or simply be the aggregate of the transaction details for the reporting period.
  • the transaction processing system 210 can be specified to be used as the detailed subledger to support the credit usage. In this sense, the transaction processing system 210 functions much like conventional credit-issuing institutions (including credit card issuing institutions), with the credit issuer being provided summary or detail information.
  • a variety of security-related functions are implemented with the transaction management system 210 , depending upon the application and the desired level of security.
  • data flowing to the transaction processing system 210 from sponsoring financial institutions ( 230 , 240 ) are encrypted using standard encryption technologies.
  • data flowing from the transaction processing system 210 to sponsoring financial institutions ( 230 , 240 ) can also be encrypted using standard encryption technologies.
  • Communications between any distributed computing devices and the transaction processing system 210 can also be encrypted using standard encryption technologies. For instance, where the various system implementations 1, 2 and N are employed at physically different locations, communication between these system implementations and the transaction management system 210 is encrypted.
  • profiles stored in the database 220 may include security type information, such as password and/or encryption information that users accessing the transaction management system 210 may employ.
  • the transaction processing system 210 addresses synchronization issues between various financial institutions and organizations, such as those discussed above, by implementing pricing and/or other transaction rules that have previously been agreed upon such that disputes over transaction price are typically eliminated.
  • These rules may include, for example, criterion defining pricing data that can be automatically approved (e.g., transaction fees within a selected variance), and also control pricing information made available to different users.
  • the pricing rules may also include, for example, prices associated with particular transaction characteristics, with different prices being assigned for particular transactions (e.g., such as with a volume or amount discount).
  • a credit-processing approach is implemented with a transaction management arrangement, such as that shown in FIG. 2 and discussed above.
  • the transaction processing system 210 can facilitate the extension of credit on behalf of one or more sponsoring financial institutions, or another financial institution, in connection with a particular user participant in a transaction.
  • a buyer-sponsoring bank sponsors a buyer into the transaction processing system 210 and network with an active connection to a line of credit for usage within the transaction processing system and network.
  • the buyer creates trading partner relationships with sellers who are sponsored into the transaction processing system 210 , which facilitates the relationships and related transaction processing.
  • the buyer sends an electronic copy of an order for the purchase to the transaction processing system 210 and network.
  • the seller fulfills an order and issues an invoice electronically to the transaction processing system 210 .
  • events or conditions are provided by an appropriate party to a transaction (e.g., buyer, seller or third party (such as customs or a freight forwarder)).
  • buyer, seller or third party such as customs or a freight forwarder
  • business rules as discussed above, with the transaction processing system 210 implementing the business rules.
  • the transaction processing system 210 uses business rules and/or profiles for users to match incoming information such as order, invoice, receipt and/or event notices. This incoming information is audited and reconciled by the transaction processing system 210 using appropriate business rules. For example, where a buyer establishes profiles, the transaction processing system 210 implements those profiles to audit and reconcile the information.
  • the transaction processing system 210 verifies that the extension of credit to the buyer and/or associated buyer party is appropriate. Where the extension of credit is appropriate, the transaction processing system 210 sends authorization to the appropriate financial institution following rules established by that financial institution via profiles within the transaction processing system.
  • the transaction processing system and network electronically funds a seller with a single payment across all credit issuing institutions via a finds delivery pathway specified in the seller-sponsoring financial institution's profile.
  • the cost to the seller for this payment is varied based on the financial institution supplying the credit.
  • the funds are delivered to the seller net of the seller-sponsoring bank's fees to the seller (e.g., fees are withheld prior to delivery of payment).
  • the seller-sponsoring financial institution uses the pricing capabilities of the transaction processing system and network to compute and render the bill to the seller. Detailed data supporting the payment continues to be resident in the transaction processing system and network and does not add overhead to the banking industries money movement networks.
  • the transaction processing system 210 provides the buyer-sponsoring bank with a data feed that enables it to update its credit line to the buyer to acknowledge the draw down of that credit line to pay invoices.
  • the buyer-sponsoring bank will also use the transaction processing system 210 to calculate and render the invoice to the bank's buyer customer, and facilitates the linking of transaction data to the invoice.
  • the buyer-sponsoring bank provides the transaction processing system 210 with information for processing the invoice accordingly, in profile and/or business rule information.
  • FIG. 3 shows a flow diagram for transaction processing involving the association of a particular financial institution with a transaction, according to another example embodiment of the present invention.
  • transaction data having financial transaction identification information is received from a user node.
  • the financial transaction identification information may include identification data that pertains, for example, to a particular party to the transaction, to a financial institution or to other identification information specific to the particular transaction to which it applies.
  • the financial transaction data is compared with financial institution identification data. If no match between the financial transaction data and a financial institution is found at block 330 , a failure notice is returned to a sender at block 335 indicating that the transaction cannot be processed.
  • transaction processing data corresponding to the match is loaded at block 340 .
  • this loaded transaction processing information includes information exclusively provided by a financial institution that is the subject of the match.
  • the loaded transaction processing data includes information for parties to the transaction in addition to the financial institution that is the subject of the match (e.g., for specifying user preferences or profiles as discussed above).
  • the audit generally involves parsing the financial transaction data using loaded processing data such as rules that can be implemented to specify whether the financial transaction data indicates that payment can be made.
  • a price term engine can be used to derive a payment amount for the financial transaction, using information in the financial transaction data and in the loaded transaction data (e.g., specifying pre-agreed contract terms used in arriving at a price).
  • Such a price term can be used for setting the price of one or more aspects of the financial transaction data.
  • the audit is then used at block 360 to generate a payment term for the transaction, and the payment term is used to facilitate payment for the transaction.
  • the payment term may include one or more of a payment amount, a time of payment, a credit term, a method of payment or a source from where to draw the payment.

Abstract

Transaction processing for financial institution-based transactions is facilitated. According to an example embodiment of the present invention, a transaction processing approach involves the processing of financial aspects of a transaction between buying and selling parties using transaction rules associated with a sponsoring financial institution. Transaction-related information is processed as a function of business rules associated with the sponsoring financial institution to facilitate payment for the transaction and the assessment of fees associated with the transaction processing.

Description

    RELATED PATENT DOCUMENTS
  • This patent document claims priority under 35 U.S.C. §119 to U.S. Provisional Patent Application No. 60/578,375, entitled “Financial Transaction Processing System and Approach” and filed on Jun. 9, 2004; this patent document is also a continuation-in-part of U.S. patent application Ser. No. 10/437,405 (USBA.117PA), filed on May 12, 2003, to which benefit is claimed under 35 U.S.C. §120 for common subject matter; U.S. patent application Ser. No. 10/437,405 is a continuation-in-part of U.S. patent application Ser. No. 09/259,657 (USBA.002C1), filed Feb. 26, 1999 now U.S. Pat. No. 6,571,149, which is a continuation of U.S. patent application Ser. No. 08/748,243, filed on Nov. 12, 1996, now U.S. Pat. No. 5,910,896; U.S. patent application Ser. No. 10/437,405 further claims priority under 35 U.S.C. §120 for common subject matter to U.S. Provisional Patent Application Ser. No. 60/379,561 (USBA.101P1) and filed on May 10, 2002.
  • FIELD OF THE INVENTION
  • The present invention is directed to communications and data processing and, more specifically, to communications and data processing involving transaction-related financial processing.
  • BACKGROUND
  • Operational management of contractual and transactional interactions between buyers, sellers, financial institutions and others involved in the exchange of products for purposes of commerce have typically been labor and time intensive. Generally, the processes of managing transactions between business entities have been unduly burdensome and inefficient.
  • Financial institutions employ transaction processing parameters that are unique to each institution. In addition, these transaction processing parameters typically need to be kept separate (and confidential), relative to other financial institutions. Often, transaction processing is dependent upon these parameters, which are specific to a particular financial institution involved in financing the transaction. In this regard, transaction processing for portions of a transaction that are related to a financial institution has generally been limited to implementation by a processing engine or system employed by the financial institution participating in the transaction.
  • When a transaction reaches the payment step, financial institutions for different parties to the transaction must interact with each other. This interaction typically involves complex agreements and associations that facilitate the transfer of funds. At times, there can be delays in payment or disputes regarding terms of payment. In addition, this process is highly susceptible to error. Interaction complexity, delay and error, as well as a multitude of other characteristics of transaction payment can cost one or more parties to a transaction (including financial institutions) a significant amount of funds.
  • Most industries are quite competitive and any cost savings are therefore important. Administrative costs are targeted for reduction as no revenue is directly generated from administrative functions. However, administrative costs associated with commercial transactions have been difficult to reduce in the current business environment with widely diffused data.
  • The above and other difficulties in the management and coordination of financial transactions have presented administrative and cost challenges to entities involved in various aspects of transactions, including financial institutions and others.
  • SUMMARY
  • The present invention is directed to overcoming the above-mentioned challenges and others related to the types of devices and applications discussed above and in other applications. The present invention is exemplified in a number of implementations and applications, some of which are summarized below.
  • According to an example embodiment of the present invention, financial transactions involving financial institutions are managed using an approach generally involving the use of rules for processing payment-related aspects of the financial transactions.
  • In a more particular example embodiment of the present invention, a transaction management system is configured for using sets of rules associated with financial institutions for processing transactions. When transaction information is received, it is associated with a particular sponsoring financial institution. Rules for the sponsoring institution are used to process the transaction. In some instances, the rules are further selected and implemented as a function of one or more of the sponsored transaction parties (e.g., a buyer or seller).
  • In another example embodiment of the present invention, an automated transaction processing system is adapted for processing transactions involving a plurality of financial institutions. The system includes a central processing node adapted to audit (e.g., validate or otherwise approve) transactions between contracting parties according to different sets of transaction rules. Each of the respective sets of transaction rules are defined as a function of a unique one of the plurality of financial institutions and a relationship between the unique financial institution and at least one of the contracting parties.
  • According to another example embodiment of the present invention, an automated transaction processing system audits transactions between contracting parties on behalf of a plurality of financial institutions. The automated transaction processing system includes a central processing node adapted, for different transactions involving various financial institutions, to associate each transaction with a unique one of the plurality of financial institutions and to audit each associated transaction according to a set of transaction rules. These transaction rules are defined as a function of the unique financial institution and a business relationship between the unique financial institution and at least one of the contracting parties. In this regard, the audit involves using information in the rules, upon which payment can be authorized, and comparing or otherwise processing information for a particular transaction (e.g., receipt of goods, issuance of an invoice) to approve payment for the transaction (or deny payment where transaction information fails to satisfy payment-type conditions). The central processing node facilitates payment for each transaction as a function of the audit.
  • The above summary of the present invention is not intended to describe each illustrated embodiment or every implementation of the present invention. The figures and detailed description that follow more particularly exemplify these embodiments.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The invention may be more completely understood in consideration of the detailed description of various embodiments of the invention in connection with the accompanying drawings, in which:
  • FIG. 1 shows a transaction processing arrangement, according to an example embodiment of the present invention;
  • FIG. 2 shows an arrangement and approach for transaction management, according to another example embodiment of the present invention; and
  • FIG. 3 shows a flow diagram for transaction processing, according to another example embodiment of the present invention.
  • While the invention is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not necessarily to limit the invention to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims.
  • DETAILED DESCRIPTION
  • The present invention is believed to be applicable to a variety of different types of communications and financial process management approaches, and has been found to be particularly useful for applications involving the operational implementation and application of financial institution rules and processes with transactions, payments, tracking and related aspects thereof. While the present invention is not necessarily limited to such approaches, various aspects of the invention may be appreciated through a discussion of various examples using these and other contexts.
  • According to an example embodiment of the present invention, a financial rules-based transaction approach is implemented with multiple sponsoring financial institutions for automatically processing financial transactions. The sponsoring financial institutions sponsor transaction parties (e.g., buyers and sellers); financial aspects of transactions between two or more of the sponsored transaction parties are carried out as a function of business rules for the financial institution sponsoring each party.
  • In another example embodiment of the present invention, a central transaction management system uses business rules (e.g., included in profile information) associated with financial institutions to process financial transactions between parties sponsored by the financial institutions. When the central transaction management system receives transaction information, the information is parsed for identifying characteristics that can be associated with sponsoring financial institutions. When these identifying characteristics match a particular financial institution, the central transaction management system uses business rules for the financial institution to process the financial transaction. In addition, when identifying characteristics for different parties to the transaction match different financial institutions, financial aspects of the transaction that are specific to each party are processed according to the each party's corresponding sponsoring financial institution. Funds relating to the financial transaction are thus transferred according to the business rules associated with sponsoring financial institutions for each party and to the particular characteristics of the financial transaction.
  • In one implementation, the central transaction management system audits data for transactions between the different parties as a function of business rules for one or more of the transaction parties. For example, where a particular party specifies conditions, in its business rules, upon which payment can be authorized, the central transaction management system implements those conditions in connection with the audit and determines therefrom a condition of payment for the transaction (e.g., whether some or all of a particular invoice can be paid). As another example, different parties to a contract may specify rules upon which transaction data is to be audited to indicate that the transaction is valid and/or ripe for payment. This auditing may include, for example, setting a price for a particular transaction, such as setting the price for a shipment involving bill of lading (BOL) rating or setting the price for a transaction based on characteristics of the transaction such as quantity of goods and/or receipt of the goods. In another example, the auditing involves comparing terms in transaction data from an electronic invoice to previously agreed upon contract terms; where the invoice matches the terms, or is within a tolerance where specified, the auditing results in an approval (i.e., validation of the transaction) for payment of the invoice. A multitude of such auditing approaches can selectively be implemented, based on various terms set by different transaction parties, by sponsoring financial institutions or other related entities.
  • In another implementation, the central transaction management system further uses business rules associated with individual parties to a transaction in processing financial transactions involving the individual parties. For instance, when the central transaction management system receives transaction information, the information is parsed (as discussed above) to identify sponsoring financial institutions as well as the parties to the transaction. The transaction is then process according to the business rules of the sponsoring financial institutions as well as the business rules of the parties to the transaction. These party-specific business rules may be stored, for example, in a user profile that is accessible by the central transaction management system. The user profiles may include identifiers used to identify buyer or seller transaction parties and/or sponsoring financial institutions.
  • In some instances, the sponsoring financial institution for a particular party is identified as a function of the identity of the party and corresponding business rules for the party. For example, when a party sets business rules to identify a particular sponsoring financial institution, these business rules are implemented in selecting the sponsoring financial institution. Correspondingly, the business rules for the financial institution identified by the party's business rules are used to process the financial transaction.
  • In other instances, two or more financial institutions can be specified by a particular party, including sponsoring and/or non-sponsoring financial institutions. Business rules for the particular party may include financial institution selection criteria that is implemented as a function of the particular transaction. For instance, selection criteria may be configured to indicate that payment for transactions under a certain value be processed (financed) using a first financial institution, while payment for transactions at or over the certain value be processed using a second financial institution. This approach may be implemented, for example, where large value transactions that may involve a longer payment period are desirably financed through a financial institution offering terms that are practicable for maintaining a longer payment term (i.e., lower rates). Small value transactions typically involving a shorter (or no) payment term may preferably be serviced using a financial institution offering desirable services or low service fees, but higher rates.
  • Sponsoring financial institutions may implement criteria similar to that discussed in the paragraph above for selecting a particular institution via which to process transactions, with selected criteria being implemented for making such selections. This approach may be useful, for example, where parties to the transaction agree to use a financial institution selected by the sponsoring financial institution that sponsors the party into the automated transaction process. In this regard, the financial institution selected for providing payment for a particular transaction is selectively different than the sponsoring financial institution. Such a financial institution may be selected by the sponsoring financial institution using, for example, a geographical location of a seller to which payment is to be made.
  • In some implementations, the central transaction management system works to keep separate the transaction rules for each financial institution (and transaction parties, where appropriate). Access to the transaction rules is restricted to the institution (or party) to which the rules belong. This restricted access approach may be implemented using, for example, encryption, passwords, tracking and other security-type measures typically implemented for data access and protection.
  • In some applications, a data access controller facilitates the restriction of access to transaction information by providing access to each financial institution for data relating to their clients. The data access controller selectively facilitates access via an overview type of data presentation that shows a financial overview for each customer to whom the financial institution issues credit. For example, for buyer customers, the data access controller selectively implements an overview showing each buyer's net position between payments due from the buyer and payments due to sellers (suppliers) through the transaction processing system.
  • In another application, the data access controller discussed above is further configured and arranged, for each sponsoring financial institution, to perform customer service functions related to transaction processing for the financial institution's customers within the transaction processing system. Such customer service functions are defined in the sponsoring financial institution's business rules in association with each customer. The data access controller implements the business rules in performing the customer service functions.
  • Business rules used by the central transaction management system may be stored using one or more of a variety of approaches. For example, a database accessible by the central transaction management system and having labels or other identifying characteristics that associate the business rules with a particular financial institution can be used. This database can be physically local or remote to the central transaction management system, as long as the central transaction management system can access the database and control access to the database by other entities.
  • The central transaction management system is further configured to interface with financial institutions for a particular transaction party, in addition to a sponsoring financial institution for the transaction party. For instance, where a transaction party has primary banking functions with a non-sponsoring financial institution, the sponsoring financial institution, via the central transaction management system, facilitates the transaction by exchanging funds via the non-sponsoring financial institution. The sponsoring financial institution may further implement processing type fees via the central transaction management system, charged for facilitating the financial transaction.
  • In some instances, the central transaction management system interfaces directly with financial institutions that, from a hierarchical perspective, pass-through information received from one or more parties to the transaction. The central transaction management system uses transaction rules based on the transaction information received from a financial institution. Effectively, the financial institutions use the central transaction management system to execute transaction-processing functions that are carried out using transaction-based rules specific to the particular financial institution providing the transaction information.
  • In other instances, the central transaction management system is adapted to interface directly with parties to a transaction and to use transaction rules based on information received from one or more of the parties (i.e., without a sponsoring financial institution). For example, a buyer or seller can interface with the central transaction management system using rules, implemented with the system, which are based on profile information for the particular buyer or seller. These parties may contract with a system administration entity, effectively acting as a sponsoring financial institution in some regards, relative to the above discussion, to facilitate transactions in this manner.
  • According to another example embodiment of the present invention, a central transaction management system uses transaction information for buyers and sellers of products and/or services to automatically derive pricing and/or payment options for individual transactions. These products and services may include, for example, tangible goods, shipment services, consulting services and financial services (e.g., where the seller may be a financial institution selling a financing package for a transaction between a buyer and another seller). The transaction information may include, for example, the identities of the buyer and seller, the products and/or services being purchased, the date of the purchase and the specific contract under the terms of which the transaction is being executed. For instance, specific contracts under the terms of which a transaction is being prosecuted may include prices agreed upon between a buyer and seller for a particular product and/or service.
  • Transaction-related contracts facilitated by the central transaction management system may also (or in the alternative) include rules agreed upon for setting certain financial and/or price terms between a buyer and seller. In one instance, terms associated with a particular transaction are automatically set by the central transaction management system to correspond to transaction information assigned to a particular buyer. The terms may be set, for example, using predetermined terms agreed to by the buyer and seller involved in the transaction. In another implementation, pricing arrangements such as quantity discounts, group discounts and conditional price variances (e.g., an acceptable percentage of variance in cost associated with for fluctuating shipping costs, product prices, financing costs and others) are further automatically implemented in response to the transaction information and the approved contract details in the central transaction management system. In still another implementation, financing terms such as processing fees for facilitating a transaction, interest-related fees, credit-extension fees and others are automatically set as a function of such a transaction-related contract. Where credit is extended, a rating engine is optionally implemented to assign an interest rate to an applicable transaction, for extending credit on behalf of a contracting party to the transaction.
  • Turning now to the figures, one or more of the above-discussed approaches are selectively implemented in connection with the processors and other functions shown in the figures and discussed as follows. Beginning with FIG. 1, a transaction processing arrangement 100 includes a central transaction processor 110 programmed to automatically process transaction information according to business rules corresponding to particular financial institutions, according to another example embodiment of the present invention. When transaction information is received at the central transaction processor 110, the information is associated with sponsoring financial institutions for each party to the transaction and processed according to business rules for the sponsoring financial institutions. The central transaction processor 110 may be implemented, for example, in connection with the above-discussed approaches including those involving the discussion of a central transaction management system and/or with a central transaction node in a network node-based arrangement.
  • Business rules are supplied by a multitude of financial institutions employing the central transaction node 110, represented here by financial institution nodes 120 and 128. In some instances, parties involved in transactions facilitated by the central transaction node also supply business rules. The central transaction processor 110 is in communication with a database 112 where transaction-related information including the above-discussed financial institution rules is stored. The database 112 is optionally coupled to (or part of) the central transaction processor 110 and further may include a plurality of data storage arrangements at different locations. The central transaction node 110 maintains separate (and secure) storage for these business rules by restricting access to the rules by the financial institutions (or others such as transaction parties).
  • The central transaction node 110 is further adapted to communicate with a variety of different parties to a transaction, represented by transaction parties 122, 124 and 126. These transaction parties and the financial institutions represented by user nodes 120, 122, 124, 126 and 128 are communicatively coupled with the central transaction processor 110. The user nodes 120-128 may, for example, include one or more of a buyer, seller, distributor, shipper, carrier, government agency, financial institution or other type of individual, group or agency that would be involved in a transaction, with parties shown in the figure by way of example.
  • The nodes 120-128 interact with the central transaction processor 110 for providing transaction-related information, such as financial processing rules, accounting rules, orders, invoices, shipping documents, payment authorization data, payment execution data, customs documents, security documents and others. In addition, this transaction-related information may include information for relating the application of rules to transaction data, such as payment processes, credit extension and finance charges. In some instances, financial institution nodes provide rules that are stored in the database 112, with other party nodes simply interacting with the central transaction node 110 (e.g., without providing any information for storage in the database 112). Transactions are thus processed as a function of stored rules for a particular financial institution (or institutions) with which the transactions are associated. In other instances, the database 112 is also implemented for maintaining transaction party-type information, such as user preferences (e.g., reporting, billing, credit extension) and financial institution preferences (e.g., which institution to use).
  • The transaction parties 122, 124 and 126 may be implemented via sponsoring financial institutions, with nodes 122, 124 and 126 representing this combination of transaction parties with a particular sponsoring financial institution. This combinatorial representation may also maintain direct interaction between transaction parties and the central transaction node 110 for facilitating party-specific communications, such as for setting business rules or profile information for individual parties.
  • In some implementations, one or more of the nodes 120-128 are used as interfaces to the central transaction processor 110, with users at the nodes being able to provide transaction-related information such as classification rules. In other implementations, the central transaction processor 110 automatically accesses information from the user nodes for a variety of purposes, such as retrieving classification rules (e.g., accounting codes and/or business rules) or updating related accounting fields. This interaction between the nodes and the central transaction processor 110 is controlled using, for example, access authorization such as those involving password-protected authorization and others.
  • When transaction data is received at the central transaction node 110 for financial institution-type processing, the central transaction node parses the data and automatically associates the transaction data with a particular financial institution sponsoring the transaction to which the data applies. This automatic association is implemented using business rules in the database 112 and/or as a function of the node sending the transaction data. In some instances, profile information for various sponsoring financial institutions (and/or transaction parties) is stored in the database 112 and used in connection with identifiers in received transaction information to automatically associate the transaction information with sponsoring financial institutions. The central transaction node 110 processes the associated data according to applicable business rules that may be tailored, for example, to a particular type of transaction or to particular transaction characteristics.
  • Where credit is extended on behalf of users, the central transaction processor 110 selectively assigns an interest rate to the extension of credit, either directly wherein an administrator of the central transaction processor extends credit, or in connection with an interest rate offered by a financial institution extending the credit. In some applications, the central transaction processor 110 implements a rating engine to assign an interest rate to an applicable transaction, for extending credit on behalf of a contracting party to the transaction. The rating engine uses information about the contracting party in order to establish such an interest rate.
  • In another example embodiment, the central transaction processor 110 is further adapted to grant and control information exchange with the database 112 as a function of inputs received from the nodes 120-128, such as authorization inputs and transaction-specific inputs. When users at one of the nodes 120-128 attempt to send information to or retrieve information from the central transaction processor 110, authorization information from the users is used to control the information transfer. The authorization information may include, for example, access-type information (e.g., a password or user ID) or simply document information that the central transaction processor 110 recognizes.
  • In another example embodiment, the central transaction processor 110 maintains data for business rules and processed transactions over time for a variety of purposes, such as for generating reports, tracking compliance and for taking appropriate action where errors or non-compliance occurs. For example, when a particular transaction is processed or when business rules are changed, the central processor monitors associated information and stores and/or processes the monitored information for these purposes.
  • The user profiles and/or business rules discussed herein in connection with FIG. 1 above and otherwise may include a variety of information for use in transaction management and financial processing. For instance, in addition to the above-discussed approaches, a typical such profile may include one or more of the following data: general ledger charts of accounts, identification of computer systems submitting contract or transaction data, customer lists, vendor lists, financial institution lists, contract and price approval policies, transactional approval policies, business rules, operational roles (e.g., defining what functions a user associated with that role can perform), organizational hierarchy (e.g., defining how much of a company's data a user associated with a particular organizational node can access), and individual users. Financial institution profiles may also include information further defining the business relationship with selected customers or other financial institutions and financial processing organizations from the financial institution's perspective.
  • FIG. 2 shows an arrangement and approach for transaction management in an automated transaction network, according to another example embodiment of the present invention. A transaction processing system 210 interfaces with a plurality of financial institutions for facilitating transactions, using data stored in a database 220 for implementing rules for the transactions. These rules are used to process financial aspects of the transactions, relative to information received via sponsoring financial institutions.
  • Two sponsoring financial institutions (230 and 240) are shown, with multiple such institutions being contemplated but not shown for brevity. Each sponsoring financial institution 230 and 240 works with multiple users, represented as users 1-N for institution 230, and users A-i for institution 240. Communications between the sponsoring financial institutions and the transaction processing system 210, as shown by communication links, may be implemented directly from the sponsoring financial institutions. In addition, the shown communication links may represent a direct communication from a sponsored user, the user including in the communication sufficient information (and security type information, where appropriate) to designate the appropriate sponsoring financial institution.
  • The transaction processing system 210 also interfaces with a variety of funds processing originators. By way of example, automatic clearing house (ACH) originators 250 and 270, and SWIFT (a European-based, straight through processing (STP) transaction system) originators 260 and 280 are shown. These funds processing originators are typically implemented as financial institutions having appropriate funds processing capabilities for implementing, for example, ACH or SWIFT-type functions. In this regard, the transaction processing system 210 interfaces with financial transaction processing entities for obtaining authorization to proceed with a transaction and to coordinate fund transfer using the respective originators (i.e., as conventional). The transaction processing system's interface with ACH and other providers is selectively specified by business rules used in processing a particular transaction for payment and facilitation functions.
  • The business rules in database 220 typically include user-specified rules that are provided by the financial institutions using the transaction processing system 210 for processing financial transactions. For example, user profile information for each sponsoring financial institution can be stored in the database 220 for use by the transaction processing system 210. This profile information may include, for example, business rules specifying one or more various conditions or approaches related to financial transaction processing, as discussed herein. For more information regarding transaction processing in general, and for specific information regarding the use of user profiles and business rules for transactions, as well as computer and processing arrangements and systems for use with the same (and as may be implemented in connection with one or more example embodiments herein), reference may be made to U.S. patent application Ser. No. 10/436,878 (USBA.101PA), entitled “Automated Transaction Processing System and Approach” and filed May 12, 2003, and to U.S. Pat. No. 5,910,896 (USBA.002PA) filed Nov. 12, 1996, all of which are incorporated herein by reference.
  • When the transaction processing system 210 receives transaction data identifying a particular sponsoring financial institution, the database 220 is accessed to retrieve profile information (and corresponding business rules) for processing the transaction data. The business rules are used to determine a variety of transaction-related characteristics, such as fees to be charged for different parties to the transaction, including buyer, seller and their respective financial institutions. Additional rules-based processing examples are discussed further below.
  • The storage of information in the database 220 may involve the use of a single database, or may involve multiple databases, either in a single or at multiple locations, communicatively coupled with the transaction management system 210. In one implementation, all transaction data for all buyers and sellers sponsored by all financial institutions is stored in one centralized database. The transaction management system 210 manages the centralized database such that information in the database that has a common relationship with other information in the database can be cross-referenced and updated. For instance, where information for a buyer and seller for a single transaction is stored in the centralized database, updates made to the buyer's information can be appropriately made to similar seller's information. This approach can be implemented to ensure that any buyer and any seller can do business with each other and see up-to-date status and documents without latencies typically involved attempting to replicate and synchronize data across multiple databases.
  • Business rules stored in the database 220 are optionally tailored to particular users that are being sponsored by the financial institution. In this regard, the business rules pertaining to a particular sponsoring financial institution, as well as the user being sponsored for a particular transaction, are retrieved from the database 220 and used accordingly. In some instances, sponsored users also store profile information in the database 220, such as preferred banking institution (i.e., with the sponsoring financial institution simply sponsoring the transaction for a fee and not funding the transaction).
  • In some instances, the transaction processing system 210 includes two or more system implementations, represented by system implementations 1 and 2-N. These system implementations may involve virtually separate implementations at a single location to facilitate data security and continuity for particular sponsoring financial institutions. For instance, each system implementation may be implemented for a particular financial institution, with communication between each system implementation and other system implementations being facilitated within the transaction processing system 210. In this regard, each user (sponsoring financial institution) may tailor it's specific system implementation to its own needs.
  • The system implementations with transaction processing system 210 may also be implemented at physically separate locations, with virtual ties to the transaction processing system 210. For example, the implementation of various aspects of the transaction processing system may be appropriate for applications in different countries or for point-of-use type applications (e.g., to reduce long distance data communications). This physically separate approach may also be implemented, for example, to address laws associated with transactions, including taxation and other processing rules.
  • As discussed above, various business rules stored at the database 220 are implemented by the transaction processing system 210 for a variety of transaction characteristics. One such characteristic involves the determination of fees to be charged to users (buyers and sellers), to sponsoring financial institutions and, where applicable, to other financial institutions involved in the transaction. In this regard, the database 220 stores business rules characterizing these fees, and the transaction processing system 210 uses these characterizing business rules to process financial transactions. In addition, the database 220 may store party-identifying information for use by the fee-based rules in characterizing the fees to be assessed for a particular transaction.
  • In some applications, the business rules are implemented to arrive at a collaborative transaction term, such as a price or other term automatically implemented as an agreed-upon term by using previously agreed-upon business rules for generating such a term. Fee-based rules implemented in connection with these approaches may involve, for example, information for determining the amount of fees to assess for one or more of the following:
  • fees to be charged to the seller for the transaction based on the identity of the seller and the identity of the seller's sponsoring bank;
  • fees to be charged to the buyer for this transaction based on the identity of the buyer and the identity of the buyer's sponsoring bank;
  • fees the seller's sponsoring bank owes the buyer's sponsoring bank for this transaction;
  • fees the buyer's sponsoring bank owes the seller's sponsoring bank for this transaction; and
  • fees the buyer's sponsoring bank and the seller's sponsoring bank owe the transaction processing system 210 for this transaction.
  • These collaborative type terms and approaches for implementing the same are selectively carried out using, for example, the transaction processing arrangement 100 shown in FIG. 1 and/or the transaction processing system 210 shown in FIG. 2, with transactions involving buyers and sellers sponsored into the processing network by a sponsoring bank. In these approaches, for each of a plurality of transactions involving a buyer and a seller, an association processor 212 identifies a particular sponsoring bank for each buyer and seller as a function of stored identifiers. The association identifies respective business rules, set in accordance with the particular sponsoring bank and the particular buyer or seller for which the rules are set, for respectively processing transactions on behalf of the buyer and on behalf of the seller for a particular transaction. These and other association processor 212 functions can be implemented separately from or in connection with (e.g., as a software-implemented function) the transaction processing system 210.
  • In some applications, the association processor facilitates the identification of business rules using a geographic location of a party to the transaction, for example where transaction payment characteristics are affected by such a location (e.g., where tariffs and/or taxes are involved).
  • In other applications, the association processor identifies business rules for a sponsoring financial institution using historical information for a particular transaction party. For example, where a financial institution implements different sets of business rules based on payment characteristics, credit rating, business volume or other historical-type information pertaining to a transaction party, that information is used to select a set of business rules to use in facilitating a transaction involving the transaction party.
  • A collaborative contracts processor uses the identified business rules and a business agreement between the buyer and seller to determine the amount of fees assessed in accordance with one or more of the above fees discussed in connection with the fee-based rules. Other approaches involving a collaborative contracts approach are discussed further below.
  • Turning back to FIG. 2 and with approaches involving the above assessed fees, the transaction processing system 210 uses information in profiles for facilitating the transfer of funds from, or the extension of credit on behalf of, the entity to which fees are assessed. For instance, where a particular fee is to be assessed against sponsoring financial institution 230 and/or one of the users 1-N, funds from that institution are provided directly (e.g., funds transfer) or indirectly (e.g., extension of credit), from the sponsoring financial institution 230 or from another financial institution specified by the user, where applicable.
  • The user (e.g., buyer, seller and financial institution) profiles discussed herein and implemented with collaborative-type approaches may include a variety of information for use in transaction management and otherwise. In some applications, typical profiles include one or more of the following data: a general ledger chart of accounts, identification of a computer system authorized for submitting contract or transaction data, customer and/or vendor lists, policies for contract, price or transactional approval and business rules. Where individuals within an organization participating in the collaborative-type approaches are selectively authorized, operational roles for such users are defined and include, e.g., access authorization for the users as well as individual access tracking. Seller customer list profiles may also include information further defining the business relationship with the customer from the Seller's perspective, for example, such as a retail buyer relationship or a wholesale buyer relationship. List profiles for buyers who act as vendors (e.g., as a seller or distributor) may also include information further defining the business relationship with the vendor from the Buyer's perspective.
  • In one particular implementation, profile information such as business rules, operational roles, authorization levels and/or other attributes are specific to particular levels and/or individuals within a particular entity. This profile information is stored for access by the transaction processing system 210 and used for implementing transactions. For example, when a particular financial institution or sponsored user includes different subsidiaries, divisions or locations, profile information can be tailored for the particular source. Certain profile information can also be implemented to supersede other profile information, for example, when a particular subsidiary is assigned different specific pricing terms, relevant to another subsidiary of a common entity.
  • In another example embodiment facilitating collaborative approaches, the transaction processing system 210 stores information for transaction parties including one or more of financial institutions and sponsored users (e.g., buyers and sellers), and communicates therewith using an identification approach for users at the buyer and/or seller level. The transaction processing system 210 controls access to the stored information as a function of user identification (ID), with access parameters controlled for processes such as contract modification, price modification, display configuration, access to the stored information for that particular user and others.
  • As an example using seller offerings that make up at least part of the stored information for a particular seller as well as buyer access controls, the seller offerings are automatically configured for usage by the individual users. In this context, seller offerings may involve real goods and/or services, as well as or in the alternative to financial offerings, such as the extension of credit and/or financial processing services. The automatic configuration may, for example, include price, delivery and payment options. In response to the seller offerings and other stored information, the transaction processing system 210 is adapted for accepting requests from buyers and communicating the requests to the seller. The transaction processing system 210 is further adapted for accepting acknowledgment of receipt by the buyer either manually (e.g., an individual buyer logs into the system with a user ID and confirms receipt) or electronically (e.g., buyer's inventory receiving systems automatically generate and transmit a detailed notice of receipt or acceptance). Once receipt or acceptance is acknowledged, the system communicates that acknowledgment to the seller. In one implementation, the system is further adapted for automatically paying the seller in response to the receipt/acceptance acknowledgment. In another implementation, the system is further adapted to invoice the buyer for the offerings. Further, “payment” in this context may involve the drawdown of a credit line, or extension of credit in manners as appropriate for the particular transaction.
  • In some applications, the transaction processing system 210 implements a settlement processor 214 in connection with facilitating payment for a particular transaction between a buyer and a seller. The settlement processor 212 performs inter-bank settlement by calculating the amount of funds to be collected from a sponsoring bank for the buyer and remitted to a sponsoring bank for the seller. The settlement is used to fund a payment that the seller's sponsoring bank will make to the seller for all transactions that achieve payable status, e.g., within a payment period defined as a function of the business rules.
  • The settlement processor 214 is implemented to facilitate payment/settlement in a variety of manners, depending upon the application and appropriate contract terms and other information relative to the truncation parties and/or sponsoring financial institutions involved in a particular transaction. In this regard, some applications involve one or more of the following electronic payment approaches as facilitated by the settlement processor 214 for a transaction involving a buyer and a seller, with sponsoring banks for each. In one approach, the settlement processor 214 facilitates the submission of an electronic payment demand at a defined period to the buyer's sponsoring bank for all net monies due to at least one of the transaction processing system and the seller's sponsoring bank, when the buyer's sponsoring bank is in a net funds due (to the transaction processing system) position. In another approach, the settlement processor 214 facilitates the submission of an electronic payment demand at a defined period to the seller's sponsoring bank for all net monies due to at least one of the transaction processing system and the buyer's sponsoring bank, when the seller's sponsoring bank is in a net funds due position. In another approach, the settlement processor 214 facilitates the submission of an electronic payment notice at a defined period to the buyer's sponsoring bank for all net monies due to the buyer's sponsoring bank, after subtraction of funds due to at least one of the transaction processing system and the seller's sponsoring bank, when the buyer's sponsoring bank is in a net funds due to processor position. In still another approach, the settlement processor 214 facilitates the submission of an electronic payment demand at a defined payment period to the seller's sponsoring bank for all net monies due to the seller's sponsoring bank after subtraction of funds due to at least one of the transaction processing system and the buyer's sponsoring bank, when the seller's sponsoring bank is in a net funds due to processor position. In each of the above approaches, the net funds due to processor position selectively characterizes funds due, and in certain applications, characterizes funds due to an administrator of the transaction processing system 210 for transaction payment (e.g., from a buyer to a seller) and/or for fees associated with the processing of the transaction payment.
  • In another implementation, the transaction management system discussed in the preceding paragraph is further adapted for accepting a receipt of purchase acknowledgment including receipt characteristics. For example, characteristics such as total acceptance of goods, partial acceptance of goods and rejection of goods at the invoice or receipt line item level can be included in the acknowledgment. These characteristics are tied to transaction levels involving users sponsored by the financial institutions (e.g., 230 or 240, shown by way of example). Where compliance before payment for a transaction is executed is to be ensured, this information is required to be verified a priori. An invoice or invoices for a particular transaction are updated with this and other transaction-fulfillment-related information. Using this approach, problems with received purchases, such as damaged goods, improper goods and improper financial terms are readily addressed. The various invoicing and payment-related characteristics are correspondingly modified (e.g., payment is only made for accepted portions of goods, or credit for the cost of returning goods is granted, or payment is made using only accepted terms such as those relating to an accepted credit-related interest rate).
  • In a more particular example embodiment, financial institutions approve financial contracts using a collaborative contract manager and submit order and invoice quantities for executing the contracts to the transaction processing system 210 (e.g., implementing a collaborative contract manager). The transaction processing system 210 then uses the terms from the collaborative contracts manager to establish financial processing terms (e.g., credit rate or other cost) between a user of financial services and the corresponding financial service provider. In one instance, financial service providers use the collaborative contracts manager as the central repository called by various provider systems. In another instance, the financial service user implements the collaborative contracts manager as the central repository called by various procurement systems.
  • For general information regarding the implementation of transaction functions and for specific information regarding collaborative-type functions that can be implemented in connection with one or more example embodiments discussed herein, reference may be made to U.S. patent application Ser. Nos. 10/436,878 (USBA.101PA) and 10/437,405 (USBA.117PA), both filed on May 12, 2003 and fully incorporated herein by reference.
  • In another embodiment, the transaction processing system 210 is configured for settling inter-bank issues relating to fees and/or other transaction characteristics. When a buyer and seller enter into a transaction, the transaction processing system 210 calculates the amount of funds to be collected from the buyer's sponsoring bank and remitted to the seller's sponsoring bank. These funds are used to fund the payment that the seller's sponsoring bank will make to the seller for all transactions that achieve payable status within a particular payment period (e.g., a network day) for the transaction processing system's.
  • Once the amount of funds to be collected are determined, the transaction processing system 210 further acts to facilitate the collection of these funds in one or more of a variety of manners. For instance, the transaction processing system 210 may simply make the amount of funds known to parties to the transaction using conventional communications methods. In other instances, the transaction processing system 210 actively facilitates collection of these funds.
  • In one example, an electronic payment demand is submitted on an interval (e.g., at least daily) to the buyer's sponsoring bank for all net monies due either to the transaction processing system or to the seller's sponsoring bank when the buyer's sponsoring bank has net funds due. An electronic payment demand is also submitted on an interval to the seller's sponsoring bank for all net monies due either to the transaction processing system or to the buyer's sponsoring bank when the seller's sponsoring bank has net finds due. In addition, an electronic payment notice is submitted on an interval (e.g., at least daily) to the buyer's sponsoring bank for all net monies due to the buyer's sponsoring bank. The net monies due are contemplated after subtraction of funds due to either the transaction processing system or the seller's sponsoring bank when the buyer's sponsoring bank has net funds due. An electronic payment notice is also submitted to the seller's sponsoring bank for all net monies due to the seller's sponsoring bank. Similarly as above, these net monies due are contemplated after subtraction of funds due to either the transaction processing system or the buyer's sponsoring bank when the seller's sponsoring bank has net funds due.
  • In connection with the various example embodiments discussed in connection with FIG. 2 (and otherwise), a fee engine is selectively implemented to facilitate the assessment of transaction processing fees. In some applications, the fee engine is implemented with a transaction processor (e.g., with transaction processing system 210), as a software-implemented engine. In this regard, fees such as those assessed in accordance with a business relationship between a financial institution and a buyer or seller party contracting therewith, or with a business relationship between a financial institution and an administrative transaction processor auditor, can be assessed using the fee engine. That is, the fee engine applies a fee appropriate for each transaction, and either directly or indirectly facilitates payment of that fee.
  • Access to information at the database 220 is controlled in one or more of a variety of manners, with information made available to users selectively and in a variety of formats, depending upon the implementation. Various examples using this general approach are discussed below. These examples are selectively implemented with a data access controller 216 and may involve approaches discussed above in connection with similar data access controller functions.
  • In one example embodiment, each buyer-sponsoring financial institution and each seller-sponsoring institution has access to the transactions naming their sponsored buyer or seller organization. By enabling such access, each financial institution is granted access to perform customer service functions related to transaction processing for their customers within the transaction processing system. These customer service functions may, for example, include the provision of accounting-related data in an appropriate format and at a selected interval, or include providing a notification to the customer upon certain predefined events related to transaction processing and/or financial status of transactions or accounts. In addition, each financial institution can maintain an overview of their net position with each of their customers to whom they are issuing credit. The financial institution is presented a view into the transaction processing system that shows their customers' net position between payments due from customer and payments due to suppliers (through the transaction processing system).
  • In another embodiment, each buyer-sponsoring financial institution has the capability, as enabled by user profiles stored at the database 220, to specify a variety of bank-specific operating characteristics. For example, each buyer-sponsoring financial institution may specify the financial institution that is to perform foreign currency translation on its sponsored buyer's behalf. This approach may be implemented, for example, where the seller desires to be paid in currency local to the seller and the buyer desires to be billed in currency local to the buyer. Each buyer-sponsoring financial institution may also specify a currency translation markup amount to add to translation services being provided to its buyers. The buyer-sponsoring financial institution may also specify the financial institution to use for remittance collection from its buyers. For general information regarding transaction processing, and for specific currency conversion implementations that may be implemented in connection with currency conversion as discussed here in connection with FIG. 2, reference may be made to U.S. patent application Ser. No. 11/104,394 (USBA.134PA), filed on Apr. 12, 2005 and entitled “Automated Transaction Processing System and Approach with Currency Conversion,” which is fully incorporated herein by reference.
  • Seller-sponsoring institutions may also specify the financial institution(s) to use for delivering payments to the seller. For instance, one institution may be used for ACH origination for sellers holding US-domiciled bank accounts and another institution (e.g., a SWIFT institution) for European-based sellers, and another for Latin American-based sellers.
  • Financial institutions issuing credit to either the buyer or the seller can also specify where credit-related information is retrieved from for use in the transaction. For example, the location from which credit drawdown advice (e.g., relative to available credit in an appropriate credit account) is to be delivered can be specified. In addition, credit-issuing financial institutions can specify whether the drawdown advice is to include transaction details or simply be the aggregate of the transaction details for the reporting period. For the latter case, the transaction processing system 210 can be specified to be used as the detailed subledger to support the credit usage. In this sense, the transaction processing system 210 functions much like conventional credit-issuing institutions (including credit card issuing institutions), with the credit issuer being provided summary or detail information.
  • A variety of security-related functions are implemented with the transaction management system 210, depending upon the application and the desired level of security. For example, in some implementations, data flowing to the transaction processing system 210 from sponsoring financial institutions (230, 240) are encrypted using standard encryption technologies. Similarly, data flowing from the transaction processing system 210 to sponsoring financial institutions (230, 240) can also be encrypted using standard encryption technologies. Communications between any distributed computing devices and the transaction processing system 210 can also be encrypted using standard encryption technologies. For instance, where the various system implementations 1, 2 and N are employed at physically different locations, communication between these system implementations and the transaction management system 210 is encrypted.
  • In addition to security-related functions for transaction communications, access to data within the transaction processing system 210 can also be controlled using security measures. For instance, profiles stored in the database 220 may include security type information, such as password and/or encryption information that users accessing the transaction management system 210 may employ.
  • In some instances, the transaction processing system 210 addresses synchronization issues between various financial institutions and organizations, such as those discussed above, by implementing pricing and/or other transaction rules that have previously been agreed upon such that disputes over transaction price are typically eliminated. These rules may include, for example, criterion defining pricing data that can be automatically approved (e.g., transaction fees within a selected variance), and also control pricing information made available to different users. The pricing rules may also include, for example, prices associated with particular transaction characteristics, with different prices being assigned for particular transactions (e.g., such as with a volume or amount discount).
  • In various other example embodiments of the present invention, a credit-processing approach is implemented with a transaction management arrangement, such as that shown in FIG. 2 and discussed above. For example, the transaction processing system 210 can facilitate the extension of credit on behalf of one or more sponsoring financial institutions, or another financial institution, in connection with a particular user participant in a transaction.
  • In one such credit-processing implementation, a buyer-sponsoring bank sponsors a buyer into the transaction processing system 210 and network with an active connection to a line of credit for usage within the transaction processing system and network. The buyer creates trading partner relationships with sellers who are sponsored into the transaction processing system 210, which facilitates the relationships and related transaction processing. When a buyer makes a purchase from a seller, the buyer sends an electronic copy of an order for the purchase to the transaction processing system 210 and network. The seller fulfills an order and issues an invoice electronically to the transaction processing system 210.
  • Where particular events are to occur and/or conditions are to be met before an invoice becomes payable, these events or conditions are provided by an appropriate party to a transaction (e.g., buyer, seller or third party (such as customs or a freight forwarder)). These events and/or conditions can be specified using business rules as discussed above, with the transaction processing system 210 implementing the business rules.
  • The transaction processing system 210 uses business rules and/or profiles for users to match incoming information such as order, invoice, receipt and/or event notices. This incoming information is audited and reconciled by the transaction processing system 210 using appropriate business rules. For example, where a buyer establishes profiles, the transaction processing system 210 implements those profiles to audit and reconcile the information.
  • Where payment is ripe as determined, e.g., via an audit as discussed above, and where payment is via the extension of credit, the transaction processing system 210 verifies that the extension of credit to the buyer and/or associated buyer party is appropriate. Where the extension of credit is appropriate, the transaction processing system 210 sends authorization to the appropriate financial institution following rules established by that financial institution via profiles within the transaction processing system.
  • When authorization is received and all other conditions required for payment are met, the transaction processing system and network electronically funds a seller with a single payment across all credit issuing institutions via a finds delivery pathway specified in the seller-sponsoring financial institution's profile. In some instances, the cost to the seller for this payment is varied based on the financial institution supplying the credit. The funds are delivered to the seller net of the seller-sponsoring bank's fees to the seller (e.g., fees are withheld prior to delivery of payment). The seller-sponsoring financial institution uses the pricing capabilities of the transaction processing system and network to compute and render the bill to the seller. Detailed data supporting the payment continues to be resident in the transaction processing system and network and does not add overhead to the banking industries money movement networks.
  • In connection with the authorization above, the transaction processing system 210 provides the buyer-sponsoring bank with a data feed that enables it to update its credit line to the buyer to acknowledge the draw down of that credit line to pay invoices. In some instances, the buyer-sponsoring bank will also use the transaction processing system 210 to calculate and render the invoice to the bank's buyer customer, and facilitates the linking of transaction data to the invoice. In these instances, the buyer-sponsoring bank provides the transaction processing system 210 with information for processing the invoice accordingly, in profile and/or business rule information.
  • FIG. 3 shows a flow diagram for transaction processing involving the association of a particular financial institution with a transaction, according to another example embodiment of the present invention. At block 310, transaction data having financial transaction identification information is received from a user node. The financial transaction identification information may include identification data that pertains, for example, to a particular party to the transaction, to a financial institution or to other identification information specific to the particular transaction to which it applies. At block 320, the financial transaction data is compared with financial institution identification data. If no match between the financial transaction data and a financial institution is found at block 330, a failure notice is returned to a sender at block 335 indicating that the transaction cannot be processed.
  • If a match between the financial transaction data and a financial institution is found at block 330, transaction processing data corresponding to the match is loaded at block 340. In some instances, this loaded transaction processing information includes information exclusively provided by a financial institution that is the subject of the match. In other instances, the loaded transaction processing data includes information for parties to the transaction in addition to the financial institution that is the subject of the match (e.g., for specifying user preferences or profiles as discussed above).
  • After the transaction processing data has been loaded, it is used to audit the transaction data at block 350 for facilitating financial aspects of the transaction. The audit generally involves parsing the financial transaction data using loaded processing data such as rules that can be implemented to specify whether the financial transaction data indicates that payment can be made. For instance, a price term engine can be used to derive a payment amount for the financial transaction, using information in the financial transaction data and in the loaded transaction data (e.g., specifying pre-agreed contract terms used in arriving at a price). Such a price term can be used for setting the price of one or more aspects of the financial transaction data. The audit is then used at block 360 to generate a payment term for the transaction, and the payment term is used to facilitate payment for the transaction. In this regard, the payment term may include one or more of a payment amount, a time of payment, a credit term, a method of payment or a source from where to draw the payment.
  • While certain aspects of the present invention have been described with reference to several particular example embodiments, those skilled in the art will recognize that many changes may be made thereto without departing from the spirit and scope of the present invention, aspects of which are set forth in the following claims.

Claims (33)

1. An automated transaction processing system for auditing transactions between contracting parties on behalf of a plurality of financial institutions, the system comprising:
a central processing node adapted, for different transactions involving various financial institutions, to
associate each transaction with a unique one of the plurality of financial institutions,
audit each transaction according to a set of transaction rules defined as a function of the unique financial institution and a business relationship between the unique financial institution and at least one of the contracting parties, and
facilitate payment for each transaction as a function of the audit.
2. The system of claim 1, wherein the central processing node is adapted to associate each transaction with a first unique financial institution associated with one of the contracting parties and with a second unique financial institution associated with another one of the contracting parties, and to audit each transaction according to sets of transaction rules defined as a function of each of the unique financial institutions and respective business relationships between each unique financial institution and the respective contracting parties.
3. The system of claim 1, wherein the central processing node is adapted to audit transactions according to third party information.
4. The system of claim 1, wherein the central processing node includes a fee engine adapted for applying a fee to each audited transaction and to assess the fee as a function of the business relationship between the unique financial institution and at least one of the contracting parties for the audited transaction.
5. The system of claim 1, wherein the central processing node includes a rating engine configured and arranged to assign an interest rate to a transaction between contracting parties, the rate being implemented for extending credit on behalf of one of the contracting parties.
6. The system of claim 5, wherein the central processing node is further adapted to maintain a credit account for transaction parties and wherein the rate is implemented in extending credit via the credit account.
7. The system of claim 1, wherein the central processing node is adapted to audit transactions between contracting parties according to different sets of transaction rules by implementing the transaction rules to determine a condition of validity of the transaction.
8. The system of claim 7, wherein the central processing node is adapted to audit transactions between contracting parties according to different sets of transaction rules by implementing the transaction rules to authorize payment for a valid transaction.
9. An automated transaction processing system and network for processing transactions for buyers and sellers sponsored into the processing network by a sponsoring bank, the system comprising:
an association processor configured and arranged, for each of a plurality of transactions involving a buyer and a seller, to identify a particular sponsoring bank for each buyer and seller as a function of stored identifiers, the association identifying respective business rules, set in accordance with the particular sponsoring bank and the particular buyer or seller for which the rules are set, for respectively processing transactions on behalf of the buyer and on behalf of the seller for a particular transaction; and
a collaborative contracts processor configured and arranged, for each particular transaction involving a buyer and a seller, to use the identified business rules and a business agreement between the buyer and seller to determine the amount of fees that
should be charged to the seller,
should charged to the buyer as a function of the identity of the buyer and the identity of the buyer's sponsoring bank,
the seller's sponsoring bank owes the buyer's sponsoring bank,
the buyer's sponsoring bank owes the seller's sponsoring bank, and
the buyer's sponsoring bank and the seller's sponsoring bank owe the automated transaction processing system and network.
10. The automated transaction processing system and network of claim 9, further comprising a settlement processor configured and arranged, for each particular transaction involving a buyer and a seller, to:
perform inter-bank settlement by calculating the amount of funds to be collected from the buyer's sponsoring bank and remitted to the seller's sponsoring bank to fund a payment that the seller's sponsoring bank will make to the seller for all transactions that achieve payable status within a payment period defined as a function of the business rules.
11. The automated transaction processing system and network of claim 10, wherein the settlement processor is configured and arranged, for each particular transaction involving a buyer and a seller, to:
submit an electronic payment demand at a defined period to the buyer's sponsoring bank for all net monies due to at least one of the transaction processing system and the seller's sponsoring bank, when the buyer's sponsoring bank is in a net funds due to processor position;
submit an electronic payment demand at a defined period to the seller's sponsoring bank for all net monies due to at least one of the transaction processing system and the buyer's sponsoring bank, when the seller's sponsoring bank is in a net funds due to processor position;
submit an electronic payment notice at a defined period to the buyer's sponsoring bank for all net monies due the buyer's sponsoring bank after subtraction of funds due to at least one of the transaction processing system and the seller's sponsoring bank, when the buyer's sponsoring bank is in a net funds due to processor position; and
submit an electronic payment demand at a defined payment period to the seller's sponsoring bank for all net monies due to the seller's sponsoring bank after subtraction of funds due to at least one of the transaction processing system and the buyer's sponsoring bank, when the seller's sponsoring bank is in a net funds due to processor position.
12. The automated transaction processing system and network of claim 9, further comprising a data access controller configured and arranged, for each sponsoring financial institution, to:
provide access to transactions naming a buyer or seller organization sponsored by the sponsoring financial institution; and
maintain an overview of their net position with each of their customers to whom they are issuing credit, the overview showing each customer's net position between payments due from the customer and payments due to suppliers through the transaction processing system.
13. The automated transaction processing system and network of claim 12, wherein the data access controller is further configured and arranged, for each sponsoring financial institution, to perform customer service functions related to transaction processing for their customers within the transaction processing system, the customer service functions defined in the sponsoring financial institution's business rules in association with each customer.
14. The automated transaction processing system and network of claim 9, wherein the collaborative contracts processor is configured and arranged to implement profiles for each sponsoring financial institution for specifying bank-specific operating characteristics to use in processing transactions involving the sponsoring financial institution.
15. The automated transaction processing system and network of claim 14, wherein the collaborative contracts processor is configured and arranged to perform a currency conversion using a financial institution to process the currency conversion as specified in the profile for a particular sponsoring financial institution.
16. The automated transaction processing system and network of claim 15, wherein the collaborative contracts processor is configured and arranged to assess a markup fee to a sponsored user as a function of profiles for the particular sponsoring financial institution's profile.
17. The automated transaction processing system and network of claim 14, wherein the collaborative contracts processor is configured and arranged to use information in the profiles to identify a financial institution to use for remittance collection from buyers sponsored by the sponsoring financial institution.
18. The automated transaction processing system and network of claim 14, wherein the collaborative contracts processor is configured and arranged to use information in the profiles to identify a financial institution that the sponsoring financial institution specifies to use for payments to each seller sponsored by the sponsoring financial institution.
19. The automated transaction processing system of claim 18, wherein the collaborative contracts processor is configured and arranged to use information in the profiles to identify a financial institution that the sponsoring financial institution wants to use for payments to each seller sponsored by the sponsoring financial institution, as a function of a geographical location of each seller.
20. The automated transaction processing system and network of claim 14, wherein the collaborative contracts processor is configured and arranged to use information in the profiles to identify a location to which credit drawdown advice is to be delivered and to specify the content of the credit drawdown advice
21. The automated transaction processing system and network of claim 9, further comprising a data storage arrangement configured and arranged for storing all transaction data for transactions involving sponsored buyers and sellers, and to provide access to all of the transaction data to the collaborative contracts processor.
22. The automated transaction processing system and network of claim 21, wherein the data storage arrangement includes at least two different databanks connected via a network link.
23. The automated transaction processing system and network of claim 9, wherein the association processor is configured and arranged to identify a particular set of business rules to implement for a particular transaction as a function of a credit term associated with the particular transaction.
24. The automated transaction processing system and network of claim 9, wherein the association processor is configured and arranged to identify a particular set of business rules to implement for a particular transaction as a function of the geographic location of at least one party to the particular transaction.
25. The automated transaction processing system and network of claim 9, wherein the association processor is configured and arranged to identify a particular set of business rules to implement for a particular transaction as a function of historical information associated with at least one party to the particular transaction.
26. The automated transaction processing system and network of claim 9, wherein the association processor is configured and arranged to store and implement identifiers to identify a particular sponsoring bank for each of the buyer and seller by storing and implementing user profiles for each buyer and seller, the user profiles specifying the identifiers that identify a particular sponsoring bank for each buyer and seller.
27. The automated transaction processing system and network of claim 26, wherein the association processor is configured and arranged to store and implement user profiles, for each buyer and seller, that specify a non-sponsoring financial institution that the buyer or seller wishes to use with the transfer of funds for transactions.
28. The automated transaction processing system and network of claim 27, wherein the association processor is configured and arranged to select a store and implement user profiles, for each buyer and seller, that specify a non-sponsoring financial institution as a function of at least one of: the amount of a particular transaction, the type of a purchase associated with the transaction, the location of a purchase associated with the transaction, taxes on the transaction, the interest rate available from the financial institution, and insurance for the transaction.
29. The automated transaction processing system and network of claim 9, wherein the collaborative contracts processor configured and arranged, for each particular transaction, to use the identified business rules to select ACH (automatic clearing house) outbound payment & facilitation functions to implement for each particular transaction.
30. A method for auditing transactions between contracting parties on behalf of a plurality of financial institutions, the method comprising:
associating each transaction with a unique one of the plurality of financial institutions;
auditing each transaction according to a set of transaction rules defined as a function of the unique financial institution and a business relationship between the unique financial institution and at least one of the contracting parties, and
facilitating payment for each transaction as a function of the audit.
31. The method of claim 30, further comprising, for each transaction, defining a set of transaction rules for a unique financial institution associated with the transaction as a function of the unique financial institution and a business relationship between the unique financial institution and at least one of the contracting parties.
32. A system for auditing transactions between contracting parties on behalf of a plurality of financial institutions, the system comprising:
means for associating each transaction with a unique one of the plurality of financial institutions;
means for auditing each transaction according to a set of transaction rules defined as a function of the unique financial institution and a business relationship between the unique financial institution and at least one of the contracting parties, and
means for facilitating payment for each transaction as a function of the audit.
33. A method for processing transactions for buyers and sellers sponsored into a processing network by a sponsoring bank, the method comprising:
for each of a plurality of transactions involving a buyer and a seller, identifying a particular sponsoring bank for each buyer and seller as a function of stored identifiers, the association identifying respective business rules, set in accordance with the particular sponsoring bank and the particular buyer or seller for which the rules are set, for respectively processing transactions on behalf of the buyer and on behalf of the seller for a particular transaction; and
for each particular transaction involving a buyer and a seller, use the identified business rules and a business agreement between the buyer and seller to determine the amount of fees that
should be charged to the seller,
should charged to the buyer as a function of the identity of the buyer and the identity of the buyer's sponsoring bank,
the seller's sponsoring bank owes the buyer's sponsoring bank,
the buyer's sponsoring bank owes the seller's sponsoring bank, and
the buyer's sponsoring bank and the seller's sponsoring bank owe the automated transaction processing system and network.
US11/151,747 1996-11-12 2005-06-09 Financial institution-based transaction processing system and approach Abandoned US20080172314A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US11/151,747 US20080172314A1 (en) 1996-11-12 2005-06-09 Financial institution-based transaction processing system and approach
US12/492,986 US8589268B2 (en) 1996-11-12 2009-06-26 Financial institution-based transaction processing system and approach
US12/492,965 US8595099B2 (en) 1996-11-12 2009-06-26 Financial institution-based transaction processing system and approach

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US08/748,243 US5910896A (en) 1996-11-12 1996-11-12 Shipment transaction system and an arrangement thereof
US09/259,657 US6571149B1 (en) 1996-11-12 1999-02-26 Shipment transaction system and method
US37956102P 2002-05-10 2002-05-10
US10/437,405 US20040010463A1 (en) 1996-11-12 2003-05-12 Automated transaction processing system and approach
US57837504P 2004-06-09 2004-06-09
US11/151,747 US20080172314A1 (en) 1996-11-12 2005-06-09 Financial institution-based transaction processing system and approach

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/437,405 Continuation-In-Part US20040010463A1 (en) 1996-11-12 2003-05-12 Automated transaction processing system and approach

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US12/492,986 Continuation US8589268B2 (en) 1996-11-12 2009-06-26 Financial institution-based transaction processing system and approach
US12/492,965 Continuation US8595099B2 (en) 1996-11-12 2009-06-26 Financial institution-based transaction processing system and approach

Publications (1)

Publication Number Publication Date
US20080172314A1 true US20080172314A1 (en) 2008-07-17

Family

ID=46328262

Family Applications (3)

Application Number Title Priority Date Filing Date
US11/151,747 Abandoned US20080172314A1 (en) 1996-11-12 2005-06-09 Financial institution-based transaction processing system and approach
US12/492,965 Expired - Fee Related US8595099B2 (en) 1996-11-12 2009-06-26 Financial institution-based transaction processing system and approach
US12/492,986 Expired - Fee Related US8589268B2 (en) 1996-11-12 2009-06-26 Financial institution-based transaction processing system and approach

Family Applications After (2)

Application Number Title Priority Date Filing Date
US12/492,965 Expired - Fee Related US8595099B2 (en) 1996-11-12 2009-06-26 Financial institution-based transaction processing system and approach
US12/492,986 Expired - Fee Related US8589268B2 (en) 1996-11-12 2009-06-26 Financial institution-based transaction processing system and approach

Country Status (1)

Country Link
US (3) US20080172314A1 (en)

Cited By (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020162027A1 (en) * 2001-02-23 2002-10-31 Mark Itwaru Secure electronic commerce
US20070156584A1 (en) * 2005-11-22 2007-07-05 Primerevenue, Inc. Supply Chain Financing Systems and Methods
US20080154739A1 (en) * 2006-12-22 2008-06-26 Yahoo! Inc Social Network Commerce Model
US20100138325A1 (en) * 2008-11-26 2010-06-03 Hahn-Carlson Dean W Methods and arrangements involving adaptive auditing and rating for disparate data processing
US8392285B2 (en) 1996-11-12 2013-03-05 Syncada Llc Multi-supplier transaction and payment programmed processing approach with at least one supplier
US8396811B1 (en) 1999-02-26 2013-03-12 Syncada Llc Validation approach for auditing a vendor-based transaction
US20130212004A1 (en) * 2011-05-11 2013-08-15 Mark Itwaru Customized transaction flow for multiple transaction types using encoded image representation of transaction information
US20130254073A1 (en) * 2012-03-23 2013-09-26 Oracle International Corporation System and method for returning individual lines of a purchase requisition for correction and approval
US8560439B2 (en) 2004-06-09 2013-10-15 Syncada Llc Transaction processing with core and distributor processor implementations
US8589268B2 (en) 1996-11-12 2013-11-19 Syncada Llc Financial institution-based transaction processing system and approach
US8650119B2 (en) 2004-06-09 2014-02-11 Syncada Llc Order-resource fulfillment and management system and approach
US8712884B2 (en) 2006-10-06 2014-04-29 Syncada Llc Transaction finance processing system and approach
US8751337B2 (en) 2008-01-25 2014-06-10 Syncada Llc Inventory-based payment processing system and approach
US8762238B2 (en) 2004-06-09 2014-06-24 Syncada Llc Recurring transaction processing system and approach
US8825549B2 (en) 1996-11-12 2014-09-02 Syncada Llc Transaction processing with core and distributor processor implementations
US20140343982A1 (en) * 2013-05-14 2014-11-20 Landmark Graphics Corporation Methods and systems related to workflow mentoring
US8967480B2 (en) 2011-05-11 2015-03-03 Riarera Corp. System and method for processing funds transfer between entities based on received optical machine readable image information
US9547861B2 (en) 2011-05-11 2017-01-17 Mark Itwaru System and method for wireless communication with an IC chip for submission of pin data
US9715704B2 (en) 2011-05-11 2017-07-25 Riavera Corp Merchant ordering system using optical machine readable image representation of invoice information
US9721243B2 (en) 2011-05-11 2017-08-01 Riavera Corp. Mobile payment system using subaccounts of account holder
US9734498B2 (en) 2011-05-11 2017-08-15 Riavera Corp Mobile image payment system using short codes
US9785935B2 (en) 2011-05-11 2017-10-10 Riavera Corp. Split mobile payment system
US10026120B2 (en) 2012-01-06 2018-07-17 Primerevenue, Inc. Supply chain finance system
WO2018237264A1 (en) * 2017-06-22 2018-12-27 Jpmorgan Chase Bank, N.A. System and method for implementing an interbank information network
US10592943B2 (en) 2011-05-20 2020-03-17 Primerevenue, Inc. Supply chain finance system
EP3596679A4 (en) * 2017-03-17 2021-01-06 Baton Systems, Inc. Transaction settlement systems and methods
US11295280B2 (en) 2011-05-11 2022-04-05 Riavera Corp. Customized transaction flow for multiple transaction types using encoded image representation of transaction information
US11601498B2 (en) 2016-09-12 2023-03-07 Baton Systems, Inc. Reconciliation of data stored on permissioned database storage across independent computing nodes

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9542690B2 (en) * 2006-07-18 2017-01-10 American Express Travel Related Services Company, Inc. System and method for providing international coupon-less discounts
US20100293091A1 (en) * 2009-05-18 2010-11-18 Kurczodyna Joseph E Method and system for implementing a fast amortization schedule (fas) index mortgage fund
US20110167423A1 (en) * 2010-01-07 2011-07-07 Bank Of America Corporation Intelligent Keying Center Workflow Optimization
US20140143147A1 (en) * 2011-12-20 2014-05-22 Rajesh Poornachandran Transaction fee negotiation for currency remittance
US20140025451A1 (en) * 2012-07-20 2014-01-23 First Data Corporation Enhanced transaction processing
WO2016029194A1 (en) * 2014-08-21 2016-02-25 Shaaban Ahmed Farouk System and method for inter-company billing processing
IL293232A (en) * 2016-11-19 2022-07-01 Costanz Mario A System and method for interaction object reconciliation in a public ledger blockchain environment
US11062400B1 (en) * 2020-01-14 2021-07-13 VALID8 Financial Inc. System and method for data synchronization and verification
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
US11809390B2 (en) 2021-07-29 2023-11-07 Intuit Inc. Context-dependent event cleaning and publication

Citations (98)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4507778A (en) * 1981-10-30 1985-03-26 Fuji Xerox Co., Ltd. Digital transmission system
US4567359A (en) * 1984-05-24 1986-01-28 Lockwood Lawrence B Automatic information, goods and services dispensing system
US4725719A (en) * 1986-07-21 1988-02-16 First City National Bank Of Austin Restricted purpose, commercial, monetary regulation method
US4799156A (en) * 1986-10-01 1989-01-17 Strategic Processing Corporation Interactive market management system
US4992940A (en) * 1989-03-13 1991-02-12 H-Renee, Incorporated System and method for automated selection of equipment for purchase through input of user desired specifications
US4995112A (en) * 1988-07-05 1991-02-19 Kabushiki Kaisha Toshiba Security system
US4996662A (en) * 1983-10-03 1991-02-26 Wang Laboratories, Inc. Method for generating document using tables storing pointers and indexes
US5285383A (en) * 1990-09-14 1994-02-08 Plains Cotton Cooperative Association Method for carrying out transactions of goods using electronic title
US5293310A (en) * 1992-05-22 1994-03-08 Pitney Bowes Inc. Flexible method for applying customized rating adjustments to transaction charges
US5393963A (en) * 1992-03-17 1995-02-28 Company Chex, Inc. Check authorization system and process
US5483445A (en) * 1992-10-22 1996-01-09 American Express Trs Automated billing consolidation system and method
US5485369A (en) * 1993-09-28 1996-01-16 Tandata Corporation Logistics system for automating tansportation of goods
US5500513A (en) * 1994-05-11 1996-03-19 Visa International Automated purchasing control system
US5712990A (en) * 1991-10-03 1998-01-27 International Technology Corporation Of California Economical automated process for averting physical dangers to people, wildlife or environment due to hazardous waste
US5717989A (en) * 1994-10-13 1998-02-10 Full Service Trade System Ltd. Full service trade system
US5719771A (en) * 1993-02-24 1998-02-17 Amsc Subsidiary Corporation System for mapping occurrences of conditions in a transport route
US5732400A (en) * 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US5870719A (en) * 1996-07-03 1999-02-09 Sun Microsystems, Inc. Platform-independent, usage-independent, and access-independent distributed quote configuraton system
US6012041A (en) * 1996-03-01 2000-01-04 I.S.R. (Logistics) Limited Apparatus for the control of inventory
US6016477A (en) * 1997-12-18 2000-01-18 International Business Machines Corporation Method and apparatus for identifying applicable business rules
US6021202A (en) * 1996-12-20 2000-02-01 Financial Services Technology Consortium Method and system for processing electronic documents
US6026374A (en) * 1996-05-30 2000-02-15 International Business Machines Corporation System and method for generating trusted descriptions of information products
US6029150A (en) * 1996-10-04 2000-02-22 Certco, Llc Payment and transactions in electronic commerce system
US6029140A (en) * 1994-07-21 2000-02-22 Micron Technology, Inc. On-time delivery, tracking and reporting
US6044362A (en) * 1997-09-08 2000-03-28 Neely; R. Alan Electronic invoicing and payment system
US6043819A (en) * 1990-01-16 2000-03-28 Digital Image Systems, Corp Image based document processing and information management system and apparatus
US6169542B1 (en) * 1998-12-14 2001-01-02 Gte Main Street Incorporated Method of delivering advertising through an interactive video distribution system
US6199046B1 (en) * 1997-07-29 2001-03-06 Adsura Pty Ltd. Method system and article of manufacture for performing real time currency conversion
US6204763B1 (en) * 1999-03-22 2001-03-20 Jujitsu Limited Household consumable item automatic replenishment system including intelligent refrigerator
US6338044B1 (en) * 1999-03-17 2002-01-08 Loudeye Technologies, Inc. Personal digital content 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
US20020016765A1 (en) * 2000-07-11 2002-02-07 David Sacks System and method for third-party payment processing
US20020026374A1 (en) * 2000-05-02 2002-02-28 Moneymaker Vincent B. Comprehensive third-party transactional processing and payment in an online environment
US6357042B2 (en) * 1998-09-16 2002-03-12 Anand Srinivasan Method and apparatus for multiplexing separately-authored metadata for insertion into a video data stream
US20020032649A1 (en) * 2000-04-13 2002-03-14 Balamurugan Selvarajan High-security E-currency IDs for E-commerce transactions
US20020035488A1 (en) * 2000-04-03 2002-03-21 Anthony Aquila System and method of administering, tracking and managing of claims processing
US20020038305A1 (en) * 2000-08-04 2002-03-28 Bottomline Technologies (De) Inc. Automated invoice receipt and management system
US20020038277A1 (en) * 2000-02-22 2002-03-28 Yuan Frank S. Innovative financing method and system therefor
US20030004823A1 (en) * 2001-06-28 2003-01-02 Epylon Corporation Integrated procurement system facilitating the sharing of research and purchasing across multiple buying organizations
US6505172B1 (en) * 1994-08-10 2003-01-07 Eplus Inc. Electronic sourcing system
US6505169B1 (en) * 2000-01-26 2003-01-07 At&T Corp. Method for adaptive ad insertion in streaming multimedia content
US20030005876A1 (en) * 2001-06-04 2003-01-09 Anthony Boswell Guide device & car park
US6507826B1 (en) * 1999-01-29 2003-01-14 Koriel, Inc. Remote electronic invoice entry and validation system and method therefor
US20030014325A1 (en) * 2001-06-27 2003-01-16 Peter Biffar Automatic pricing and negotiation system
US6510384B2 (en) * 2000-11-15 2003-01-21 International Business Machines Corporation Route search system and route search method
US6510383B1 (en) * 2000-03-01 2003-01-21 Arrivalstar, Inc. Vehicular route optimization system and method
US20030018563A1 (en) * 2001-07-13 2003-01-23 Efficient Capital Corporation Trading and processing of commercial accounts receivable
US20030026404A1 (en) * 1998-09-15 2003-02-06 Joyce Simon James Convergent communications system and method with a rule set for authorizing, debiting, settling and recharging a mobile commerce account
US20030033205A1 (en) * 2000-01-10 2003-02-13 D.K. Nowers Method and system for facilitating fulfillment of electronic commercial transactions
US20030033240A1 (en) * 2001-06-11 2003-02-13 Opt4 Derivatives, Inc. Integrated electronic exchange of structured contracts with dynamic risk-based transaction permissioning
US6526443B1 (en) * 1999-05-12 2003-02-25 Sandia Corporation Method and apparatus for managing transactions with connected computers
US20030041008A1 (en) * 2001-08-22 2003-02-27 William Grey System and method for facilitating transactions among disparate entities
US20030046089A1 (en) * 2001-03-23 2003-03-06 Restaurant Services, Inc. System, method and computer program product for an access-based revenue model involving a supply chain management framework
US20030050876A1 (en) * 1998-11-17 2003-03-13 Staas & Halsey Llp Accounting system and method for processing transaction data
US20030055783A1 (en) * 2000-11-06 2003-03-20 Cataline Glen R. System and method for optimized funding of electronic transactions
US20030055675A1 (en) * 2001-09-17 2003-03-20 Klein Twennaar Robbert Frank Arrangement and method for tele-commerce with client profiles
US20030055779A1 (en) * 2001-09-06 2003-03-20 Larry Wolf Apparatus and method of collaborative funding of new products and/or services
US6673479B2 (en) * 2001-03-15 2004-01-06 Hydrogenics Corporation System and method for enabling the real time buying and selling of electricity generated by fuel cell powered vehicles
US20040010463A1 (en) * 1996-11-12 2004-01-15 Hahn-Carlson Dean W. Automated transaction processing system and approach
US6684384B1 (en) * 1997-03-28 2004-01-27 International Business Machines Corporation Extensible object oriented framework for general ledger
US20040019562A1 (en) * 2002-06-03 2004-01-29 Viberg Jon Jay Term allowance clearinghouse
US6687713B2 (en) * 2000-02-29 2004-02-03 Groupthink Unlimited, Inc. Budget information, analysis, and projection system and method
US20040034578A1 (en) * 2002-08-16 2004-02-19 Oney Bruce A. Data collection method and report generation apparatus including an automatch function for generating a report illustrating a field order and associated invoice
US6697702B1 (en) * 1999-03-12 2004-02-24 U.S. Bancorp Shipment transaction system and an arrangement thereof
US20040039696A1 (en) * 2002-06-25 2004-02-26 Richard Harmon System and method for executing a payment transaction over a computer network
US20040039693A1 (en) * 2002-06-11 2004-02-26 First Data Corporation Value processing network and methods
US20050015332A1 (en) * 2003-07-18 2005-01-20 Grace Chen Cashless payment system
US20050021363A1 (en) * 2003-07-25 2005-01-27 Stimson Gregory F. Debit card per-transaction charitable contribution
US20050021527A1 (en) * 2003-07-10 2005-01-27 Jian Zhang System for resource accounting for multiple entities in an arbitrary value chain
US6850900B1 (en) * 2000-06-19 2005-02-01 Gary W. Hare Full service secure commercial electronic marketplace
US20050027613A1 (en) * 1997-12-08 2005-02-03 Nippon Steel Corporation Goods dealing apparatus, goods, dealing system, goods dealing method, and storage medium
US20050027651A1 (en) * 2003-07-28 2005-02-03 Devault Ricky W. Transaction workflow and data collection system
US20050033760A1 (en) * 1998-09-01 2005-02-10 Charles Fuller Embedded metadata engines in digital capture devices
US20050033660A1 (en) * 1998-06-29 2005-02-10 Netmarket Group Inc. Interactive computer-implemented system and method for negotiating sale of goods and/or services
US6983278B1 (en) * 2001-04-10 2006-01-03 Arena Solutions, Inc. System and method for access control and for supply chain management via a shared bill of material
US20060004670A1 (en) * 1999-09-24 2006-01-05 Mckenney Mary K System and method for providing payment services in electronic commerce
US20060010058A1 (en) * 2004-07-09 2006-01-12 Microsoft Corporation Multidimensional database currency conversion systems and methods
US6988111B2 (en) * 2001-11-29 2006-01-17 I2 Technologies Us, Inc. Mapping between part numbers that are based on different part numbering schemes
US20060015454A1 (en) * 2004-06-09 2006-01-19 Hahn-Carlson Dean W Distributor-based transaction processing arrangement and approach
US6999943B1 (en) * 2000-03-10 2006-02-14 Doublecredit.Com, Inc. Routing methods and systems for increasing payment transaction volume and profitability
US20060036476A1 (en) * 2004-08-13 2006-02-16 Klem Jeffrey B System and method for tracking information in a business environment
US20060041487A1 (en) * 2003-02-19 2006-02-23 Albert Santalo System and method for managing account receivables
US7162458B1 (en) * 1998-11-16 2007-01-09 Sky Technologies, Llc System and method for process mining
US20070022021A1 (en) * 2000-05-12 2007-01-25 Walker Jay S Systems and methods wherein a buyer purchases products in a plurality of product categories
US7177836B1 (en) * 1999-12-30 2007-02-13 First Data Corporation Method and system for facilitating financial transactions between consumers over the internet
US7181017B1 (en) * 2001-03-23 2007-02-20 David Felsher System and method for secure three-party communications
US7324976B2 (en) * 2004-07-19 2008-01-29 Amazon Technologies, Inc. Automatic authorization of programmatic transactions
US7327952B2 (en) * 2004-07-26 2008-02-05 Pentax Corporation Stage apparatus and camera shake correction apparatus using the stage apparatus
US7475024B1 (en) * 2000-12-13 2009-01-06 Microsoft Corporation System and method for distributing in real-time, inventory data acquired from in-store point of sale terminals
US7496519B2 (en) * 2002-05-10 2009-02-24 U.S. Bank National Association Automated transaction processing system and approach
US20100017315A1 (en) * 2008-07-21 2010-01-21 Hahn-Carlson Dean W Resource-allocation processing system and approach with adaptive-assessment processing
US7660788B1 (en) * 2003-05-23 2010-02-09 E2Open, Inc. Mapping part numbers and other identifiers
US20100049650A1 (en) * 2000-09-05 2010-02-25 Primerevenue, Inc. Factoring system and method
US20110004544A1 (en) * 2003-04-17 2011-01-06 Baum Diane T Environmental audit method
US20110029404A1 (en) * 2006-10-06 2011-02-03 Hahn-Carlson Dean W Transaction payables processing system and approach
US7890395B2 (en) * 2004-05-19 2011-02-15 Turnberry Partners, LP Method and system for processing tax pertaining to a goods and services transaction
US8103575B1 (en) * 2006-03-27 2012-01-24 Icap Services North America Llc System and method for use in auditing financial transactions
US8126785B2 (en) * 2004-06-09 2012-02-28 Syncada Llc Automated transaction accounting processing engine and approach

Family Cites Families (356)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4412287A (en) 1975-05-29 1983-10-25 Braddock Iii Walter D Automated stock exchange
US4114027A (en) 1976-09-13 1978-09-12 The Mosler Safe Company On-line/off-line automated banking system
US4270042A (en) 1977-08-01 1981-05-26 Case John M Electronic funds transfer system
FR2543327A1 (en) 1978-05-29 1984-09-28 Glay Jean Louis Data communications or remote canvassing, for financially guaranteed external commerce
US4305059A (en) 1980-01-03 1981-12-08 Benton William M Modular funds transfer system
US4713761A (en) 1985-07-18 1987-12-15 Pitney Bowes, Inc. System for centralized processing of accounting and payment functions
US5222018A (en) 1985-07-18 1993-06-22 Pitney Bowes Inc. System for centralized processing of accounting and payment functions
US5218188A (en) 1989-10-24 1993-06-08 Norand Corporation Compact hand-held RF data terminal
US4750119A (en) 1986-10-10 1988-06-07 Tradevest, Inc. Purchasing system with rebate feature
US5025372A (en) 1987-09-17 1991-06-18 Meridian Enterprises, Inc. System and method for administration of incentive award program through use of credit
JP2698588B2 (en) 1987-11-13 1998-01-19 株式会社東芝 Portable electronic devices
US4871258A (en) 1988-04-29 1989-10-03 Boehringer Mannheim Corporation Color test meter
US4926325A (en) 1988-08-23 1990-05-15 Moneyfax, Inc. Apparatus for carrying out financial transactions via a facsimile machine
US5054096A (en) 1988-10-24 1991-10-01 Empire Blue Cross/Blue Shield Method and apparatus for converting documents into electronic data for transaction processing
US4949272A (en) 1988-12-16 1990-08-14 Pitney Bowes Inc. Flexible billing rate for mail communication systems
US5077694A (en) 1988-12-16 1991-12-31 Pitney Bowes Inc. Distribution mailing system having a control database for storing mail handling categories common to the databases of selected mailer stations
US5008827A (en) 1988-12-16 1991-04-16 Pitney Bowes Inc. Central postage data communication network
US5161109A (en) 1988-12-16 1992-11-03 Pitney Bowes Inc. Up/down loading of databases
US4960981A (en) 1989-01-17 1990-10-02 Moneyfax, Inc. Method of and system for electronic funds transfer via facsimile machines
US5040132A (en) 1989-03-15 1991-08-13 Pitney Bowes Inc. System for preparing shipping documents
DE69023705T2 (en) 1989-05-25 1996-07-04 Reuters Ltd Distributed system and method for establishing business relationships between buyers and sellers.
US5159667A (en) 1989-05-31 1992-10-27 Borrey Roland G Document identification by characteristics matching
CA2025170A1 (en) 1989-09-28 1991-03-29 John W. White Portable and dynamic distributed applications architecture
US5043908A (en) 1989-10-03 1991-08-27 Pitney Bowes Inc. Mail delivery system with arrival monitoring
ZA907106B (en) 1989-10-06 1991-09-25 Net 1 Products Pty Ltd Funds transfer system
US5202981A (en) 1989-10-23 1993-04-13 International Business Machines Corporation Process and apparatus for manipulating a boundless data stream in an object oriented programming system
US5168444A (en) 1989-11-15 1992-12-01 Teknekron Transportation Systems Shipment system including processing of document images
US5220501A (en) 1989-12-08 1993-06-15 Online Resources, Ltd. Method and system for remote delivery of retail banking services
US5153842A (en) 1990-02-05 1992-10-06 Pitney Bowes Inc. Integrated circuit package label and/or manifest system
US5117364A (en) 1990-03-02 1992-05-26 Barns Slavin Ileana D Carrier management method and system having auto-rate shopping
US5151948A (en) 1990-03-12 1992-09-29 International Business Machines Corporation System and method for processing documents having amounts recorded thereon
US5231569A (en) 1990-06-12 1993-07-27 Sears Payment Systems, Inc. Account transaction system
CA2059078C (en) 1991-02-27 1995-10-03 Alexander G. Fraser Mediation of transactions by a communications system
US5426281A (en) 1991-08-22 1995-06-20 Abecassis; Max Transaction protection system
US5208446A (en) 1991-09-19 1993-05-04 Martinez Jerry R Method and apparatus for validating credit information during home delivery of order
CA2091640A1 (en) 1991-09-19 1994-09-16 Jerry R. Martinez Method and apparatus for validating credit information during home delivery of order
GB9121995D0 (en) 1991-10-16 1991-11-27 Jonhig Ltd Value transfer system
US7448063B2 (en) 1991-11-25 2008-11-04 Actv, Inc. Digital interactive system for providing full interactivity with live programming events
US7079176B1 (en) 1991-11-25 2006-07-18 Actv, Inc. Digital interactive system for providing full interactivity with live programming events
US5428210A (en) 1992-01-10 1995-06-27 National Bancard Corporation Data card terminal with embossed character reader and signature capture
US5334823A (en) 1992-01-10 1994-08-02 National Bancard Corporation Systems and methods for operating data card terminals for transaction chargeback protection
US5238349A (en) 1992-03-10 1993-08-24 Grace Sr Robert W Article sorting and retrieval system
US5337246A (en) 1992-05-22 1994-08-09 Pitney Bowes Inc. Flexible apparatus and method for applying customized rating adjustments to transaction charges
US6323894B1 (en) 1993-03-12 2001-11-27 Telebuyer, Llc Commercial product routing system with video vending capability
US5594936A (en) 1993-04-16 1997-01-14 Trans Video Electronics, Inc. Global digital video news distribution system
US6275813B1 (en) 1993-04-22 2001-08-14 George B. Berka Method and device for posting financial transactions in computerized accounting systems
RU2183854C2 (en) 1993-05-20 2002-06-20 Мур Бизнес Формз, Инк. System of applications and application accompanying system
US5794207A (en) 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US5666493A (en) 1993-08-24 1997-09-09 Lykes Bros., Inc. System for managing customer orders and method of implementation
US5920847A (en) 1993-11-01 1999-07-06 Visa International Service Association Electronic bill pay system
JPH07194139A (en) 1993-12-27 1995-07-28 Hitachi Ltd Cooling device of inverter for electric automobile
US5649117A (en) 1994-06-03 1997-07-15 Midwest Payment Systems System and method for paying bills and other obligations including selective payor and payee controls
US6996542B1 (en) 1994-06-03 2006-02-07 Midwest Payment Systems System and method for paying bills and other obligations including selective payor and payee controls
US5978567A (en) 1994-07-27 1999-11-02 Instant Video Technologies Inc. System for distribution of interactive multimedia and linear programs by enabling program webs which include control scripts to define presentation by client transceiver
GB9416673D0 (en) 1994-08-17 1994-10-12 Reuters Ltd Data exchange filtering system
WO1996008095A1 (en) 1994-09-08 1996-03-14 Virtex Communications, Inc. Method and apparatus for electronic distribution of digital multi-media information
DK0787334T3 (en) 1994-10-14 1999-05-03 United Parcel Service Inc Multistage packet tracking system
US5754854A (en) 1994-11-14 1998-05-19 Microsoft Corporation Method and system for providing a group of parallel resources as a proxy for a single shared resource
US5774170A (en) 1994-12-13 1998-06-30 Hite; Kenneth C. System and method for delivering targeted advertisements to consumers
US5652749A (en) 1995-02-03 1997-07-29 International Business Machines Corporation Apparatus and method for segmentation and time synchronization of the transmission of a multiple program multimedia data stream
US7165174B1 (en) 1995-02-13 2007-01-16 Intertrust Technologies Corp. Trusted infrastructure support systems, methods and techniques for secure electronic commerce transaction and rights management
US5892900A (en) 1996-08-30 1999-04-06 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
EP1431864B2 (en) 1995-02-13 2012-08-22 Intertrust Technologies Corporation Systems and methods for secure transaction management and electronic rights protection
US7124302B2 (en) 1995-02-13 2006-10-17 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US6658568B1 (en) 1995-02-13 2003-12-02 Intertrust Technologies Corporation Trusted infrastructure support system, methods and techniques for secure electronic commerce transaction and rights management
US5930363A (en) 1995-03-17 1999-07-27 Transmo Limited Card charging systems
US5671362A (en) 1995-04-04 1997-09-23 Cowe; Alan B. Materials monitoring systems, materials management systems and related methods
US5677955A (en) 1995-04-07 1997-10-14 Financial Services Technology Consortium Electronic funds transfer instruments
US6889194B1 (en) 1995-06-01 2005-05-03 United Parcel Service Of America, Inc. Method and system for preparing an electronic record for shipping a parcel
US5799286A (en) 1995-06-07 1998-08-25 Electronic Data Systems Corporation Automated activity-based management system
US5893080A (en) 1995-07-25 1999-04-06 Bottomline Technologies, Inc. Disbursement system and method
US6223168B1 (en) 1995-07-25 2001-04-24 Bottomline Technologies, Inc. Automatic remittance delivery system
US7133835B1 (en) 1995-08-08 2006-11-07 Cxn, Inc. Online exchange market system with a buyer auction and a seller auction
US20050075964A1 (en) 1995-08-15 2005-04-07 Michael F. Quinn Trade records information management system
DE19539801C2 (en) 1995-10-26 2001-04-19 Ibm Monitoring transactions with smart cards
US5699528A (en) 1995-10-31 1997-12-16 Mastercard International, Inc. System and method for bill delivery and payment over a communications network
US6058380A (en) 1995-12-08 2000-05-02 Mellon Bank, N.A. System and method for electronically processing invoice information
JP3133243B2 (en) 1995-12-15 2001-02-05 株式会社エヌケーインベストメント Online shopping system
WO1997024688A1 (en) 1995-12-29 1997-07-10 Tele-Communications, Inc. Method and aparatus for processing billing transactions
US5758328A (en) 1996-02-22 1998-05-26 Giovannoli; Joseph Computerized quotation system and method
US20020049832A1 (en) 1996-03-08 2002-04-25 Craig Ullman Enhanced video programming system and method for incorporating and displaying retrieved integrated internet information segments
US5845283A (en) 1996-04-24 1998-12-01 Lingua Teq, Inc. Method and apparatus for rationalizing different data formats in a data management system
US5778187A (en) 1996-05-09 1998-07-07 Netcast Communications Corp. Multicasting method and apparatus
US5924083A (en) 1996-05-29 1999-07-13 Geneva Branch Of Reuters Transaction Services Limited Distributed matching system for displaying a book of credit filtered bids and offers
US6266640B1 (en) 1996-08-06 2001-07-24 Dialogic Corporation Data network with voice verification means
US5918216A (en) 1996-08-22 1999-06-29 Microsoft Corporation Automatic recognition of periods for financial transactions
US5931917A (en) 1996-09-26 1999-08-03 Verifone, Inc. System, method and article of manufacture for a gateway system architecture with system administration information accessible from a browser
US5806063A (en) 1996-10-03 1998-09-08 Mcdonnell Douglas Corporation Date formatting and sorting for dates spanning the turn of the century
US5960407A (en) 1996-10-08 1999-09-28 Vivona; Robert G. Automated market price analysis system
US5995976A (en) 1996-10-11 1999-11-30 Walker Asset Management Limited Partnership Method and apparatus for distributing supplemental information related to printed articles
US6317737B1 (en) 1996-10-18 2001-11-13 Sagent Technologies, Inc. Data descriptions in a database system
US6070150A (en) 1996-10-18 2000-05-30 Microsoft Corporation Electronic bill presentment and payment system
US5917830A (en) 1996-10-18 1999-06-29 General Instrument Corporation Splicing compressed packetized digital video streams
US5790790A (en) 1996-10-24 1998-08-04 Tumbleweed Software Corporation Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof
JPH10143732A (en) 1996-11-12 1998-05-29 Kuresutetsuku Internatl Corp:Kk Automatic vending machine and distribution management system
US7110959B2 (en) 1996-11-12 2006-09-19 Hahn-Carlson Dean W Processing and management of transaction timing characteristics
US20050165699A1 (en) 1996-11-12 2005-07-28 Hahn-Carlson Dean W. Processing and management of transaction timing characteristics
US20070055582A1 (en) 1996-11-12 2007-03-08 Hahn-Carlson Dean W Transaction processing with core and distributor processor implementations
US20080172314A1 (en) 1996-11-12 2008-07-17 Hahn-Carlson Dean W Financial institution-based transaction processing system and approach
US7627499B2 (en) 1996-11-12 2009-12-01 Syncada Llc Automated transaction processing system and approach
US5910896A (en) 1996-11-12 1999-06-08 Hahn-Carlson; Dean W. Shipment transaction system and an arrangement thereof
US8392285B2 (en) 1996-11-12 2013-03-05 Syncada Llc Multi-supplier transaction and payment programmed processing approach with at least one supplier
US6607081B2 (en) 1996-11-15 2003-08-19 Diebold, Incorporated Automated transaction machine system
US6148377A (en) 1996-11-22 2000-11-14 Mangosoft Corporation Shared memory computer networks
US5897645A (en) 1996-11-22 1999-04-27 Electronic Data Systems Corporation Method and system for composing electronic data interchange information
US5987506A (en) 1996-11-22 1999-11-16 Mangosoft Corporation Remote access and geographically distributed computers in a globally addressable storage environment
US6490567B1 (en) 1997-01-15 2002-12-03 At&T Corp. System and method for distributed content electronic commerce
US6167378A (en) 1997-01-21 2000-12-26 Webber, Jr.; Donald Gary Automated back office transaction method and system
WO1998044442A1 (en) 1997-04-02 1998-10-08 Citibank, N.A. Method and system for standardizing and reconciling invoices from vendors
US5991728A (en) 1997-04-30 1999-11-23 Deroyal Industries, Inc. Method and system for the tracking and profiling of supply usage in a health care environment
US6097834A (en) 1997-06-13 2000-08-01 Paystation America Inc. Financial transaction processing systems and methods
US5949044A (en) 1997-06-13 1999-09-07 Walker Asset Management Limited Partnership Method and apparatus for funds and credit line transfers
US5973685A (en) 1997-07-07 1999-10-26 International Business Machines Corporation Scheme for the distribution of multimedia follow-up information
US6826544B1 (en) 1997-07-09 2004-11-30 Advanceme, Inc. Automated loan repayment
US5899980A (en) 1997-08-11 1999-05-04 Trivnet Ltd. Retail method over a wide area network
US5956690A (en) 1997-09-03 1999-09-21 The Detroit Medical Center Bundled billing accounting computer systems
CA2303513A1 (en) 1997-09-15 1999-03-25 Maintenet Corporation Electronic information network for inventory control and transfer
US6832212B1 (en) 1997-09-30 2004-12-14 Ncr Corporation Method and apparatus for manipulating billing and payment information within a browser interface system
US5970475A (en) 1997-10-10 1999-10-19 Intelisys Electronic Commerce, Llc Electronic procurement system and method for trading partners
US6055519A (en) 1997-10-11 2000-04-25 I2 Technologies, Inc. Framework for negotiation and tracking of sale of goods
US6128602A (en) 1997-10-27 2000-10-03 Bank Of America Corporation Open-architecture system for real-time consolidation of information from multiple financial systems
US6442533B1 (en) 1997-10-29 2002-08-27 William H. Hinkle Multi-processing financial transaction processing system
US6047268A (en) 1997-11-04 2000-04-04 A.T.&T. Corporation Method and apparatus for billing for transactions conducted over the internet
US6131087A (en) 1997-11-05 2000-10-10 The Planning Solutions Group, Inc. Method for automatically identifying, matching, and near-matching buyers and sellers in electronic market transactions
US6157924A (en) 1997-11-07 2000-12-05 Bell & Howell Mail Processing Systems Company Systems, methods, and computer program products for delivering information in a preferred medium
US5943670A (en) 1997-11-21 1999-08-24 International Business Machines Corporation System and method for categorizing objects in combined categories
US6085200A (en) 1997-12-23 2000-07-04 Unisys Corporation System and method for arranging database restoration data for efficient data recovery in transaction processing systems
JP4025450B2 (en) 1998-03-06 2007-12-19 三谷産業株式会社 Approval processing apparatus and recording medium recording approval processing program
US6154738A (en) 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US6721715B2 (en) 1998-03-30 2004-04-13 Martin A. Nemzow Method and apparatus for localizing currency valuation independent of the original and objective currencies
US6741968B2 (en) 1998-04-24 2004-05-25 Fuel Partners, L.P. Method for processing information through a clearinghouse
US6879962B1 (en) 1998-05-24 2005-04-12 Joseph D. Smith Logistics system and method
US6366289B1 (en) 1998-07-17 2002-04-02 Microsoft Corporation Method and system for managing a display image in compressed and uncompressed blocks
JP2000048264A (en) 1998-07-27 2000-02-18 Fujitsu Ltd Journal sheets of paper management method, transaction processor and transaction recording journal sheets of paper
US6499036B1 (en) 1998-08-12 2002-12-24 Bank Of America Corporation Method and apparatus for data item movement between disparate sources and hierarchical, object-oriented representation
US6324551B1 (en) 1998-08-31 2001-11-27 Xerox Corporation Self-contained document management based on document properties
WO2000017773A2 (en) 1998-09-18 2000-03-30 I2 Technologies, Inc. System and method for displaying logistics information associated with a supply chain
EP1116132A2 (en) 1998-09-22 2001-07-18 Science Applications International Corporation User-defined dynamic collaborative environments
US6973258B1 (en) 1998-10-02 2005-12-06 Lg Electronics Inc. Method and apparatus for recording digital data streams
US6366829B1 (en) 1998-10-06 2002-04-02 J. P. Donmoyer, Inc. Bulk inventory network system (BINS)
US7131069B1 (en) 1998-10-22 2006-10-31 Made2 Manage Systems, Inc. Navigational interface for ERP system
US20010014878A1 (en) 1998-11-09 2001-08-16 Nilotpal Mitra Transaction method and apparatus
US6254000B1 (en) 1998-11-13 2001-07-03 First Data Corporation System and method for providing a card transaction authorization fraud warning
US6141653A (en) 1998-11-16 2000-10-31 Tradeaccess Inc System for interative, multivariate negotiations over a network
US6260024B1 (en) 1998-12-02 2001-07-10 Gary Shkedy Method and apparatus for facilitating buyer-driven purchase orders on a commercial network system
US6330550B1 (en) 1998-12-30 2001-12-11 Nortel Networks Limited Cross-media notifications for e-commerce
US20040095237A1 (en) 1999-01-09 2004-05-20 Chen Kimball C. Electronic message delivery system utilizable in the monitoring and control of remote equipment and method of same
US6598026B1 (en) 1999-01-25 2003-07-22 Nextag.Com, Inc. Methods and apparatus for brokering transactions
US6539360B1 (en) 1999-02-05 2003-03-25 United Parcel Service Of America, Inc. Special handling processing in a package transportation system
US6493685B1 (en) 1999-02-10 2002-12-10 The Chase Manhattan Bank Electronic account presentation and response system and method
US6246994B1 (en) 1999-02-19 2001-06-12 Therightsize, Inc. System and method for providing standardized individual information
US7590575B2 (en) 1999-03-08 2009-09-15 Microsoft Corporation Method and apparatus for converting, formatting, and displaying currency values
US6477510B1 (en) 1999-03-15 2002-11-05 Andrew Johnson, Inc. Euro booking currency conversion method
US6944595B1 (en) 1999-03-25 2005-09-13 International Business Machines Corporation Apparatus and method for performing conversion between different units of currency using an encapsulated conversion path of exchange rates
WO2000062225A1 (en) 1999-04-08 2000-10-19 Kay Alan F Marketplace system fees enhancing market share and participation
CA2366517C (en) 1999-04-13 2006-11-07 Orbis Patents Limited Person-to-person, person-to-business, business-to-person, and business-to-business financial transaction system
US6789252B1 (en) 1999-04-15 2004-09-07 Miles D. Burke Building business objects and business software applications using dynamic object definitions of ingrediential objects
US6721713B1 (en) 1999-05-27 2004-04-13 Andersen Consulting Llp Business alliance identification in a web architecture framework
US7606760B2 (en) 1999-06-18 2009-10-20 Echarge Corporation Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account
US7340433B1 (en) 1999-07-30 2008-03-04 Orbian Management Limited System and method of transaction settlement using trade credit
AU5840900A (en) 1999-07-30 2001-02-19 Orbian Management Limited System and method of transaction settlement using trade credit
US6873997B1 (en) 1999-08-04 2005-03-29 Agile Software Corporation Data management system and method for automatically propagating information to disparate information systems from a central location
US7120871B1 (en) 1999-09-15 2006-10-10 Actv, Inc. Enhanced video programming system and method utilizing a web page staging area
US7634455B1 (en) 1999-09-23 2009-12-15 Agile Software Corporation Method and apparatus for providing controlled access to software objects and associated documents
US7742967B1 (en) 1999-10-01 2010-06-22 Cardinalcommerce Corporation Secure and efficient payment processing system
US7047219B1 (en) 1999-10-04 2006-05-16 Trade Finance Systems, Inc. Trade finance automation system
US7117170B1 (en) 1999-10-06 2006-10-03 Stamps.Com Inc. Apparatus, systems and methods for applying billing options for multiple carriers for online, multi-carrier, multi-service parcel shipping management
CA2390167A1 (en) 1999-11-05 2001-05-17 Greg E. Smith Payment method and system for online commerce
US6873963B1 (en) 1999-11-30 2005-03-29 Daimlerchrysler Corporation Shipment tracking analysis and reporting system (STARS)
US20010032154A1 (en) 1999-12-17 2001-10-18 Eric Schummer Internet communications and e-commerce platform
US7366684B1 (en) 1999-12-17 2008-04-29 Douglas William B Blind-supply open commerce business system
US6629081B1 (en) 1999-12-22 2003-09-30 Accenture Llp Account settlement and financing in an e-commerce environment
US7069234B1 (en) 1999-12-22 2006-06-27 Accenture Llp Initiating an agreement in an e-commerce environment
US7047210B1 (en) 1999-12-23 2006-05-16 Qwest Communications International Inc. Method and system for auctioning a product on a computer network
US7318047B1 (en) 1999-12-29 2008-01-08 Pitney Bowes Inc. Method and apparatus for providing electronic refunds in an online payment system
US20060206413A1 (en) 2000-01-14 2006-09-14 Van Luchene Andrew S Systems and methods for facilitating a transaction by matching seller information and buyer information
US6829590B1 (en) 2000-01-31 2004-12-07 Goldman, Sachs & Co. Enhanced online sales risk management system
CA2310589A1 (en) 2000-02-06 2001-12-02 Jason Frank Saxon System and method for ordering products or services
US20020062278A1 (en) 2000-02-18 2002-05-23 Ingram Bradley Kent Method and system for international e-commerce
US20050278244A1 (en) 2000-02-22 2005-12-15 Yuan Frank S Auction with methods and mechanisms to avoid fraud
AU2656500A (en) 2000-02-29 2001-09-12 Swisscom Mobile Ag Transaction confirmation method, authentication server and wap server
US7865414B2 (en) 2000-03-01 2011-01-04 Passgate Corporation Method, system and computer readable medium for web site account and e-commerce management from a central location
GB2375863A (en) 2000-03-06 2002-11-27 Wellogix Inc Method and process for providing relevant data comparing proposal alternatives and reconciling proposals invoices and purchase orders with actual costs in a w
US20010032171A1 (en) 2000-03-07 2001-10-18 Brink Jerry Ten System and method for trading commodities
GB2360373A (en) 2000-03-15 2001-09-19 Nadeem Ahmed Computer apparatus for monitoring and updating accountancy records
AUPQ628900A0 (en) 2000-03-16 2000-04-15 Ip3 Systems Pty Ltd E-commerce facilitation
AU2001245754A1 (en) 2000-03-17 2001-10-03 Ebay, Inc. Method and apparatus for facilitating online payment transactions in a network-based transaction facility using multiple payment instruments
US7499875B1 (en) 2000-03-17 2009-03-03 Ebay Inc. Method and apparatus for facilitating online payment transactions in a network-based transaction facility using multiple payment instruments
US20020046125A1 (en) 2000-03-24 2002-04-18 Charles Speicher Systems and methods for correcting supply/demand imbalances in multi-tier exchanges
US7437310B1 (en) 2000-03-27 2008-10-14 International Business Machines Corporation Third party contract depository for E-commerce transactions
US7263506B2 (en) 2000-04-06 2007-08-28 Fair Isaac Corporation Identification and management of fraudulent credit/debit card purchases at merchant ecommerce sites
US7558793B1 (en) 2000-04-10 2009-07-07 Arena Solutions, Inc. System and method for managing data in multiple bills of material over a network
US20010047311A1 (en) 2000-04-13 2001-11-29 Bhavesh Singh Method for communicating, collaborating and transacting commerce via a communication network
WO2001082193A1 (en) 2000-04-26 2001-11-01 Oracle Corporation Many-to-many correspondance: methods and systems for replacing interbank funds transfers
US20020049622A1 (en) 2000-04-27 2002-04-25 Lettich Anthony R. Vertical systems and methods for providing shipping and logistics services, operations and products to an industry
EP1150227A1 (en) 2000-04-28 2001-10-31 Lucent Technologies Inc. Anonymous and secure electronic commerce
US7698240B1 (en) 2000-05-15 2010-04-13 I2 Technologies Us, Inc. System and method for providing electronic financial transaction services
US7133848B2 (en) 2000-05-19 2006-11-07 Manugistics Inc. Dynamic pricing system
US20020065736A1 (en) 2000-05-23 2002-05-30 David Willner Electronic procurement system
US7565326B2 (en) 2000-05-25 2009-07-21 Randle William M Dialect independent multi-dimensional integrator using a normalized language platform and secure controlled access
US20010056395A1 (en) 2000-06-09 2001-12-27 Khan Saadat H. Internet bargaining system
US10185936B2 (en) 2000-06-22 2019-01-22 Jpmorgan Chase Bank, N.A. Method and system for processing internet payments
US20050119980A1 (en) 2000-06-29 2005-06-02 Neat Group Corporation Electronic negotiation systems
US20020055850A1 (en) 2000-07-06 2002-05-09 Powell A. Leigh Commerce exchange system
US20030037100A1 (en) 2000-07-17 2003-02-20 Modelwire, Inc. Streamlined data distribution system for commercial applications
US6751630B1 (en) 2000-07-20 2004-06-15 Ge Medical Technology Services, Inc. Integrated multiple biomedical information sources
US7146337B1 (en) 2000-09-13 2006-12-05 Precept Corporation System and method for originating loans
WO2002011027A1 (en) 2000-07-28 2002-02-07 Union Carbide Chemicals & Plastics Technology Corporation Transport logistics systems and methods
US7130822B1 (en) 2000-07-31 2006-10-31 Cognos Incorporated Budget planning
NO312427B1 (en) 2000-08-04 2002-05-06 Usertrade As Electronic trading system
US6882986B1 (en) 2000-08-07 2005-04-19 Tymetrix Method for automatic processing of invoices
WO2002015098A2 (en) 2000-08-11 2002-02-21 Loy John J Trade receivable processing method and apparatus
US7206768B1 (en) 2000-08-14 2007-04-17 Jpmorgan Chase Bank, N.A. Electronic multiparty accounts receivable and accounts payable system
US8131627B2 (en) 2000-08-17 2012-03-06 Mamoud Sadre Open clearing system
US7099304B2 (en) 2000-09-05 2006-08-29 Flexiworld Technologies, Inc. Apparatus, methods and systems for anonymous communication
US6895438B1 (en) 2000-09-06 2005-05-17 Paul C. Ulrich Telecommunication-based time-management system and method
AU2001288936A1 (en) 2000-09-07 2002-03-22 Closingguard.Com, Inc. System and method of managing financial transactions over an electronic network
WO2002029670A1 (en) 2000-10-02 2002-04-11 Subrao Shenoy Methods and systems for creating and managing capital asset business exchange
US7222081B1 (en) 2000-10-05 2007-05-22 Fujitsu Limited System and method for continuous delivery schedule including automated customer notification
CA2322599A1 (en) 2000-10-06 2002-04-06 Ibm Canada Limited-Ibm Canada Limitee System and method for workflow control of contractual activities
CA2322602A1 (en) 2000-10-06 2002-04-06 Ibm Canada Limited-Ibm Canada Limitee System and method for generating a contract and conducting contractual activities under the contract
WO2002029608A2 (en) 2000-10-06 2002-04-11 Optiant, Inc. System and method for determining the optimum configuration strategy for systems with multiple decision options
US6820038B1 (en) 2001-09-04 2004-11-16 Accenture Global Services Gmbh Component provisioning or issuance in a maintenance, repair or overhaul environment
US6785718B2 (en) 2000-10-23 2004-08-31 Schneider Logistics, Inc. Method and system for interfacing with a shipping service
US8577794B2 (en) 2000-10-24 2013-11-05 Bank Of America Corporation System and method for collecting information to facilitate enrollment in an electronic funds transfer program
CA2324729A1 (en) 2000-10-30 2002-04-30 Ibm Canada Limited-Ibm Canada Limitee System and method for representation of business policy and governing the conduct of business activities using business rules book
JP3982168B2 (en) 2000-11-13 2007-09-26 コクヨ株式会社 Purchasing management system, purchasing management method, and purchasing management program
US20020059134A1 (en) 2000-11-15 2002-05-16 Sun Microsystems, Inc. Flexible and extensible e-commerce architecture
US7266524B1 (en) 2000-11-28 2007-09-04 Goldman Sachs & Co. Method, software program, and system for isolating risk in a financial transaction
US6839692B2 (en) 2000-12-01 2005-01-04 Benedor Corporation Method and apparatus to provide secure purchase transactions over a computer network
US20020107761A1 (en) 2000-12-10 2002-08-08 Donald Kark Methods and systems for improved channel sales support in electronic commerce
US6792459B2 (en) 2000-12-14 2004-09-14 International Business Machines Corporation Verification of service level agreement contracts in a client server environment
JP2002203135A (en) 2000-12-28 2002-07-19 Tokai Bank Ltd Electronic commerce system
US6937992B1 (en) 2000-12-29 2005-08-30 Arrowstream, Inc. Transport vehicle capacity maximization logistics system and method of same
US8311911B2 (en) 2000-12-30 2012-11-13 E*Trade Financial Corporation Global foreign exchange system
US20020095355A1 (en) 2001-01-18 2002-07-18 Doreen A. Labit Computer-implemented international trade system
US8326754B2 (en) 2001-02-05 2012-12-04 Oracle International Corporation Method and system for processing transactions
US6882983B2 (en) 2001-02-05 2005-04-19 Notiva Corporation Method and system for processing transactions
US20020111886A1 (en) 2001-02-12 2002-08-15 Chenevich William L. Payment management
US7509288B2 (en) 2001-02-22 2009-03-24 International Business Machines Corporation Invoice processing system
GB2372616A (en) 2001-02-23 2002-08-28 Hewlett Packard Co Transaction method and apparatus using two part tokens
US7136467B2 (en) 2001-03-02 2006-11-14 Symphony Service Corp Customer-oriented telecommunications data aggregation and analysis method and object oriented system
US20020147655A1 (en) 2001-03-19 2002-10-10 Say Mustafa Erhan Method of exchanging goods by an auction
US20030074206A1 (en) 2001-03-23 2003-04-17 Restaurant Services, Inc. System, method and computer program product for utilizing market demand information for generating revenue
US20020143858A1 (en) 2001-03-29 2002-10-03 William Teague Report scheduler
US20020198829A1 (en) 2001-04-03 2002-12-26 Bottomline Technologies, Inc. Modular business transactions platform
US20020156797A1 (en) 2001-04-04 2002-10-24 Alorica Inc. Method, system, and program for customer service and support management
US7464092B2 (en) 2001-04-04 2008-12-09 Alorica, Inc Method, system and program for customer service and support management
US6963885B2 (en) 2001-04-11 2005-11-08 International Business Machines Corporation System and method for identifying invoices that may be duplicate prior to payment
CA2444238A1 (en) 2001-04-23 2002-10-31 Oracle Corporation Methods and systems for carrying out contingency-dependent payments via secure electronic bank drafts supported by online letters of credit and/or online performance bonds
US20020161719A1 (en) 2001-04-27 2002-10-31 Manning David Franklin Method of and apparatus for on-line enrolment
GB2400963B (en) 2001-05-02 2004-12-29 Virtual Access Ltd Secure payment method and system
WO2002091113A2 (en) 2001-05-03 2002-11-14 Thermodynamic Design, Llc Method and system of exchanging and deriving economic benefit from exchanging securities
GB0110893D0 (en) 2001-05-03 2001-06-27 Gems Dev Organisation The Ltd Transaction management systems
US20020174034A1 (en) 2001-05-17 2002-11-21 International Business Machines Corporation Method and apparatus for a distributed web commerce system
US7730528B2 (en) 2001-06-01 2010-06-01 Symantec Corporation Intelligent secure data manipulation apparatus and method
US20030139985A1 (en) 2001-06-29 2003-07-24 Terri Hollar Lease transaction management and accounting system
US20030126047A1 (en) 2001-06-29 2003-07-03 Terri Hollar Accounting engine for a lease transaction management and accounting system
US20030074298A1 (en) 2001-07-09 2003-04-17 Wolfgang Daum Information product market system and method
US20030158811A1 (en) 2001-07-18 2003-08-21 Ventanex System and method for rules based electronic funds transaction processing
US7203662B2 (en) 2001-07-25 2007-04-10 International Business Machines Corporation Apparatus, system and method for automatically making operational selling decisions
JP2003044778A (en) 2001-07-30 2003-02-14 Fujitsu Ltd Specification notice method, specification notice program, specification displaying method
US7574363B2 (en) 2001-08-23 2009-08-11 International Business Machines Corporation Intelligent merchandise indicator
US7149744B1 (en) 2001-09-27 2006-12-12 I2 Technologies Us, Inc. Third party document storage and reuse
US7054841B1 (en) 2001-09-27 2006-05-30 I2 Technologies Us, Inc. Document storage and classification
US7958049B2 (en) 2001-11-01 2011-06-07 Metavante Corporation System and method for obtaining customer bill information and facilitating bill payment at biller websites
US7536362B2 (en) 2001-11-07 2009-05-19 Ariba, Inc. Method for selecting an optimal balance between direct cost and a number of suppliers
EP1446778A2 (en) 2001-11-14 2004-08-18 Encorus Technologies GmbH Payment protocol and data transmission method and data transmission device for conducting payment transactions
AU2002351195A1 (en) 2001-11-28 2003-06-10 Isuppli Corporation Supply chain network
US7415471B1 (en) 2001-11-30 2008-08-19 Midland Loan Services, Inc. Methods and systems for automated data collection and analysis for use in association with asset securitization
US20030233321A1 (en) 2001-11-30 2003-12-18 Scolini Anthony J. Integrated invoice solution
US20030117446A1 (en) 2001-12-21 2003-06-26 Expeditors International Of Washington Inc. System and method for processing transaction information
US7346575B1 (en) 2002-01-07 2008-03-18 First Data Corporation Systems and methods for selectively delaying financial transactions
US20030135425A1 (en) 2002-01-11 2003-07-17 Leavitt Harold O. Method and apparatus for a cryptographically assisted commercial system designed to facilitate seller driven sales offers
US20030135435A1 (en) 2002-01-15 2003-07-17 Amos Aharoni E-DRAFT collection
US20030144901A1 (en) 2002-01-25 2003-07-31 Coulter Jeffery R. Managing supplier and alliance partner performance data
US20030149674A1 (en) 2002-02-01 2003-08-07 Pakhound, Inc. Shipment monitoring method and system
US7398248B2 (en) 2002-02-08 2008-07-08 Catalina Marketing Corporation System and method for using cards for sponsored programs
CA2477690A1 (en) 2002-03-06 2003-09-18 Siemens Medical Solutions Health Services Corporation System and method for providing a generic health care data repository
US7925576B2 (en) 2002-03-26 2011-04-12 First Data Corporation Systems for processing transponder-based transactions
US8103605B2 (en) 2002-04-12 2012-01-24 Hewlett-Packard Development Company, L.P. Customs information system with selective transaction audit
US7233928B2 (en) 2002-04-12 2007-06-19 Vendavo, Inc. Rule-based system for determining price adjustments in a product catalog
US8050938B1 (en) 2002-04-19 2011-11-01 Greenway Medical Technologies, Inc. Integrated medical software system with enhanced portability
US7363261B2 (en) 2002-05-08 2008-04-22 Regions Asset Company Method, computer program product and system for verifying financial data
US20030212617A1 (en) 2002-05-13 2003-11-13 Stone James S. Accounts payable process
US20030220863A1 (en) 2002-05-24 2003-11-27 Don Holm System and method for varying electronic settlements between buyers and suppliers with dynamic discount terms
AU2003239916A1 (en) 2002-06-03 2003-12-19 Sevenspace System and method for reliable delivery of event information
US7356516B2 (en) 2002-06-13 2008-04-08 Visa U.S.A. Inc. Method and system for facilitating electronic dispute resolution
US7801826B2 (en) 2002-08-08 2010-09-21 Fujitsu Limited Framework and system for purchasing of goods and services
US20040230601A1 (en) 2002-09-09 2004-11-18 Joao Raymond A. Apparatus and method for facilitating shipping commerce
US20070271160A1 (en) 2002-09-12 2007-11-22 The Pnc Financial Services Group, Inc. Accounts payable process
EP1403793A1 (en) 2002-09-27 2004-03-31 Sap Ag Method for automatic integrated document filing in the logging of business transactions
JP2006508427A (en) 2002-10-07 2006-03-09 ガートナー インコーポレイテッド Method and system for assessing business performance
US8577795B2 (en) 2002-10-10 2013-11-05 Convergys Information Management Group, Inc. System and method for revenue and authorization management
US7925569B2 (en) 2002-10-29 2011-04-12 Ebs Group Limited Electronic trading system having increased liquidity provision
US7584192B2 (en) 2002-11-18 2009-09-01 Sap Aktiengesellschaft Collection and analysis of document traffic in an electronic marketplace
US20030093320A1 (en) 2002-11-18 2003-05-15 Sullivan Daniel L. Method, system and computer program product for facilitating a tax transaction
US7603300B2 (en) 2002-11-18 2009-10-13 Sap Aktiengesellschaft Collection and analysis of trading data in an electronic marketplace
WO2004063863A2 (en) 2003-01-08 2004-07-29 Discovery Mining, Inc. Document management apparatus, system and method
US7720732B2 (en) 2003-01-23 2010-05-18 Lortscher Jr Frank D System and method for generating transaction based recommendations
US7340422B2 (en) 2003-02-10 2008-03-04 Asentinel Llc Systems and method for managing and processing of telecommunications invoices
JP2004247947A (en) 2003-02-13 2004-09-02 Olympus Corp Optical apparatus
GB2398894A (en) 2003-02-28 2004-09-01 C6 Ltd A networked computer system for selling/distributing goods/products directly or indirectly to a customer based on the customers status/rating.
US20040172360A1 (en) 2003-02-28 2004-09-02 Mabrey Sheila M. Methods and systems for managing accounts payable
US20040181468A1 (en) 2003-03-12 2004-09-16 Richard Harmon System and method of funding a charity
US8510179B2 (en) 2003-03-24 2013-08-13 Siebel Systems, Inc. Inventory transaction common object
US7005751B2 (en) 2003-04-10 2006-02-28 Formfactor, Inc. Layered microelectronic contact and method for fabricating same
US8260673B2 (en) 2003-05-09 2012-09-04 International Business Machines Corporation Method, system and computer program product for selective data disclosure and contract negotiation in an E-marketplace based on predetermined preferences
US7796744B1 (en) 2003-05-19 2010-09-14 American Teleconferencing Services Dynamic reporting tool for conferencing customers
US7113964B1 (en) 2003-06-05 2006-09-26 Iteration Software, Inc. Method and apparatus for archiving data in a relational database system
US7941353B2 (en) 2003-06-17 2011-05-10 Oracle International Corporation Impacted financial statements
US7257560B2 (en) 2003-07-31 2007-08-14 Cisco Technology, Inc. Cost minimization of services provided by multiple service providers
SG120112A1 (en) 2003-08-06 2006-03-28 Oneempower Pte Ltd Transaction method and system
US20050240592A1 (en) 2003-08-27 2005-10-27 Ascential Software Corporation Real time data integration for supply chain management
US7548884B1 (en) 2003-10-21 2009-06-16 Neil Thomas Computerized process to, for example, automate the home sale, mortgage loan financing and settlement process, and the home mortgage loan refinancing and settlement processes
GB2407658A (en) 2003-10-31 2005-05-04 Daniele Grazioli Computer network for processing received event data
US20050125260A1 (en) 2003-12-08 2005-06-09 Agflex, Inc. Method for quoting and contracting for management of inputs and services under a commercial service agreement, with a service loss guaranty or insurance policy and using an information management system
US7386518B2 (en) 2003-12-16 2008-06-10 Pitney Bowes Inc. Method and system for facilitating transactions
US7958028B2 (en) 2003-12-23 2011-06-07 Sap Ag Enterprise management application providing availability control checks on revenue budgets
US20050149378A1 (en) 2004-01-02 2005-07-07 Cyr Keneth K. System and method for management of clinical supply operations
US8108269B2 (en) 2004-02-27 2012-01-31 Sap Ag Systems and methods for managing product returns using decision codes
AU2005223680B2 (en) 2004-03-18 2011-09-01 Manhattan Associates, Inc. Transportation management system and method for shipment planning optimization
CA2560277A1 (en) 2004-03-19 2005-09-29 Oversight Technologies, Inc. Methods and systems for transaction compliance monitoring
US7373365B2 (en) 2004-04-13 2008-05-13 Satyam Computer Services, Ltd. System and method for automatic indexing and archiving of paper documents
US8660950B2 (en) 2004-04-16 2014-02-25 Wells Fargo, N.A. System and method for bill pay with credit card funding
US7254588B2 (en) 2004-04-26 2007-08-07 Taiwan Semiconductor Manufacturing Company, Ltd. Document management and access control by document's attributes for document query system
US20050251478A1 (en) 2004-05-04 2005-11-10 Aura Yanavi Investment and method for hedging operational risk associated with business events of another
US7822653B2 (en) 2004-06-09 2010-10-26 Syncada Llc Transaction accounting payment and classification system and approach
US7925551B2 (en) 2004-06-09 2011-04-12 Syncada Llc Automated transaction processing system and approach
US20050278255A1 (en) 2004-06-09 2005-12-15 Hahn-Carlson Dean W Transaction data exchange system and approach
US7392934B2 (en) 2004-06-09 2008-07-01 U.S. Bank National Association Transaction accounting processing system and approach
CN101036169A (en) 2004-06-09 2007-09-12 美国银行和许可股份有限公司 Order-resource fulfillment and management system and approach
US7574386B2 (en) 2004-06-09 2009-08-11 U.S. Bank National Association Transaction accounting auditing approach and system therefor
US8762238B2 (en) 2004-06-09 2014-06-24 Syncada Llc Recurring transaction processing system and approach
US8554673B2 (en) 2004-06-17 2013-10-08 Jpmorgan Chase Bank, N.A. Methods and systems for discounts management
US7529706B2 (en) 2004-07-14 2009-05-05 Yahoo! Inc. Systems and methods for performing international money exchanges
EP1659526A3 (en) 2004-11-01 2008-06-04 Sap Ag System and method for management and verification of invoices
US20060167791A1 (en) 2004-12-29 2006-07-27 Hahn-Carlson Dean W Multi-party transaction processing system and approach
US20060167792A1 (en) 2004-12-29 2006-07-27 Hahn-Carlson Dean W Multi-supplier transaction and payment programmed processing system and approach
US20070262140A1 (en) 2005-02-03 2007-11-15 Long Kenneth W Sr Apparatus, System, and Method for Delivering Products or Services
US7970671B2 (en) 2005-04-12 2011-06-28 Syncada Llc Automated transaction processing system and approach with currency conversion
US20060287953A1 (en) 2005-06-16 2006-12-21 Siamr Solutions, Inc. Global web-based financial remitance system and process
CA2625907A1 (en) 2005-10-12 2007-04-19 First Data Corporation System and method for authorizing electronic payment transactions
US20070156584A1 (en) 2005-11-22 2007-07-05 Primerevenue, Inc. Supply Chain Financing Systems and Methods
US20070282744A1 (en) 2005-11-22 2007-12-06 Primerevenue, Inc. Supply chain financing and credit memo systems and methods
US20070214077A1 (en) 2006-02-21 2007-09-13 Primerevenue, Inc. Systems and methods for asset based lending (abl) valuation and pricing
US20070282724A1 (en) 2006-02-21 2007-12-06 Primerevenue, Inc. Asset based lending (abl) systems and methods
US20070299769A1 (en) * 2006-06-21 2007-12-27 E-Net Financial Services, Inc. Lender selection system and method
US8712884B2 (en) 2006-10-06 2014-04-29 Syncada Llc Transaction finance processing system and approach
US7725372B2 (en) 2006-10-06 2010-05-25 Syncada Llc Transaction payables processing system and approach
GB0621189D0 (en) 2006-10-25 2006-12-06 Payfont Ltd Secure authentication and payment system
US20080215456A1 (en) 2006-11-14 2008-09-04 Auctionpal, Llc Systems and methods for facilitating exchanges of items
US8751337B2 (en) 2008-01-25 2014-06-10 Syncada Llc Inventory-based payment processing system and approach
EP2321775A4 (en) 2008-07-21 2013-10-02 Syncada Llc Resource-allocation processing system and approach with resource pooling
WO2010062974A1 (en) 2008-11-26 2010-06-03 Syncada Llc Methods and arrangements involving adaptive auditing and rating for disparate data processing
US20100205054A1 (en) 2009-02-06 2010-08-12 Hahn-Carlson Dean W Contingency-based electronic auditing

Patent Citations (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4507778A (en) * 1981-10-30 1985-03-26 Fuji Xerox Co., Ltd. Digital transmission system
US4996662A (en) * 1983-10-03 1991-02-26 Wang Laboratories, Inc. Method for generating document using tables storing pointers and indexes
US4567359A (en) * 1984-05-24 1986-01-28 Lockwood Lawrence B Automatic information, goods and services dispensing system
US4725719A (en) * 1986-07-21 1988-02-16 First City National Bank Of Austin Restricted purpose, commercial, monetary regulation method
US4799156A (en) * 1986-10-01 1989-01-17 Strategic Processing Corporation Interactive market management system
US4995112A (en) * 1988-07-05 1991-02-19 Kabushiki Kaisha Toshiba Security system
US4992940A (en) * 1989-03-13 1991-02-12 H-Renee, Incorporated System and method for automated selection of equipment for purchase through input of user desired specifications
US6043819A (en) * 1990-01-16 2000-03-28 Digital Image Systems, Corp Image based document processing and information management system and apparatus
US5285383A (en) * 1990-09-14 1994-02-08 Plains Cotton Cooperative Association Method for carrying out transactions of goods using electronic title
US5712990A (en) * 1991-10-03 1998-01-27 International Technology Corporation Of California Economical automated process for averting physical dangers to people, wildlife or environment due to hazardous waste
US5393963A (en) * 1992-03-17 1995-02-28 Company Chex, Inc. Check authorization system and process
US5293310A (en) * 1992-05-22 1994-03-08 Pitney Bowes Inc. Flexible method for applying customized rating adjustments to transaction charges
US5483445A (en) * 1992-10-22 1996-01-09 American Express Trs Automated billing consolidation system and method
US5719771A (en) * 1993-02-24 1998-02-17 Amsc Subsidiary Corporation System for mapping occurrences of conditions in a transport route
US5485369A (en) * 1993-09-28 1996-01-16 Tandata Corporation Logistics system for automating tansportation of goods
US5500513A (en) * 1994-05-11 1996-03-19 Visa International Automated purchasing control system
US6029140A (en) * 1994-07-21 2000-02-22 Micron Technology, Inc. On-time delivery, tracking and reporting
US6505172B1 (en) * 1994-08-10 2003-01-07 Eplus Inc. Electronic sourcing system
US5717989A (en) * 1994-10-13 1998-02-10 Full Service Trade System Ltd. Full service trade system
US5732400A (en) * 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US6012041A (en) * 1996-03-01 2000-01-04 I.S.R. (Logistics) Limited Apparatus for the control of inventory
US6026374A (en) * 1996-05-30 2000-02-15 International Business Machines Corporation System and method for generating trusted descriptions of information products
US5870719A (en) * 1996-07-03 1999-02-09 Sun Microsystems, Inc. Platform-independent, usage-independent, and access-independent distributed quote configuraton system
US6029150A (en) * 1996-10-04 2000-02-22 Certco, Llc Payment and transactions in electronic commerce system
US20040010463A1 (en) * 1996-11-12 2004-01-15 Hahn-Carlson Dean W. Automated transaction processing system and approach
US6021202A (en) * 1996-12-20 2000-02-01 Financial Services Technology Consortium Method and system for processing electronic documents
US6209095B1 (en) * 1996-12-20 2001-03-27 Financial Services Technology Consortium Method and system for processing electronic documents
US6684384B1 (en) * 1997-03-28 2004-01-27 International Business Machines Corporation Extensible object oriented framework for general ledger
US6199046B1 (en) * 1997-07-29 2001-03-06 Adsura Pty Ltd. Method system and article of manufacture for performing real time currency conversion
US6044362A (en) * 1997-09-08 2000-03-28 Neely; R. Alan Electronic invoicing and payment system
US20050027613A1 (en) * 1997-12-08 2005-02-03 Nippon Steel Corporation Goods dealing apparatus, goods, dealing system, goods dealing method, and storage medium
US6016477A (en) * 1997-12-18 2000-01-18 International Business Machines Corporation Method and apparatus for identifying applicable business rules
US20050033660A1 (en) * 1998-06-29 2005-02-10 Netmarket Group Inc. Interactive computer-implemented system and method for negotiating sale of goods and/or services
US20050033760A1 (en) * 1998-09-01 2005-02-10 Charles Fuller Embedded metadata engines in digital capture devices
US20030026404A1 (en) * 1998-09-15 2003-02-06 Joyce Simon James Convergent communications system and method with a rule set for authorizing, debiting, settling and recharging a mobile commerce account
US6357042B2 (en) * 1998-09-16 2002-03-12 Anand Srinivasan Method and apparatus for multiplexing separately-authored metadata for insertion into a video data stream
US7162458B1 (en) * 1998-11-16 2007-01-09 Sky Technologies, Llc System and method for process mining
US20030050876A1 (en) * 1998-11-17 2003-03-13 Staas & Halsey Llp Accounting system and method for processing transaction data
US6169542B1 (en) * 1998-12-14 2001-01-02 Gte Main Street Incorporated Method of delivering advertising through an interactive video distribution system
US6507826B1 (en) * 1999-01-29 2003-01-14 Koriel, Inc. Remote electronic invoice entry and validation system and method therefor
US6697702B1 (en) * 1999-03-12 2004-02-24 U.S. Bancorp Shipment transaction system and an arrangement thereof
US6338044B1 (en) * 1999-03-17 2002-01-08 Loudeye Technologies, Inc. Personal digital content system
US6204763B1 (en) * 1999-03-22 2001-03-20 Jujitsu Limited Household consumable item automatic replenishment system including intelligent refrigerator
US6526443B1 (en) * 1999-05-12 2003-02-25 Sandia Corporation Method and apparatus for managing transactions with connected computers
US20060004670A1 (en) * 1999-09-24 2006-01-05 Mckenney Mary K System and method for providing payment services in electronic commerce
US7177836B1 (en) * 1999-12-30 2007-02-13 First Data Corporation Method and system for facilitating financial transactions between consumers over the internet
US20030033205A1 (en) * 2000-01-10 2003-02-13 D.K. Nowers Method and system for facilitating fulfillment of electronic commercial transactions
US6505169B1 (en) * 2000-01-26 2003-01-07 At&T Corp. Method for adaptive ad insertion in streaming multimedia content
US20020038277A1 (en) * 2000-02-22 2002-03-28 Yuan Frank S. Innovative financing method and system therefor
US6687713B2 (en) * 2000-02-29 2004-02-03 Groupthink Unlimited, Inc. Budget information, analysis, and projection system and method
US6510383B1 (en) * 2000-03-01 2003-01-21 Arrivalstar, Inc. Vehicular route optimization system and method
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
US6999943B1 (en) * 2000-03-10 2006-02-14 Doublecredit.Com, Inc. Routing methods and systems for increasing payment transaction volume and profitability
US20020035488A1 (en) * 2000-04-03 2002-03-21 Anthony Aquila System and method of administering, tracking and managing of claims processing
US20020032649A1 (en) * 2000-04-13 2002-03-14 Balamurugan Selvarajan High-security E-currency IDs for E-commerce transactions
US20020026374A1 (en) * 2000-05-02 2002-02-28 Moneymaker Vincent B. Comprehensive third-party transactional processing and payment in an online environment
US20070022021A1 (en) * 2000-05-12 2007-01-25 Walker Jay S Systems and methods wherein a buyer purchases products in a plurality of product categories
US6850900B1 (en) * 2000-06-19 2005-02-01 Gary W. Hare Full service secure commercial electronic marketplace
US20020016765A1 (en) * 2000-07-11 2002-02-07 David Sacks System and method for third-party payment processing
US20020038305A1 (en) * 2000-08-04 2002-03-28 Bottomline Technologies (De) Inc. Automated invoice receipt and management system
US20100049650A1 (en) * 2000-09-05 2010-02-25 Primerevenue, Inc. Factoring system and method
US20030055783A1 (en) * 2000-11-06 2003-03-20 Cataline Glen R. System and method for optimized funding of electronic transactions
US6510384B2 (en) * 2000-11-15 2003-01-21 International Business Machines Corporation Route search system and route search method
US7475024B1 (en) * 2000-12-13 2009-01-06 Microsoft Corporation System and method for distributing in real-time, inventory data acquired from in-store point of sale terminals
US6673479B2 (en) * 2001-03-15 2004-01-06 Hydrogenics Corporation System and method for enabling the real time buying and selling of electricity generated by fuel cell powered vehicles
US7181017B1 (en) * 2001-03-23 2007-02-20 David Felsher System and method for secure three-party communications
US20030046089A1 (en) * 2001-03-23 2003-03-06 Restaurant Services, Inc. System, method and computer program product for an access-based revenue model involving a supply chain management framework
US6983278B1 (en) * 2001-04-10 2006-01-03 Arena Solutions, Inc. System and method for access control and for supply chain management via a shared bill of material
US20030005876A1 (en) * 2001-06-04 2003-01-09 Anthony Boswell Guide device & car park
US20030033240A1 (en) * 2001-06-11 2003-02-13 Opt4 Derivatives, Inc. Integrated electronic exchange of structured contracts with dynamic risk-based transaction permissioning
US20030014325A1 (en) * 2001-06-27 2003-01-16 Peter Biffar Automatic pricing and negotiation system
US20030004823A1 (en) * 2001-06-28 2003-01-02 Epylon Corporation Integrated procurement system facilitating the sharing of research and purchasing across multiple buying organizations
US20030018563A1 (en) * 2001-07-13 2003-01-23 Efficient Capital Corporation Trading and processing of commercial accounts receivable
US20030041008A1 (en) * 2001-08-22 2003-02-27 William Grey System and method for facilitating transactions among disparate entities
US20030055779A1 (en) * 2001-09-06 2003-03-20 Larry Wolf Apparatus and method of collaborative funding of new products and/or services
US20030055675A1 (en) * 2001-09-17 2003-03-20 Klein Twennaar Robbert Frank Arrangement and method for tele-commerce with client profiles
US6988111B2 (en) * 2001-11-29 2006-01-17 I2 Technologies Us, Inc. Mapping between part numbers that are based on different part numbering schemes
US7496519B2 (en) * 2002-05-10 2009-02-24 U.S. Bank National Association Automated transaction processing system and approach
US20040019562A1 (en) * 2002-06-03 2004-01-29 Viberg Jon Jay Term allowance clearinghouse
US20040039693A1 (en) * 2002-06-11 2004-02-26 First Data Corporation Value processing network and methods
US20040039696A1 (en) * 2002-06-25 2004-02-26 Richard Harmon System and method for executing a payment transaction over a computer network
US20040034578A1 (en) * 2002-08-16 2004-02-19 Oney Bruce A. Data collection method and report generation apparatus including an automatch function for generating a report illustrating a field order and associated invoice
US20060041487A1 (en) * 2003-02-19 2006-02-23 Albert Santalo System and method for managing account receivables
US20110004544A1 (en) * 2003-04-17 2011-01-06 Baum Diane T Environmental audit method
US7660788B1 (en) * 2003-05-23 2010-02-09 E2Open, Inc. Mapping part numbers and other identifiers
US20050021527A1 (en) * 2003-07-10 2005-01-27 Jian Zhang System for resource accounting for multiple entities in an arbitrary value chain
US20050015332A1 (en) * 2003-07-18 2005-01-20 Grace Chen Cashless payment system
US20050021363A1 (en) * 2003-07-25 2005-01-27 Stimson Gregory F. Debit card per-transaction charitable contribution
US20050027651A1 (en) * 2003-07-28 2005-02-03 Devault Ricky W. Transaction workflow and data collection system
US7890395B2 (en) * 2004-05-19 2011-02-15 Turnberry Partners, LP Method and system for processing tax pertaining to a goods and services transaction
US20060015454A1 (en) * 2004-06-09 2006-01-19 Hahn-Carlson Dean W Distributor-based transaction processing arrangement and approach
US8126785B2 (en) * 2004-06-09 2012-02-28 Syncada Llc Automated transaction accounting processing engine and approach
US20060010058A1 (en) * 2004-07-09 2006-01-12 Microsoft Corporation Multidimensional database currency conversion systems and methods
US7324976B2 (en) * 2004-07-19 2008-01-29 Amazon Technologies, Inc. Automatic authorization of programmatic transactions
US7327952B2 (en) * 2004-07-26 2008-02-05 Pentax Corporation Stage apparatus and camera shake correction apparatus using the stage apparatus
US20060036476A1 (en) * 2004-08-13 2006-02-16 Klem Jeffrey B System and method for tracking information in a business environment
US8103575B1 (en) * 2006-03-27 2012-01-24 Icap Services North America Llc System and method for use in auditing financial transactions
US20110029404A1 (en) * 2006-10-06 2011-02-03 Hahn-Carlson Dean W Transaction payables processing system and approach
US20100017315A1 (en) * 2008-07-21 2010-01-21 Hahn-Carlson Dean W Resource-allocation processing system and approach with adaptive-assessment processing

Cited By (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8825549B2 (en) 1996-11-12 2014-09-02 Syncada Llc Transaction processing with core and distributor processor implementations
US8392285B2 (en) 1996-11-12 2013-03-05 Syncada Llc Multi-supplier transaction and payment programmed processing approach with at least one supplier
US8589268B2 (en) 1996-11-12 2013-11-19 Syncada Llc Financial institution-based transaction processing system and approach
US8595099B2 (en) 1996-11-12 2013-11-26 Syncada Llc Financial institution-based transaction processing system and approach
US8396811B1 (en) 1999-02-26 2013-03-12 Syncada Llc Validation approach for auditing a vendor-based transaction
US10152716B2 (en) 2001-02-23 2018-12-11 Riavera Corp. Secure electronic commerce
US20020162027A1 (en) * 2001-02-23 2002-10-31 Mark Itwaru Secure electronic commerce
US8650119B2 (en) 2004-06-09 2014-02-11 Syncada Llc Order-resource fulfillment and management system and approach
US8762238B2 (en) 2004-06-09 2014-06-24 Syncada Llc Recurring transaction processing system and approach
US8560439B2 (en) 2004-06-09 2013-10-15 Syncada Llc Transaction processing with core and distributor processor implementations
US20070156584A1 (en) * 2005-11-22 2007-07-05 Primerevenue, Inc. Supply Chain Financing Systems and Methods
US8712884B2 (en) 2006-10-06 2014-04-29 Syncada Llc Transaction finance processing system and approach
US8055552B2 (en) * 2006-12-22 2011-11-08 Yahoo! Inc. Social network commerce model
US20080154739A1 (en) * 2006-12-22 2008-06-26 Yahoo! Inc Social Network Commerce Model
US8751337B2 (en) 2008-01-25 2014-06-10 Syncada Llc Inventory-based payment processing system and approach
US20100138325A1 (en) * 2008-11-26 2010-06-03 Hahn-Carlson Dean W Methods and arrangements involving adaptive auditing and rating for disparate data processing
US11475492B2 (en) 2010-05-21 2022-10-18 Primerevenue, Inc. Supply chain finance system
US11741513B2 (en) 2010-05-21 2023-08-29 Primerevenue, Inc. Supply chain finance system
US8967480B2 (en) 2011-05-11 2015-03-03 Riarera Corp. System and method for processing funds transfer between entities based on received optical machine readable image information
US10223674B2 (en) * 2011-05-11 2019-03-05 Riavera Corp. Customized transaction flow for multiple transaction types using encoded image representation of transaction information
US9715704B2 (en) 2011-05-11 2017-07-25 Riavera Corp Merchant ordering system using optical machine readable image representation of invoice information
US9721243B2 (en) 2011-05-11 2017-08-01 Riavera Corp. Mobile payment system using subaccounts of account holder
US9734498B2 (en) 2011-05-11 2017-08-15 Riavera Corp Mobile image payment system using short codes
US9785935B2 (en) 2011-05-11 2017-10-10 Riavera Corp. Split mobile payment system
US20130212004A1 (en) * 2011-05-11 2013-08-15 Mark Itwaru Customized transaction flow for multiple transaction types using encoded image representation of transaction information
US11295280B2 (en) 2011-05-11 2022-04-05 Riavera Corp. Customized transaction flow for multiple transaction types using encoded image representation of transaction information
US9547861B2 (en) 2011-05-11 2017-01-17 Mark Itwaru System and method for wireless communication with an IC chip for submission of pin data
US10592943B2 (en) 2011-05-20 2020-03-17 Primerevenue, Inc. Supply chain finance system
US10878498B2 (en) 2012-01-06 2020-12-29 Primerevenue, Inc. Supply chain finance system
US11334942B2 (en) 2012-01-06 2022-05-17 Primerevenue, Inc. Supply chain finance system
US10026120B2 (en) 2012-01-06 2018-07-17 Primerevenue, Inc. Supply chain finance system
US20130254073A1 (en) * 2012-03-23 2013-09-26 Oracle International Corporation System and method for returning individual lines of a purchase requisition for correction and approval
US20140343982A1 (en) * 2013-05-14 2014-11-20 Landmark Graphics Corporation Methods and systems related to workflow mentoring
US11601498B2 (en) 2016-09-12 2023-03-07 Baton Systems, Inc. Reconciliation of data stored on permissioned database storage across independent computing nodes
EP3596679A4 (en) * 2017-03-17 2021-01-06 Baton Systems, Inc. Transaction settlement systems and methods
WO2018237264A1 (en) * 2017-06-22 2018-12-27 Jpmorgan Chase Bank, N.A. System and method for implementing an interbank information network

Also Published As

Publication number Publication date
US20090287598A1 (en) 2009-11-19
US8595099B2 (en) 2013-11-26
US8589268B2 (en) 2013-11-19
US20090307114A1 (en) 2009-12-10

Similar Documents

Publication Publication Date Title
US8589268B2 (en) Financial institution-based transaction processing system and approach
AU2005255453B2 (en) Financial institution-based transaction processing system and approach
AU2005330645B2 (en) Automated transaction processing system and approach with currency conversion
US8825549B2 (en) Transaction processing with core and distributor processor implementations
US8650119B2 (en) Order-resource fulfillment and management system and approach
AU2008200560B2 (en) Financial institution-based transaction processing system and approach
AU2008200685B2 (en) Transaction processing with core and distributor processor implementations

Legal Events

Date Code Title Description
AS Assignment

Owner name: U.S. BANCORP LICENSING, INC., MINNESOTA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HAHN-CARLSON, DEAN W.;REEL/FRAME:016668/0552

Effective date: 20050727

AS Assignment

Owner name: U.S. BANK NATIONAL ASSOCIATION, MINNESOTA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:U.S. BANCORP LICENSING, INC.;REEL/FRAME:020492/0862

Effective date: 20080211

Owner name: U.S. BANK NATIONAL ASSOCIATION,MINNESOTA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:U.S. BANCORP LICENSING, INC.;REEL/FRAME:020492/0862

Effective date: 20080211

AS Assignment

Owner name: SYNCADA LLC, MINNESOTA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:U.S. BANK NATIONAL ASSOCIATION;REEL/FRAME:023254/0091

Effective date: 20090701

Owner name: SYNCADA LLC,MINNESOTA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:U.S. BANK NATIONAL ASSOCIATION;REEL/FRAME:023254/0091

Effective date: 20090701

STCB Information on status: application discontinuation

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