Sales processing device, sales processing method, and sales processing program

Abstract

To provide a sales processing device that can take into account the purchaser's cash flow by deferring the payment deadline for seasonal products.SOLUTION: A sales processing device according to this embodiment is equipped with sales input means for inputting and registering in a storage area a first master in which accounting start date, accounting end date, seasonal product class, and first site information are associated and registered as well as sales data including sales date, billing destination, class, sales amount, and scheduled collection date, and at that time, obtaining the first site information from the first master using the sales date and class as keys, and calculating the scheduled collection date based on the sales date and the obtained first site information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a sales processing device, a sales processing method, and a sales processing program.

Background Art

[0002] For example, products that are expected to have large sales during a specific period, such as New Year's osechi cuisine, are called "seasonal products". Conventionally, as a system related to a payment site, for example, there is Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, from the perspective of purchasers (for example, customers) who purchase seasonal products, there are cases where cash flow becomes tight due to purchasing a large quantity of high-unit-price seasonal products.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a sales processing device, a sales processing method, and a sales processing program that can consider the cash flow of purchasers by granting a grace period for the payment due date for seasonal products.

Means for Solving the Problems

[0006] In order to solve the above-described problems and achieve the object, the present invention is a sales processing apparatus including a control unit, wherein the control unit is configured to be able to access a first master in which a billing start date, a billing end date, a variety of seasonal products, and first site information are registered in association with each other, input sales data including a sales date, a billing destination, a variety, a sales amount, and a scheduled collection date, and register the sales data in a storage area. At this time, the first site information is acquired from the first master using the sales date and the variety as keys, and a sales input means for calculating the scheduled collection date based on the sales date and the acquired first site information is provided.

[0007] Further, according to one aspect of the present invention, the first master further registers a reference amount in association with each other. When the sales input means acquires the first site information from the first master, for the sales data, those in which the total sales amount of those having the same billing destination and variety in the same month is equal to or more than the reference amount may be acquired.

[0008] Further, according to one aspect of the present invention, the control unit is further configured to be able to access a second master in which a billing destination, a closing date, and second site information are registered in association with each other. The sales input means acquires the closing date and the second site information from the second master using the billing destination of the sales data as a key, and may calculate the scheduled collection date based on the closing date and the second site information acquired in addition to the first site information.

[0009] Further, according to one aspect of the present invention, the first site information and the second site information may include an addition number of months and an addition number of days.

[0010] Further, according to one aspect of the present invention, the control unit may further include a billing processing means for issuing a bill in units of a billing destination, a closing date, and a scheduled collection date based on the sales data registered in the storage area.

[0011] Also, in order to solve the above-described problems and achieve the object, the present invention is a sales processing method executed by an information processing apparatus including a control unit, wherein the control unit is configured to be able to access a first master in which a billing start date, a billing end date, types of seasonal products, and first site information are registered in association with each other, and sales data including a sales date, a billing destination, a type, a sales amount, and a scheduled collection date is input to the control unit and registered in a storage area. At this time, based on the sales date and the type as keys, the first site information is acquired from the first master, and a scheduled collection date is calculated based on the sales date and the acquired first site information, including a sales input step.

[0012] Also, in order to solve the above-described problems and achieve the object, the present invention is a sales processing program for causing an information processing apparatus including a control unit to execute, wherein the control unit is configured to be able to access a first master in which a billing start date, a billing end date, types of seasonal products, and first site information are registered in association with each other, and sales data including a sales date, a billing destination, a type, a sales amount, and a scheduled collection date is input to the control unit and registered in a storage area. At this time, based on the sales date and the type as keys, the first site information is acquired from the first master, and a sales processing program is characterized in that a scheduled collection date is calculated based on the sales date and the acquired first site information to execute a sales input step.

Effects of the Invention

[0013] According to the present invention, for seasonal products, it is possible to consider the cash flow of purchasers by granting a grace period for the payment deadline.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

[0015] Embodiments of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited by these embodiments.

[0016] [1. Overview] The overview of the present invention will be described in the order of "1-1. Regarding seasonal products", "1-2. Problems", "1-3. Solution", "1-4. Effects", and "1-5. Outline of the mechanism" in handling seasonal products.

[0017] "1-1. Regarding seasonal products" For example, products such as New Year's osechi that are expected to achieve large sales during a specific period are called seasonal products. Companies dealing with seasonal products can expect explosive sales that are not available in other seasons.

