Domain-specific data records synchronization

1 . A computer-implemented method for programmatically synchronizing a first set of data schemas associated with a computing server and a second data schema associated with a third-party server, comprising:

receiving the first set of data schemas that include a plurality of schemas, the plurality of schemas comprising a first schema corresponding to a first domain belonging to an organization and a second schema corresponding to a second domain belonging to the organization, the first schema defining a first set of externally defined tabular fields and the second schema defining a second set of externally defined tabular fields;

receiving, from the third-party server that operates independently of the computing server, the second data schema that is required to be used in the third-party server;

synchronizing, by the computing server, a server-defined structure for the first set of the plurality of schemas based on the second data schema received from the third-party server, wherein synchronizing the server-defined structure comprises:

identifying a first field that is in the first set of externally defined tabular fields and a second field that is the second set of externally defined tabular fields,

retrieving a third field that is in the second data schema that is required to be used in the third-party server, and

maintaining, in the server-defined structure, a mapping that the first field and the second field both mapped to the third field that is in the second data schema that is required to be used in the third-party server;

receiving, at the computing server, a selection of a parameter-assigning rule of the organization, the parameter-assigning rule being associated with a server-defined structure associated with the computing server, the server-defined structure being independent of the plurality of schemas used by the third-party server, the parameter-assigning rule automatically assigning at least one data parameter to records, the records comprising at least one externally defined tabular field;

recording a first occurrence of a first instance of transaction and a second occurrence of a second instance of transaction that are associated with the organization, wherein the first instance and the second instance are processed as transactions that belong to the organization and are processed according to the server-defined structure;

creating a first data record corresponding to the first instance and a second data record corresponding to the second instance, both the first data record and the second data record automatically assigned with data parameters according to the parameter-assigning rule of the organization associated with the server-defined structure;

determining that the first data record belongs to the first domain and that the second data record belongs to the second domain based on the automatically assigned data parameters;

causing to display, at a graphical user interface, a collection of data records, the collection of data records including the first data record, wherein the collection is displayed with one or more externally defined tabular fields that are defined by the first schema used by the third-party server, wherein one or more values for the externally defined tabular fields are pre-filled based on one or more parameter-assigning rules of the first domain to which the first data record belongs, wherein the graphical user interface allows the one or more values to be manually edited;

receiving a request to export the collection of data records to the third-party server; and

creating a payload for the third-party server, creating the payload comprising applying the mapping the server-defined structure to map the first field and the second field to the third field that is in the second data schema that is required to be used in the third-party server, the payload comprising the data records of the transactions that belong to the organization, wherein the payload comprises (1) a first subset of data records that includes the first data record that is automatically assigned in the third-party server to the first domain and (2) a second subset of data records that includes the second data record that is automatically assigned in the third-party server to the second domain, wherein the first subset of data records in the payload comprises one or more third party externally defined tabular fields in the first set defined by the first schema and converted from the server-defined structure that was independent of the first schema and wherein the second subset of data records in the payload comprises one or more externally defined tabular fields in the second set defined by the second schema and converted from the server-defined structure that was independent of the first schema.

2 . The computer-implemented method of claim 1 , wherein determining that the first data record belongs to the first domain and that the second record belongs to the second domain comprises:

selecting the first domain from a list of domains based on a specific unique identifier associated with the transaction.

3 . The computer-implemented method of claim 1 , further comprising:

receiving, from the third-party server, a set of available values for a specific externally defined tabular field, the set of available values corresponding to values available in the third-party server to be assigned to the specific externally defined tabular field, wherein determining the one or more values for the set of externally defined tabular fields comprises selecting a value from the set of available values received from the third-party server.

4 . The computer-implemented method of claim 1 , wherein creating the payload for the third-party server comprises generating an export file based at least on the one or more values for the set of externally defined tabular fields, and further comprising:

sending the export file to the third-party server to instruct the third-party server to create a third-party data record according to values stored in the export file.

5 . The computer-implemented method of claim 1 , further comprising:

sending an API call to the third-party server to instruct the third-party server to create a third-party data record based at least on the created payload.

6 . The computer-implemented method of claim 1 , further comprising:

receiving, from a client device, a selection of a new domain for the first data record; and

responsive to receiving the selection of the new domain, determining one or more new values for the set of externally defined tabular fields based on the new domain.

7 . The computer-implemented method of claim 1 , further comprising:

receiving, from a client device, a selection of a new domain for the first data record; and

responsive to receiving the selection of the new domain, for each externally defined tabular field of the first data record:

determining whether a value assigned to the externally defined tabular field is included in a list of available values received from the third-party server, and

responsive to determining that the value assigned to the externally defined tabular field is not included in the list of available values, deleting the value from the externally defined tabular field.

8 . The computer-implemented method of claim 1 , wherein the first instance of transaction is a transaction corresponds to a virtual credit card.

