Systems and methods for importing a batch of receiver accounts onto an application platform of a real-time payment network

1. A method of importing a batch of receiver accounts onto an application platform associated with a real-time transaction system, the method comprising:

receiving, at an import receiver account options screen on a graphical user interface of the application platform, a selection to import a receiver file, wherein the receiver file comprises a listing of a plurality of receiver accounts;

determining, subsequent to the receiving, that at least a subset of the plurality of receiver accounts are invalid;

isolating, based on the determining, the subset of the plurality of receiver accounts that are invalid from a remainder of the plurality of receiver accounts that are valid;

presenting, on an imported receiver account results page of the application platform, an indication of the subset of the plurality of receiver accounts that are invalid;

displaying, on the imported receiver account results page, a deficient receiver account download icon;

downloading, upon detecting selection input provided to the deficient receiver account download icon, data associated with each of the subset of the plurality of receiver accounts;

providing the downloaded data in an editable document;

receiving, at the import receiver account options screen on the graphical user interface, another selection to import the editable document containing user edits to portions of the downloaded data for each of the subset of the plurality of receiver accounts;

determining that the subset of the plurality of receiver accounts containing the user edits in the imported editable document are valid; and

updating, responsive to the determining, a receiver accounts record with the subset of the plurality of receiver accounts containing the user edits.

2. The method of claim 1 , further comprising:

determining, subsequent to the receiving and using a processor associated with the real-time transaction system, whether the receiver file is in a predetermined file format; and

automatically converting the receiver file to the predetermined file format responsive to determining that the receiver file is not in the predetermined file format.

3. The method of claim 1 , wherein the determining comprises:

identifying, via analysis of the receiver file, one or more data points associated with each of the plurality of receiver accounts in the listing;

accessing, via communication with another financial entity associated with at least one of the one or more data points, a storage database;

comparing the identified one or more data points against one or more other data points in the storage database; and

ascertaining, based on determining that a discrepancy exists between the identified one or more data points and the one or more other data points, that an error exists in the one or more data points.

4. The method of claim 1 , wherein the presenting the indication comprises displaying, within an import status table on the imported receiver account results page, a deficient accounts table comprising information that identifies: a row location in the receiver file where an error in each of the subset of the plurality of receiver accounts is located, a beneficiary associated with each of the subset of the plurality of receiver accounts, and an error description explaining the error.

5. The method of claim 1 , wherein the presenting the indication comprises displaying, on the imported receiver account results page, a duplicate accounts table that identifies a row location in the receiver file where of one or more duplicate accounts are located.

6. A real-time transaction system, comprising:

one or more computer readable media storing instructions for importing a batch of receiver accounts onto an application platform; and

one or more processors configured to execute the instructions to perform operations comprising:

receiving, at an import receiver account options screen on a graphical user interface of the application platform, a selection to import a receiver file, wherein the receiver file comprises a listing of a plurality of receiver accounts;

determining, subsequent to the receiving, that at least a subset of the plurality of receiver accounts are invalid;

isolating, based on the determining, the subset of the plurality of receiver accounts that are invalid from a remainder of the plurality of receiver accounts that are valid;

presenting, on an imported receiver account results page of the application platform, an indication of the subset of the plurality of receiver accounts that are invalid;

displaying, on the imported receiver account results page, a deficient receiver account download icon;

downloading, upon detecting selection input provided to the deficient receiver account download icon, data associated with each of the subset of the plurality of receiver accounts;

providing the downloaded data in an editable document;

receiving, at the import receiver account options screen on the graphical user interface, another selection to import the editable document containing user edits to portions of the downloaded data for each of the subset of the plurality of receiver accounts;

determining that the subset of the plurality of receiver accounts containing the user edits in the imported editable document are valid; and

updating, responsive to the determining, a receiver accounts record with the subset of the plurality of receiver accounts containing the user edits.

7. The real-time transaction system of claim 6 , further comprising:

