JP7613927B2 - Expense payment system, expense payment method, and expense payment program - Google Patents

Description

The present invention relates to an expense payment system, an expense payment method, and an expense payment program.

For example, there are many aspects of fixed asset registration that require specialized knowledge, and payment application personnel are unable to determine the information necessary for fixed asset registration. For example, Patent Document 1 describes a system for fixed asset registration.

JP 2006-107175 A

However, the above-mentioned Patent Document 1 does not state anything about how payment application personnel can easily register the information required for fixed asset registration.

The present invention has been made in consideration of the above, and aims to provide an expense payment system, expense payment method, and expense payment program that enable payment application personnel to easily register the information required for fixed asset registration.

To solve the above problems and achieve the objective, the present invention provides an expense payment system equipped with a control unit, the control unit being configured to be able to access a master group in which information required for fixed asset registration is registered in association with input items for payment applications, and the system is equipped with a payment application means for referencing the master group, inputting input items for payment applications, and creating payment application data, and an integration means for integrating the created payment application data with a fixed asset system.

According to one aspect of the present invention, the control unit may include an approval means for approving the created payment application data, and the linking means may link the approved payment application data with the fixed asset system.

According to one aspect of the present invention, the payment application data may include a voucher type that specifies whether or not the data is subject to fixed asset registration, and the linking means may link with the fixed asset system when the voucher type of the payment application data is subject to fixed asset registration.

According to one aspect of the present invention, the fixed asset system may refer to the master and generate fixed asset registration information based on the payment application data.

In order to solve the above-mentioned problems and achieve the objective, the present invention is an expense payment method executed by an information processing device equipped with a control unit, the control unit being configured to be able to access a master group in which information required for fixed asset registration is registered in association with input items of a payment application, and the method includes a payment application process executed by the control unit for referencing the master group, inputting input items of the payment application, and creating payment application data, and an integration process for linking the created payment application data with a fixed asset system.

In order to solve the above-mentioned problems and achieve the objective, the present invention is an expense payment program to be executed on an information processing device equipped with a control unit, and is configured to be able to access a master group in which information required for fixed asset registration is registered in association with input items of a payment application, and the control unit executes a payment application process of inputting input items of a payment application to create payment application data by referring to the master group, and an integration process of linking the created payment application data with a fixed asset system.

The present invention has the effect of enabling payment application personnel to easily register the information required for fixed asset registration.

FIG. 1 is a block diagram showing an example of the configuration of an expense payment system according to the present embodiment. FIG. 2 is a diagram showing an example of the configuration of various masters. FIG. 3 is a diagram showing an example of the configuration of various masters. FIG. 4 is a diagram showing an example of the configuration of various masters. FIG. 5 is a diagram showing a flow for explaining an outline of the overall processing of the control unit of the expense payment system according to the present embodiment. FIG. 6 is a diagram for explaining a specific example of the process of the control unit of the expense payment system according to the present embodiment. FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the expense payment system according to the present embodiment.

Below, an embodiment of the expense payment system, expense payment method, and expense payment program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Overview]
For example, there are many aspects of fixed asset registration that require specialized knowledge, and payment application personnel were not able to determine the information necessary for fixed asset registration. Therefore, all asset registration was carried out by asset management personnel. For example, at each branch, the main assets are purchased equipment, and the number of purchases is about several thousand per year, so a large number of fixed asset registrations are required.

Specifically, (1) payment operations and asset management operations are separate, with payment operations only making payments and asset registration being done separately as asset management operations; the processes are separated. As a result, when assets are purchased, data registration is required in two separate business areas, and the registration burden is high in asset management operations. (2) It is difficult for payment application personnel to determine the information required to register fixed assets, so the burden is unevenly distributed among asset management personnel.

Therefore, in this embodiment, the information to be entered when applying for a payment is simplified, and a master that determines the information required for asset registration is provided, allowing even payment application personnel to register assets with simple input, thereby reducing the burden of asset management work.

Specifically, for example, for supplies and other items that are purchased in large quantities at each branch, we focused on the fact that a master can be set up to determine the information required for fixed asset registration, and made it possible for each branch to enter the information required for fixed asset registration. Also, by providing an explanation in the linking master, we made it possible to select the correct target.

According to this embodiment, (1) even payment application personnel can register assets with simple input, which reduces the burden of asset management work. (2) Duplicate registration is not required when purchasing an asset, which reduces operational errors such as incorrect registration.

