JP2024013346A - Credit management system, credit management method, and credit management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a credit management system that allows a company headquarter or a head office to additionally register an adjustment fund (including a non-operation billing expense) and issue an invoice for POS data obtained from a store.

SOLUTION: A credit management system according to an embodiment includes: import means that imports POS data including a sales number, a business date, a store, a billing destination, a product, and a sales amount from a POS terminal of a store, and generates, on the basis of the imported POS data, recovery scheduled data including the sales number, a recovery scheduled date, a recovery method, a billing number, and a recovery scheduled amount; receivable input means that adds, on a receivable input screen displayed on a display unit, an adjustment amount to an invoiced amount, which is an expected recovery amount of the recovery scheduled data, and generates billing data including a billing number, a billing date, the store, a billing destination, and an adjusted billing amount; and bill issuing means that issues a bill based on the billing data.

SELECTED DRAWING: Figure 1

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to a credit management system, a credit management method, and a credit management program.

For example, using a POS system, the head office (headquarters) may acquire POS data (receivables data) of stores and manage the receivables of each store. 2. Description of the Related Art Conventionally, there is, for example, Patent Document 1 as a system for managing accounts receivable at a store using a POS system.

Japanese Patent Application Publication No. 2009-176121

However, Patent Document 1 does not describe anything about additionally registering adjustment fees (including non-business billing expenses) and issuing invoices for POS data acquired from stores at the head office or the head office side.

The present invention has been made in view of the above, and allows the head office or the head office side to additionally register adjustment fees (including non-business billing expenses) and issue invoices for POS data acquired from stores. The purpose of the present invention is to provide a receivables management system, a receivables management method, and a receivables management program that can perform the following tasks.

In order to solve the above-mentioned problems and achieve the objects, the present invention provides a receivables management system including a control section, the control section is configured to collect information such as sales numbers, business days, stores, and invoices from a POS terminal in a store. an importing means for importing POS data including destination, product, and sales amount, and generating collection schedule data including sales number, scheduled collection date, collection method, billing number, and scheduled collection amount based on the imported POS data; On the accounts receivable input screen displayed in the section, adjust the billed amount, which is the scheduled collection amount in the collection schedule data, by adding the adjustment amount, and enter the billing number, billing date, store, billing destination, and adjusted billing amount. The present invention is characterized by comprising: an accounts receivable input means for generating billing data including the billing data; and a bill issuing means for issuing a bill based on the billing data.

Further, according to one aspect of the present invention, the accounts receivable input means performs an adjustment using an adjustment amount when the billing party for the POS data is an individual customer, and the adjustment amount includes a store advance payment. Good too.

Further, according to one aspect of the present invention, the adjustment amount may include a discount amount.

Further, according to one aspect of the present invention, when making the adjustment using the adjustment money, the accounts receivable input means generates collection schedule breakdown data including the sales number, the classification of the adjustment money, and the sales amount. You may also do so.

Further, according to one aspect of the present invention, the accounts receivable input means is configured to input an invoice including a bill destination, a destination name, a person in charge name, and an address in response to an operator's operation on the accounts receivable input screen. You may decide to generate destination information.

Further, in order to solve the above-mentioned problems and achieve the objects, the present invention provides a receivables management method executed by an information processing device including a control unit, the method being executed at a store POS terminal, which is executed by the control unit. Import POS data including sales number, business day, store, billing address, product, and sales amount, and based on the imported POS data, collect information including sales number, scheduled collection date, collection method, billing number, and estimated collection amount. In the import process that generates schedule data and on the accounts receivable input screen displayed on the display unit, adjustments are made by adding an adjustment amount to the billing amount, which is the scheduled collection amount of the collection schedule data, and the billing number, billing date, The method is characterized by including a receivable input step of generating billing data including the store, billing destination, and adjusted billing amount, and a bill issuing step of issuing a bill based on the billing data.