9 . A non-transitory computer readable medium configured to store computer code for programmatically synchronizing a first set of data schemas associated with a computing server and a second data schema associated with a third-party server, the computer code comprising instructions, the instructions when executed by a processor, causes the processor to:

receive the first set of data schemas that include a plurality of schemas, the plurality of schemas comprising a first schema corresponding to a first domain belonging to an organization and a second schema corresponding to a second domain belonging to the organization, the first schema defining a first set of externally defined tabular fields and the second schema defining a second set of externally defined tabular fields;

receive, from the third-party server that operates independently of the computing server, the second data schema that is required to be used in the third-party server;

synchronize, by the computing server, a server-defined structure for the first set of the plurality of schemas based on the second data schema received from the third-party server, wherein synchronizing the server-defined structure comprises:

identifying a first field that is in the first set of externally defined tabular fields and a second field that is the second set of externally defined tabular fields,

retrieving a third field that is in the second data schema that is required to be used in the third-party server, and

maintaining, in the server-defined structure, a mapping that the first field and the second field both mapped to the third field that is in the second data schema that is required to be used in the third-party server;

receive, at the computing server, a selection of a parameter-assigning rule of the organization, the parameter-assigning rule being associated with a server-defined structure associated with the computing server, the server-defined structure being independent of the plurality of schemas used by the third-party server, the parameter-assigning rule automatically assigning at least one data parameter to records, the records comprising at least one externally defined tabular field;

record a first occurrence of a first instance of transaction and a second occurrence of a second instance of transaction that are associated with the organization, wherein the first instance and the second instance are processed as transactions that belong to the organization and are processed according to the server-defined structure;

create a first data record corresponding to the first instance and a second data record corresponding to the second instance, both the first data record and the second data record automatically assigned with data parameters according to the parameter-assigning rule of the organization associated with the server-defined structure;

determine that the first data record belongs to the first domain and that the second data record belongs to the second domain based on the automatically assigned data parameters;

cause to display, at a graphical user interface, a collection of data records, the collection of data records including the first data record, wherein the collection is displayed with one or more externally defined tabular fields that are defined by the first schema used by the third-party server, wherein one or more values for the externally defined tabular fields are pre-filled based on one or more parameter-assigning rules of the first domain to which the first data record belongs, wherein the graphical user interface allows the one or more values to be manually edited;

receive a request to export the collection of data records to the third-party server; and

create a payload for the third-party server, creating the payload comprising applying the mapping the server-defined structure to map the first field and the second field to the third field that is in the second data schema that is required to be used in the third-party server, the payload comprising the data records of the transactions that belong to the organization, wherein the payload comprises (1) a first subset of data records that includes the first data record that is automatically assigned in the third-party server to the first domain and (2) a second subset of data records that includes the second data record that is automatically assigned in the third-party server to the second domain, wherein the first subset of data records in the payload comprises one or more externally defined tabular fields in the first set defined by the first schema and converted from the server-defined structure that was independent of the first schema and wherein the second subset of data records in the payload comprises one or more externally defined tabular fields in the second set defined by the second schema and converted from the server-defined structure that was independent of the first schema.

10 . The non-transitory computer readable medium of claim 9 , wherein the instructions that cause the processor to determine that the first data record belongs to the first domain and that the second record belongs to the second domain comprises instructions to:

select the first domain from a list of domains based on a specific unique identifier associated with the transaction.

11 . The non-transitory computer readable medium of claim 9 , wherein the instructions when executed by the processor, further causes the processor to:

receive, from the third-party server, a set of available values for a specific externally defined tabular field, the set of available values corresponding to values available in the third-party server to be assigned to the specific externally defined tabular field,

wherein determining the one or more values for the set of externally defined tabular fields comprises selecting a value from the set of available values received from the third-party server.

12 . The non-transitory computer readable medium of claim 9 , wherein the instructions that cause the processor to create the payload corresponding to the collection of data records for the third-party server comprises instructions to generate an export file based at least on the one or more values for the set of externally defined tabular fields, and further comprising:

send the export file to the third-party server to instruct the third-party server to create a third-party data record according to values stored in the export file.

13 . The non-transitory computer readable medium of claim 9 , wherein the instructions when executed by the processor, further causes the processor to:

send an API call to the third-party server to instruct the third-party server to create a third-party data record based at least on the created payload.

14 . The non-transitory computer readable medium of claim 9 , wherein the instructions when executed by the processor, further causes the processor to:

receive, from a client device, a selection of a new domain for the first data record; and

responsive to receiving the selection of the new domain, determine one or more new values for the set of externally defined tabular fields based on the new domain.

15 . The non-transitory computer readable medium of claim 9 , wherein the instructions when executed by the processor, further causes the processor to:

receive, from a client device, a selection of a new domain for the first data record; and

responsive to receiving the selection of the new domain, for each externally defined tabular field of the first data record:

determine whether a value assigned to the externally defined tabular field is included in a list of available values received from the third-party server, and

responsive to determining that the value assigned to the externally defined tabular field is not included in the list of available values, delete the value from the externally defined tabular field.

16 . A system or programmatically synchronizing a first set of data schemas associated with a computing server and a second data schema associated with a third-party server comprising:

a graphical user interface (GUI) configured to display transaction records for transactions performed by an organization; and

the computing server in communication with the GUI, the computing server comprising a processor and memory, the memory configured to store a set of code instructions, the set of code instructions, when executed by the processor, causes the processor to:

receive the first set of data schemas that include a plurality of schemas, the plurality of schemas comprising a first schema corresponding to a first domain belonging to an organization and a second schema corresponding to a second domain belonging to the organization, the first schema defining a first set of externally defined tabular fields and the second schema defining a second set of externally defined tabular fields;

receive, from the third-party server that operates independently of the computing server, the second data schema that is required to be used in the third-party server;

synchronize, by the computing server, a server-defined structure for the first set of the plurality of schemas based on the second data schema received from the third-party server, wherein synchronizing the server-defined structure comprises:

identifying a first field that is in the first set of externally defined tabular fields and a second field that is the second set of externally defined tabular fields,

retrieving a third field that is in the second data schema that is required to be used in the third-party server, and

maintaining, in the server-defined structure, a mapping that the first field and the second field both mapped to the third field that is in the second data schema that is required to be used in the third-party server;

receive, at the computing server, a selection of a parameter-assigning rule of the organization, the parameter-assigning rule being associated with a server-defined structure associated with the computing server, the server-defined structure being independent of the plurality of schemas used by the third-party server, the parameter-assigning rule automatically assigning at least one data parameter to records, the records comprising at least one externally defined tabular field;

record a first occurrence of a first instance of transaction and a second occurrence of a second instance of transaction that are associated with the organization, wherein the first instance and the second instance are processed as transactions that belong to the organization and are processed according to the server-defined structure;

create a first data record corresponding to the first instance and a second data record corresponding to the second instance, both the first data record and the second data record automatically assigned with data parameters according to the parameter-assigning rule of the organization associated with the server-defined structure;

determine that the first data record belongs to the first domain and that the second data record belongs to the second domain based on the automatically assigned data parameters;

cause to display, at a graphical user interface, a collection of data records, the collection of data records including the first data record, wherein the collection is displayed with one or more externally defined tabular fields that are defined by the first schema used by the third-party server, wherein one or more values for the externally defined tabular fields are pre-filled based on one or more parameter-assigning rules of the first domain to which the first data record belongs, wherein the graphical user interface allows the one or more values to be manually edited;

receive a request to export the collection of data records to the third-party server; and

create a payload for the third-party server, creating the payload comprising applying the mapping the server-defined structure to map the first field and the second field to the third field that is in the second data schema that is required to be used in the third-party server, the payload comprising the data records of the transactions that belong to the organization, wherein the payload comprises (1) a first subset of data records that includes the first data record that is automatically assigned in the third-party server to the first domain and (2) a second subset of data records that includes the second data record that is automatically assigned in the third-party server to the second domain, wherein the first subset of data records in the payload comprises one or more externally defined tabular fields in the first set defined by the first schema and converted from the server-defined structure that was independent of the first schema and wherein the second subset of data records in the payload comprises one or more externally defined tabular fields in the second set defined by the second schema and converted from the server-defined structure that was independent of the first schema.

17 . The system of claim 16 , wherein the instructions that cause the processor to determine that the first data record belongs to the first domain and that the second record belongs to the second domain comprises instructions to:

select the first domain from a list of domains based on a specific unique identifier associated with the transaction.

18 . The system of claim 16 , wherein the instructions when executed by the processor, further causes the processor to:

receive, from the third-party server, a set of available values for a specific externally defined tabular field, the set of available values corresponding to values available in the third-party server to be assigned to the specific externally defined tabular field,

wherein determining the one or more values for the set of externally defined tabular fields comprises selecting a value from the set of available values received from the third-party server.

19 . The system of claim 16 , wherein the instructions that cause the processor to create the payload corresponding to the collection of data records for the third-party server comprises instructions to generate an export file based at least on the one or more values for the set of externally defined tabular fields, and further comprising:

send the export file to the third-party server to instruct the third-party server to create a third-party data record according to values stored in the export file.

20 . The system of claim 16 , wherein the instructions when executed by the processor, further causes the processor to:

receive, from a client device, a selection of a new domain for the first data record; and

responsive to receiving the selection of the new domain, for each externally defined tabular field of the first data record:

determine whether a value assigned to the externally defined tabular field is included in a list of available values received from the third-party server, and

responsive to determining that the value assigned to the externally defined tabular field is not included in the list of available values, delete the value from the externally defined tabular field.