2. Configuration
The configuration of an expense payment system 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 expense payment system 100 according to this embodiment.

The expense payment system 100 is a commercially available desktop personal computer. Note that the expense payment system 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

As shown in FIG. 1, the expense payment system 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the expense payment system 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the expense payment 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 the communication line. Here, the network 300 has a function of communicatively connecting the expense payment system 100 to the terminal 250, the fixed asset system 400, and the server 200, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106, which will be described later, may be stored in the server 200.

The fixed asset system 400 includes a communication interface unit, a control unit, a memory unit for storing various master data, and the like. As described above, the expense payment system 100 is configured to be capable of data communication with the fixed asset system 400, and is configured to be able to access, for example, various master data of the fixed asset system 400, and is also configured to be able to link with the payment application data described below.

The terminals 250... are terminals used by payment application personnel and their approvers, etc., and allow the payment application personnel and their approvers to access the expense payment system 100. The expense payment system 100 and the terminals 250... constitute a server-client system. For example, the expense payment system 100 provides various screens in response to access from the terminals 250..., and accepts input from the terminals 250... on the input screen.

The input/output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. In addition, "output" includes displaying on the monitor of the output device 114 and printing on the printer of the output device 114. In addition, a user's operation on the information displayed on the monitor 114 using the input device 112 or the like may be referred to as a "user operation via a UI."

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work with the OS (Operating System) to give commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, 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, or an optical disk. The storage unit 106 also includes a transaction category master 106a, a slip type master 106b, a closing category master 106c, a settlement condition master 106d, an acquisition category master 106e, an expense category master 106f, a tax category master 106g, a tax-inclusive category master 106h, and a data table 106i.

The fixed asset system 400 also includes a transaction classification asset type mapping master 401, an asset type master 402, an asset type master by business department 403, an asset business establishment master 404, and a structural details master 405.

Figures 2 to 4 show examples of the configuration of various masters. The transaction category master 106a is managed by the expense payment system 100. The transaction category asset type mapping master 401 is managed by the expense payment system 100 and the fixed asset system 400. The asset type master 402, the business department asset type master 403, and the asset business establishment master 404 are managed by the fixed asset system 400. The structural details master 405 is an extended function of the fixed asset system 400.

As shown in FIG. 2(A), the transaction category master 106a can be configured as a table in which data such as transaction category, transaction category name, and description are associated and registered. In the example shown in the figure, the first line has transaction category "10001", transaction category name "tools", and description "used when purchasing tools used in processing and assembly", the second line has transaction category "10002", transaction category name "appliances and fixtures", and description "used when purchasing furniture, electrical equipment, household goods, office equipment, clocks, and signs", and the third line has transaction category "10003", transaction category name "buildings", and description "used when purchasing buildings".

As shown in FIG. 2(B), the transaction category asset type mapping master 401 can be configured as a table in which data such as transaction category, transaction category name, asset type code, and asset type name are associated and registered. In the example shown in the figure, the first line has transaction category "10001", transaction category name "tools", asset type code "010", and asset type name "tools", the second line has transaction category "10002", transaction category name "fixtures and fixtures", asset type code "020", and asset type name "fixtures and fixtures", and the third line has transaction category "10003", transaction category name "building", asset type code "030", and asset type name "building".

The asset type master 402 can be composed of a table or the like in which data such as asset type code, asset type name, declared asset type, asset type name, asset type, asset type name, useful life classification, and useful life classification name are associated and registered, as shown in Figure 3 (C). In the example shown in the figure, the first line has an asset type code of "010", an asset type name of "tools", a declared asset type of "010", an asset type name of "tools, furniture, and fixtures", an asset type of "6", an asset type name of "tools, furniture, and fixtures", a useful life category of "70", and a useful life category name of "tools". The second line has an asset type code of "020", an asset type name of "fixtures and fixtures", a declared asset type of "010", an asset type name of "tools, furniture, and fixtures", an asset type of "6", an asset type name of "tools, furniture, and fixtures", a useful life category of "80", and a useful life category name of "fixtures and fixtures". The third line has an asset type code of "030", an asset type name of "building", a declared asset type of "030", an asset type name of "not subject to local tax", an asset type of "0", an asset type name of "not subject to local tax", a useful life category of "10", and a useful life category name of "building".

