CN115082137A - Enterprise service platform-based invoice issuing method and system - Google Patents
Enterprise service platform-based invoice issuing method and system Download PDFInfo
- Publication number
- CN115082137A CN115082137A CN202210680102.7A CN202210680102A CN115082137A CN 115082137 A CN115082137 A CN 115082137A CN 202210680102 A CN202210680102 A CN 202210680102A CN 115082137 A CN115082137 A CN 115082137A
- Authority
- CN
- China
- Prior art keywords
- input
- invoice
- information
- company
- input information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
Landscapes
- Business, Economics & Management (AREA)
- Development Economics (AREA)
- Accounting & Taxation (AREA)
- Economics (AREA)
- Finance (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application relates to the technical field of enterprise service, in particular to an invoice issuing method and system based on an enterprise service platform; the method comprises the following steps: the method comprises the steps of obtaining invoice types, obtaining input catalogues based on the invoice types, arranging the input catalogues according to the sequence to form an input sequence, obtaining input information corresponding to the input catalogues based on the input sequence, judging whether errors exist in the input information or not, issuing an invoice based on the input information if the errors do not exist in the input information, and prompting the errors and obtaining the input information again if the errors exist in the input information. This application helps reducing the possibility that the invoice application error appears to help avoiding repeated invoicing, not only labour saving and time saving still helps resources are saved.
Description
Technical Field
The application relates to the technical field of enterprise service, in particular to an invoice issuing method and system based on an enterprise service platform.
Background
The invoice refers to the business certificate issued and received by all units and individuals in purchasing and selling goods, providing or receiving services and doing other business activities, is the original basis for accounting and also is the important basis for the law enforcement check of the auditing and tax authorities, and the invoice should be issued to the payer by the payer when the business confirmation business receipt occurs, and is issued to the payee by the payer under special conditions. At the same time, the invoicing range is consistent with the invoice usage range. Therefore, invoices cannot be issued when non-commercial business occurs to the ticket user, invoices cannot be issued when business transaction settlement between departments inside the unit occurs, and internal settlement vouchers can be used. The invoicing is an important link for realizing the use value of the invoice and reflecting economic business activities, and whether the invoicing is real, complete and correct directly relates to whether the expected purpose of invoice management can be achieved.
In the related art, the invoicing mode of a unit or an individual is usually to go offline to an organization with bill invoice authority such as a tax bureau or to go online through a regular webpage allowed by the related organization, so as to realize invoicing.
In view of the above-mentioned related technologies, the inventor believes that when an application unit or an individual issues an invoice, since the input information is complicated, the situation of wrong input information is easy to occur, which results in the wrong issue of the invoice, and the invoice cannot be cancelled after the invoice application is submitted, and only the invoice can be reapplied, which not only wastes time and labor, but also wastes resources.
Disclosure of Invention
In order to help reduce the possibility of errors in invoice application, the application provides an invoice application invoice issuing method and system based on an enterprise service platform.
In a first aspect, the application provides an invoice issuing method based on an enterprise service platform, which adopts the following technical scheme:
an invoice issuing method based on an enterprise service platform comprises the following steps:
acquiring the invoice type;
acquiring an input catalog based on the invoice type;
arranging the input catalogues according to a sequence to form an input sequence;
acquiring entry information corresponding to each entry catalog based on the entry sequence;
judging whether the input information has errors or not;
if the input information has no error, issuing an invoice based on the input information;
and if the input information has errors, prompting the errors and acquiring the input information again.
By adopting the technical scheme, when the invoice is applied, the input information is detected, whether the input information has errors is judged, if the input information has errors, the errors are prompted and the input information is obtained again, the possibility of error occurrence in invoice application is reduced, and repeated invoicing is avoided.
Optionally, before the obtaining entry information corresponding to each entry directory based on the entry order, the method further includes:
acquiring a current input focus;
judging whether the current input focus is positioned in the current input catalog or not;
and if the current input focus is not located in the current input catalog, prompting and moving the current input focus to the current input catalog again.
By adopting the technical scheme, whether the input focus is located in the current input catalog or not is judged, so that the possibility of information input errors caused by the fact that the input focus is not located in the current input catalog due to an accident condition is reduced.
Optionally, the specific step of obtaining entry information corresponding to each entry directory based on the entry order includes:
judging whether the company to be invoiced has a historical invoicing record or not based on the input sequence;
if the historical billing record exists in the invoice company to be invoiced, acquiring residual input information based on the historical billing record;
and if the to-be-invoiced company does not have the historical invoicing record, acquiring the residual input information of the to-be-invoiced company.
By adopting the technical scheme, whether the invoice company to be invoiced has the historical invoicing record or not is judged, if the historical invoicing record exists, the invoice can be directly invoiced through the historical invoicing record, the invoicing personnel does not need to manually input the input information again, time and labor are saved, and the possibility of errors caused by input of the input information is reduced.
Optionally, the specific step of determining whether the to-be-invoiced company has a historical invoicing record based on the entry sequence includes:
acquiring a historical invoicing record database;
comparing target information with the input information of the invoice company to be issued one by one, wherein the target information is the input information corresponding to any input catalog in the historical invoicing records;
judging whether any target information is completely consistent with the input information of the company to be invoiced;
if any target information is completely consistent with the input information of the company with the invoice to be issued, judging that the company with the invoice to be issued has a historical invoice record;
and if any target information is not completely consistent with the input information of the company with the invoice to be issued, judging that the company with the invoice to be issued does not have a historical invoice record.
By adopting the technical scheme, the name of the invoice company to be applied is input, and if any target information in the historical invoicing record database is completely consistent with the input information of the invoice company to be invoiced, the invoice company to be invoiced is judged to have the invoicing record.
Optionally, if the to-be-invoiced company has the historical invoicing record, the specific step of obtaining the remaining input information based on the historical invoicing record includes:
if the company to be invoiced has a historical invoicing record, acquiring an invoicing link of the historical invoicing record;
and acquiring the input information based on the link.
By adopting the technical scheme, after the name of the company to be invoiced is input by the invoicing personnel, the historical invoiced record can appear, and the input information of the company to be invoiced can be obtained by clicking the historical invoiced record through the link of the historical invoiced record.
Optionally, the specific step of determining whether the entry information has an error includes:
acquiring the input information in the current input catalog;
judging whether the input information accords with the input rule of the current input catalog;
if yes, judging that the input information has no error;
and if not, judging that the input information has errors.
By adopting the technical scheme, the input information is judged to meet the input rule of the current input catalog, so that whether the input information has errors or not is judged.
Optionally, the entry directory includes a company name, and the specific step of determining whether the entry information conforms to the entry rule of the current entry directory includes:
judging whether the company name meets the preset company name requirement or not;
and if the company name does not meet the company name requirement, judging that the input information has an error.
By adopting the technical scheme, if the company name does not meet the company name requirement, the input information is judged to have errors, the input information needs to be acquired again, and the possibility of issuing wrong tickets is reduced.
Optionally, the entry directory includes the taxpayer identification number, and further includes:
if the company name meets the company name requirement, judging whether the taxpayer identification number meets a preset tax number requirement;
and if the taxpayer identification number does not meet the tax number requirement, judging that the input information has errors.
By adopting the technical scheme, when the company name meets the preset company name requirement, whether the taxpayer identification number meets the tax number requirement is judged, so that whether errors exist in the input information is judged.
In a second aspect, the application also discloses an invoice issuing system based on the enterprise service platform, which adopts the following technical scheme:
an enterprise service platform based invoicing system comprising:
the first obtaining module is used for obtaining the invoice type;
the second acquisition module is used for acquiring an input catalog based on the invoice type;
the sorting module is used for arranging the input catalogues according to a sequence to form an input sequence;
the third acquisition module is used for acquiring the entry information corresponding to each entry catalog based on the entry sequence;
the judging module is used for judging whether the input information has errors or not;
the first execution module is used for issuing an invoice based on the input information if the input information has no error;
and the second execution module is used for prompting an error and acquiring the input information again if the input information has an error.
Through adopting above-mentioned technical scheme, when applying for the invoice, detect the input information of typing, judge whether the information of typing has the mistake, if the information of typing has the mistake, then indicate the mistake and reacquire the information of typing, help reducing the possibility that the invoice applies for the mistake to help avoiding repeated invoicing, not only labour saving and time saving still helps resources are saved.
To sum up, the application comprises the following beneficial technical effects:
when applying for the invoice, the input entry information is detected, whether the entry information has an error is judged, if the entry information has an error, the error is prompted and the entry information is obtained again, the possibility of error occurrence in invoice application is reduced, repeated invoicing is avoided, time and labor are saved, and resources are saved.
Drawings
FIG. 1 is a main flowchart of an invoicing method based on an enterprise service platform according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating the detailed steps of determining whether the current entry focus is located in the current entry directory;
FIG. 3 is a flowchart illustrating the detailed steps of step S400 in FIG. 1;
FIG. 4 is a flowchart illustrating the detailed steps of step S410 in FIG. 3;
FIG. 5 is a flowchart illustrating the detailed steps of step S420 in FIG. 3;
FIG. 6 is a flowchart illustrating the detailed steps of step S500 in FIG. 1;
fig. 7 is a flowchart illustrating the detailed steps of step S502 in fig. 6;
fig. 8 is a block diagram of an invoicing system based on an enterprise service platform according to an embodiment of the present application.
Description of reference numerals:
1. a first acquisition module; 2. a second acquisition module; 3. a sorting module; 4. a third obtaining module; 5. a judgment module; 6. a first execution module; 7. and a second execution module.
Detailed Description
In a first aspect, the application discloses an invoice issuing method based on an enterprise service platform.
The enterprise service platform is a platform for serving agent enterprises and agency organizations, aims to better facilitate the agent enterprises and the agency organizations, allows the agent enterprises and the agency organizations to handle registration companies and invoice issuing services through the platform, allows a platform administrator to track and inquire company registration progress and application data, and can manage services such as invoice issuing application and tax return reward on line.
Referring to fig. 1, an invoice issuing method based on an enterprise service platform includes steps S100 to S700:
step S100: the invoice type is obtained.
Specifically, in this embodiment, the invoice types may include a general value-added tax invoice, a special value-added tax invoice, and the like.
Step S200: based on the invoice type, an entry catalog is obtained.
Specifically, in this embodiment, the entry list refers to a list corresponding to content that must be filled in when the invoice is applied, for example, the entry list of the general value-added tax invoice includes a company name and a taxpayer identification number, and the entry list of the special value-added tax invoice includes a company name, a taxpayer identification number, a company address, a company telephone, an account bank, a bank account, and the like.
Step S300: arranging all the input catalogues according to a sequence to form an input sequence;
specifically, in this embodiment, the entry order is the order of the entry catalog on the invoice from top to bottom.
Step S400: acquiring entry information corresponding to each entry catalog based on the entry sequence;
specifically, in this embodiment, the entry information refers to information that needs to be input in the entry directory.
Step S500: and judging whether the recorded information has errors or not.
Specifically, in this embodiment, determining whether the entry information is wrong refers to whether the entry information has a format error or a form error.
Step S600: if the input information has no error, invoicing is carried out based on the input information.
Specifically, in this embodiment, when it is not detected that the entry information is incorrect, an invoice is issued according to the entry information input by the invoicing staff.
Step S700: and if the input information has errors, prompting the errors and acquiring the input information again.
Specifically, in this embodiment, when there is an error in the input information, the invoice will not be issued, but the invoicing person is prompted that the input information is incorrect, and the input information needs to be acquired again.
When applying for the invoice, the information of typing to the input detects, judges to type the information and whether have the mistake, if type the information and have the mistake, then the suggestion mistake reacquires and types the information to help avoiding repeated invoicing, when especially having invoiced the invoice online, when the invoice is wrong, still need go to the invoice point of making out invoice many times, not only waste time and energy, but also having invoiced the invoice again and need time, therefore treat very easily that the company of making out invoice causes influence or commercial loss. Therefore, the invoice application error possibility is reduced, time and labor are saved, resources are saved, and invoice paper waste is avoided.
Referring to fig. 2, in one implementation of the present embodiment, before step S400, step S310 to step S330 are further included:
step S310: acquiring a current input focus;
specifically, in this embodiment, the current input focus is the current input indicator position, for example, the mouse cursor position.
Step S320: and judging whether the current input focus is positioned in the current input catalog.
Step S330: and if the current input focus is not located in the current input catalog, prompting and moving the current input focus to the current input catalog again.
Judging whether the input focus is positioned in the current input catalog or not is helpful for reducing the possibility of information input errors caused by the fact that the input focus is not positioned in the current input catalog due to unexpected conditions, for example, when the input information is input, the system pops up an advertisement, or a computer cursor moves to other places due to misoperation, and the like.
Referring to fig. 3, in one implementation manner of this embodiment, the specific step of step S400 includes steps S410 to S430:
step S410: and judging whether the company to be invoiced has a historical invoicing record or not based on the input sequence.
Specifically, in this embodiment, if an invoice company to be applied for invoicing invoices before the invoice is applied for this time, a historical invoicing record may exist in a system for invoicing, a historical database corresponding to a webpage or an applet for invoicing, and certainly, if an operator deletes the historical invoicing record in the system for invoicing, the webpage or the applet for invoicing, there is no historical invoicing record.
Step S420: and if the company to be invoiced has a historical invoicing record, acquiring the residual input information based on the historical invoicing record.
Step S430: and if the to-be-invoiced company does not have the historical invoicing record, acquiring the residual input information of the to-be-invoiced company.
Whether the historical invoicing record exists in the invoice company to be invoiced is judged, if the historical invoicing record exists, the input information can be directly obtained through the historical invoicing record, the invoicing personnel do not need to manually input the input information again, time and labor are saved, and the possibility of errors caused by input of the input information is reduced.
Referring to fig. 4, in one implementation of this embodiment, the specific step of step S410 includes steps S411 to S415:
step S411: and acquiring a historical invoicing record database.
Specifically, in this embodiment, the historical invoicing record database is a storage address for storing the historical invoicing records, in which all the historical invoicing records that have been invoiced on the website or the applet are stored.
Step S412: the target information is compared one by one with the entered information of the company to be invoiced.
Specifically, in this embodiment, the target information is entry information corresponding to any entry directory in the historical billing record. For example, in the embodiment, a company name is entered first, and then the company names in all the historical invoicing records in the historical invoicing record database are compared with the company name of the company to be invoiced. In addition, in this embodiment, comparison is preferentially started from the history billing record closest to the current time.
Step S413: and judging whether any target information is completely consistent with the input information of the company to be invoiced.
Step S414: and if the company name in any historical invoicing record is completely consistent with the company name of the company to be invoiced, judging that the company has the historical invoicing record.
Specifically, in this embodiment, the company name in any historical billing record is completely consistent with the company name of the company to be invoiced, that is, the company name in a certain historical billing record in the historical billing record database is completely consistent with the company name of the company to be invoiced.
If no arbitrary target information completely accords with the input information of the company to be invoiced, the step S415 judges that the company to be invoiced has no historical invoicing record.
Specifically, in this embodiment, there is no company name in any historical billing record completely consistent with the company name of the company to be invoiced, that is, there is no company name in the historical billing record database completely consistent with the company name of the company to be invoiced.
When preparing to apply for invoices for a company to be invoiced, an operator manually inputs the name of the company to be invoiced, if a company which is completely consistent with the name of the company to be invoiced exists in a historical invoiced record database, the company to be invoiced is judged to have an invoiced record in the historical invoiced record database, and if the company which is completely consistent with the name of the company to be invoiced does not exist in the historical invoiced record database, the company to be invoiced is judged to have no invoiced record in the historical invoiced record database.
Referring to fig. 5, in one implementation of this embodiment, the specific step of step S420 includes steps S421 to S422:
step S421: if the company to be invoiced has the historical invoicing record, acquiring the invoicing link of the historical invoicing record.
Linking refers to the process of passing parameters and control commands between modules of an electronic computer program and assembling them into an executable whole. The link is also called a hyperlink, and refers to a connection relationship from one web page to a directory, and the directory to be pointed to may be another web page, or different positions on the same web page, or a picture, an email address, a file, or even an application program. Specifically, in this embodiment, the link for making out an invoice can acquire the link for inputting information.
Step S422: and acquiring the input information based on the link.
Specifically, in this embodiment, the entry information can be acquired by entering the billing link.
After the invoicing personnel inputs the name of the company to be invoiced, a historical invoicing record appears, and the input information of the company to be invoiced can be obtained through the link of the historical invoicing record by clicking the historical invoicing record.
Referring to fig. 6, in one implementation manner of this embodiment, the specific step of step S500 includes steps S501 to S504:
step S501: and acquiring the entry information in the current entry directory.
Step S502: and judging whether the input information accords with the input rule of the current input catalog.
Specifically, the entry rule in this embodiment includes a character number specification, a format specification, and the like.
Step S503: if yes, judging that the recorded information has no error.
Step S504: if not, judging that the recorded information has errors.
And judging whether the input information meets the input rule of the current input catalog, thereby judging whether the input information has errors.
Referring to fig. 7, in one implementation manner of this embodiment, the specific step of step S502 includes steps S5021 to S5022:
step S5021: and judging whether the company name meets the preset company name requirement or not.
Specifically, in the present embodiment, the preset company name requirement refers to a requirement that needs to be satisfied by "the provision for registration management of company name" when registering a company name, and in the present embodiment, specifically, a symbol or the like that is not specified exists.
Step S5022: and if the company name does not meet the company name requirement, judging that the input information has errors.
Specifically, in the present embodiment, if the company name input by the operator does not satisfy the company name requirement, that is, if there is a content that does not satisfy the company name setting requirement, such as a special symbol, in the company name, it is determined that there is an error in the entry information.
Referring to fig. 7, in one implementation manner of this embodiment, the method for issuing an invoice based on an enterprise service platform further includes steps S5023 to S5025:
step S5023: and if the company name meets the requirement of the company name, judging whether the taxpayer identification number meets the preset tax requirement.
Specifically, in this embodiment, the preset tax requirement refers to the character number requirement and the format requirement of the taxpayer identification number.
The taxpayer identification number is uniformly composed of 15-bit, 18-bit or 20-bit codes (character type), the taxpayer code issued by the national tax administration is 15-bit, wherein 1-2 bit is province and city code, 3-6 bit is area code, 7-8 bit is economic property code, 9-10 bit industry code, and 11-15 bit is self-set sequence code of each region. The taxpayer identification number of the 18-digit code is represented by 18-digit Arabic numerals or capital English letters and consists of 5 parts, namely a registration management department code (1 digit), an organization type code (1 digit), a registration management organization administrative division code (6 digits), a main body identification code (organization code) (9 digits) and a check code (1 digit). The tax registration code is unified by the personal identification number plus two-digit sequence code (the sequence code is the number from 01 to 99), so the taxpayer identification number is 20-digit code, and the first six-digit code is the administrative division code of the registration management authority.
Step S5024: and if the taxpayer identification number does not meet the tax number requirement, judging that the input information has errors.
Specifically, in this embodiment, if the taxpayer identification number input by the operator does not satisfy the tax number requirement, that is, the taxpayer identification number has a special symbol or other contents that do not satisfy the company name setting requirement, it is determined that the entry information has an error. For example, when a special symbol such as a punctuation mark exists in the taxpayer identification number input by the operator or when the bit code of the taxpayer identification number does not satisfy the bit code requirement, it is determined that the entry information has an error.
Step S5025: and if the taxpayer identification number meets the preset tax number requirement, judging that no error exists in the input information.
If the company name does not meet the company name requirement, judging that the input information has errors, acquiring the input information again to reduce the possibility of wrong invoice, and judging whether the input information has errors or not by judging whether the taxpayer identification number meets the tax number requirement or not when the company name meets the preset company name requirement to further reduce the possibility of wrong invoice.
In addition, if the invoice type is a value-added tax special invoice, the input catalog further comprises a company address, a company telephone, an account opening bank, a bank account and the like, and all the types can be used as judgment points to judge whether the input information has errors.
For example, if the administrative division code of the tax payer identification number registration management authority for the 18-digit code of the invoice company to be applied is 440104, the company registration address is the overseall area of Guangzhou city, Guangdong province, and if the acquired company address is not the overseall area of Guangzhou city, it is determined that the entry information is wrong.
It should be noted that if the tax payer identification number does not match the company address after the company address is changed, the company address can be set to meet the address requirement by reconfirming after the company address is judged to have an error in the entered information because the company address does not meet the address requirement.
The implementation principle of the invoice issuing method based on the enterprise service platform in the embodiment of the application is as follows:
the method comprises the steps of obtaining invoice types, obtaining input catalogues based on the invoice types, arranging the input catalogues according to the sequence to form an input sequence, obtaining input information corresponding to the input catalogues based on the input sequence, judging whether errors exist in the input information or not, issuing an invoice based on the input information if the errors do not exist in the input information, and prompting the errors and obtaining the input information again if the errors exist in the input information.
In a second aspect, the application further discloses an invoice issuing system based on the enterprise service platform.
Referring to fig. 8, an invoicing system based on an enterprise service platform includes:
the first obtaining module 1 is used for obtaining the invoice type;
the second acquisition module 2 is used for acquiring the input catalog based on the invoice type;
the sorting module 3 is used for arranging the input catalogues according to a sequence to form an input sequence;
the third acquisition module 4 is used for acquiring the entry information corresponding to each entry catalog based on the entry sequence;
the judging module 5 is used for judging whether the input information has errors;
the first execution module 6 is used for issuing an invoice based on the input information if the input information has no error;
and if the entry information has an error, the second execution module 7 is used for prompting the error and reacquiring the entry information.
The implementation principle of the invoice issuing system based on the enterprise service platform in the embodiment of the application is as follows: the first acquisition module 1 acquires the invoice type and sends the invoice type information to the second acquisition module 2, the second acquisition module 2 acquires the entry list based on the invoice type information received from the first acquisition module 1, and sends the logging information to the sorting module 3, the sorting module 3 arranges the logging catalogues according to the order to form a logging order based on the logging catalogues received from the second acquisition module 2, and sends the logging order to the third obtaining module 4, the third obtaining module 4 obtains the logging information in sequence according to the logging order, and sends the logging information to the judging module 5, and the judging module 5 judges whether the logging information has errors or not based on the logging information received from the third obtaining module 4, and if not, the information is sent to the first execution module 6, and the first execution module 6 invoices based on the input information; if an error exists, the information is sent to the second execution module 7, the second execution module 7 prompts the error information and obtains the input information again, and therefore the technical effect same as that of the invoice issuing method based on the enterprise service platform is achieved.
The above embodiments are preferred embodiments of the present application, and the protection scope of the present application is not limited by the above embodiments, so: all equivalent changes made according to the structure, shape and principle of the present application shall be covered by the protection scope of the present application.
Claims (9)
1. An invoice issuing method based on an enterprise service platform is characterized by comprising the following steps:
acquiring the invoice type;
acquiring an input catalog based on the invoice type;
arranging the input catalogues according to a sequence to form an input sequence;
acquiring entry information corresponding to each entry catalog based on the entry sequence;
judging whether the input information has errors or not;
if the input information has no error, issuing an invoice based on the input information;
and if the input information has errors, prompting the errors and acquiring the input information again.
2. The enterprise service platform-based invoicing method according to claim 1, further comprising, before the obtaining the entry information corresponding to each entry catalog based on the entry order:
acquiring a current input focus;
judging whether the current input focus is positioned in the current input catalog or not;
and if the current input focus is not located in the current input catalog, prompting and moving the current input focus to the current input catalog again.
3. The enterprise service platform-based invoicing method according to claim 1, wherein the specific step of obtaining the entry information corresponding to each entry directory based on the entry order comprises:
judging whether the company to be invoiced has a historical invoicing record or not based on the input sequence;
if the historical billing record exists in the invoice company to be invoiced, acquiring residual input information based on the historical billing record;
and if the to-be-invoiced company does not have the historical invoicing record, acquiring the residual input information of the to-be-invoiced company.
4. The method as claimed in claim 3, wherein the step of determining whether the company to be invoiced has a historical invoicing record based on the entry order comprises:
acquiring a historical billing record database;
comparing target information with the input information of the invoice company to be invoiced one by one, wherein the target information is the input information corresponding to any input catalog in the historical invoicing record;
judging whether any target information is completely consistent with the input information of the company to be invoiced;
if any target information is completely consistent with the input information of the company with the invoice to be issued, judging that the company with the invoice to be issued has a historical invoice record;
and if any target information is not completely consistent with the input information of the company with the invoice to be issued, judging that the company with the invoice to be issued does not have a historical invoice record.
5. The enterprise service platform-based invoice issuing method according to claim 3, wherein if the to-be-issued invoice company has the historical invoice records, the specific step of obtaining the remaining entered information based on the historical invoice records comprises:
if the company to be invoiced has a historical invoicing record, acquiring an invoicing link of the historical invoicing record;
and acquiring the input information based on the link.
6. The enterprise service platform-based invoicing method according to claim 1, wherein the specific step of determining whether the entered information is wrong comprises:
acquiring the input information in the current input catalog;
judging whether the input information accords with the input rule of the current input catalog;
if yes, judging that the input information has no error;
and if not, judging that the input information has errors.
7. The enterprise service platform-based invoicing method according to claim 6, wherein the entered directory comprises a company name, and the specific step of judging whether the entered information conforms to the entered rule of the currently entered directory comprises:
judging whether the company name meets the preset company name requirement or not;
and if the company name does not meet the company name requirement, judging that the entry information has errors.
8. The enterprise service platform-based invoicing method according to claim 6, wherein the entry list comprises taxpayer identification numbers, and further comprising:
if the company name meets the company name requirement, judging whether the taxpayer identification number meets a preset tax number requirement;
and if the taxpayer identification number does not meet the tax number requirement, judging that the input information has errors.
9. An invoice issuing system based on an enterprise service platform, comprising:
the first obtaining module (1) is used for obtaining the invoice type;
the second acquisition module (2) is used for acquiring an input catalog based on the invoice type;
the sorting module (3) is used for arranging the input catalogues according to a sequence to form an input sequence;
the third acquisition module (4) is used for acquiring the entry information corresponding to each entry catalog based on the entry sequence;
the judging module (5) is used for judging whether the input information has errors or not;
the first execution module (6) is used for issuing an invoice based on the input information if the input information has no error;
and the second execution module (7) is used for prompting an error and re-acquiring the entry information if the entry information has an error.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210680102.7A CN115082137A (en) | 2022-06-16 | 2022-06-16 | Enterprise service platform-based invoice issuing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210680102.7A CN115082137A (en) | 2022-06-16 | 2022-06-16 | Enterprise service platform-based invoice issuing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115082137A true CN115082137A (en) | 2022-09-20 |
Family
ID=83254003
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210680102.7A Pending CN115082137A (en) | 2022-06-16 | 2022-06-16 | Enterprise service platform-based invoice issuing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115082137A (en) |
-
2022
- 2022-06-16 CN CN202210680102.7A patent/CN115082137A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7606422B2 (en) | System, method and computer program for an integrated digital workflow for processing a paper form | |
| US7416131B2 (en) | Electronic transaction processing server with automated transaction evaluation | |
| US6952681B2 (en) | Tracking the distribution of prescription drugs and other controlled articles | |
| US8452623B2 (en) | System and method for processing payroll-related employee and insurance data | |
| US8126787B1 (en) | System and method for preparing a tax return using electronically distributed tax return data | |
| US20140304179A1 (en) | Method for Complying with Employment Eligibility Verification Requirements | |
| CN108269183B (en) | Financial accounting intelligent agent service system, electronic equipment and method | |
| US20080270293A1 (en) | Accounts payable automation system with automated discount and factoring management | |
| US8190482B1 (en) | Organic supplier enablement based on a business transaction | |
| US20080201190A1 (en) | System and method for electronic processing of default case files | |
| CN111199222B (en) | Bill management method and electronic equipment | |
| JP2004302574A (en) | Payment processing system and method | |
| US20080255970A1 (en) | Method, system,apparatus or device for providing reconciled bookkeeping or accounting electronically | |
| CN115082137A (en) | Enterprise service platform-based invoice issuing method and system | |
| CN115018485A (en) | Aggregated payment operation management platform and aggregated payment method | |
| KR102562186B1 (en) | System for providing rental property management based official letter sending service | |
| CN113822603A (en) | Cloud computing processing method based on SaaS | |
| CN112232752A (en) | Sales invoice management platform and management method | |
| JPH11328292A (en) | Installment erasure system | |
| CN111340517A (en) | Method, system and related equipment for rapidly inquiring authenticity of invoice | |
| KR101683015B1 (en) | System for providing tax processing service | |
| JP7414470B2 (en) | Server equipment, programs, user terminal equipment, and systems | |
| AU2008201398B2 (en) | A method, system, apparatus or device for providing reconciled bookkeeping or acounting electronically | |
| US20020060244A1 (en) | Account settlement system and account settlement method for call sales | |
| JPH1139519A (en) | Device and system for collecting deferred payment fare information and recording medium for computer program to execute deferred payment fare information collection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |