WO2024075887A1 - Method for managing payment information and electronic device for supporting same - Google Patents

Abstract

A method for managing information on payment for an ordered item by an electronic device is disclosed, the method comprising the steps of: in response to occurrence of a business event, acquiring business event information at least including order identification information; generating and storing first accounting event information on the basis of the business event information and order information identified on the basis of the order identification information; providing a vendor management server with occurred payment information generated on the basis of the first accounting event information and settlement period information; and in response to the provision of the occurred payment information, generating confirmed payment information on the basis of first information received from the vender management server.

Description

Method for managing payment information and electronic devices that support it

The present invention relates to an electronic device and method for managing payment information, and specifically, a payment information management method and support for confirming the price for ordered and delivered items and performing payment processing for multiple suppliers. It is about electronic devices that

With the development of electronic technology, e-commerce has become a field of shopping. Customers can purchase items online without having to go to a shopping mall, market, or store in person, and items purchased online are delivered to the delivery address requested by the customer.

In the case of e-commerce, the provision of detailed and accurate information about products has a significant impact on service satisfaction, so various ways to provide more detailed and accurate information are being discussed.

The payment information management system for e-commerce services as described above can be operated to effectively manage payments with service providers and item suppliers in order to provide more effective services.

Additionally, in order to effectively operate the above e-commerce service, accounting for the amount paid for the delivered item may be performed.

In relation to this, prior literature such as KR101756594B1 or KR101500849B1 may be referred to.

According to the method of the present invention, the electronic device can effectively manage payment information by dynamically generating data necessary for accounting processing based on various basic data generated according to ordering or inventory management.

According to the method of the present invention, the electronic device can dynamically generate data required for accounting processing based on various basic data generated according to ordering or inventory management to facilitate accounting processing for effective operation of the service.

According to the method of the present invention, an electronic device can manage payment information by adaptively responding to various business processing methods for each vendor when managing multiple suppliers (vendors).

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

Various embodiments may provide a method for managing payment information and an electronic device that supports the same.

A method of managing information about the price of an ordered item performed on an electronic device according to various embodiments disclosed in this document includes business event information including at least order identification information in response to the occurrence of a business event. Obtaining, generating and storing first accounting event information based on ordering information confirmed based on the ordering identification information and the business event information, generating and storing first accounting event information based on settlement cycle information and the first accounting event information. It may include providing accrued payment information to a vendor management server, and generating confirmed payment information based on first information received from the vendor management server in response to the provision of the accrued payment information.

In an embodiment, the business event information may include information about an event type corresponding to the business event, quantity information, and order identification information.

In an embodiment, the event type may include a receipt event and an export event.

In an embodiment, the order information may include at least some of order item information, vendor information, price information, order quantity information, information on tax types, tax rate information, and settlement cycle information.

In an embodiment, the first accounting event information includes at least some of information about the action type corresponding to the business event, quantity information, the order identification information, item information, and vendor information confirmed based on the order information. can do.

In an embodiment, the providing step includes checking the settlement cycle information based on the order information, checking whether a settlement date corresponding to the order information has arrived based on the settlement cycle information, and When the settlement date arrives, the method may further include generating the accrued payment information based on the stored first accounting event information.

In an embodiment, the providing step includes confirming total receipt quantity information corresponding to the order identification information based on the first accounting event information, and accrued payment based on the total receipt quantity information and the order information. A step of generating information may be further included.

In an embodiment, the step of generating the confirmed price information includes generating payment target quantity information based on the first information and the total receipt quantity information, and based on the payment target quantity information and the ordering information. A step of generating confirmed payment information may be further included.

In an embodiment, the step of generating the confirmed payment information includes generating second accounting event information based on the first information, and the confirmed payment information based on the accrued payment information and the second accounting event information. The step of generating may further be included.

In an embodiment, the step of generating the second accounting event information includes generating the second accounting event information based on information regarding whether or not the accrued payment information is approved, which is confirmed based on the first information. may further include.

In an embodiment, the first information includes tax invoice information, and the step of generating the second accounting event information includes checking vendor supply quantity information based on the tax invoice information, and the vendor supply quantity information. And it may further include confirming information regarding whether or not the accrued payment information is approved based on a result of comparing the accrued payment information.

In an embodiment, the payment information management method may further include providing the confirmed payment information to an accounting server.

In an embodiment, the cost information management method includes generating cost of goods sold information of an item corresponding to the ordering information based on the accrued price information and the confirmed price information, and providing the generated cost of goods sold information to an accounting server. Additional steps may be included.

An electronic device according to various embodiments disclosed in this document includes a memory, a transceiver, and a processor, wherein the processor acquires business event information including at least order identification information in response to the occurrence of a business event, Create and store first accounting event information based on ordering information confirmed based on ordering identification information and the business event information, and manage vendor information on settlement cycle information and accrued payment information generated based on the first accounting event information. It may be set to provide to the server and generate confirmed payment information based on the first information received from the vendor management server in response to the provision of the accrued payment information.

According to the method of the present invention, the electronic device provides a method of dynamically generating data required for accounting processing based on various basic data generated according to ordering or inventory management, thereby providing a technical effect in terms of effectively managing payment information. has

According to the method of the present invention, the electronic device presents a method of dynamically generating data required for accounting processing based on various basic data generated according to ordering or inventory management, thereby facilitating accounting processing for effective operation of the service. It has a technical effect in terms of

According to the method of the present invention, the electronic device presents a method of adaptively processing information received from the vendor according to the settlement cycle for each vendor and the data processing method for each vendor, thereby effectively managing payment information according to the characteristics of multiple vendors. It has a technical effect in terms of what it can do.

The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

FIG. 1 is a diagram illustrating a billing information management system in which a method of managing billing information by an electronic device can be implemented according to various embodiments.

FIG. 2 is a diagram illustrating the configuration of an electronic device, a manager device, an accounting server, and a vendor management server according to various embodiments.

Figure 3 is a flowchart of an operation in which an electronic device manages billing information according to various embodiments.

FIG. 4 illustrates functional modules included in an electronic device according to various embodiments.

FIG. 5 is a flowchart of an operation in which an electronic device manages billing information based on first information according to various embodiments.

Figure 6 shows a method of managing payment information according to settlement cycle information according to various embodiments.

Figure 7 shows accounting event information generated by an electronic device according to various embodiments.

FIG. 8 is a flowchart of an operation in which an electronic device generates cost of sales information according to various embodiments.