[0018] "1-2. Problems" However, from the perspective of customers who purchase seasonal products, there are cases where the cash flow becomes tight due to the large-scale purchase of high-unit-price seasonal products. Thus, the customer's cash flow may deteriorate, resulting in the loss of sales opportunities.

[0019] The deterioration of the customer's cash flow will lead to the loss of sales opportunities for companies dealing with seasonal products. As a result, it becomes an obstacle to maximizing the sales amount during the corresponding period.

[0020] "1-3. Solution Method" In this embodiment, by setting payment sites (hereinafter also simply referred to as "sites") in the master according to sales recording dates, handled products, and amounts, a mechanism is constructed that gives a grace period for the payment deadline only for seasonal products, taking into account the cash flow of purchasers (for example, customers).

[0021] "1-4. Effect" This leads to the mitigation of the deterioration of the customer's cash flow due to the purchase of seasonal products. That is, it leads to the prevention of opportunity losses and contributes to the maximization of sales.

[0022] "1-5. Outline of the Mechanism" In this embodiment, a "site management master by recording date, product type, and amount" for managing the sites of seasonal products is constructed. By referring to this master during sales recording and billing processing, it becomes possible to calculate a collection schedule date different from the normal one only for seasonal products.

[0023] The sales processing apparatus of the present invention is widely applicable to, for example, industries and enterprises dealing with seasonal products.

[0024] [2. Configuration] An example of the configuration of the sales processing apparatus 100 according to this embodiment will be described with reference to FIG. 1. FIG. 1 is a block diagram showing an example of the configuration of the sales processing apparatus 100.

[0025] The sales processing device 100 is a commercially available desktop personal computer. Note that the sales processing device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer.

[0026] The sales processing device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the sales processing device 100 is communicably connected via an arbitrary communication path.

[0027] The communication interface unit 104 communicably connects the sales processing device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of communicably connecting the sales processing device 100 and the server 200, and is, for example, the Internet or a LAN (Local Area Network).

[0028] An input device 112 and an output device 114 are connected to the input / output interface unit 108. As the output device 114, in addition to a monitor (including a touch panel), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be described as the monitor 114 or the printer 114, and the input device 112 may be described as the keyboard 112 or the mouse 112. Also, "output" means output by the output device 114, etc., and includes, for example, display output to the monitor 114, print output by the printer 114, and transmitting data to the outside.

[0029] In the memory unit (memory area) 106, various databases, tables, files, etc. are stored. In the memory unit 106, a computer program for giving instructions to the CPU (Central Processing Unit) to perform various processes in cooperation with the OS (Operating System) is recorded. As the memory unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc. can be used.

[0030] The memory unit 106 stores a site management master by accounting date, variety, and amount (first master) 106a, a billing destination master (second master) 106b, a variety master 106c, sales data 106d, etc.

[0031] FIG. 2 is a diagram showing a configuration example of a site management master by accounting date, variety, and amount (first master) 106a. FIG. 3 is a diagram showing a configuration example of a billing destination master (second master) 106b. FIG. 4 is a diagram showing a configuration example of a variety master 106c.

[0032] As shown in FIG. 2, the site management master 106a by accounting date, variety, and amount can be composed of a table or the like in which the accounting start date, accounting end date, variety of seasonal products (variety code and / or variety name), reference amount (above), first site information (number of additional months, number of additional days) are associated and registered. In the example shown in the figure, the first row has an accounting start date of "2023 / 11 / 1", an accounting end date of "2023 / 12 / 31", a variety code of seasonal products "HI001", a reference amount (above) of "500,000", a number of additional months of "1", and a number of additional days of "0".

[0033] As shown in FIG. 3, the billing destination master 106b can be composed of a table or the like in which the billing destination (billing destination code and / or billing destination name), closing date, second site information (number of additional months, number of additional days) are associated and registered. In the example shown in the figure, the first row has a billing destination code of "SE001", a billing destination name of "Billing Destination A", a closing date of "end of month", a number of months of "1", and a number of days of "0".

[0034] As shown in FIG. 4, the product type master 106c can be composed of a table or the like that registers by associating the product type code and the product type name. In the example shown in the figure, the first row has the product type code "HI001" and the product type "Osechi". In the example shown in FIG. 4, "Osechi", "Kotsu no Ko", and "Ikura" are seasonal products. The product type master 106c is referred to when converting the product type code and the product type name.

[0035] The sales data 106d may include a sales NO, a sales date, a billing destination (billing destination code and / or billing destination name), a line NO, a product type (product type code and / or product type name), a sales amount, a recovery scheduled date, and a billing number.