As shown in FIG. 3(C), the business establishment department-specific asset type master 403 can be composed of a table or the like that associates and registers data such as asset type code, asset type name, tax depreciation method, tax depreciation method name, tax survival rate, tax depreciation limit rate, tax memorandum value, accounting depreciation method, accounting depreciation method name, accounting survival rate, accounting depreciation limit rate, and accounting memorandum value.

In the example shown in the figure, the first line has asset type code "010", asset type name "tools", tax depreciation method "8", tax depreciation method name "straight line", service survival rate "0", tax depreciation limit rate "0", tax memorandum value "1", accounting depreciation method "8", accounting depreciation method name "straight line", service survival rate "0", accounting depreciation limit rate "0", and accounting memorandum value "1". The second line has asset type code "020 asset type name "furnishings and fixtures", tax depreciation method "8", tax depreciation method name "straight line", service survival rate "0", tax depreciation limit rate "0", tax memorandum value "1", accounting depreciation method "8", accounting depreciation method name "straight line", service survival rate "0", tax depreciation limit rate "0", and accounting memorandum value "1". The third line has the asset type code "030", asset type name "Building", tax depreciation method "8", tax depreciation method name "Straight-line method", accounting survival rate "0", tax depreciation limit rate "0", tax memorandum value "1", accounting depreciation method "8", accounting depreciation method name "Straight-line method", accounting survival rate "0", accounting depreciation limit rate "0", and accounting memorandum value "1".

As shown in FIG. 3(C), the asset establishment master 404 can be configured as a table in which data such as establishment code, asset type name, municipality code, and municipality name are associated and registered. In the example shown in the figure, the first line has the establishment code "001", asset type name "Tokyo Head Office", municipality code "131024", and municipality name "Chuo-ku, Tokyo", and the second line has the establishment code "002", asset type name "Osaka Head Office", municipality code "271004", and municipality name "Osaka City, Osaka Prefecture".

As shown in FIG. 3(D), the structural details master 405 can be composed of a table or the like in which data such as structural details code, structural details name, asset type code, useful life category, useful life category name, structure, structure name, details, details name, useful life, and description are associated and registered.

In the example shown in the figure, the first line has the structural detail code "701010", structural detail name "measuring tool", asset type code "010", useful life category "70", useful life category name "tool", structure "10", structure name "measuring tool", detail "10", detail name "measuring tool", useful life "5", and explanation "Tools used for measurement in the production process. Block gauge, standard tape measure, dial gauge, roughness measuring device." The second line has the structural detail code "702010", structural detail name "inspection tool", asset type code "010", useful life category "70", useful life category name "tool", structure "20", structure name "inspection tool", detail "10", detail name "inspection tool", useful life "5", and explanation "Tools used for inspection in the production process. Block gauge, standard tape measure, dial gauge, roughness measuring device." The third line has the following: structural detail code "703010", structural detail name "jig", asset type code "010", useful life category "70", useful life category name "tool", structure "30", structural name "jig", detail "10", detail name "jig", useful life "3", and description "Tools used to secure products and assist in the production process. Cutting jig, welding jig, bending jig."

As shown in FIG. 4(A), the voucher type master 106b can be configured as a table in which voucher types and voucher type names are associated and registered. In the example shown in the figure, the first line has voucher type "10" and voucher type name "asset acquisition", and the second line has voucher type "20" and voucher type name "expenses". When the voucher type is "10: asset acquisition", which is subject to fixed asset registration, it links with the fixed asset system 400. The voucher type "expenses" is a voucher broadly related to expense claims, such as non-asset equipment, entertainment expenses, events, etc.

As shown in FIG. 4B, the spot payment classification master 106c is a master that determines the cycle of scheduled payment dates, and can be configured as a table in which spot payment classifications and spot payment classification names are associated with each other. In the example shown in the figure, the first line has spot payment classification "0" and spot payment classification name "this time", the second line has spot payment classification "1" and spot payment classification name "next time", the third line has spot payment classification "2" and spot payment classification name "next time", and the fourth line has spot payment classification "3" and spot payment classification name "spot payment (each time)".

As shown in FIG. 4(C), the payment condition master 106d can be configured as a table in which payment conditions and payment condition names are associated and registered. In the example shown in the figure, the first line has payment condition "1000" and payment condition name "cash", the second line has payment condition "1020" and payment condition name "check", the third line has payment condition "1040" and payment condition name "FB transfer", and the fourth line has payment condition "1060" and payment condition name "bill of exchange".