The following embodiments combine components and features of various embodiments in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form that is not combined with other components or features. Additionally, various embodiments may be configured by combining some components and features. The order of operations described in various embodiments may change. Some features or features of one embodiment may be included in other embodiments or may be replaced with corresponding features or features of other embodiments.

In the description of the drawings, procedures or steps that may obscure the gist of the various embodiments are not described, and procedures or steps that can be understood at the level of a person with ordinary knowledge in the relevant technical field are not described. did.

Throughout the specification, when a part is said to “comprise or include” a certain element, this means that it does not exclude other elements but may further include other elements, unless specifically stated to the contrary. do. In addition, terms such as "... unit", "... unit", and "module" used in the specification refer to a unit that processes at least one function or operation, which refers to hardware, software, or a combination of hardware and software. It can be implemented as: Additionally, the terms “a or an,” “one,” “the,” and similar related terms are used herein in the context of describing various embodiments (particularly in the context of the claims below). Unless otherwise indicated or clearly contradicted by context, it may be used in both singular and plural terms.

Hereinafter, preferred embodiments according to various embodiments will be described in detail with reference to the attached drawings. The detailed description set forth below in conjunction with the accompanying drawings is intended to illustrate exemplary embodiments of various embodiments and is not intended to represent the only embodiment.

In addition, specific terms used in various embodiments are provided to aid understanding of the various embodiments, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the various embodiments. .

At this time, it will be understood that each block of the processing flow diagram diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

FIG. 1 is a diagram illustrating a billing information management system 100 in which a method of managing billing information by an electronic device can be implemented according to various embodiments.

Referring to FIG. 1, a billing information management system 100 according to various embodiments may be implemented in various types of devices. For example, the payment information management system 100 may be implemented in an electronic device 101, an administrator device 102, an accounting server 103, and a vendor management server 104. In other words, the electronic device 101, the manager device 102, the accounting server 103, and the vendor management server 104 are implemented in various embodiments of the present disclosure based on the billing information management system 100 implemented in each device. Operations according to the examples can be performed. Meanwhile, the billing information management system 100 according to various embodiments is not limited to what is shown in FIG. 1, and may be implemented in a wider variety of electronic devices and servers.

The electronic device 101 according to various embodiments performs wireless and wired communication with one or more manager devices 102, accounting server 103, and/or vendor management server 104, and has a large storage capacity. It may be a device containing storage. For example, the electronic device 101 may be a cloud device connected to one or more manager devices 102, accounting server 103, and/or vendor management server 104.

The manager device 102 according to various embodiments may be a device that can be used by an individual user, such as a desktop PC, tablet PC, personal digital assistant (PDA), or mobile terminal. In addition, other electronic devices that perform similar functions may be used as the manager device 102.

The accounting server 103 according to various embodiments performs wireless and wired communication with the electronic device 101, one or more manager devices 102, and/or the vendor management server 104, and has a large storage capacity. It may be a device containing storage. For example, the accounting server 103 may be a cloud device connected to one or more manager devices 102, electronic devices 101, and/or vendor management servers 104.

The vendor management server 104 according to various embodiments performs wireless and wired communication with the electronic device 101, one or more manager devices 102, and/or the accounting server 103, and has a large storage capacity. It may be a device containing storage. For example, the vendor management server 104 may be a cloud device connected to one or more manager devices 102, electronic devices 101, and/or accounting servers 103.

The billing information management system 100 according to various embodiments may include various modules for operation. The modules included in the billing information management system 100 enable the physical device (e.g., electronic device 101) on which the billing information management system 100 is implemented (or included in the physical device) to perform a specified operation. It may be implemented computer code or one or more instructions. In other words, the physical device on which the billing information management system 100 is implemented stores a plurality of modules in the memory in the form of computer code, and when the plurality of modules stored in the memory are executed, the physical device stores the plurality of modules in the memory. It is possible to perform designated operations corresponding to .

FIG. 2 is a diagram illustrating the configuration of an electronic device and a user device according to various embodiments.

Referring to FIG. 2, the electronic device 101, the manager device 102, the accounting server 103, and the vendor management server 104 include an input/output unit 210, a communication unit 220, a storage 230, and a processor. It may include (240).

The input/output unit 210 may be various interfaces or connection ports that receive user input or output information to the user. The input/output unit 210 may include an input module and an output module, and the input module receives user input from the user. User input can take various forms, including key input, touch input, and voice input. Examples of input modules that can receive such user input include traditional keypads, keyboards, and mice, as well as touch sensors that detect the user's touch, microphones that receive voice signals, cameras that recognize gestures through image recognition, etc. A proximity sensor including at least one of an illumination sensor or an infrared sensor that detects user approach, a motion sensor that recognizes user movement through an acceleration sensor or gyro sensor, and various other types of sensors that detect or receive user input. There is an input means, and the input module according to an embodiment of the present disclosure may include at least one of the devices listed above. Here, the touch sensor may be implemented as a piezoelectric or capacitive touch sensor that detects touch through a touch panel or touch film attached to the display panel, or an optical touch sensor that detects touch by an optical method. In addition, the input module may be implemented in the form of an input interface (USB port, PS/2 port, etc.) that connects an external input device that receives user input instead of a device that detects user input itself. Additionally, the output module can output various information. The output module may include at least one of a display that outputs an image, a speaker that outputs sound, a haptic device that generates vibration, and various other types of output means. In addition, the output module may be implemented in the form of a port-type output interface that connects the individual output means described above.

As an example, a display-type output module can display text, still images, and moving images. Displays include liquid crystal display (LCD), light emitting diode (LED) display, organic light emitting diode (OLED) display, flat panel display (FPD), and transparent display. Among various types of devices that can perform image output functions such as display, curved display, flexible display, 3D display, holographic display, projector, and other It can contain at least one. This display may be in the form of a touch display integrated with the touch sensor of the input module.

The communication unit 220 can communicate with other devices. Accordingly, the electronic device 101, the manager device 102, the accounting server 103, and the vendor management server 104 can transmit and receive information with other devices through the communication unit. For example, the electronic device 101, the manager device 102, the accounting server 103, and the vendor management server 104 may communicate with each other or with other devices using a communication unit.

Here, communication, that is, transmission and reception of data, can be accomplished wired or wirelessly. To this end, the communication department includes a wired communication module that connects to the Internet, etc. through a LAN (Local Area Network), a mobile communication module that transmits and receives data by connecting to a mobile communication network through a mobile communication base station, and a WLAN (Wireless Local Area Network) such as Wi-Fi. A short-distance communication module using an Area Network-type communication method or a WPAN (Wireless Personal Area Network)-type communication method such as Bluetooth or Zigbee, and a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System) ) may be composed of a satellite communication module using a satellite communication module or a combination thereof.