[0036] Returning to FIG. 1, the control unit 102 is a CPU or the like that comprehensively controls the sales processing device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processes based on these stored programs.

[0037] The control unit 102 is configured to be able to access the site management master 106a by accounting date, product type, and amount, the billing destination master 106b, the product type master 106c, the sales data 106d, etc. stored in the storage unit 106. Note that the site management master 106a by accounting date, product type, and amount, the billing destination master 106b, the product type master 106c, the sales data 106d, etc. may be provided in another location (for example, the server 200), as long as the control unit 102 can access it.

[0038] Conceptually in terms of functions, the control unit 102 includes a sales processing unit 102a, a billing processing unit 102b, a master maintenance unit 102c, a screen display control unit 102d, etc.

[0039] The sales processing unit 102a inputs sales data including the sales date, the billing destination, the product type, the sales amount, and the scheduled collection date in response to, for example, an operator's input operation on a sales input screen (not shown) displayed on the monitor 114, registers it in the storage unit 106, and at that time, acquires first site information from the site management master 106a classified by accounting date, product type, amount, and site using the sales date and the product type as keys, and calculates the scheduled collection date based on the sales date and the acquired first site information.

[0040] Further, when the sales processing unit 102a acquires the first site information from the site management master 106a classified by accounting date, product type, amount, and site, it may acquire sales data in which the total sales amount of those with the same billing destination and product type in the same month is equal to or greater than the reference amount.

[0041] Also, the sales processing unit 102a may acquire the closing date and second site information from the billing destination master 106b using the billing destination of the sales data as a key, and calculate the scheduled collection date based on the closing date and the second site information acquired in addition to the first site information.

[0042] Also, the first site information and the second site information may include the number of months to be added and the number of days to be added.

[0043] The billing processing unit 102b issues a bill based on the sales data registered in the storage unit 106 in units of the billing destination, the closing date, and the scheduled collection date in response to, for example, an operator's input operation on a bill issuance screen (see FIG. 9(B)) displayed on the monitor 114.

[0044] The master maintenance unit 102c performs editing such as data input, addition, and modification on the site management master 106a classified by accounting date, product type, amount, and site, the billing destination master 106b, and the product type master 106c in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

[0045] The screen display control unit 102d controls the display of various screens (for example, sales input screen, invoice issuance screen, master maintenance screen, etc.) to be displayed on the monitor 114 and the input thereof.

[0046] [3. Specific Example] With reference to FIGS. 1 to 9, a specific example of the processing of the control unit 102 of the sales processing apparatus 100 in the present embodiment will be described. FIGS. 5 to 9 are diagrams for explaining a specific example of the processing of the control unit of the sales processing apparatus 100 according to the present embodiment.

[0047] [3-1. Overall Processing] FIG. 5 is a diagram showing a flow for explaining an overview of the overall processing of the control unit of the sales processing apparatus 100 according to the present embodiment. With reference to FIG. 5, an overview of the overall processing of the control unit of the sales processing apparatus 100 according to the present embodiment will be described.

[0048] In FIG. 5, the master maintenance unit 102c executes a master maintenance process (step S1). Specifically, in the master maintenance process, the master maintenance unit 102c sets data for the date-of-entry-by-item-by-amount site management master 106a, the billing destination master 106b, and the item master 106c in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114, for example.

[0049] The sales processing unit 102a executes sales processing (step S2). Specifically, in the sales processing, the sales processing unit 102a inputs and registers sales data including the sales date, the billing destination, the product type, the sales amount, and the scheduled collection date in the storage unit 106 in response to an operator's input operation on a sales input screen (not shown) displayed on the monitor 114, for example. At this time, the first site information is acquired from the site management master 106a for each accounting date, product type, amount, and site using the sales date and the product type as keys, and the scheduled collection date is calculated based on the sales date and the acquired first site information. Also, when the sales processing unit 102a acquires the first site information from the site management master 106a for each accounting date, product type, amount, and site, it may be configured to acquire sales data for which the total sales amount for the same billing destination and product type in the same month is equal to or greater than the reference amount. Further, the sales processing unit 102a may acquire the closing date and the second site information from the billing destination master 106b using the billing destination of the sales data as a key, and calculate the scheduled collection date based on the closing date and the second site information acquired in addition to the first site information.