Further, in order to solve the above-mentioned problems and achieve the objects, the present invention provides a receivables management program to be executed by an information processing device equipped with a control unit, the program being executed by the control unit. Import POS data including sales number, business day, store, billing address, product, and sales amount from the POS terminal, and based on the imported POS data, calculate the sales number, scheduled collection date, collection method, billing number, and scheduled collection amount. In the import process that generates collection schedule data including the collection schedule data, and on the accounts receivable input screen displayed on the display unit, an adjustment is made by adding an adjustment amount to the billing amount, which is the scheduled collection amount of the collection schedule data, and the billing number, billing amount, etc. A receivables management program for executing an accounts receivable input step that generates billing data including date, store, billing address, and adjusted billing amount, and an invoice issuing step that issues a bill based on the billing data. It is characterized by

According to the present invention, it is possible for the head office or the head office side to additionally register adjustment fees (including non-business billing expenses) and issue invoices for POS data acquired from stores. .

FIG. 1 is a block diagram showing an example of the configuration of a credit management system according to the present embodiment. FIG. 2 is a flowchart illustrating an overview of the overall processing of the control unit of the credit management system according to the present embodiment. FIG. 3 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment. FIG. 4 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment. FIG. 5 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment. FIG. 6 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment. FIG. 7 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment. FIG. 8 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment. FIG. 9 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment. FIG. 10 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment. FIG. 11 is a diagram for explaining a specific example of processing of the control unit of the credit management system according to the present embodiment.

Embodiments of the present invention will be described in detail based on the drawings. Note that the present invention is not limited to this embodiment.

[1. overview]
For example, using a POS system, the head office (headquarters) may acquire POS data (receivables data) of stores and manage the receivables of each store. In this case, for example, in the case of an individual customer, the cost of the meal used on the day + the store's advance payment will be treated as expenses together, so a single bill for the day is often required, but basically it is done in chronological order. On top of that, since the store advance payment cannot be included in the POS data, it is not possible to link the meal charge and the store advance payment, resulting in separate billing processes.

In addition, although it was technically possible to include store advance payments in POS data (on the store side) by modifying the POS system, in order to prevent fraudulent billing processing at stores, is entered into the POS data, and the advance payment (other expense reimbursement) is entered at the head office, so that the meal charges + store advance payments are linked and managed in the data after being separated for business purposes. There was a need. When operated within the existing system, processing became complicated and there were control issues.

In addition, even in the case of the same customer, the billing address differs depending on the purpose of use, but it was not possible to register each individual customer as a master each time, including the workload. Therefore, the management of billing address information for individual customers and the creation of invoices were performed outside the system.

In the receivables management system of this embodiment, invoices can be issued all at once by allowing the head office or the head office side to register adjustment funds (including store advance funds) with respect to POS data. .

Specifically, in the receivables management system of this embodiment, POS data and store advance data can be linked at the head office, (2) all invoices can be issued from the system, and (3) It is now possible to register the purpose of use in the system along with billing address information.

This will strengthen control and make invoice creation more efficient.

The receivables management system of this embodiment is widely applicable to industries that manage accounts receivable for individual customers.

[2. composition]
An example of the configuration of the credit management system 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 a credit management system according to the present embodiment. The receivables management system 100 of this embodiment is introduced into a head office or headquarters that manages one or more stores.

The debt management system 100 is a commercially available desktop personal computer. Note that the receivables management system 100 is not limited to stationary information processing devices such as desktop personal computers, but also portable types such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, and tablet personal computers. It may be an information processing device.

The debt management system 100 includes a control section 102, a communication interface section 104, a storage section 106, and an input/output interface section 108. Each unit included in the debt management system 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicably connects the debt management system 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 connecting the receivables management system 100, the server 200, the POS terminals 400 of each store, etc. so that they can communicate with each other, for example, via the Internet, LAN (Local Area Network), etc. be.

Each store is provided with a POS terminal 400. The receivables management system 100 and the POS terminals 400 constitute a POS system, and the receivables management system 100 functions as a server of the POS system. The receivables management system 100 acquires POS data from the POS terminals 400 and performs receivables management of the store.

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 home television), 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. Note that in the following description, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving instructions to a CPU (Central Processing Unit) to perform various processes in cooperation with an OS (Operating System). As the storage 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. Furthermore, the storage unit 106 includes a data table 106a.