Storage 230 can store various types of information. Storage can store data temporarily or semi-permanently. For example, the storage of the electronic device 101 includes an operating program (OS: Operating System) for driving the electronic device 101, a program for generating data or Braille for hosting a website, or an application (e.g., Data related to web applications) may be stored. Additionally, the storage may store modules in the form of computer code as described above.

Examples of storage 230 include hard disk drive (HDD), solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This can be. This storage can be provided as a built-in or detachable type.

The processor 240 controls the overall operation of the electronic device 101, the manager device 102, the accounting server 103, and the vendor management server 104. To this end, the processor 240 can perform computation and processing of various information and control the operation of components of the electronic device 101. For example, the processor 240 may execute a program or application for managing payment information. The processor 240 may be implemented as a computer or similar device using hardware, software, or a combination thereof. In hardware, the processor 240 may be implemented in the form of an electronic circuit that processes electrical signals to perform a control function, and in software, it may be implemented in the form of a program that drives the hardware processor 240. Meanwhile, unless otherwise specified in the following description, the operations of the electronic device 101, the manager device 102, the accounting server 103, and the vendor management server 104 are assumed to be performed under the control of the processor 240. It can be interpreted. That is, when the modules implemented in the above-described payment information management system 100 are executed, the modules are the processor 240 connected to the electronic device 101, the manager device 102, the accounting server 103, and the vendor management server 104. ) can be interpreted as controlling to perform the following operations.

In summary, various embodiments may be implemented through various means. For example, various embodiments may be implemented by hardware, firmware, software, or a combination thereof.

In the case of hardware implementation, methods according to various embodiments include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and FPGAs. It can be implemented by (field programmable gate arrays), processor, controller, microcontroller, microprocessor, etc.

In the case of implementation by firmware or software, methods according to various embodiments may be implemented in the form of modules, procedures, or functions that perform the functions or operations described below. For example, software code can be stored in memory and run by a processor. The memory may be located inside or outside the processor, and may exchange data with the processor through various known means.

Below, various embodiments will be described in more detail based on the above technical idea. The contents described above may be applied to various embodiments described below. For example, operations, functions, terms, etc. that are not defined in various embodiments described below may be performed and explained based on the contents described above.

In the following description, various embodiments will be described on the premise that the electronic device 101 and the manager device 102 perform an operation to manage payment information. According to various embodiments, the electronic device 101 and the manager device 102 The device 102 may transmit and receive information related to the operation of managing payment information with the user device 103.

Figure 3 is a flowchart of an operation in which an electronic device manages billing information according to various embodiments.

According to various embodiments, in operation S301, the electronic device 101 may acquire business event information.

In embodiments, business events may include various types of events related to bill payment. For example, it may include at least some of an ordering event, an ordering information creation event, an ordering information change event, a stocking event, a carryout event, and a shipping event. Business events may include inventory change events. The electronic device 101 may obtain business event information in response to the occurrence of a business event. The business event information may correspond to each event type and correspond to at least one of receipt event information, export event information, order event information, and order change event information. According to one embodiment, business event information may include information about event type, quantity information, and order identification information.

In an embodiment, the inventory change event may include an event in which a change in inventory for payment of an item may occur among business events. Inventory for payment may include inventory of ordered and received items and shipped items. For example, inventory change events may include ordering events, stocking events, and carryout events.

In an embodiment, a receipt event may be understood as an event in which a delivered item is entered into inventory. For example, when an item stocking event occurs, the worker device 102 may obtain stocking event information and provide it to the electronic device 101. The electronic device 101 may obtain warehousing event information from the operator device 102 in response to the warehousing event. According to one embodiment, information about a stocking event provided by the worker device 102 to the electronic device 101 may include basic information about a business event. For example, warehousing event information may include order identification information, information about event type, and quantity information. The worker device 102 may provide at least part of ordering information regarding the received item to the electronic device 101 . According to one embodiment, the worker device 102 may scan the order form corresponding to the item to be received through a sensor included in the input module. The order form may include orderer identification information corresponding to the order. According to one embodiment, the electronic device 101 may generate stock event information based on basic information about a business event. For example, in response to a warehousing event, the electronic device 101 receives information about the event type, quantity information, and order identification information from the operator device 102, and receives order information confirmed based on the order identification information. You can create warehousing event information. Receiving event information may include at least some of event type information, quantity information, item information, order identification information, and vendor information.

In embodiments, a take-out event may be understood as an event in which a delivered item is taken out of inventory. For example, a carry-out event may occur when a received item has a defect, is not marketable, or is returned by a service user after being shipped. For example, when an item export event occurs, the worker device 102 may obtain export event information and provide it to the electronic device 101. The electronic device 101 may obtain export event information from the operator device 102 in response to the export event. According to one embodiment, information about the export event provided by the worker device 102 to the electronic device 101 may include basic information about the business event. For example, export event information may include order identification information, information about event type, and quantity information. The operator device 102 may provide at least part of ordering information regarding the shipped item to the electronic device 101 . According to one embodiment, the worker device 102 may scan the order form corresponding to the item to be exported through a sensor included in the input module. The order form may include orderer identification information corresponding to the order. According to one embodiment, the electronic device 101 may generate export event information based on basic information about a business event. For example, in response to a carry-out event, the electronic device 101 receives information about the event type, quantity information, and order identification information from the operator device 102, and based on the order information confirmed based on the order identification information, You can create export event information. Export event information may include at least some of event type information, quantity information, item information, order identification information, timing information, and vendor information.

In an embodiment, an ordering event may be understood as an event for ordering an item to be delivered to a vendor. The electronic device 101 may obtain order event information in response to the occurrence of an order event. Order event information may include order identification information and order information. For example, when an order event occurs, the worker device 102 may generate order information and order event information and provide them to the electronic device 101 and/or the vendor management server 104. In an embodiment, the ordering information may include at least some of ordering identification information, vendor information, item information, unit price information, ordering quantity information, information on tax types, tax rate information, and settlement cycle information. Order identification information may be provided in response to the occurrence of an order event. According to one embodiment, the electronic device 101 may check settlement cycle information based on vendor information. The electronic device 101 may store vendor management information in advance, and the vendor management information may include vendor information, item information, and settlement cycle information.

In an embodiment, an order change event may occur when order information regarding an existing order is changed. The electronic device 101 may obtain order change event information in response to the occurrence of an order change event. Order change event information may include order identification information and changed order information. For example, when an order change event occurs, the worker device 102 may generate changed order information and order change event information and provide them to the electronic device 101 and/or the vendor management server 104. According to one embodiment, at least some of the order information excluding order identification information may be changed in response to an order change event.