[0050] The billing processing unit 102b executes billing processing (step S3). Specifically, in the billing processing, the billing processing unit 102b issues a bill for each billing destination, closing date, and scheduled collection date unit based on the sales data registered in the storage unit 106 in response to an operator's operation on a bill issuance screen (not shown) displayed on the monitor 114, for example.

[0051] [3-2. Sample Data] Figs. 6 to 9 are diagrams showing sample data for explaining a specific example of the processing of the control unit of the sales processing apparatus 100 according to the present embodiment. With reference to Figs. 6 to 9, a specific example of the processing of the control unit of the sales processing apparatus 100 according to the present embodiment will be described.

[0052] In the following description, data examples of the site management master (first master) 106a for each accounting date, product type, amount, and site, the billing destination master (second master) 106b, and the product type master 106c shown in Figs. 2 to 4 will be used for the description.

[0053] (S1: Sales Processing) With reference to FIGS. 6 to 8, a specific example of sales processing will be described. In the sales processing, sales are recorded in response to an order from a customer. At that time, the scheduled collection date is calculated with reference to the customer master 106b and the site management master 106a by date of billing, item type, and amount.

[0054] The sales processing unit 102a inputs and registers sales data including the sales date, customer, item type, sales amount, and scheduled collection date in the storage unit 106 in response to, for example, an operator's input operation on a sales input screen (not shown) displayed on the monitor 114. At that time, for the sales data, using the customer as a key, the closing date and the second site information are acquired from the customer master 106b. Also, using the sales date, item type, and the total sales amount of items with the same customer and item type in the same month as a key, the first site information is acquired from the site management master 106a by date of billing, item type, and amount. Based on the sales date, the acquired closing date, second site information, and first site information, the scheduled collection date is calculated.

[0055] (Sales recording in October: Time series (1)) FIG. 6 is a diagram showing a data example of sales data for October. The sales data is for holding sales information and the scheduled collection date. The scheduled collection date is also printed on the invoice to the customer.

[0056] As shown in FIG. 6, the sales data includes items such as sales number, sales date, customer code, line number, item type code, item type name, sales amount, scheduled collection date, and invoice number. The "invoice number" may be automatically sequentially numbered at the end of the month, for example, in units of customer, closing date, and scheduled collection date.

[0057] In the example shown in the figure, the first line shows sales number UR1001, sales date 2023 / 10 / 1, customer code "SE001", line number "1", item type code "HI002", item type name "baby eels", sales amount "600,000", scheduled collection date "2023 / 11 / 30", and invoice number " ".

[0058] An example of the calculation logic for the scheduled collection date will be described.

[0059] 1. Using the billing destination of the sales data as the key, obtain the closing date and the second site information (additional months and additional days) from the billing destination master 106b. 2. Using the sales date, product code of the sales data, and the total sales amount of records with the same billing destination code and product code within the same month as the key, obtain the first site information (additional months, additional days) from the site management master 106a by accounting date, product, and amount. 3. Update the scheduled collection date of the sales data based on each item obtained in 3.1.2.

[0060] Example of calculating the scheduled collection date: For the first row of sales data with sales number = "UR1001", sales date "2023 / 10 / 1", row number = "1", billing destination code = "SE001", and product code "H002".

[0061] 1. In the billing destination master 106b, the closing date = end of month, the additional months of the second site information = 1, and the additional days = 0. 2. The data to be billed for the current month (billing number = blank), and the total sales amount of the same billing destination code and product code in October = 600,000. However, since the sales date "2023 / 10 / 1" is outside the target period (target period: 2023 / 11 / 1 - 2023 / 12 / 13) in the site management master 106a by accounting date, product, and amount, the additional months of the second site information = 0 and the additional days = 0. 3. The scheduled collection date is the closing date "end of month" of the sales date "2023 / 10 / 1" + the additional months "1" of the second site information, so it is "2023 / 11 / 30".

[0062] (Sales accounting in November: Time series (2)) Figure 7 is obtained by adding the sales data for the first ten days of November to Figure 6.

[0063] Example of calculating the scheduled collection date: For the fourth row of sales data with sales number = "UR1101", sales date "2023 / 11 / 1", row number = "1", billing destination code = "SE001", and product code "HI002".

[0064] 1. In the billing master 106b, the closing date = end of month, the additional months for the second site information = 1, and the additional days = 0. 2. Since the data subject to billing for the current month (billing number = blank) and the total sales amount for the same billing destination code and product code in November = 600,000, in the site management master 106a by posting date, product, amount, and site, the additional months for the second site information = 2, and the additional days = 0. 3. The scheduled collection date is the closing date "end of month" of the sales date "2023 / 11 / 1" + the additional months for the second site information "1" + the additional months for the first site information "2" = "2024 / 2 / 28".