The data table 106a is a table for storing various data such as POS data, collection schedule data, collection schedule breakdown data, billing data, and bill destination data.

The POS data may include sales number, line number, business day, store, billing destination, product, sales amount, sales amount, sales consumption tax amount, and receivable item classification.

Collection schedule data includes collection SEQ, slip type (POSor input), sales number, line number, scheduled collection date, collection method, invoice number, scheduled collection amount, collected amount, and application completion information (applied or unexpired). (included), payment number, collection date, and receivable item classification (accounts receivable or advance payment). For the "slip type", set "POS" if created using POS data, and "input" if created using accounts receivable input. POS data and collection schedule data are linked by sales number and line number.

Billing data includes billing number, bill type, billing date, store, billing address, billing address, scheduled collection date, billing amount, billing amount (main amount), billing amount (consumption tax amount), bill issue date, billing It may also include information on whether or not the document is required. Collection schedule data and billing data are linked by billing number.

The bill destination data may include the bill destination, destination name, person in charge, address, telephone number, proviso, summary, and notes. Billing data and billing address data are linked by billing address.

The collection schedule breakdown data may include collection SEQ, slip type, sales number, line number, head office additional transaction classification, sales amount, sales amount, sales consumption tax amount, and tax rate information. Collection schedule data and collection schedule breakdown data are linked by collection SQ, sales number, and line number.

The control unit 102 is a CPU or the like that controls the debt management system 100 in an integrated manner. The control unit 102 has an internal memory for storing control programs such as an OS, programs specifying various processing procedures, required data, etc., and performs various information processing based on these stored programs. Execute.

The control unit 102 is configured to be able to access a data table 106a stored in the storage unit 106. Note that the data table 106a may be provided in another location (for example, the server 200), and may have any configuration as long as it can be accessed by the control unit 102.

Functionally, the control section 102 includes an acquisition section 102a, an accounts receivable input section 102b, an invoice issuing section 102c, and a screen display control section 102d.

The import unit 102a imports POS data including sales number, business day, store, billing destination, product, and sales amount from the POS terminal 400 of each store, and stores it in the data table 106e. Furthermore, the importing unit 102a generates collection schedule data including a sales number, scheduled collection date, collection method, billing number, and scheduled collection amount based on the imported POS data, and stores the data in the data table 106a. "Generation" of data includes "creation", "addition", and "update" of data.
Further, if the billing party is other than an "individual customer", the importing unit 102a generates billing data based on the collection schedule data and registers it in the data table 106a.

For example, the accounts receivable input unit 102b adjusts the invoice amount, which is the expected collection amount of the collection schedule data, by adding an adjustment amount, in response to an operator's operation on the accounts receivable input screen displayed on the monitor 114, and Billing data including the number, billing date, store, billing destination, and adjusted billing amount is generated and registered in the data table 106a.

The accounts receivable input unit 102b may perform an adjustment using an adjustment amount when the billing party for the POS data is an individual customer, and the adjustment amount may include a store advance payment. Further, the adjustment amount may include a discount amount (rebate).

When making adjustments using adjustment funds, the accounts receivable input unit 102b may generate collection schedule breakdown data including the sales number, the classification of the adjustment funds, and the sales amount, and register the data in the data table 106b.

The accounts receivable input unit 102b generates bill destination information including the bill destination, destination name, person in charge name, and address in response to operator operations on the accounts receivable input screen displayed on the monitor 114. The data may also be registered in the data table 106a.

The bill issuing unit 102c issues (displays and/or prints) a bill based on the billing data in response to an operator's operation on the bill issuing screen displayed on the monitor 114.

The screen display control unit 102g controls the display and input of various screens (for example, accounts receivable input screen, bill issuance screen, etc.) displayed on the monitor 114.

[3. Concrete example]
A specific example of the processing of the credit management system 100 in this embodiment will be described with reference to FIGS. 1 to 11. First, with reference to FIG. 2, an overview of the overall processing of the credit management system 100 in this embodiment will be explained. FIG. 2 is a flowchart illustrating an outline of the overall processing of the credit management system 100 according to the present embodiment.