According to various embodiments, in operation S302, the electronic device 101 may generate first accounting event information. The accounting event may include an event regarding data to be processed accountingly by the electronic device 101 in relation to payment. According to one embodiment, an accounting event may occur in response to at least some of the business events.

In embodiments, the first accounting event information may include information for generating accrued payment information. The first accounting event information may include at least some of information about the action type corresponding to the type of business event, quantity information, order identification information, item information, and vendor information. The electronic device 101 may generate first accounting event information based on business event information and order information. At this time, the electronic device 101 confirms the ordering information through the vendor management server 104 based on the ordering identification information corresponding to the business event information, or checks the ordering information through an ordering database loaded with separate ordering information. You can. According to one embodiment, the electronic device 101 may check ordering information corresponding to the business event information based on ordering identification information included in the business event information and generate first accounting event information based on the ordering information. You can. The action type may include type information regarding an arithmetic operation for combining quantity information included in each of the plurality of first accounting event information. For example, action types corresponding to a receipt event and an export event may be defined, respectively. According to one embodiment, each action type may correspond to one or more business events. For example, the action type corresponding to a receipt event and the action type corresponding to an order change event may be defined as 'RECEIVE_TEMP'. According to an embodiment, the electronic device 101 may generate and store a first accounting event. The electronic device 101 may include a separate database for first accounting event information and store the generated first accounting event information.

According to various embodiments, in operation S303, the electronic device 101 may provide accrued payment information. The accrued payment information may include information about the payment for inventory that occurred in response to a receipt event and/or a delivery event that occurred in response to an order. The accrued payment information is, for example, related to an accounts payable (AP) in financial statements, and may specifically correspond to information about an accrual account payable (accrual AP). In an embodiment, the accrued payment information may include quantity information and amount information corresponding to the quantity. The accrued payment information may include the quantity according to the actual receipt event and export event, that is, the quantity information confirmed based on the first accounting event information corresponding to the receipt event information and the first accounting event information corresponding to the export event information. there is. The electronic device 101 may generate accrued payment information by calculating each first accounting event information based on the action type of each first accounting event information. For example, the electronic device 101 may calculate quantity information by adding the quantity included in the first accounting event information according to the stocking event and deleting the quantity included in the first accounting event information according to the export event. The electronic device 101 may receive a message queue containing first accounting event information loaded in the first accounting event database and generate accrued payment information based on the action type. According to one embodiment, the electronic device 101 may generate accrued payment information based on unit price information and quantity information confirmed based on order information. The electronic device 101 may check information about the total quantity received based on the first accounting event information. For example, the electronic device 101 may check the total received quantity excluding the total quantity shipped out from the total quantity received based on the action type and quantity information of each piece of one or more first accounting event information. The electronic device 101 may generate accrued payment information based on total receipt quantity information and order information.

The electronic device 101 may generate accrued payment information based on settlement cycle information and first accounting event information. According to one embodiment, the electronic device 101 may generate accrued payment information based on order information confirmed based on order identification information and first accounting event information. The settlement cycle information may be information about the payment settlement cycle for orders agreed upon for each vendor in the service provided by the electronic device 101. Settlement cycle information may include period information regarding the cycle in which the vendor receives payment, information regarding the settlement date on which the accrued payment is to be settled, and information regarding the deadline by which the vendor must receive payment after delivery. According to one embodiment, the same item delivered by the same vendor may have the same payment settlement cycle even for different orders. According to one embodiment, different orders for different items delivered by the same vendor may have different payment settlement cycles. According to one embodiment, each vendor may have a different payment settlement cycle. According to one embodiment, the electronic device 101 may check the payment settlement cycle corresponding to the vendor information based on vendor information confirmed based on order information. The electronic device 101 may generate accrued payment information based on information about the settlement date confirmed based on the payment settlement cycle. The electronic device 101 may check whether the settlement date corresponding to the order information has arrived based on the settlement cycle information. When the settlement date arrives, the electronic device 101 may generate accrued payment information based on the stored first accounting event information.

In an embodiment, the electronic device 101 may provide the generated accrued payment information to the accounting server 103 and/or the vendor management server 104.

According to various embodiments, in operation S304, the electronic device 101 may receive first information. The first information may include information that the electronic device 101 receives from the vendor management server 104 in response to the provision of accrued payment information. The first information may include information regarding whether the vendor approves the payment incurred. The electronic device 101 may generate second accounting event information based on information regarding whether or not the accrued payment information is approved. According to one embodiment, the first information may include approval information approving accrued payment information or change request information requesting a change in accrued payment information. The electronic device 101 may generate second accounting event information including information about the action type based on the information about approval included in the first information. According to one embodiment, the second accounting event information may include the same action type regardless of approval. For example, if the first information includes change request information for accrued payment information, the electronic device 101 may need to change the accrued payment information. In this case, the electronic device 101 may modify the total receipt quantity information corresponding to the accrued payment information based on the change quantity information included in the change request information. The electronic device 101 may generate second accounting event information including information about the quantity to be changed and action type information about the quantity change. For another example, if the accrued payment information is approved, there may be no need to change the accrued payment information, and in the case where it is not approved (in the case of a change request), even if the action type is the same, information about the quantity to be changed is not available. It can have a value of '0'. Alternatively, the electronic device 101 may generate second accounting event information only when a change to accrued payment information is requested. In an embodiment, the first information may include vendor supply quantity information. For example, the first information may include information regarding the quantity that the vendor claims to have supplied. The electronic device 101 may check information regarding approval based on a comparison result between the quantity claimed to be supplied by the vendor, that is, the quantity information included in the vendor supply quantity information and the accrued payment information. The electronic device 101 may generate second accounting event information regarding an event for modifying accrued payment information based on vendor supply quantity information and accrued payment information.

In embodiments, the first information may include tax invoice information. According to one embodiment, the first information may include tax invoice information provided by the vendor. The tax invoice information may include information about the vendor's tax on the price to be paid for the item delivered by the vendor. According to one embodiment, the electronic device 101 may check vendor supply quantity information based on tax invoice information. The electronic device 101 uses order item information, vendor information, price information, tax type information, tax rate information, and settlement cycle information confirmed based on order information to provide vendor supply quantity information corresponding to tax invoice information. You can check it.