determining, subsequent to the receiving and using a processor associated with the real-time transaction system, whether the receiver file is in a predetermined file format; and

automatically converting the receiver file to the predetermined file format responsive to determining that the receiver file is not in the predetermined file format.

8. The real-time transaction system of claim 6 , wherein the determining comprises:

identifying, via analysis of the receiver file, one or more data points associated with each of the plurality of receiver accounts in the listing;

accessing, via communication with another financial entity associated with at least one of the one or more data points, a storage database;

comparing the identified one or more data points against one or more other data points in the storage database; and

ascertaining, based on determining that a discrepancy exists between the identified one or more data points and the one or more other data points, that an error exists in the one or more data points.

9. The real-time transaction system of claim 6 , wherein the presenting the indication comprises displaying, within an import status table on the imported receiver account results page, a deficient accounts table comprising information that identifies: a row location in the receiver file where each of the subset of the plurality of receiver accounts are located, a beneficiary associated with each of the subset of the plurality of receiver accounts, and an error description associated with each of the subset of the plurality of receiver accounts.

10. The real-time transaction system of claim 6 , wherein the presenting the indication comprises displaying, on the imported receiver account results page, a duplicate accounts table that identifies a row location in the receiver file where of one or more duplicate accounts are located.

11. A non-transitory computer-readable medium storing instructions for importing a batch of receivers accounts onto an application platform, the instructions, when executed by one or more processors, causing the one or more processors to perform operations, comprising:

receiving, at an import receiver account options screen on a graphical user interface of the application platform, a selection to import a receiver file, wherein the receiver file comprises a listing of a plurality of receiver accounts;

determining, subsequent to the receiving, that at least a subset of the plurality of receiver accounts are invalid;

isolating, based on the determining, the subset of the plurality of receiver accounts that are invalid from a remainder of the plurality of receiver accounts that are valid;

presenting, on an imported receiver account results page of the application platform, an indication of the subset of the plurality of receiver accounts that are invalid;

displaying, on the imported receiver account results page, a deficient receiver account download icon;

downloading, upon detecting selection input provided to the deficient receiver account download icon, data associated with each of the subset of the plurality of receiver accounts;

providing the downloaded data in an editable document;

receiving, at the import receiver account options screen on the graphical user interface, another selection to import the editable document containing user edits to portions of the downloaded data for each of the subset of the plurality of receiver accounts;

determining that the subset of the plurality of receiver accounts containing the user edits in the imported editable document are valid; and

updating, responsive to the determining, a receiver accounts record with the subset of the plurality of receiver accounts containing the user edits.

12. The non-transitory computer-readable medium of claim 11 , further comprising:

determining, subsequent to the receiving and using a processor associated with a real-time transaction system, whether the receiver file is in a predetermined file format; and

automatically converting the receiver file to the predetermined file format responsive to determining that the receiver file is not in the predetermined file format.

13. The non-transitory computer-readable medium of claim 11 , wherein the determining comprises:

identifying, via analysis of the receiver file, one or more data points associated with each of the plurality of receiver accounts in the listing;

accessing, via communication with another financial entity associated with at least one of the one or more data points, a storage database;

comparing the identified one or more data points against one or more other data points in the storage database; and

ascertaining, based on determining that a discrepancy exists between the identified one or more data points and the one or more other data points, that an error exists in the one or more data points.

14. The non-transitory computer-readable medium of claim 11 , wherein the presenting the indication comprises displaying, within an import status table on the imported receiver account results page, a deficient accounts table comprising information that identifies: a row location in the receiver file where each of the subset of the plurality of receiver accounts are located, a beneficiary associated with each of the subset of the plurality of receiver accounts, and an error description associated with each of the subset of the plurality of receiver accounts.

15. The non-transitory computer-readable medium of claim 11 , wherein the presenting the indication comprises displaying, on the imported receiver account results page, a duplicate accounts table that identifies a row location in the receiver file where of one or more duplicate accounts are located.