As shown in FIG. 4(D), the acquisition category master 106e is composed of a table in which the acquisition category and the acquisition category name are registered in association with each other. In the example shown in the figure, the first line is the acquisition category "0" and the acquisition category name "New", the second line is the acquisition category "1" and the acquisition category name "Used", and the third line is the acquisition category "2" and the acquisition category name "Moved".

As shown in FIG. 4(E), the expense category master 106f is composed of a table in which expense categories and expense category names are associated and registered. In the figure, the first line has expense category "0" and expense category name "general expenses", the second line has expense category "1" and expense category name "manufacturing expenses", and the third line has expense category "2" and expense category name "non-operating expenses".

As shown in FIG. 4(F), the tax category master 106g is composed of a table in which tax categories and tax category names are associated and registered. In the example shown in the figure, the first line has tax category "0" and tax category name "Non-subject or non-taxable purchases", the second line has tax category "21" and tax category name "Taxable sales (10%)", the third line has tax category "71" and tax category name "Taxable purchases of taxable sales (8%)", and the fourth line has tax category "81" and tax category name "Taxable purchases of taxable sales (10%)".

As shown in FIG. 4(G), the tax-inclusive category master 106h is composed of a table in which tax-inclusive categories and tax-inclusive category names are associated and registered. In the example shown in the figure, the first line is tax-inclusive category "0" and tax category name "Not applicable", the second line is tax-inclusive category "1" and tax-inclusive category name "Tax included", the third line is tax-inclusive category "2" and tax-inclusive category name "Tax excluded", the fourth line is tax-inclusive category "3" and tax-inclusive category name "Tax excluded breakdown (inside)", and the fifth line is tax-inclusive category "4" and tax-inclusive category name "Tax excluded breakdown (outside)".

Data table 106i is a file for storing various data such as payment application data. Payment application data has a header section and a detail section (see Figure 6). The header section may include data on the invoice type, supplier, purchase date, closing category, closing date, scheduled payment date, settlement conditions, and reason for application. The detail section may include data on the business establishment, department, transaction category, name, structure detail code, summary, purchase amount, consumption tax, asset name, quantity, inventory management department, acquisition category, expense category, tax category, and tax included category.

The control unit 102 is a CPU or the like that controls the expense payment system 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 processing based on these stored programs. The transaction classification master 106a, slip type master 106b, closing classification master 106c, settlement condition master 106d, acquisition classification master 106e, expense classification master 106f, tax classification master 106g, tax-inclusive classification master 106h, and data table 106i provided in the memory unit 106, and the transaction classification asset type mapping master 401, asset type master 402, business division asset type master 403, asset business master 404, and structure details master 405 provided in the fixed asset system 400 are referred to as the "master group". The control unit 102 is configured to be able to access the master group. These master groups may be provided in the memory unit 106 or the fixed asset system 400, or may be provided elsewhere (e.g., the server 200), as long as they are accessible by the control unit 102. In terms of function and concept, the control unit 102 includes a payment application unit 102a, an approval unit 102b, a linkage unit 102c, a master maintenance unit 102d, and a screen display control unit 102e.

For example, in response to operations by the payment application clerk on a payment application input screen (not shown) provided to the terminal 250 in response to access from the terminal 250, the payment application unit 102a refers to a master group in which information required for fixed asset registration is registered and linked to the input items of the payment application, enters the input items of the payment application to create payment application data, and registers it in the data table 106i.

The approval unit 102b approves the payment application data registered in the data table 106i, for example, in response to the operation of the approver on an approval screen (not shown) provided to the terminal 250 in response to access from the terminal 250.

The linking unit 102c links the payment application data approved by the approval unit 102b with the fixed asset system 400. The payment application data may include a voucher type that specifies whether or not the data is subject to fixed asset registration, and the linking unit 102c may link with the fixed asset system 400 when the voucher type of the payment application data is subject to fixed asset registration (for example, voucher type "10: asset acquisition").

The fixed asset system 400 may refer to masters (e.g., transaction category asset type mapping master 401, asset type master 402, business department asset type master 403, asset business master 404, structural details master 405) to generate and store fixed asset registration information based on payment application data.

The master maintenance section 102d is for editing, such as inputting, adding, and changing data in the transaction category master 106a, the document type master 106b, the closing category master 106c, the settlement condition master 106d, the acquisition category master 106e, the expense category master 106f, the tax category master 106g, the tax-inclusive category master 106h, and the data table 106i, in response to the administrator's operation of the input device 112 on a master maintenance screen (not shown) displayed on the monitor 114, for example.