According to one embodiment, tax invoice information may include image data for electronic documents and/or hand-written documents. The electronic device 101 may obtain tax-related information based on tax invoice information. According to one embodiment, the electronic device 101 may perform an optical character recognition (OCR) operation and obtain tax-related information included in tax invoice information based on the OCR operation. The electronic device 101 may check vendor quantity information based on tax information.

According to various embodiments, in operation S305, the electronic device 101 may generate confirmed payment information based on the first information. In the service provided by the electronic device 101, the confirmed payment information may include at least part of information regarding the amount of the confirmed payment to be paid to the vendor and information regarding the quantity to be paid corresponding to the confirmed payment. Confirmed payment information relates to accounts payable (AP) on financial statements, and may specifically correspond to information about actual accounts payable (actual AP). The electronic device 101 may generate confirmed payment information based on information regarding approval included in the first information. For example, when the vendor approves the accrued payment information, the electronic device 101 may generate confirmed payment information that is the same as the accrued payment information. If the vendor does not approve the accrued payment information and requests a change, the electronic device 101 may generate confirmed payment information by changing the accrued payment information based on the vendor supply quantity information included in the first information.

According to one embodiment, the electronic device 101 may generate payment target quantity information based on the first information and accrued payment information. The payment target quantity information may include information about the quantity of the delivery item for which payment is to be made. The electronic device 101 may generate payment target quantity information based on the first information and the total received quantity information. According to one embodiment, the electronic device 101 may generate payment target quantity information based on second accounting event information and accrued payment information. The electronic device 101 may generate confirmed payment information based on payment target quantity information and order information. The electronic device 101 may provide confirmed payment information to the accounting server 103.

FIG. 4 illustrates functional modules included in an electronic device according to various embodiments.

The electronic device 101 according to various embodiments of this document includes an ordering module 410, an inventory management module 420, an event data module 430, an AP module 440, and a database 450 as functional modules. It can be included.

According to various embodiments, the ordering module 410 and the inventory management module 420 may each provide basic information about business events to the event data module 430. According to one embodiment, the event data module 430 generates a queue of messages containing basic information about business events each generated by the ordering module 410 and/or the inventory management module 420, and the basic information about the business event. Business event information can be received based on order identification information included in the information, and business event information can be generated based on basic information about the business event.

For example, when the ordering module 410 generates ordering event information in response to an ordering event, the ordering module 410 sends basic information about the business event, including ordering identification information and ordering information, to the event data module 430. The event data module 430 can generate order event information including order identification information, information about the event type, and order information.

The inventory management module 420 may generate basic information about a receipt event. For example, the inventory management module 420 provides basic information about warehousing events, including order identification information, event type information, and quantity information, to the event data module 430, and the event data module 430 provides order information. Receiving event information may be generated by mapping at least part of the ordering information confirmed based on the identification information, for example, vendor information.

The inventory management module 420 may generate basic information about the export event. For example, the inventory management module 420 provides basic information about the carry-out event, including order identification information, information about the event type, and information about the quantity, to the event data module 430, and the event data module 430 provides the order information. Export event information may be generated by mapping at least part of the order information confirmed based on the identification information, for example, vendor information.

According to various embodiments, the event data module 430 may provide generated business event information to the account payable (AP) module 440. The AP module 440 may generate accounting event information. According to one embodiment, the AP module 440 may generate first accounting event information based on business event information. According to one embodiment, the AP module 440 may generate second accounting event information based on the first information. The AP module 440 may receive business event information based on settlement cycle information confirmed based on order information. For example, the AP module 440 may receive business event information by distinguishing it according to order identification information in response to the settlement cycle. The AP module 440 may store the generated accounting event information in the database 450.

FIG. 5 is a flowchart of an operation in which an electronic device manages billing information based on first information according to various embodiments.

According to various embodiments, in operation S501, the electronic device 101 may receive first information. The first information may include information that the electronic device 101 receives from the vendor management server 104 in response to the provision of accrued payment information. The first information may include information regarding whether the vendor approves the payment incurred. In an embodiment, the first information may include vendor supply quantity information. For example, the first information may include information about the quantity claimed to be supplied by the vendor, that is, vendor supply quantity information. The electronic device 101 may check information regarding approval based on a comparison result between the quantity information included in the vendor supply quantity information and the accrued payment information. The electronic device 101 may generate second accounting event information regarding an event for modifying accrued payment information based on vendor supply quantity information and accrued payment information.

In embodiments, the first information may include tax invoice information. According to one embodiment, the first information may include tax invoice information provided by the vendor. The tax invoice information may include information about the vendor's tax on the price to be paid for the item delivered by the vendor. According to one embodiment, the electronic device 101 may check vendor supply quantity information based on tax invoice information. The electronic device 101 uses order item information, vendor information, price information, tax type information, tax rate information, and settlement cycle information confirmed based on order information to provide vendor supply quantity information corresponding to tax invoice information. You can check it.

According to one embodiment, tax invoice information may include image data for electronic documents and/or hand-written documents. The electronic device 101 may obtain tax-related information based on tax invoice information. According to one embodiment, the electronic device 101 may perform an optical character recognition (OCR) operation and obtain tax-related information included in tax invoice information based on the OCR operation. The electronic device 101 may check vendor quantity information based on tax information.

According to various embodiments, in operation S502, the electronic device 101 may generate second accounting event information based on the first information. According to one embodiment, the electronic device 101 may generate second accounting event information based on information regarding whether or not accrued payment information is approved. According to one embodiment, the first information may include approval information approving accrued payment information or change request information requesting a change in accrued payment information. The electronic device 101 may generate second accounting event information including information about the action type based on the information about approval included in the first information. According to one embodiment, the second accounting event information may include the same action type regardless of approval. For example, if the first information includes change request information for accrued payment information, the electronic device 101 may need to change the accrued payment information. In this case, the electronic device 101 may modify the total receipt quantity information corresponding to the accrued payment information based on the change quantity information included in the change request information. The electronic device 101 may generate second accounting event information including information about the quantity to be changed and action type information about the quantity change. For another example, if the accrued payment information is approved, there may be no need to change the accrued payment information, and in the case where it is not approved (in the case of a change request), even if the action type is the same, information about the quantity to be changed is not available. It can have a value of '0'. Alternatively, the electronic device 101 may generate second accounting event information only when a change to accrued payment information is requested.

According to various embodiments, in operation S305, the electronic device 101 may generate confirmed payment information based on accrued payment information and second accounting event information. In the service provided by the electronic device 101, the confirmed payment information may include at least part of information regarding the amount of the confirmed payment to be paid to the vendor and information regarding the quantity to be paid corresponding to the confirmed payment. The electronic device 101 may generate confirmed payment information based on information regarding approval included in the first information. For example, when the vendor approves the accrued payment information, the electronic device 101 may generate confirmed payment information that is the same as the accrued payment information. If the vendor does not approve the accrued payment information and requests a change, the electronic device 101 may generate confirmed payment information by changing the accrued payment information based on the vendor supply quantity information included in the first information.