(3-1. Overall processing)
In FIG. 2, the accounts receivable input unit 102b executes an accounts receivable input process (step S1). In the specific accounts receivable input process, the accounts receivable input unit 102b inputs the invoiced amount, which is the scheduled collection amount of the scheduled collection data, in response to an operator's operation on the accounts receivable input screen displayed on the monitor 114, for example. Adjustments are made by adding the adjustment amount, and billing data including billing number, billing date, store, billing destination, and adjusted billing amount is generated and registered in the data table 106a.

In this case, the accounts receivable input unit 102b may make an adjustment using an adjustment amount when the billing party for the POS data is an individual customer, and the adjustment amount may include a store advance payment.

Further, when making adjustments using adjustment funds, the accounts receivable input unit 102b may generate collection schedule breakdown data including the sales number, the classification of the adjustment funds, and the sales amount, and register the data in the data table 106a.

In addition, the accounts receivable input unit 102b inputs bill destination information including the destination name, the name of the person in charge, and the address regarding the bill destination according to the operator's operation on the accounts receivable input screen displayed on the monitor 114. may be generated and registered in the data table 106a.

The bill issuing unit 102c executes bill issuing processing (step S2). Specifically, in the bill issuing process, the bill issuing unit 102c issues a bill based on billing data (display output) in response to an operator's operation on the bill issuing screen displayed on the monitor 114. and/or printout).

(3-2. Sample data)
3 to 11 are diagrams showing sample data for explaining specific examples of processing by the control unit 102 of the debt management system 100 according to the present embodiment. A specific example of the processing of the control unit 102 of the debt management system 100 according to the present embodiment will be described with reference to FIGS. 8 to 10.

(Prerequisite data)
FIG. 3A shows an example of POS data captured by the capture unit 102a. The POS data includes items such as sales number, line number, business day, store, billing destination, product, sales amount, sales amount, sales consumption tax amount, and receivable item classification. In the example shown in the figure, the third line is sales number "P003", line number "1", business day "2022/5/11", store "TEN001: Kyobashi Branch", billing address "SEI999: individual customer" , product "SH01: Meal fee", sales amount "¥1,400", sales amount "¥1,260", sales consumption tax amount "¥140", and credit category "Accounts receivable".

FIG. 3B shows an example of collection schedule data created based on the POS data imported by the importing unit 102a. Collection schedule data includes collection SEQ, slip type, sales number, line number, scheduled collection date, collection method, invoice number, scheduled collection amount, collected amount, clearing completion information, payment number, collection date, and receivable item classification. Equipped with items. In the example shown in the figure, the third line includes collection SEQ "SQ03", slip type "POS", sales number "P003", line number "1", scheduled collection date "2022/6/30", and collection method " The expected collection amount is ``¥1,400'', the collected amount is ``0'', and the receivables category is ``Accounts Receivable''.

(S1: Accounts receivable input processing)
A specific example of the accounts receivable input process will be described with reference to FIGS. 4 to 7. For example, the accounts receivable input unit 102b makes an adjustment by adding an adjustment amount to the billed amount, which is the expected collection amount, in response to an operator's operation on the accounts receivable input screen displayed on the monitor 114, and inputs the billing number and billing date. , the billing data including the store, billing destination, and adjusted billing amount is generated and registered in the data table 106a.

The accounts receivable information displayed on the accounts receivable input screen is displayed after linking various data such as POS data, collection schedule data, collection schedule breakdown data, billing data, and bill destination data. Furthermore, after pressing the registration button on the accounts receivable input (details screen), billing data, bill destination data, and collection schedule breakdown data are newly registered, and the collection schedule data is overwritten and updated.

FIG. 4 is a diagram showing a display example of the main screen of the accounts receivable input screen. As shown in FIG. 4, the main screen of the accounts receivable input screen includes an extraction condition setting area 501 for specifying business days, stores, and billing destinations, as well as business days, stores, billing destinations, billing destinations, and billing amounts. , an extraction result display area 502 in which a statement including a billing number, a scheduled collection date, finalized information, a displayed total amount that is the displayed total amount, and a finalized total amount in which the finalized amount is displayed. ing. The confirmed information is set based on the expected collection amount and the collected amount of the collection schedule data. If the item has been collected, the confirmed information is set to confirmed (checked), and if the item has not been collected, it is set to unconfirmed (unchecked).