[0065] (Sales posting in November: Time series (3)) Figure 8 is obtained by adding the sales data in the middle of November to Figure 7.

[0066] Example of calculating the scheduled collection date: For the sales number = "UR1103" in the 7th row, sales date "2023 / 11 / 10", row number = "1", billing destination code = "SE001", and product code "HI003".

[0067] 1. In the billing master 106b, the closing date = end of month, the additional months for the second site information = 1, and the additional days = 0. 2. Since the data subject to billing for the current month (billing number = blank) and the total sales amount for the same billing destination code and product code in November = 300,000 (= 200,000 + 100,000), in the site management master 106a by posting date, product, amount, and site, the additional months for the second site information = 1, and the additional days = 20. The breakdown is that for sales number = "UR1101", row number = "2", it is 100,000, and for sales number = "UR1103", row number = "1", it is 200,000. 3. The scheduled collection date is the closing date "end of month" of the sales date "2023 / 11 / 10" + the additional months for the second site information "1" + the additional months for the first site information "1" + the additional days for the first site information "20", so it is "2024 / 1 / 20".

[0068] Update the scheduled collection date of the record with the sales invoice number "UR1101" on the 5th line and line number "2" from "2023 / 12 / 31" to "2024 / 1 / 20". When calculating the scheduled collection date, update the scheduled collection dates of other records with the same customer code and product code in the same month that have not been billed to the same date.

[0069] (S3: Billing Process) Referring to Figure 9, a specific example of the billing process will be described. In the billing process, billing and invoice issuance are performed based on the sales data recorded in the sales process. Invoice numbers are sequentially numbered in units of the customer, closing date, and scheduled collection date, and invoices are issued.

[0070] The billing processing unit 102b issues invoices in units of the customer, closing date, and scheduled collection date based on the sales data registered in the storage unit 106 in response to, for example, the input operations of the operator on the invoice issuance screen displayed on the monitor 114.

[0071] Figure 9(A) shows an example of sales data (extracted only for November).

[0072] Figure 9(B) shows an example of the display of the invoice issuance screen. The invoice issuance screen 400 has fields for specifying the reference date, closing date, and customer code, and a print button. When the closing date and customer code are specified and the print button is pressed, sales data is extracted using the closing date and customer code as extraction conditions, and invoices are issued in units of the customer, closing date, and scheduled collection date.

[0073] Figures 9(C) and 9(D) are diagrams showing examples of the issued invoices. The invoice includes, for example, the customer, invoice number, billing closing date, purchase amount, payment due date (= scheduled collection date), item, transaction date, and amount. Figure 9(C) shows an example of the November invoice (1) for the customer "SE001", and Figure 9(D) shows an example of the November invoice (2) for the customer "SE001".

[0074] As described above, according to the present embodiment, a site management master 106a for registering by associating a counting start date, a counting end date, the variety of seasonal products, and first site information, and sales data including a sales date, a billing destination, a variety, a sales amount, and a collection scheduled date are input and registered in a storage area. At this time, based on the sales date and the variety as keys, the first site information is acquired from the first master, and a collection scheduled date is calculated based on the sales date and the acquired first site information. Since the sales processing unit 102a is provided, it is possible to consider the cash flow of the purchaser by granting a grace period for the payment due date for seasonal products.

[0075] [4. Contribution to the United Nations Sustainable Development Goals (SDGs)] According to the present embodiment, it is possible to contribute to promoting business efficiency and appropriate business judgment of the enterprise, so it is possible to contribute to Goals 8 and 9 of the SDGs.

[0076] In addition, according to the present embodiment, it is possible to contribute to reducing waste loss and promoting paperless and digitization, so it is possible to contribute to Goals 12, 13, and 15 of the SDGs.

[0077] In addition, according to the present embodiment, it is possible to contribute to strengthening control and governance, so it is possible to contribute to Goal 16 of the SDGs.

[0078] [5. Other Embodiments] The present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the above-described embodiments.

[0079] For example, among the processes described in the embodiment, all or part of the processes described as being automatically performed can be manually performed, or all or part of the processes described as being manually performed can be automatically performed by a known method.

[0080] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and the drawings can be arbitrarily changed unless otherwise specified.

[0081] Regarding the sales processing apparatus 100, each illustrated component is conceptually functional and does not necessarily have to be physically configured as shown in the figure.

