RU2021113362A

RU2021113362A - Purchase management system and method

Info

Publication number: RU2021113362A
Application number: RU2021113362A
Authority: RU
Inventors: Патрик ЭРИКССОН
Original assignee: Еаси Б2Б Аб
Priority date: 2018-12-07
Filing date: 2019-12-06
Publication date: 2023-01-09

Claims

1. Purchase management system (100), comprising a central database (110), a client interface (120) to the central database (110), and a database module (130) associated with the bank, capable of communicating with the transaction authorization module (520) in within the bank (500), while:

- the central data base (110) is capable of receiving from the purchasing organization (200) through the client interface (120) the purchase rules applied to the group (300) of buyers, and contains a central processing means (115) capable of:

- add the selected group (300) of buyers as metadata associated with the first transaction identifier to the central database (110) data;

- add the purchase rules applied to the group (300) of buyers as metadata associated with the first transaction identifier to the central database (110) data; and

- to transfer the metadata associated with the first identifier of the transaction, associated with the bank module (130) database;

- the database module (130) associated with the bank is capable of receiving a request for approval of the purchase from the transaction authorization module (520), containing information about the transaction, including at least the purchase amount associated with the first transaction identifier, and contains a bank processing means (135) capable of:

- decide on the purchase approval request, approving or rejecting it depending on whether the requested purchase satisfies the purchase rules associated with the first transaction identifier in the bank-related database module (130);

- respond to the transaction authorization module (520) by approving or rejecting the purchase approval request;

- add the transaction information received from the transaction authorization module (520) as metadata associated with the first transaction identifier to the database module (130) associated with the bank; and

- transmit information about the transaction associated with the first identifier of the transaction, in the central database (110) data;

- the central means (115) for processing the central database (110) is also capable of transmitting transaction information associated with the first transaction identifier to the buying organization (200), so that the purchase information can be automatically entered into at least one management system of the buying organization ( 200).

2. The system of claim 1, wherein the bank-related database module (130) is located within the bank (500).

3. The system of claim 1 or 2, wherein the purchase rules are applied to a group (300) of purchasers including at least one individual purchaser.

4. The system according to any one of paragraphs. 1-3, in which the buying rules are applied to a group (300) of buyers, including the entire buying organization (200).

5. The system according to any one of paragraphs. 1-4, in which the purchase rules are the general purchase rules for the unit of the purchasing organization (200), and the central processing unit (115) of the central database (110) is able to add the purchase rules applied to the group (300) of buyers as metadata, associated with the first transaction identifier to the central database (110) based on the determination of which department the group (300) of buyers belongs to.

6. The system according to any one of paragraphs. 1-5, in which the transaction information contains information about the merchant, and the banking engine (135) associated with the bank of the database module (130) is able to decide on the request for approval of the purchase by approving or rejecting it, also depending on the information about the merchant .

7. The system according to any one of paragraphs. 1-6, in which the purchase rules indicate the need to add certain metadata associated with the transaction ID to the central database (110) prior to making a purchase, and the banking engine (135) associated with the bank of the database module (130) is able to reject the request to approve the purchase if the bank-related database module (130) does not have this metadata associated with the transaction ID.

8. The system according to any one of paragraphs. 1-7, in which the central means (115) for processing the central database (110) of the data is also capable of transmitting information directly or through the payment card management module (510) within the bank (500) to the organization-issuer (600) of payment cards issuing payment cards for the buying organization (200).

9. The system according to any one of paragraphs. 1-8, in which the central database (110) and the bank-related database module (130) are synchronized and are mirror versions of each other.

10. The system according to any one of paragraphs. 1-9, in which the central database (110) is capable of communicating with a number of different parties (200, 300, 400, 500, 600, 150) and contains adapters (205, 305, 405, 505, 605, 155) capable of converting the data format used by each of these parties into a single data format, preferably a data format defined by the purchasing entity (200).

11. Method (700) for managing purchases, including:

- input (710) through the interface (120) of the client to the central database (110) data of the purchase rules applied to the group (300) of buyers;

- adding (720) the selected group (300) of buyers as metadata associated with the first transaction identifier to the central database (110) data;

- adding (725) the rules of purchases applied to the group (300) of buyers, as metadata associated with the first transaction identifier, in the central database (110) data;

- transferring (730) metadata associated with the first transaction identifier from the central data base (110) to the database module (130) associated with the bank;

- receiving (740) in the module (520) authorization of the transaction, located in the bank (500), the first request for authorization of the transaction associated with the first identifier of the transaction and containing information for authorizing the transaction;

- transmitting (750) a purchase approval request from the transaction authorization module (520) to a bank-related database module (130), wherein the purchase approval request contains information about the transaction, including at least the amount of the purchase;

- deciding (760) on the purchase approval request by approving or rejecting it, depending on whether the requested purchase satisfies the purchase rules associated with the first transaction identifier in the bank-related database module (130);

- response (765) to the module (520) authorizing the transaction by approving or rejecting the purchase approval request;

- a response (770) from the transaction authorization module (520) to the first transaction authorization request associated with the first transaction identifier;

- adding (780) information about the transaction received from the module (520) authorization of the transaction, as metadata associated with the first identifier of the transaction, associated with the bank module (130) database;

- transmitting (785) information about the transaction associated with the first transaction identifier to the central database (110) data; and

transmitting (790) the transaction information associated with the first transaction ID to the purchasing entity (200) so that the purchase information can be automatically entered into at least one management system of the purchasing entity (200).

12. The method of claim 11, wherein the bank-related database module (130) is located within the bank (500).

13. The method of claim. 11 or 12, in which the group (300) buyers includes at least one buying individual.

14. The method according to any one of paragraphs. 11-13, in which the buyer group (300) includes the entire buying organization (200).

15. The method according to any one of paragraphs. 11-14, in which the purchase rules are the general purchase rules for the purchasing entity unit (200), and adding (725) the purchase rules applicable to a group (300) of customers as metadata associated with the first transaction ID to the central database ( 110) of the data includes determining which department a customer group (300) belongs to.

16. The method according to any one of paragraphs. 11-15, in which the transaction information contains information about the seller, and the decision (760) on the request for approval of the purchase by approving or rejecting it also depends on the information about the seller.

17. The method according to any one of paragraphs. 11-16, in which the purchase rules indicate the need to add certain metadata associated with the transaction ID to the central database (110) prior to making a purchase, and the decision (760) on the request for approval of the purchase includes the rejection of the request for approval of the purchase if the bank-related database module (130) does not have this metadata associated with the transaction ID.

18. The method according to any one of paragraphs. 11-17, also including transmitting (705) information from the central data base (110) to the payment card issuing organization (600) directly or through the payment card management module (510) within the bank (500), so that the issuing organization (600) payment cards could issue payment cards for the buying organization (200).

19. The method according to any one of paragraphs. 11-18, wherein transferring (730) the metadata associated with the first transaction ID from the central database (110) to the bank-associated database module (130) and transferring (785) the transaction information associated with the first transaction ID, to the central database (110) include synchronizing the central database (110) and the database module (130) associated with the bank so that they are mirror versions of each other.

20. The method according to any one of paragraphs. 11-19, in which the central database (110) is capable of communicating with a number of different parties (200, 300, 400, 500, 600, 150) and contains adapters (205, 305, 405, 505, 605, 155) that convert the format data used by each of these parties into a single data format, preferably a data format defined by the purchasing entity (200).