(1) Displaying target data In the extraction condition setting area 501, specify extraction conditions such as business days, store, and billing destination, and press the display button. In actual business, processing is performed for each specific business day/store, so extraction is often performed by specifying one business day for "business day" and one store for "store." In the example shown in FIG. 4, the business day "2022/5/11" and the store "TEN001" are specified as the extraction conditions.

(2) Selection of processing target (1) Data of target items of scheduled collection data and POS data that meet the extraction conditions are read from the data table 106a and displayed in the extraction result display area 502. When a processing target is selected in the extraction result display area 502, a transition is made to a detailed screen where the contents of collection schedule data, collection schedule breakdown data, billing data, and bill destination data associated with the selected processing target are displayed. If collection schedule breakdown data, billing data, and bill destination data are not registered in the data table 106a, the corresponding items are hidden.

The grayed-out (hatched) item "Claim number: GEN001" is not subject to update processing in accounts receivable entry because cash was collected on the business day. In the example shown in FIG. 4, the third line of the statement (billing address: SEI999: individual customer) is selected, and a statement screen as shown in FIG. 5 is displayed.

FIG. 5 is a diagram showing a display example of the details screen of the accounts receivable input screen (when the third line of the details is selected). As shown in FIG. 5, the details screen of the accounts receivable input screen includes an area 503 where business days, stores, billing destinations, billing destinations, billing amounts, and status are displayed, as well as an area 503 that displays adjustments for the accounts receivable amount (store advances, area 504 for setting collection schedule (discounts, etc.), area 505 for setting collection schedule, area 506 for setting billing address information, area 506 for setting notes, and a registration button. , is equipped with.

The "Status" in the area 503 is displayed based on the billing number, scheduled collection amount, and collected amount of the scheduled collection data in one of the following four patterns. The four patterns are (1) "unconfirmed", (2) "confirmed/uncollected", (3) "confirmed/partially collected", and (4) "confirmed/collected". In the example shown in the figure, the status is "unconfirmed."

In FIG. 5, input is not allowed in grayed-out (hashing) locations (reference locations). White areas can be entered (for input items).

(1) Input contents In the area 504 (amount of accounts receivable), store advances and discounts determined by the head office are entered, the amount is determined, and whether or not an invoice is required is selected. Specifically, for the adjustment amount, details of transaction classification, invoiced amount, invoiced consumption tax amount, tax rate information, and receivable item classification are entered, and amount determination information and invoice unnecessary information are set. Additionally, the store billing amount and total billing amount are displayed for reference. In the example shown in Figure 5, the details of the adjustment amount include the transaction category "taxi fare", the billed amount "¥300", the billed consumption tax amount "¥30", and the tax rate information "excluding tax: tax rate 10%". ", Receivables item classification "Advance payment", second line shows transaction classification "Rebate (discount)", bill amount "¥-100", billed consumption tax amount "¥-10", tax rate information "Tax included: tax rate 10%,” the credit item classification “Accounts Receivable,” the amount confirmation information “ON,” and the no-invoice information “OFF” specified. Additionally, the store billed amount "¥1,400" and the total billed amount "¥1,620" are displayed.

In area 505 (collection schedule), select billing date, scheduled collection date = transfer request date, and collection method = deposit request method. In the example shown in FIG. 5, the billing date "2022/5/16", the scheduled collection date "2022/5/20", and the collection method "transfer" are input.

In area 506 (bill destination information), the bill destination and print information (destination name, name of person in charge, address, telephone number, etc.) are input. In the example shown in Figure 5, the billing address is "SS001: Obi-shichi 1st Secretarial Division", the address name is "Obi-shichi 1st Secretarial Division", the name of the person in charge is "○○ △△", and the address is "Chuo-ku, Tokyo." ○○” has been entered.

In area 507 (remarks), the customer's purpose of use is input. In the example shown in the same figure, the note "Use for entertaining Mr. XXX" is input.

After inputting various items, when the registration button is pressed, the billing data, bill destination data, and collection schedule breakdown data according to the input contents are newly updated, and the collection schedule data is overwritten.

Figure 6 (A) is a data example of billing data, Figure 6 (B) is a data example of billing data, Figure 6 (C) is a data example of collection schedule data, and Figure 6 (D) is collection schedule breakdown data. An example of data is shown. When updating with the above contents, the items that will be updated are indicated by hatching, and if all items are hatched, a new record will be created.

As shown in Figure 6(A), the billing data includes the billing number, slip type, billing date, store, billing address, billing address, scheduled collection date, billing amount, billing amount (main amount), billing amount ( Consumption tax amount), invoice issue date, and invoice necessity information (necessary or unnecessary). In the example shown in the figure, the third line includes billing number "SE001", slip type "billing", billing date "2022/5/16", store "TEN001: Kyobashi Branch", billing address "SEI999: individual customer" , Billing address: "SS001: Obi 7 1st Secretarial Division", Expected collection date: "2022/5/20", Billed amount: "¥1,620", Billed amount (main amount): "¥1,458", Request The amount (consumption tax amount) “¥162” and the invoice necessity information “Required” are added.

As shown in FIG. 6(B), the bill destination data includes the following items: bill destination, destination name, person in charge, address, telephone number, proviso, summary, and remarks. In the example shown in the figure, the first line contains the billing address "SS001: Obi-shichi 1st Secretarial Division", the addressee name "Obi-shichi 1st Secretarial Division", the name of the person in charge "○○ △△", and the address. ``○○, Chuo-ku, Tokyo'', phone number ``03-0000-0000'', and notes ``Used for entertaining Mr. ○○'' are added.

As shown in Figure 6(C), the collection schedule data includes the scheduled collection date "2022/5/20", collection method "transfer", and billing number "SE001" on the 3rd line, and collection SEQ on the 6th line. "SQ06", slip type "input", sales number "P003", line number "2", scheduled collection date "2022/5/20", collection method "transfer", billing number "SE001", scheduled collection amount "¥ 330'', collected amount ``0'', receivable item classification ``advance payment'', 7th line, collection SEQ ``SQ07'', document type ``input'', sales number ``P003'', line number ``3'', scheduled collection date “2022/5/20”, collection method “transfer”, billing number “SE001”, expected collection amount “¥330”, collected amount “0”, and credit category “advance money” are added. There are two types of slips: "POS" and "input." If the document is created by POS import, it is "POS," and if it is created by accounts receivable input, it is "input."

As shown in Figure 6 (D), the collection schedule breakdown data includes items such as collection SEQ, document type, sales number, line number, head office additional transaction classification, sales amount, sales amount, sales consumption tax amount, and tax rate information. ing. In the example shown in the figure, the first line is collection SEQ "SQ06", slip type "input", sales number "P003", line number "2", head office additional transaction classification "taxi fare", sales amount "¥330". ”, sales amount “¥300”, sales consumption tax amount “¥30”, tax rate information “excluding tax: tax rate 10%”, second line is collection SEQ “SQ07”, slip type “input”, sales number “P003” ”, line number “3”, head office additional transaction classification “Rebate (discount), sales amount “¥-110”, sales amount “¥-100”, sales consumption tax amount “¥-10”, tax rate information “Tax included: 10% tax rate will be added.

FIG. 7 is a diagram showing a display example of the main screen that changes after the registration button is pressed on the details screen of FIG. The extraction result display area 502, the displayed amount meter, and the confirmed amount meter have been updated. The record displayed on the main screen is only the slip type "POS". Collection schedule SEQ "SQ06" and "SQ07" are details added from accounts receivable input, so they are linked to collection schedule SEQ "SQ03" which has the same sales number, and the collection schedule amount is aggregated and displayed. .

(S2: Invoice issue processing)
A specific example of bill issuing processing will be described with reference to FIGS. 8 to 11. The bill issuing unit 102c issues a bill based on billing data registered in the data table 106a, for example, in response to an operator's operation on a bill issuing screen displayed on the monitor 114.

FIG. 8 is a diagram showing a display example of the bill issuing screen. The invoice issue screen includes fields for specifying business days, billing dates, billing destinations, extraction conditions for issued/unissued bills, and an output button. When the extraction conditions are specified and the output button is pressed, billing data corresponding to the extraction conditions is extracted from the data table 106a and a bill is issued.

The operating procedure is to specify the invoice to be output using the extraction conditions and press the output button. In actual business, the "Billing date" specifies the amount processed on the same day, the "Invoice not issued" is checked (specified), the billing data is extracted, and the unissued portion for which the receivables were entered on that day is issued. conduct. You can also respond to reissue requests based on customer requests by checking the already issued box.

In the example shown in FIG. 8, the invoice date "2022/5/16" and the invoice not yet issued are specified, and the output button is pressed. For example, an invoice as shown in FIG. 9(A) is output (display output and/or printer output). Further, as shown in FIG. 9(B), the bill issue date "2022/5/16" of the billing data of the billing number "SE001" is updated.

FIG. 10 is a diagram showing a display example of the main screen of the accounts receivable input screen after the invoice is issued in FIG. 8.
In the extraction condition setting area 501, the business day and store are specified based on the report or receipt from the store. This section represents the screen image when no extraction conditions are specified.
In the extraction result display area 502, collection schedule data, including cash collection data, is displayed for each sales number. Confirmed state = bill can be issued. In addition, in actual business, the displayed amount totals are set to the finalized amount totals for each store and each business day to check closing processing on business days.

Supplementing the screen display, it is possible to control whether or not to update the data based on whether or not the scheduled collection data has been collected. Patterns that cannot be updated include, for example, cases in which collection has been completed on the same day, or payment has been made after processing by inputting accounts receivable; in other cases, updates are basically possible. The reason why non-updateable details are also displayed is to make it possible to check the collection status and refer to past data on the details screen.

FIG. 11 is a diagram showing a display example of the details screen when the third line is selected in the extraction result display area 502 of the main screen of FIG. 10. In FIG. 11, the status in area 503 is "confirmed/uncollected."

In area 504, advance payments are input based on reports or receipts from stores, and discount information determined by the head office is input. In area 505, processing for adding head office details to the collection schedule data selected on the main screen, processing for determining billing amounts, and processing for linking and registering bill destination data are performed. Additionally, it is possible to check the collection status of data scheduled for collection. By pressing the registration button, billing data is created/updated.

As explained above, according to the present embodiment, POS data including sales number, business day, store, billing address, product, and sales amount is imported from a store's POS terminal, and based on the imported POS data, sales are The importing unit 102a generates collection schedule data including number, scheduled collection date, collection method, invoice number, and scheduled collection amount, and on the accounts receivable input screen displayed on the monitor 114, the invoice that is the scheduled collection amount of the collection schedule data is The accounts receivable input unit 102b performs an adjustment by adding an adjustment amount to the amount and generates billing data including the billing number, billing date, store, billing destination, and adjusted billing amount, and issues an invoice based on the billing data. Since the head office or the head office side is equipped with an invoice issuing unit 102c, the head office or the head office side can additionally register adjustment fees (including non-business billing expenses) and issue invoices for the POS data acquired from stores. becomes possible.

[4. Contribution to the Sustainable Development Goals (SDGs) led by the United Nations]
This embodiment can contribute to improving business efficiency and promoting appropriate business decisions of companies, and thus can contribute to Goals 8 and 9 of the SDGs.

Furthermore, this embodiment can contribute to reducing waste loss and promoting paperless and electronic systems, making it possible to contribute to Goals 12, 13, and 15 of the SDGs.

Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all of the processes described as being performed manually can be performed manually. Alternatively, some of the steps can be performed automatically using known methods.

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

Furthermore, with respect to the credit management system 100, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, all or any part of the processing functions provided in the receivables management system 100, especially each processing function performed by the control unit, may be realized by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware using wired logic. Note that the program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is stored in the receivables management system as necessary. Machine read to 100. That is, a storage unit such as a ROM or an HDD (Hard Disk Drive) stores a computer program that cooperates with an OS to give instructions to a CPU and perform various processes. This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

Further, this computer program may be stored in an application program server connected to the receivables management system 100 via an arbitrary network, and it is also possible to download all or part of it as necessary. be.

Further, a program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes 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), and an EEPR. OM (registration) Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVDs (Digital Versatile Discs), Blu-ray (registered trademark) Discs, etc. shall include any “portable physical medium”.