The screen display control unit 102e controls the display and input of various screens (e.g., payment application input screen, approval screen, master maintenance screen, etc.) that are output to the monitor 114 and provided to the terminal 250....

3. Specific Examples
A specific example of the processing in the control unit 102 of the expense payment system 100 according to the present embodiment will be described with reference to Figures 1 to 7. Figure 5 is a diagram illustrating an outline of the overall processing flow in the control unit 102 of the expense payment system 100 according to the present embodiment.

(3-1. Overall processing)
With reference to Fig. 5, an outline of the overall processing flow of the control unit 102 of the expense payment system 100 according to this embodiment will be described. In Fig. 5, the payment application unit 102a executes a payment application process (step S1). Specifically, in the payment application process, the payment application unit 102a, for example, in response to an operation by a payment application clerk on a payment application input screen (not shown) provided to the terminal 250 in response to an access from the terminal 250 of the payment applicant, refers to a master group in which information required for fixed asset registration is registered in association with the input items of the payment application, inputs the input items of the payment application to create payment application data, and registers the data in the data table 106i.

The approval unit 102b executes the approval process (step S2). Specifically, in the approval process, the approval unit 102b approves the payment application data registered in the data table 106i in response to the operation of the approver on an approval screen (not shown) provided on the terminal 250 in response to access from the terminal 250 of the approver.

The linking unit 102c executes the linking process (step S3). Specifically, in the linking process, the linking unit 102c links the payment application data approved by the approval unit 102b with the fixed asset system 400. The linking unit 102c may link with the fixed asset system 400 when the "voucher type" of the payment application data is a fixed asset registration target (for example, voucher type "10: asset acquisition").

The fixed asset system 400 creates and registers fixed asset registration information based on the linked payment application data, by referencing the transaction classification asset type mapping master 401, asset type master 402, business department asset type master 403, asset business master 404, and structural details master 405.

In this example, the fixed asset system 400 is configured to create the fixed asset registration information, but the expense payment system 100 may also create the fixed asset registration information and link the created fixed asset registration information to the fixed asset system 400.

(3-2. Sample data)
6 and 7 are diagrams showing sample data for explaining a specific example of the processing of the control unit 102 of the expense payment system 100 according to the present embodiment. A specific example of the processing of the control unit 102 of the expense payment system 100 according to the present embodiment will be explained with reference to the sample data shown in FIG. 6 and FIG.

(Payment application processing S1)
The payment application unit 102a refers to a master group in which information required for fixed asset registration is registered in association with input items of the payment application, and creates payment application data by inputting input items of the payment application in response to operations of the payment application clerk on the payment application input screen. Figure 6 is a diagram showing sample data of the payment application data.

As shown in Figure 6, the payment application data has a header section and a detail section. The header section may include data on the document type, supplier, purchase date, closing category, closing date, scheduled payment date, settlement conditions, and reason for application. The detail section may include data on the business establishment, department, transaction category, name, structure detail code, summary, purchase amount, consumption tax, asset name, quantity, inventory management department, acquisition category, expense category, tax category, and tax-inclusive category. One asset is linked to the fixed asset system 400 per detail. In the figure, as an example, "◯" indicates a link target of the fixed asset system 400, and "-" indicates a non-link target of the fixed asset system 400.

Payment application data is configured to be able to be entered on the payment application input screen. For example, when a payment application input item on the payment application input screen is right-clicked, the corresponding master data is read and a screen of input candidates is displayed, allowing the person in charge to select from the input candidates. For example, when the input item "voucher type" is right-clicked, the voucher type master 106b is referenced and input candidates for voucher type "10: asset acquisition" and voucher type "20: expense" are read and the input candidate screen is displayed, allowing the payment application person in charge to select from the input candidates.

In addition, for the "closing category", input candidates are read from the closing category master 106c, for the "payment conditions", from the payment conditions master 106d, for the "acquisition category", from the acquisition category master 106e, for the "expense category", from the expense category master 106f, for the "tax category", from the tax category master 106g, and for the "tax included category", from the tax included category master 106h, and are displayed on the input candidate screen.

For "transaction category", input candidates and their explanations are read from the transaction category master 106a and an input candidate screen is displayed. The payment application clerk can select an input item while looking at the explanation. For "structural detail code", input candidates and their explanations are read from the structural detail master 405 and displayed on the input candidate screen. The payment application clerk can select an input item while looking at the explanation.