According to one embodiment, the electronic device 101 may generate payment target quantity information based on the first information and accrued payment information. The payment target quantity information may include information about the quantity of the delivery item for which payment is to be made. The electronic device 101 may generate payment target quantity information based on the first information and the total received quantity information. According to one embodiment, the electronic device 101 may generate payment target quantity information based on second accounting event information and accrued payment information. The electronic device 101 may generate confirmed payment information based on payment target quantity information and order information. The electronic device 101 may provide confirmed payment information to the accounting server 103. According to one embodiment, the electronic device 101 may provide confirmed payment information to the accounting server 103 and receive information regarding whether or not the confirmed payment information is approved from the accounting server 103. The electronic device 101 may provide confirmed payment information to the vendor management server 104 based on information regarding approval. The vendor management server 104 may pay the price according to the delivery of the item ordered from the vendor based on the confirmed price information.

Figure 6 shows a method of managing payment information according to settlement cycle information according to various embodiments.

According to various embodiments, the electronic device 101 may generate first accounting event information, accrued payment information, second accounting event information, and/or confirmed payment information based on settlement cycle information.

The service provided by the electronic device 101 requests a vendor to deliver an item, that is, places an order, and the vendor can deliver an item corresponding to the order based on settlement cycle information. In response to this, a business event may occur, and the electronic device 101 may obtain business event information in response to the occurrence of the business event.

Referring to Figure 6, orders are periodically placed with the vendor based on certain settlement cycle information, delivery is received, and the payment is settled, and the vendor continuously receives orders based on certain settlement cycle information, makes deliveries, and the payment is settled. It can indicate the case of receiving. In the embodiment of FIG. 6, the delivery deadline is set within the Mth cycle, and it can be understood as a case of an order (e.g., the Mth order) whose settlement date arrives within the (M+1)th cycle. That is, in response to the M-th order with a delivery deadline set within the M-th cycle, confirmed payment information can be generated on the payment date set within the (M+1)-th cycle.

In an embodiment, the electronic device 101 may generate the first accounting event information within the Mth cycle. According to one embodiment, first accounting event information may be generated based on business event information. Business event information may be generated and/or obtained in response to the occurrence of a business event. Since business events such as warehousing and shipment may occur within the M cycle, the electronic device 101 may generate first accounting event information at a time 620 corresponding to the business event that occurred within the M cycle.

In an embodiment, the electronic device 101 may generate accrued payment information on a designated settlement date 630 within the Mth period. For example, the electronic device 101 may load first accounting event information into a database. The electronic device 101 stores the loaded first accounting event information as the settlement date 630 corresponding to the vendor information arrives, and the first accounting event information is confirmed based on the order identification information of the M order corresponding to the vendor information. You can generate accrued payment information by receiving. The settlement date 630 may be confirmed based on the ordering information of the M-th order, vendor information, and/or the M-th order information confirmed based on the vendor information. The electronic device 101 may provide the generated payment information to the accounting server and/or vendor management server in response to the arrival of the settlement date 630. The electronic device 101 may receive first accounting event information for the M order based on vendor information and settlement cycle information. For example, when the settlement date 630, which is confirmed based on the vendor's settlement cycle information, arrives, the electronic device 101 places an order corresponding to the current settlement date 630 among one or more order information corresponding to the vendor, that is, First accounting event information corresponding to the M order can be read from the database to generate accrued payment information.

In an embodiment, the electronic device 101 may generate second accounting event information within the (M+1)th cycle. The electronic device 101 may generate second accounting event information in response to receipt of the first information. For example, the first information may be received from the vendor management server 104 at a predetermined time within the (M+1)th cycle in response to the accrued payment information. The electronic device 101 may generate second accounting event information at a time point 640 corresponding to receipt of the first information.

In an embodiment, the electronic device 101 may generate confirmed payment information in the (M+1)th cycle. The electronic device 101 may generate confirmed payment information in response to the generation of second accounting event information.

In embodiments, electronic device 101 may generate additional accounting event information. Additional accounting event information may include accounting event information generated in response to a business event that does not normally follow settlement cycle information corresponding to a predetermined order. For example, business event information corresponding to the M-th order will be acquired within the M-th cycle, but the business event corresponding to the M-th order may occur after the M-th cycle due to various reasons. For example, it can be assumed that a business event occurs in which an item corresponding to the M order is received or shipped out after the payment corresponding to the M order has been settled based on the confirmed price information. The electronic device 101 acquires business event information in response to the occurrence of a business event, and generates a first accounting event based on the business event information. However, based on settlement cycle information, the business event that occurs after the generation of confirmed payment information is If so, additional accounting event information is generated in response. Additional accounting event information includes business events that have not been processed within the settlement cycle of orders corresponding to the previous cycle (e.g., the Mth order corresponding to the Mth cycle) and orders corresponding to the next cycle (e.g., the M+1st cycle). ) may include accounting event information for processing by being incorporated into the (M+1)th settlement cycle corresponding to the cycle. The electronic device 101 generates a second additional accounting event corresponding to the M order when the business event corresponding to the M order occurs after the confirmation payment information generation point 650 and before the start of the (M+2) cycle. Information can be generated. The second additional accounting event information that occurred in response to the M order can be used in the settlement process of the (M+1) order. In this case, the electronic device 101 responds to the (M+1) order only if the M order and the (M+1) order include the same vendor information, unit price information, and item information. The second additional accounting event information can be used in the settlement process. Likewise, the first additional accounting event information is a business event that occurred at the Mth cycle or at a time before the Mth cycle, for example, at a predetermined time 610 after the time of generating the confirmed payment information included in the (M-1) cycle. It may be accounting event information corresponding to a business event corresponding to an order prior to the M order (e.g., the (M-1) order or the (M-2) order). The electronic device 101 generates the first accounting event information and 1Accrued payment information can be created based on additional accounting event information. According to one embodiment, the additional accounting event information may include action type information and quantity information corresponding to whether it is an export event or a receipt event.

Figure 7 shows accounting event information generated by an electronic device according to various embodiments.

