System and method for reconciliation of non-currency related transaction account spend

Abstract

A system and method for facilitating automatic reconciliation of transaction card transactions is disclosed, wherein a user may request single-use account codes via the Internet. The system comprises various hardware and software systems to enable a card member, program administrator, or any other designated third-party to request one or more single-use account codes. The requestor may further assign a descriptor for each of the one or more account codes. After receiving a requested account code, the requestor may communicate the account code to a merchant to facilitate a purchase transaction. The system retrieves a list of transactions from the card issuer at regular intervals, matches the account codes in the list to an account code and associated descriptor, and records the reconciled transaction within a database.

1 - 20 . (canceled) 
     
     
         21 . A method at a computerized transaction authorization system comprising:
 receiving, by a programmed transaction listener sub-component of the computerized transaction authorization system, a transaction verification request for a transaction, wherein the transaction verification request specifies a transaction billing account code including a secondary account code;   determining that the secondary account code corresponds to a primary account code; and   comparing, at a programmed authentication sub-component of the computerized transaction authorization system, details of the transaction with an account code descriptor corresponding to the secondary account code to determine whether to verify the transaction based on one or more spending rules, wherein the one or more spending rules are specified as applying to the secondary account code by a user of a primary account corresponding to the primary account code.   
     
     
         22 . The method of  claim 21 , wherein the computerized transaction authorization system is configured to authorize the primary account to be billed in response to verifying the transaction, and wherein the primary account code and secondary account code are each independently usable as transaction billing account codes for transactions. 
     
     
         23 . The method of  claim 21 , further comprising preparing a financial statement corresponding to the primary account, wherein the financial statement includes a list of attempted transactions during a given time period, and wherein the financial statement is organized according to one or more secondary account codes used for the attempted transactions and one or more corresponding account code descriptors. 
     
     
         24 . The method of  claim 21 , wherein the one or more spending rules include a cancellation date that indicates a date on which the secondary account code is void, a transaction amount limit, or a combination thereof. 
     
     
         25 . The method of  claim 21 , further comprising:
 in response to the details of the transaction failing to meet a limit of the account code descriptor, initiating at least one of a decline of the transaction, a partial decline of the transaction, a request to use personal funds, a request to use another account, a request for additional authentication credentials, a request to use loyalty points, a request to charge at least a portion of the transaction to another company, or a combination thereof.   
     
     
         26 . The method of  claim 21 , wherein the account code descriptor includes a use limit comprising a list of authorized service establishments where the secondary account code can be used, a list of authorized locations where the secondary account code can be used, a list of authorized product types for which the secondary account code can be used, a list of authorized manufacturers, an authorized industry, an authorized geographic area where the secondary account code can be used, a list of authorized transaction dates during which the secondary account code can be used, or a combination thereof; and
 wherein the determining whether to verify the transaction includes determining whether the details of the transaction include an indication that the use limit is satisfied.   
     
     
         27 . The method of  claim 21 , further comprising causing recordation of the account code descriptor and the primary account code in association with the transaction in an account database entry corresponding to the primary account. 
     
     
         28 . The method of  claim 21 , wherein the determining whether to verify the transaction further comprises checking a first status associated with the primary account code and a second status associated with the secondary account code. 
     
     
         29 . The method of  claim 28 , further comprising denying the transaction in response to determining that the second status indicates that the secondary account code is locked. 
     
     
         30 . The method of  claim 21 , further comprising receiving a second transaction verification request corresponding to a second transaction, wherein the second transaction verification request includes the primary account code as a transaction billing account code for the second transaction. 
     
     
         31 . The method of  claim 30 , further comprising causing the primary account to be billed for the second transaction in response to verifying the second transaction. 
     
     
         32 . A system comprising:
 a processor; and   a non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause one or more components of the system to perform operations comprising:   a programmed transaction listener sub-component of the system receiving a transaction verification request corresponding to a transaction, wherein the transaction verification request specifies a transaction billing account code including a secondary account code;   determining that the secondary account code corresponds to a primary account code;   a programmed authentication sub-component of the system verifying the transaction based on the transaction complying with one or more spending rules for the secondary account code, wherein the one or more spending rules are specified by a user of a primary account corresponding to the primary account code; and   in response to verifying the transaction, causing the primary account to be billed for the transaction.   
     
     
         33 . The system of  claim 32 , wherein the operations further comprise:
 preparing a financial statement corresponding to the primary account, wherein the financial statement includes the secondary account code and a corresponding account code descriptor for each transaction billed to the primary account during a given time period.   
     
     
         34 . The system of  claim 32 , wherein the one or more spending rules include at least one of a list of authorized service establishments where the secondary account code can be used, a list of authorized locations where the secondary account code can be used, a list of authorized product types for which the secondary account code can be used, a list of authorized manufacturers, an authorized industry, an authorized geographic area where the secondary account code can be used, or a list of authorized transaction dates during which the secondary account code can be used. 
     
     
         35 . The system of  claim 32 , wherein the operations further comprise:
 receiving a request for the secondary account code from a user of the system;   selecting an unlocked account code from an account number database as the secondary account code;   sending the secondary account code to the user; and   adding an indicator to a locked field for an entry corresponding to the secondary account code in the account number database.   
     
     
         36 . The system of  claim 35 , wherein the operations further comprise:
 recording transaction details corresponding to the transaction at a records database; and   after recording the transaction details, removing the indicator to the locked field for the entry corresponding to the secondary account code.   
     
     
         37 . An article of manufacture including a non-transitory computer-readable medium having instructions stored thereon that, in response to execution by a computer system, cause the computer system to perform operations comprising:
 receiving a transaction verification request for a transaction, wherein the transaction verification request specifies a transaction billing account code that includes a secondary account code;   determining that the secondary account code corresponds to a primary account code;   determining that details of the transaction satisfy one or more spending rules specified as applying to the secondary account code by a user of a primary account corresponding to the primary account code; and   in response to determining that the details satisfy the one or more spending rules, causing the primary account to be billed for the transaction using the primary account code as the transaction billing account code.   
     
     
         38 . The article of  claim 37 , wherein the operations further comprise:
 preparing a financial statement corresponding to the primary account, wherein the financial statement includes a list of transactions during a given time period and a corresponding account code descriptor for each transaction.   
     
     
         39 . The article of  claim 37 , wherein the operations further comprise determining, based on the transaction billing account code, that the primary account is to be charged for the transaction. 
     
     
         40 . The article of  claim 37 , wherein the details of the transaction include at least one of a transaction date, a transaction amount, a service establishment identifier, a transaction geographical location, or a product type.