In the example of payment application data shown in Figure 6, the header section contains the document type "10: Asset acquisition", supplier "701010: OB Co., Ltd.", purchase date "2020/10/25", closing category "0: This time", closing date "2020/10/30", scheduled payment date "2020/11/30", payment terms "1040: FB transfer", and reason for application "Purchase of office desks".

The details are as follows: Line 1: Business location "001 Tokyo Head Office", department "5 General Affairs Department", transaction category "10002", name "Furniture and equipment", structural details code "801010 Office desks - metal", summary "Purchase of office desks", purchase amount "1,000,000", consumption tax "100,000", asset name "5 office desks", quantity "5", inventory management department "5 General Affairs Department", acquisition category "0 New", expense category "0 General expenses", tax category "81 Taxable purchases on taxable sales (10%)", tax-inclusive category "4 Breakdown excluding tax (excluding)".

The second line shows the business establishment "001 Tokyo Head Office", department "6 Sales Department", transaction category "10002", name "Furniture and fixtures", structural detail code "801010 Office desks - metal", summary "Purchase of office desks", purchase amount "1,000,000", consumption tax "100,000", asset name "6 office desks", quantity "6", inventory management department "6 Sales Department", acquisition category "0 New", expense category "0 General expenses", tax category "81 Taxable purchases on taxable sales (10%)", tax-inclusive category "4 Breakdown excluding tax (excluding)".

(Approval process S2)
The approval unit 102b approves the payment application data created by the payment application unit 102a in response to an operation by an approver.

(Cooperation process S3)
The linking unit 102c links the payment application data approved by the approval unit 102b with the fixed asset system 400. In this case, the approval unit 102b links with the fixed asset system 400 when the "voucher type" of the payment application data is "10: asset acquisition". If the "voucher type" is "20: expense", there is no linking. In the example of the payment application data shown in Figure 6, the "voucher type" is "10: asset acquisition", so there is linking.

(Fixed Assets System 400)
The fixed asset system 400 creates and registers fixed asset registration information based on the linked payment application data, by referencing a transaction classification asset type mapping master 401, an asset type master 402, an asset type master by business establishment department 403, an asset establishment master 404, and a structural details master 405. Fig. 7 is a diagram showing sample data of the fixed asset registration information.

Fixed asset registration information may include data such as asset number, branch number, asset name, asset category, asset type, asset type, business establishment, accounting department, inventory management department, reporting category, reporting municipality, acquisition date, depreciation start date, acquisition amount, consumption tax, quantity, remarks, acquisition category, expense category, tax depreciation method, tax useful life, tax survival rate, tax survival value, tax depreciation limit rate, tax depreciation limit, tax memorandum value, accounting depreciation method, accounting useful life, accounting survival rate, accounting survival value, accounting depreciation limit rate, accounting depreciation limit, accounting memorandum value, structure name, and detail name.

The "asset number" is automatically assigned. The "asset name" from the payment application data is set as the "asset name". The "asset category" is fixed to "0: main asset". The "asset type" is set by retrieving the asset type from the transaction category-asset type mapping master 401 using the "transaction category" from the payment application data as a key. The "asset type" is set by retrieving the asset type from the asset type master 402 using the "asset type" as a key. The "business establishment" from the payment application data is set as the "business establishment". The "accounting department" and "inventory management department" are set as the "department" from the payment application data.

The "declaration category" is set by retrieving the declaration category from the asset type master 402 using the "asset type" as a key. The "declaration municipality" is set by retrieving the "declaration municipality" from the asset business establishment master 404 using the "business establishment" as a key. The "acquisition date", "depreciation start date", "acquisition amount", "consumption tax", "quantity", "remarks", "acquisition category", and "expense category" are set to the "purchase date", "purchase date", "purchase amount", "consumption tax", "quantity", "reason for application", "acquisition category", and "expense category" from the payment application data, respectively.

"Tax depreciation method", "tax useful life", "tax survival rate", "tax salvage value", "tax depreciation limit rate", "tax depreciation limit amount", "tax memorandum value", "accounting depreciation method", "accounting useful life", "accounting survival rate", "accounting salvage value", "accounting depreciation limit rate", "accounting depreciation limit amount", and "accounting memorandum value" are obtained and set from the business division asset type master 403 using "asset type" as a key. "Structure name" and "detail name" are obtained and set from the structure details master 405 using "structure details code" as a key.