Furthermore, a "program" is a data processing method written in any language or writing method, and does not matter in the form of source code or binary code. Note that a "program" is not necessarily limited to a unitary structure, but may be distributed as multiple modules or libraries, or may work together with separate programs such as an OS to achieve its functions. Including things. Note that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, and the installation procedure after reading.

The various databases etc. stored in the storage unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and are used for various processing and website provision. Stores programs, tables, databases, web page files, etc.

Further, the credit management system 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Further, the debt management system 100 may be realized by installing software (including programs, data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of dispersion and integration of devices is not limited to what is shown in the diagram, and all or part of them can be functionally or physically divided into arbitrary units according to various additions or functional loads. It can be configured in a distributed/integrated manner. That is, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively.

100 Receivables management system 102 Control unit 102a Import unit 102b Accounts receivable input unit 102c Invoice issuing unit 102d Screen display control unit 104 Communication interface unit 106 Storage unit 106a Data table 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network 400 POS terminal

Claims (7)

A receivables management system comprising a control unit,
The control unit includes:
POS data including sales number, business day, store, billing address, product, and sales amount is imported from the store's POS terminal, and based on the imported POS data, sales number, scheduled collection date, collection method, billing number, and collection schedule are calculated. an acquisition means for generating collection schedule data including the amount;
On the accounts receivable input screen displayed on the display, adjust the invoice amount, which is the expected collection amount in the collection schedule data, by adding an adjustment amount, and enter the invoice number, billing date, store, billing destination, and adjusted billing amount. an accounts receivable input means for generating billing data including;
bill issuing means for issuing a bill based on the billing data;
A receivables management system characterized by: The receivables management system according to claim 1, wherein the accounts receivable input means performs an adjustment using an adjustment amount when the billing party of the POS data is an individual customer, and the adjustment amount includes a store advance payment. . 3. The receivables management system according to claim 2, wherein the adjustment amount includes a discount amount. 4. The accounts receivable input means generates collection schedule breakdown data including a sales number, a classification of the adjustment money, and the sales amount when making the adjustment using the adjustment money. receivables management system. The accounts receivable input means generates bill destination information including a bill destination, destination name, person in charge name, and address in response to an operator's operation on the accounts receivable input screen. The debt management system according to claim 1 or 2. A receivables management method executed by an information processing device including a control unit, the method comprising:
executed in the control unit,
POS data including sales number, business day, store, billing address, product, and sales amount is imported from the store's POS terminal, and based on the imported POS data, sales number, scheduled collection date, collection method, billing number, and collection schedule are calculated. an import process that generates collection schedule data including the amount;
On the accounts receivable input screen displayed on the display, adjust the invoice amount, which is the expected collection amount in the collection schedule data, by adding an adjustment amount, and enter the invoice number, billing date, store, billing destination, and adjusted billing amount. an accounts receivable entry process that generates billing data including;
an invoice issuing step of issuing an invoice based on the billing data;
A receivables management method characterized by comprising: A receivables management program to be executed by an information processing device equipped with a control unit,
executed in the control unit,
POS data including sales number, business day, store, billing address, product, and sales amount is imported from the store's POS terminal, and based on the imported POS data, sales number, scheduled collection date, collection method, billing number, and collection schedule are calculated. an import process that generates collection schedule data including the amount;
On the accounts receivable input screen displayed on the display, adjust the invoice amount, which is the expected collection amount in the collection schedule data, by adding an adjustment amount, and enter the invoice number, billing date, store, billing destination, and adjusted billing amount. an accounts receivable entry process that generates billing data including;
an invoice issuing step of issuing an invoice based on the billing data;
Receivables management program for executing.

Images