Referring to FIG. 7, FIG. 7 may be understood as showing accounting event information in a table. Referring to FIG. 7, accounting event information according to each embodiment of managing payment information for different vendors with the same settlement cycle can be confirmed. Each cycle (Mth cycle or (M+1)th cycle) included in the 'Processing Time' column of FIG. 7 is displayed, and accounting event information can be generated in each row corresponding to the cycle. 'Each order included in the target column may be displayed as the Mth order corresponding to the Mth cycle or as the (M+1)th order corresponding to the (M+1)th cycle.

Referring to FIG. 7, each accounting event information may be mapped to a corresponding action type. The action type may include type information regarding a calculation operation for combining quantitative information included in each piece of accounting event information. Each piece of accounting event information may include a corresponding action type and corresponding quantity information.

In embodiments, action types may be mapped to accounting event information corresponding to event types of business event information. For example, action type 'RECEIVE_TEMP' may be an action type corresponding to a receipt event, and action type 'RELEASE_CONFIRMED' may be an action type corresponding to an export event. In the case of a stocking event, the corresponding quantity information may be modified based on the first information received from the vendor, so the action type may be tagged with temporary information such as 'TEMP', and in the case of an export event, the corresponding quantity information may be tagged with temporary information such as 'TEMP'. Since there is no room for modification, the action type can be tagged with definitive information such as 'CONFIRMED'. That is, the first accounting event information may include action type information of 'RECEIVE_TEMP' or 'RELEASE_CONFIRMED' and corresponding quantity information.

In an embodiment, payment has already been completed, but in the case of a business event that occurs after that, the action type 'RECEIVE_TEMP_ADJUST_REVERSE' may be mapped to accounting event information. That is, additional accounting event information may include action type information of 'RECEIVE_TEMP_ADJUST_REVERSE'. For example, if a business event corresponding to the M order occurs after payment (or after the creation of confirmed payment information), it is created as additional accounting event information corresponding to the M order in the (M+2) cycle, and the additional accounting event The information may include an action type of 'RECEIVE_TEMP_ADJUST_REVERSE'. For example, referring to the example of the fourth vendor, the electronic device 101 records accounting event information corresponding to the 'RECEIVE_TEMP' action type created in the (M+1)th cycle in response to the Mth order, based on the settlement cycle information. This allows you to check with additional accounting event information. The electronic device 101 may generate additional accounting event information including an action type of 'RECEIVE_TEMP_ADJUST_REVERSE' for a correction value in response to the additional accounting event information.

In an embodiment, the electronic device 101 may generate accrued payment information based on one or more first accounting event information. According to one embodiment, the accrued payment information may include information about the total quantity received and information about the action type. The action type corresponding to the accrued payment information can be defined as 'RECEIVE_CONFIRMED'. At this time, the action type 'RECEIVE_TEMP_REVERSE' may correspond to auxiliary accounting event information defined to remove the 'TEMP' quantity from the calculation in response to quantity information corresponding to the action type of 'RECEIVE_CONFIRMED'. The electronic device 101 may generate accrued payment information including action type information of 'RECEIVE_CONFIRMED' based on the first accounting event information corresponding to the receipt event and the first accounting event information corresponding to the export event.

In an embodiment, the electronic device 101 may generate second accounting event information based on receipt of the first information. The second accounting event information may include action type information of 'RECEIVE_CONFIRMED_ADJUST'. The action type 'RECEIVE_CONFIRMED_ADJUST' may be an action type that is mapped to the difference value calculated based on the total receipt quantity information corresponding to the vendor supply quantity information and accrued payment information confirmed based on the first information. Alternatively, the electronic device 101 may obtain information about the difference value based on the first information and generate second accounting event information mapping the action type of 'RECEIVE_CONFIRMED_ADJUST'. The electronic device 101 may generate confirmed payment information 701 based on the second accounting event information and accrued payment information. The confirmed payment information may include information about the quantity subject to payment. The quantity eligible for payment may be determined based on the total quantity received and the quantity supplied by the vendor. The electronic device 101 may check the payment target quantity by calculating the total receipt quantity and vendor supply quantity based on the action type of the accrued payment information and the action type of the second accounting event information. The electronic device 101 may provide confirmed payment information to the vendor management server 104, and the vendor management server 104 may complete payment of the confirmed payment to the vendor based on the confirmed payment information. That is, the confirmed price may be determined based on the quantity to be paid confirmed based on the confirmed price information and the unit price information confirmed based on the ordering information.

FIG. 8 is a flowchart of an operation in which an electronic device generates cost of sales information according to various embodiments.

According to various embodiments, in operation S801, the electronic device 101 may generate cost of goods sold information based on accrued payment information and confirmed payment information. The cost of sales information may include information about the unit price of purchasing the item from the vendor, corresponding to the item for which sales have occurred. According to one embodiment, the information regarding the unit amount may correspond to a value obtained by dividing the confirmed amount confirmed based on payment target quantity information and order information by the total received quantity. In other words, the confirmed price information is confirmed based on the payment target quantity information and the confirmed amount corresponding to the confirmed price information is paid to the vendor, but the actual received quantity corresponding to the accrued price information, that is, the total received quantity, is the payment target quantity information. may be different from Therefore, cost of goods sold information can be generated based on the relationship between the actual received quantity and the actual confirmed payment amount. The electronic device 101 may generate information about the unit amount based on the accrued amount information and the confirmed amount information, and generate information about the total amount of additional assets based on the information about the unit amount and the total received quantity information. For example, cost of goods sold (COGS) can be generated for each item information and can be generated for each specified period.

Cost of goods sold information may be determined based on the sum of the total amount of basic assets, the total amount of additional assets, and the total amount of conversion assets divided by the sum of the quantity of basic assets, the quantity of additional assets, and the quantity of conversion assets. A conversion asset may mean that the item is a conversion product, that is, when it is received or sold in response to the receipt or sale of another product. The total amount of assets can be determined as the product of the item quantity and unit price.

The quantity of the underlying asset may correspond to the total quantity of items remaining after sale in the last cost of goods sold information generation cycle. The total amount of basic assets may correspond to the product of the total unit price corresponding to the past cost of sales information and the total quantity of remaining items (quantity of basic assets).

The quantity of additional assets can correspond to the total quantity of items received (total received quantity) in this cost of goods sold information generation cycle. The total amount of additional assets may correspond to information about the unit amount for which the item was purchased from a vendor multiplied by the total quantity received. At this time, the electronic device 101 may check the quantity of additional assets and the total amount of additional assets for generating cost of sales information based on the accrued payment information and the combined payment information.