As described above, according to this embodiment, there is provided a master group in which information required for fixed asset registration is registered in association with input items of a payment application, a payment application unit 102a which refers to the master group and inputs input items of a payment application to create payment application data, and a linking unit 102c which links the created payment application data with the fixed asset system 400, so that the person in charge of payment applications can easily register the information required for fixed asset registration.

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

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

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

5. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth 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 or part of the processes described as being performed manually can be performed automatically using a known method.

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

Furthermore, with regard to the expense payment system 100, each component shown in the figure is a functional concept and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the expense payment system 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the expense payment system 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the expense payment system 100 via any network, and may be downloaded in whole or in part as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a 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 This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

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

The expense payment 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. The expense payment system 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

100 Expense payment system 102 Control unit 102a Payment application unit 102b Approval unit 102c Linkage unit 102d Master maintenance unit 102e Screen display control unit 104 Communication interface unit 106 Memory unit 106a Transaction category master 106b Invoice type master 106c Each time closing category master 106d Settlement condition master 106e Acquisition category master 106f Expense category master 106g Tax category master 106h Tax-inclusive category master 106i Data table 108 Input/output interface unit 112 Input device 114 Output device 200 Server 250 Terminal 300 Network 400 Fixed asset system 401 Transaction category asset type mapping master 402 Asset type master 403 Business establishment department asset type master 404 Asset establishment master 405 Structure details master

Claims (5)

An information processing system including a control unit,
The control unit is
A first master group in which predetermined items constituting payment application data and input candidates thereof are associated and registered;
A second master group in which data of items constituting the payment application data and data of one or more items constituting the fixed asset registration information are associated and registered;
is configured to be accessible to
a payment application means for creating payment application data in response to operations by a person in charge on a payment application input screen that displays input items including predetermined items constituting the payment application data, and for reading and displaying input candidates for the selected predetermined item from the first master group when the person in charge selects a predetermined item, and setting the input candidate selected by the person in charge to the predetermined item;
a fixed asset registration information processing means for creating fixed asset registration information based on the created payment application data, and at that time, for data of items constituting the payment application data registered in the second master group, setting data of one or more items constituting the associated fixed asset registration information;
An information processing system comprising : The control unit is
An approval means for approving the created payment application data,
2. The information processing system according to claim 1, wherein said fixed asset registration information processing means creates fixed asset registration information for approved payment application data. The payment application data includes a slip type that specifies whether or not the payment application data is subject to fixed asset registration,
3. The information processing system according to claim 1, wherein said fixed asset registration information processing means creates fixed asset registration information when a slip type of said payment application data is a fixed asset registration target. An expense payment method executed by an information processing device having a control unit,
The control unit is
A first master group in which predetermined items constituting payment application data and input candidates thereof are associated and registered;
A second master group in which data of items constituting the payment application data and data of one or more items constituting the fixed asset registration information are associated and registered;
It is configured to be accessible,
Executed in the control unit,
a payment application process for creating payment application data in response to operations by a person in charge on a payment application input screen that displays input items including predetermined items constituting the payment application data, and when the person in charge selects a predetermined item, input candidates for the selected predetermined item are read from the first master group and displayed, and the input candidate selected by the person in charge is set to the predetermined item;
a fixed asset registration information processing step of creating fixed asset registration information based on the created payment application data, and at that time, setting data of one or more items constituting the associated fixed asset registration information for data of items constituting the payment application data registered in the second master group;
Expense payment method comprising: An expense payment program to be executed by an information processing device having a control unit,
The control unit is
A first master group in which predetermined items constituting payment application data and input candidates thereof are associated and registered;
A second master group in which data of items constituting the payment application data and data of one or more items constituting the fixed asset registration information are associated and registered;
It is configured to be accessible,
The control unit ,
a payment application process for creating payment application data in response to operations by a person in charge on a payment application input screen that displays input items including predetermined items constituting the payment application data, and when the person in charge selects a predetermined item, input candidates for the selected predetermined item are read from the first master group and displayed, and the input candidate selected by the person in charge is set to the predetermined item;
a fixed asset registration information processing step of creating fixed asset registration information based on the created payment application data, and at that time, setting data of one or more items constituting the associated fixed asset registration information for data of items constituting the payment application data registered in the second master group;
Expense payment program to carry out.

Images