[0082] For example, regarding the processing functions provided by the sales processing apparatus 100, particularly each processing function performed by the control unit, all or any part of it may be realized by a CPU and a program interpreted and executed by the CPU, or may also be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing an information processing apparatus to execute the processing described in this embodiment, and is mechanically read by the sales processing apparatus 100 as necessary. That is, in a storage unit such as a ROM or HDD (Hard Disk Drive), a computer program for giving commands to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM and constitutes the control unit in cooperation with the CPU.

[0083] In addition, this computer program may be stored in an application program server connected to the sales processing apparatus 100 via an arbitrary network, and all or part of it can be downloaded as necessary.

[0084] Also, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0085] Also, the "program" is a data processing method described in any language or description method, and is not limited to a specific form such as source code or binary code. Note that the "program" is not necessarily limited to a single configuration, and includes those that are distributed as a plurality of modules or libraries, or those that achieve their functions in cooperation with another program represented by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each device shown in the embodiment, well-known configurations and procedures can be used.

[0086] The various databases and the like stored in the storage unit are storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0087] Further, the sales processing apparatus 100 may be configured as an information processing apparatus such as a known personal computer or workstation, or may be configured as the information processing apparatus to which an arbitrary peripheral device is connected. Further, the sales processing apparatus 100 may be realized by installing software (including a program or data, etc.) for realizing the processing described in the present embodiment in the apparatus.

[0088] Furthermore, the specific form of the distribution and integration of the apparatuses is not limited to that shown in the drawings, and all or a part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or according to the functional load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Explanation of Signs

[0089] 100 Sales processing apparatus 102 Control unit 102a Sales processing unit 102b Billing processing unit 102c Master maintenance unit 102d Screen display control unit 104 Communication interface unit 106 Storage unit 106a Site management master for daily accounting, by variety, and by amount 106b Billing destination master 106c Variety master 108 Input / output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims

1. A sales processing apparatus comprising a control unit, wherein the control unit is configured to be able to access a first master in which a posting start date, a posting end date, the variety of seasonal products, and first site information are registered in association with each other, inputs sales data including a sales date, a billing destination, a variety, a sales amount, and a scheduled collection date and registers it in a storage area. At this time, using the sales date and the variety as keys, the first site information is acquired from the first master, and based on the sales date and the acquired first site information, a sales input means for calculating the scheduled collection date is provided. The sales processing apparatus is characterized by this.

2. The first master further registers a reference amount in association therewith, When the sales input means acquires the first site information from the first master, for the sales data, those in which the total sales amount of those with the same billing destination and variety in the same month is equal to or greater than the reference amount are acquired. The sales processing apparatus according to claim 1, characterized by this.

3. The control unit further is configured to be able to access a second master in which a billing destination, a closing date, and second site information are registered in association with each other, The sales input means uses the billing destination of the sales data as a key, acquires the closing date and the second site information from the second master, and based on the closing date and the second site information acquired in addition to the first site information, calculates the scheduled collection date. The sales processing apparatus according to claim 1, characterized by this.

4. The first site information and the second site information include an addition number of months and an addition number of days. The sales processing apparatus according to claim 3, characterized by this.

5. The control unit further is provided with a billing processing means for issuing a bill in units of a billing destination, a closing date, and a scheduled collection date based on the sales data registered in the storage area. The sales processing apparatus according to any one of claims 1 to 4, characterized by this.

6. A sales processing method executed by an information processing apparatus comprising a control unit, wherein the control unit is configured to be able to access a first master in which a posting start date, a posting end date, the variety of seasonal products, and first site information are registered in association with each other, Executed in the control unit, A sales processing method, comprising a sales input step of inputting sales data including a sales date, a billing destination, a product type, a sales amount, and a scheduled collection date into a storage area and registering the same, and at that time, acquiring first site information from the first master using the sales date and the product type as keys, and calculating the scheduled collection date based on the sales date and the acquired first site information.

7. A sales processing program for causing an information processing apparatus including a control unit to execute, wherein the control unit is configured to be able to access a first master in which a billing start date, a billing end date, a product type of seasonal products, and first site information are registered in association with each other, and the control unit executes a sales input step of inputting sales data including a sales date, a billing destination, a product type, a sales amount, and a scheduled collection date into a storage area and registering the same, and at that time, acquiring first site information from the first master using the sales date and the product type as keys, and calculating the scheduled collection date based on the sales date and the acquired first site information.

Images