Cost of goods sold information may be determined based on the sum of the total amount of basic assets, the total amount of additional assets, and the total amount of conversion assets divided by the sum of the quantity of basic assets, the quantity of additional assets, and the quantity of conversion assets. The electronic device 101 is configured to calculate cost of goods sold information based on the sum of the total amount of basic assets, the total amount of additional assets, and the total amount of conversion assets divided by the sum of the quantity of basic assets, the quantity of additional assets, and the quantity of conversion assets. You can check the total unit price. The electronic device 101 may generate cost of goods sold information based on the product of total unit price and shipment quantity information. The electronic device 101 may provide the generated cost of goods sold information to the accounting server (S802).

The embodiments of the present invention disclosed in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present invention and to facilitate understanding of the present invention, and are not intended to limit the scope of the present invention. In other words, it is obvious to those skilled in the art that other modifications based on the technical idea of the present invention can be implemented. Additionally, each of the above embodiments can be operated in combination with each other as needed. For example, all embodiments of the present invention can be implemented by a system by combining parts of each other.

Additionally, the method according to the system according to the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium.

As such, various embodiments of the present invention may be implemented as computer readable code on a computer readable recording medium in certain respects. A computer-readable recording medium is any data storage device capable of storing data that can be read by a computer system. Examples of computer readable recording media include read only memory (ROM), random access memory (RAM), and compact disk-read only memory (CD-ROM). ), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (data transmission over the Internet, etc.). Computer-readable recording media may also be distributed across networked computer systems, such that computer-readable code is stored and executed in a distributed manner. Additionally, functional programs, codes, and code segments for achieving various embodiments of the present invention can be easily interpreted by programmers skilled in the field to which the present invention is applied.

Additionally, it will be appreciated that the devices and methods according to various embodiments of the present invention can be implemented in the form of hardware, software, or a combination of hardware and software. Such software may, for example, use any storage device, volatile or non-volatile, such as ROM, whether erasable or rewritable, or memory such as, for example, RAM, memory chips, devices or integrated circuits; Alternatively, it may be stored on a storage medium that is optically or magnetically recordable and readable by a machine (e.g., a computer), for example, a compact disk (CD), DVD, magnetic disk, or magnetic tape. . Methods according to various embodiments of the present invention may be implemented by a computer including a control unit and a memory, or a vehicle including such memory or a computer, and such memory is a program containing instructions that implement the embodiments of the present invention. Alternatively, you can see that it is an example of a machine-readable storage medium suitable for storing programs.

Accordingly, the present invention includes a program containing code for implementing the device or method described in the claims of this specification and a machine-readable storage medium (such as a computer) storing such a program. Additionally, such programs may be transmitted electronically through any medium, such as communication signals transmitted over a wired or wireless connection, and the present invention includes equivalents thereof as appropriate.

Although the present invention has been described above with reference to embodiments of the present invention, the embodiments of the present invention disclosed in the specification and drawings are merely presented as specific examples to easily explain the technical content of the present invention and to aid understanding of the present invention. It is not intended to limit the scope. In addition, the embodiments according to the present invention described above are merely illustrative, and those skilled in the art will understand that various modifications and equivalent scope of embodiments are possible therefrom. Therefore, the true technical protection scope of the present invention should be determined by the following patent claims.

Claims (15)

1. In a method of managing information about the price of an ordered item performed on an electronic device,

   Obtaining business event information including at least order identification information in response to the occurrence of a business event;

   generating and storing first accounting event information based on order information confirmed based on the order identification information and the business event information;

   providing accrued payment information generated based on settlement cycle information and the first accounting event information to a vendor management server; and

   A payment information management method comprising generating confirmed payment information based on first information received from the vendor management server in response to the provision of the accrued payment information.
2. According to paragraph 1,

   The business event information is:

   A payment information management method including information on an event type corresponding to the business event, quantity information, and order identification information.
3. According to paragraph 2,

   The event type is a payment information management method including a receipt event and an export event.
4. According to paragraph 1,

   The above ordering information is,

   A payment information management method including at least some of order item information, vendor information, price information, order quantity information, information on tax types, tax rate information, and settlement cycle information.
5. According to paragraph 1,

   The first accounting event information is,

   A payment information management method including at least some of information about the action type corresponding to the business event, quantity information, the order identification information, item information, and vendor information confirmed based on the order information.
6. According to paragraph 1,

   The steps provided above are:

   Confirming the settlement cycle information based on the order information;

   checking whether a settlement date corresponding to the order information has arrived based on the settlement cycle information; and

   When the settlement date arrives, the payment information management method further includes generating the accrued payment information based on the stored first accounting event information.
7. According to paragraph 1,

   The steps provided above are:

   Confirming total receipt quantity information corresponding to the order identification information based on the first accounting event information; and

   A payment information management method further comprising generating accrued payment information based on the total receipt quantity information and the order information.
8. In clause 7,

   The step of generating the confirmed payment information is,

   Generating payment target quantity information based on the first information and the total received quantity information; and

   A payment information management method further comprising generating the confirmed payment information based on the payment target quantity information and the order information.
9. According to paragraph 1,

   The step of generating the confirmed payment information is,

   generating second accounting event information based on the first information; and

   A payment information management method further comprising generating the confirmed payment information based on the accrued payment information and the second accounting event information.
10. According to clause 9,

    The step of generating the second accounting event information is,

    A payment information management method further comprising generating the second accounting event information based on information on whether or not the accrued payment information is approved, which is confirmed based on the first information.
11. According to clause 9,

    The first information is,

    Contains tax invoice information;

    The step of generating the second accounting event information is,

    Confirming vendor supply quantity information based on the tax invoice information;

    A payment information management method further comprising confirming information regarding whether to approve the accrued payment information based on a result of comparing the vendor supply quantity information and the accrued payment information.
12. According to paragraph 1,

    The payment information management method is,

    A payment information management method further comprising providing the confirmed payment information to an accounting server.
13. According to paragraph 1,

    The payment information management method is,

    generating cost of goods sold information of an item corresponding to the order information based on the accrued price information and the confirmed price information; and

    A payment information management method further comprising providing the generated cost of goods sold information to an accounting server.
14. In electronic devices,

    Memory;

    transceiver; and

    Includes a processor,

    The processor,

    Obtain business event information including at least ordering identification information in response to the occurrence of a business event,

    Generate and store first accounting event information based on order information confirmed based on the order identification information and the business event information,

    Provide accrued payment information generated based on settlement cycle information and the first accounting event information to the vendor management server,

    An electronic device configured to generate confirmed payment information based on first information received from the vendor management server in response to the provision of the accrued payment information.
15. A non-transitory computer-readable recording medium that records a program for executing the method of claim 1 on a computer.

Images