CN117635354A - Service data date joining method, computer equipment and computer storage medium - Google Patents
Service data date joining method, computer equipment and computer storage medium Download PDFInfo
- Publication number
- CN117635354A CN117635354A CN202311592312.1A CN202311592312A CN117635354A CN 117635354 A CN117635354 A CN 117635354A CN 202311592312 A CN202311592312 A CN 202311592312A CN 117635354 A CN117635354 A CN 117635354A
- Authority
- CN
- China
- Prior art keywords
- date
- knot
- service data
- service
- daily
- 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
- 238000000034 method Methods 0.000 title claims abstract description 35
- 230000008520 organization Effects 0.000 claims description 23
- 238000001914 filtration Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 7
- 238000013461 design Methods 0.000 abstract description 4
- 238000004891 communication Methods 0.000 description 12
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 8
- 238000012795 verification Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 238000012217 deletion Methods 0.000 description 5
- 230000037430 deletion Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000000178 monomer Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
- G06Q40/125—Finance or payroll
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the application discloses a business data date knot method, computer equipment and a computer storage medium. The computer equipment acquires service data and judges whether the service type corresponding to the service data meets a preset date knot condition or not; if yes, performing a date knot operation on the service data to generate a date knot record; judging whether the service data meets preset credential generation conditions according to the service attribute information of the service data; if yes, generating a service credential according to the service data. Therefore, the types of the daily knots are distinguished as account types and subject types, the daily knot information of each account is displayed by taking an enterprise as a dimension, and in order to ensure the accuracy of the calculated balance of the accounting subject after the daily knot, all accounts/accounting subjects on the previous day of the selected daily knot date are checked to finish daily knot. The new design is made on the elements needed in the daily knot record list, and the refined new daily knot list design can meet the requirements of customers on single account numbers or daily knots of accounting subjects.
Description
Technical Field
The embodiment of the application relates to the field of data processing, in particular to a business data date knot method, computer equipment and a computer storage medium.
Background
In the field of financial management, the user complaints are that the transaction flowing water, settlement business and the like on the same day all need to generate accounting certificates and push all accounting certificates to a third party system, a day knot function needs to be added, day knot verification is carried out by the dimension of an account number and a subject, whether the account number/accounting subject generates accounting certificates on the transaction flowing water associated with the selected day knot date or not is checked, if no accounting certificates are generated, the day knot is not allowed, and the business associated with the account number which is not completely day-knotted is prompted. If the day knot is completed on the same day, the certificate is not allowed to be regenerated and running water cannot be carried out any more. The technical requirement is that the account dimension is required to control the day knot, so that the account B can still continuously generate accounting certificates on the same day or before after the account A finishes the day knot, thus causing inaccurate account balance calculation after the day knot, and controlling whether the account under the enterprise finishes the day knot all the day before the selected day knot date.
The existing daily setting proposal can only be integrated according to daily setting, the granularity is relatively coarse, the monomer daily setting can not be met by customers according to the relatively fine granularity of account numbers/accounting subjects, the actual requirement of customers is that after the daily setting of a single account number is finished, the account number can not generate new transactions, but other account numbers can still generate transactions, and the traditional realization proposal can not be met.
Disclosure of Invention
The embodiment of the application provides a business data date knot method, computer equipment and a computer storage medium, which are used for meeting the demands of clients on single account numbers or account numbers date knot.
An embodiment of the present application provides a service data date binding method, where the method is applied to a computer device, and the method includes:
acquiring service data, and judging whether a service type corresponding to the service data meets a preset date setting condition or not;
if yes, performing a date knot operation on the service data to generate a date knot record;
judging whether the service data meets preset credential generation conditions according to the service attribute information of the service data;
if yes, generating a service certificate according to the service data.
A second aspect of embodiments of the present application provides a computer device, the computer device comprising:
the first judging unit is used for acquiring service data and judging whether the service type corresponding to the service data meets a preset date knot condition or not;
the first execution unit is used for executing a date knot operation on the service data to generate a date knot record if the service type corresponding to the service data meets a preset date knot condition;
the second judging unit is used for judging whether the service data meets preset credential generation conditions according to the service attribute information of the service data;
and the second execution unit is used for generating a service certificate according to the service data if the service data meets the preset certificate generation condition.
A third aspect of the embodiments of the present application provides a computer device comprising a memory storing a computer program and a processor implementing the method of the first aspect when the processor executes the computer program.
A fourth aspect of the embodiments provides a computer storage medium having stored therein instructions which, when executed on a computer, cause the computer to perform the method of the first aspect described above.
A fifth aspect of the embodiments of the present application provides a computer program product which, when run on a computer device, causes the computer device to perform the method of the first aspect described above.
From the above technical solutions, the embodiments of the present application have the following advantages:
aiming at the requirement that a customer wants to refine the daily knot granularity, the embodiment firstly distinguishes the daily knot type as an account number type and a subject type, displays daily knot information of each account number by taking an enterprise as a dimension, and verifies that all account numbers/accounting subjects in the previous day of the selected daily knot date have completed daily knots in order to ensure the accuracy of the calculated accounting subject balance after daily knots. Because the service data associated with each account are more and different, the daily check is time-consuming, but the user may only actually do part of the service with a certain account, and each service type is not required to check the account before daily check.
Drawings
FIG. 1 is a schematic diagram of a network framework in an embodiment of the present application;
fig. 2 is a schematic flow chart of a business data daily junction method in an embodiment of the present application;
FIG. 3 is a schematic flow chart of checking the daily knot of a bank account and inquiring business data in the embodiment of the application;
fig. 4 is a schematic flow diagram of credential generation under a bank account date scene in an embodiment of the present application;
FIG. 5 is a schematic flow chart of checking cash daily knots and querying business data in an embodiment of the present application;
FIG. 6 is a schematic flow chart of voucher generation under a cash type daily knot scenario in an embodiment of the present application;
FIG. 7 is a schematic flow diagram of an anti-daily check flow in an embodiment of the present application;
FIG. 8 is a schematic diagram of a computer device in an embodiment of the present application;
fig. 9 is a schematic diagram of another structure of a computer device in an embodiment of the present application.
Detailed Description
The embodiment of the application provides a business data date knot method, computer equipment and a computer storage medium, which are used for meeting the demands of clients on single account numbers or account numbers date knot.
Referring to fig. 1, in an embodiment of the present application, a network framework includes:
a service server 100 and a terminal cluster; the terminal cluster may include: terminal devices 200a, 200b, 200c, … …, 200n, and the like.
The service server 100 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server that provides a cloud database, a cloud service, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, and basic cloud computing services such as a big data and an artificial intelligence platform. The terminal devices (including terminal device 200a, terminal device 200b, terminal devices 200c, … …, and terminal device 200 n) may be smart phones, tablet computers, notebook computers, desktop computers, palm computers, mobile internet devices (mobile internet device, MID), wearable devices (e.g., smart watches, smart bracelets, etc.), smart computers, smart vehicles, and other smart terminals.
The service server 100 may establish communication connection with each terminal device in the terminal cluster, and may also establish communication connection between each terminal device in the terminal cluster. In other words, the service server 100 may establish a communication connection with each of the terminal apparatuses 200a, 200b, 200c, … …, 200n, for example, a communication connection may be established between the terminal apparatus 200a and the service server 100. A communication connection may be established between terminal device 200a and terminal device 200b, and a communication connection may also be established between terminal device 200a and terminal device 200 c. The communication connection is not limited to a connection manner, and may be directly or indirectly connected through a wired communication manner, or may be directly or indirectly connected through a wireless communication manner, and the like, and may be specifically determined according to an actual application scenario, which is not limited herein.
It should be understood that each terminal device in the terminal cluster shown in fig. 1 may be provided with an application client, and when the application client runs in each terminal device, the application client may interact with the service server 100 respectively, so that the service server 100 may receive service data from each terminal device (such as financial management data uploaded by a user through the terminal device). The application client may be an application client having a function of displaying data information such as text, image, audio and video, such as a financial management application, an enterprise transaction management application, a browser application, a social application, an instant messaging application, a live broadcast application, a game application, a short video application, a music application, a shopping application, a novel application, a payment application, etc., and may specifically be determined according to actual application scene requirements, without limitation. The application client may be an independent client, or may be an embedded sub-client integrated in a certain client (such as a financial management client, an enterprise transaction management client, etc.), which may be specifically determined according to an actual application scenario, and is not limited herein.
The business data date joining method in the embodiment of the present application will be described below with reference to the network framework of fig. 1:
referring to fig. 2, an embodiment of a business data date binding method in an embodiment of the present application includes:
201. acquiring service data, and judging whether a service type corresponding to the service data meets a preset date setting condition or not;
202. if yes, performing a date knot operation on the service data to generate a date knot record;
the method of the present embodiment is applicable to a computer device, which may be the service server 100 or each terminal device in the network framework shown in fig. 1.
Judging whether the service type corresponding to the service data meets the preset date knot condition, in a preferred embodiment, judging whether a target organization identifier has a date knot record smaller than the date knot, judging whether all accounts and subjects of the target organization identifier have completed the date knot of the previous date, judging whether the date knot date checked by a user is the same as the date knot date of the current time, acquiring data that the associated account of each service data belongs to the range of the date knot account checked by the user and that the date knot date is greater than or equal to the service transaction date, inquiring an associated certificate according to the unique identifier of the service, and judging whether the associated certificate is in a generated and pushed state.
If the target organization mark has a date knot record smaller than the date knot date, all accounts and subjects of the target organization mark have completed the date knot of the previous day, the date knot date checked by the user is the same as the date knot date of the current time, and the association certificate is in a generated and pushed state, executing the date knot operation on the business data to generate the date knot record; if the unique identifier of the service is not associated with the certificate, or if the associated certificate is invalidated, not pushed or fails to be pushed, determining that the service type corresponding to the service data does not meet the preset date setting condition.
For example, referring to fig. 4 to 6, at the time of day knot, it is checked whether the corresponding service type (day knot parameter is 1-bank account number) satisfies the current day knot condition. It includes following a plurality of inspection main points:
1) Judging whether a date knot record smaller than the date of the date knot exists in the enterprise number for checking the date knot;
2) Judging whether all accounts and cash subjects are in the enterprise number and whether the last day is completed;
3) Judging whether the date of the next day of the sorting is the same or not;
4) Acquiring data of each business data associated account belonging to a checking day account number range and day account date > =business transaction date;
5) Inquiring the associated certificate according to the unique service number, and judging whether the certificate is generated and the pushed state allows a date knot; if the unassociated credentials or the associated credentials are invalidated, not pushed, and failed to push, the date knot is not allowed.
If the associated certificate is generated and the pushing fails, the associated certificate is required to be invalidated, the certificate is regenerated, and the date knot is allowed after the pushing is successful.
In this embodiment, before performing the daily knot operation on the service data, the service data may be filtered according to a preset filtering condition to obtain the target service data, so when performing the daily knot operation on the service data, the daily knot operation may be performed on the target service data to generate the daily knot record.
For example, the business data may be filtered based on the following various filtering rules to obtain the target business data:
(1) collecting and claiming:
claim status-! =4-no claim;
third party account number flag = Y.
(2) Settlement business:
detailed status-! AE-approval denial, AQ-service revocation, OD-expiration, BE-payment information error, CF-corporation approval denial, LT-total to sub-ticket refund, sub-subscriber failed statement.
(3) Internal credit:
transaction category = 1010-payment transaction, 1020-repayment transaction, 2020-settlement transaction;
flush account flag = 1-normal;
record status-! 2-counter rejection, 4-review rejection, D-online banking rejection, 5-counter deletion, F-counter enterprise deletion, Z-revoked;
associated record State-! =revoked, deleted.
(4) External financing:
transaction category = 1010-payment transaction, 1020-repayment transaction;
flush account flag = 1-normal;
record status-! 2-counter deletion, 7-counter rejection, D-internet banking rejection, B-internet banking deletion.
(5) Financial services:
transaction type = 0-bin reduction [ redemption ], 1-bin increase [ purchase ]
Transaction status-! In =2-approval denial, 4, transaction revocation, 5-revocation treatment
(6) Bill service:
transaction type = CKEP-ticketing registration, anti-unused returns;
transaction status-! =ccn-counter delete (clique), CNO-approval reject (clique), CFL-transaction fail, OVR-fail end, ECN-counter delete (business), ENO-approval reject (business), NCN-online banking delete, NNO-online banking reject, BNO-bank reject, CAL-sponsor withdraw.
203. Judging whether the service data meets preset credential generation conditions according to the service attribute information of the service data;
204. if yes, generating a service certificate according to the service data;
in this embodiment, whether the service data meets the preset credential generation condition is determined according to the service attribute information of the service data, which may be a preferred implementation manner, whether the target organization identifier is within the range of the organization identifier of the date knot is determined, and if not, the service credential is generated according to the service data; if so, judging whether the voucher entry subject belongs to the daily statement subject, if not, judging whether the voucher is associated with the account and belongs to the daily statement range, and if not, generating a service voucher according to the service data; if the voucher is not associated with the account number or belongs to the daily account number range, judging whether the corresponding billing date is larger than the next daily account date, and if so, generating a service voucher according to the service data; if not, determining that the preset credential generation condition is not met.
For example, referring to fig. 4 to 6, when a voucher is generated after the date, it is checked whether the corresponding service data satisfies the voucher generation condition, and if so, the voucher is generated. The method comprises the following verification key points:
(1) the enterprise number does not belong to the range of the enterprise number of the date knot;
(2) business transaction date > latest date;
(3) the account number does not belong to the range of the already-selected account number;
(4) the subjects in the voucher entry do not include 1131-receivable notes.
Checking flow and corresponding service description after the date is finished:
1. judging whether the enterprise number corresponding to the certificate accounting organization is in the range of the established date, if not, allowing generation of the certificate, and if so, continuing to check (2);
2. judging whether the voucher entry subjects belong to the daily knot subjects, if not, checking (3), and if so, continuing checking (4);
3. judging whether the certificate is associated with the account number and belongs to the daily account number range; checking (4) if the certificate belongs to the certificate, and allowing to generate the certificate if the certificate does not belong to the certificate;
4. judging whether the corresponding billing date is greater than the date of the current date, if so, not allowing generation of the certificate.
The daily accounting function is a core function of the financial system, after the daily business of business modules related to transactions such as a settlement module, a receipt and payment module, a bill module, a credit module and the like are processed, daily accounting is needed, corresponding transactions and running water are generated into accounting certificates which are pushed to a three-party system for checking, and the daily balance of subjects of a user enterprise is summarized and counted. The user does not allow transaction running water to be newly generated after the date is finished, and if the user needs to continue to do business, the business can be continued through the operation of the date-reversing.
In this embodiment, the computer device may further obtain an anti-date-knot verification rule, and verify the service data according to the anti-date-knot verification rule to determine whether the service data needs an anti-date-knot operation, and if it is determined that the service data needs the anti-date-knot operation, execute the anti-date-knot operation on the date-knot record.
For example, as shown in fig. 7, the following describes the reverse daily check rule:
reverse day junction: deleting the completed check record and re-executing check if necessary;
1. the accounting module provides an anti-solar junction verification interface for a third party MIS system to call;
2, MIS calls an anti-date check interface provided by accounting, and writes corresponding enterprise numbers, system names, date, state and writing time;
the CBS establishes an anti-solar junction verification rule according to the written information of the MIS system;
4. and (3) checking the operation of the reverse solar junction: according to the checked anti-date knot enterprise number and the anti-date knot date (the date of the current date knot), when the MIS returns to the state <1 and the CBS is more than or equal to the MIS, the anti-date is allowed;
the following describes the reverse date knot operation:
1) The date of the reverse date is defaulted to be [ date of the current date ] and only the latest date of the reverse date is allowed;
2) After the anti-day successful, [ last day date ] is = [ last day date ] T-1 day, [ present day date ] is = [ last day date ];
3) After the opposite day, the subject balance summary table needs to be recalculated when the opposite day is finished again.
In this embodiment, in order to determine whether each service module after the day-tie can be developed, the verification rule (development of each service module) after the day-tie of the service module is as follows:
(1) collecting and claiming: adding account conditions: the detail ' transaction date ' is less than or equal to the latest balance date ' and the account number belongs to the daily account number range, and modification, deletion and cancellation of claims are not allowed;
(2) internal credit: adding account conditions: inquiring the date of the creditor enterprise and the debtor enterprise of the transaction when the transaction is cancelled, and if the transaction date is smaller than any date and the associated running water account number belongs to the range of the daily account number, the transaction cannot be cancelled;
(3) external financing: adding account conditions: inquiring the date of the business of the transaction when the transaction is cancelled, and if the transaction date is smaller than the date of the transaction and the associated running water account number belongs to the range of the date account number, the transaction cannot be cancelled;
(4) manually importing non-direct account transaction details: increasing the conditions: when the transaction date of the transaction detail is less than or equal to the date of the accounting module and the account number is in the range of the account number of the date, giving a bullet frame to prompt that the transaction date of the current transaction detail is in the date of the date, and not allowing the operation;
(6) financial services: when the transaction is cancelled, inquiring the date of the business of the transaction, and if the transaction date is smaller than the date of the transaction and the associated running water account number belongs to the range of the daily account number, the transaction cannot be cancelled;
(7) bill service (ticket register): when the ticket is newly added and withdrawn, inquiring the date of the ticket holder enterprise, and if the transaction date is less than or equal to the date of the ticket holder enterprise, not allowing the new addition and withdrawal.
Therefore, in this embodiment, aiming at the requirement that the customer wants to refine the daily knot granularity, the daily knot type is first distinguished into account types and subject types, the daily knot information of each account is displayed by taking the enterprise as the dimension, and in order to ensure the accuracy of the accounting subject balance calculated after daily knot, all accounts/accounting subjects on the previous day of the selected daily knot date are checked to finish daily knot. Because the service data associated with each account are more and different, the daily check is time-consuming, but the user may only actually do part of the service with a certain account, and each service type is not required to check the account before daily check.
Compared with the existing daily knot scheme, the new scheme of the embodiment makes new designs for elements needed in the daily knot record table, including project numbers, enterprise numbers, daily knot types, daily knot account numbers, daily knot dates, last daily knot date and current daily knot date. The new date knot table design after refinement can meet the requirements of clients on single account numbers or date knots of accounting subjects.
The business data date binding method in the embodiment of the present application is described above, and the computer device in the embodiment of the present application is described below, referring to fig. 8, an embodiment of the computer device in the embodiment of the present application includes:
a first determining unit 801, configured to obtain service data, and determine whether a service type corresponding to the service data meets a preset date knot condition;
a first execution unit 802, configured to execute a date knot operation on the service data to generate a date knot record if the service type corresponding to the service data meets a preset date knot condition;
a second judging unit 803, configured to judge whether the service data meets a preset credential generating condition according to service attribute information of the service data;
the second execution unit 804 is configured to generate a service credential according to the service data if the service data meets a preset credential generation condition.
In a preferred implementation manner of this embodiment, the first determining unit 801 is specifically configured to:
judging whether a daily knot record smaller than the daily knot date exists in the target organization mark or not;
judging whether all accounts and subjects identified by the target organization are completed in a day knot of the previous day;
judging whether the date checked by the user is the same as the current date;
acquiring data that the associated account number of each service data belongs to the range of the daily account number checked by the user and the daily account date is greater than or equal to the service transaction date;
inquiring the associated certificate according to the unique identifier of the service, and judging whether the associated certificate is in a generated and pushed state;
if the target organization identifier has a date record smaller than the date of the date, all accounts and subjects of the target organization identifier have completed the date of the previous date, the date of the date checked by the user is the same as the date of the current date, and the association certificate is in a generated and pushed state, executing the date operation on the service data to generate the date record;
if the unique identifier of the service is not associated with the credential, or if the associated credential is invalidated, not pushed or failed to be pushed, determining that the service type corresponding to the service data does not meet the preset date knot condition.
In a preferred implementation manner of this embodiment, the first execution unit 802 is specifically configured to:
filtering the service data according to preset filtering conditions to obtain target service data;
and executing the daily knot operation on the target business data to generate the daily knot record.
In a preferred implementation manner of this embodiment, the second determining unit 803 is specifically configured to:
judging whether the target organization mark belongs to the range of the organization mark of the date knot;
if not, generating a service certificate according to the service data;
if so, judging whether the voucher entry subjects belong to the date knot subjects;
if the voucher entry subject does not belong to the daily statement subject, judging whether the voucher is associated with the account number and belongs to the daily statement number range;
if the certificate is associated with the account number and does not belong to the daily account number range, generating a service certificate according to the service data;
if the voucher is not associated with the account number or belongs to the daily account number range, judging whether the corresponding billing date is larger than the next daily account date, and if so, generating a service voucher according to the service data;
if not, determining that the preset credential generation condition is not met.
In a preferred implementation of this embodiment, the computer device further includes:
the anti-date knot unit 805 is configured to obtain an anti-date knot check rule, check the service data according to the anti-date knot check rule, so as to determine whether the service data requires an anti-date knot operation; and if the business data is determined to need the anti-date knot operation, executing the anti-date knot operation on the date knot record.
In this embodiment, the operations performed by the units in the computer device are similar to those described in the embodiment shown in fig. 2, and will not be described here again.
In this embodiment, aiming at the requirement that the customer wants to refine the daily knot granularity, the daily knot type is first distinguished into account types and subject types, the daily knot information of each account is displayed by taking the enterprise as the dimension, and in order to ensure the accuracy of the account balance calculated after daily knot, all accounts/accounts on the previous day of the selected daily knot date are checked to finish daily knot. Because the service data associated with each account are more and different, the daily check is time-consuming, but the user may only actually do part of the service with a certain account, and each service type is not required to check the account before daily check.
Referring to fig. 9, an embodiment of a computer device in the embodiment of the present application includes:
the computer device 900 may include one or more central processing units (central processing units, CPU) 901 and memory 905, with one or more applications or data stored in the memory 905.
Wherein the memory 905 may be volatile storage or persistent storage. The program stored in memory 905 may include one or more modules, each of which may include a series of instruction operations in a computer device. Still further, the central processor 901 may be arranged to communicate with the memory 905 to execute a series of instruction operations in the memory 905 on the computer device 900.
The computer device 900 may also include one or more power supplies 902, one or more wired or wireless network interfaces 903, one or more input output interfaces 904, and/or one or more operating systems, such as Windows ServerTM, mac OS XTM, unixTM, linuxTM, freeBSDTM, etc.
The cpu 901 may perform the operations performed by the computer device in the embodiment shown in fig. 2, which will not be described herein.
Embodiments of the present application also provide a computer storage medium, where one embodiment includes: the computer storage medium has stored therein instructions which, when executed on a computer, cause the computer to perform the operations performed by the computer device in the embodiment shown in fig. 2 described above.
Embodiments of the present application also provide a computer program product, one of which includes: the computer program product, when run on a computer device, causes the computer device to perform the operations performed by the computer device in the embodiment shown in fig. 2 described above.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Claims (10)
1. A business data date joining method, wherein the method is applied to a computer device, the method comprising:
acquiring service data, and judging whether a service type corresponding to the service data meets a preset date setting condition or not;
if yes, performing a date knot operation on the service data to generate a date knot record;
judging whether the service data meets preset credential generation conditions according to the service attribute information of the service data;
if yes, generating a service certificate according to the service data.
2. The method of claim 1, wherein the determining whether the service type corresponding to the service data meets a preset date knot condition comprises:
judging whether a daily knot record smaller than the daily knot date exists in the target organization mark or not;
judging whether all accounts and subjects identified by the target organization are completed in a day knot of the previous day;
judging whether the date checked by the user is the same as the current date;
acquiring data that the associated account number of each service data belongs to the range of the daily account number checked by the user and the daily account date is greater than or equal to the service transaction date;
inquiring the associated certificate according to the unique identifier of the service, and judging whether the associated certificate is in a generated and pushed state;
if the target organization identifier has a date record smaller than the date of the date, all accounts and subjects of the target organization identifier have completed the date of the previous date, the date of the date checked by the user is the same as the date of the current date, and the association certificate is in a generated and pushed state, executing the date operation on the service data to generate the date record;
if the unique identifier of the service is not associated with the credential, or if the associated credential is invalidated, not pushed or failed to be pushed, determining that the service type corresponding to the service data does not meet the preset date knot condition.
3. The method of claim 1, wherein prior to performing a day knot operation on the business data, the method further comprises:
filtering the service data according to preset filtering conditions to obtain target service data;
the performing a date knot operation on the service data to generate a date knot record includes:
and executing the daily knot operation on the target business data to generate the daily knot record.
4. The method according to claim 1, wherein the determining whether the service data satisfies a preset credential generation condition according to the service attribute information of the service data includes:
judging whether the target organization mark belongs to the range of the organization mark of the date knot;
if not, generating a service certificate according to the service data;
if so, judging whether the voucher entry subjects belong to the date knot subjects;
if the voucher entry subject does not belong to the daily statement subject, judging whether the voucher is associated with the account number and belongs to the daily statement number range;
if the certificate is associated with the account number and does not belong to the daily account number range, generating a service certificate according to the service data;
if the voucher is not associated with the account number or belongs to the daily account number range, judging whether the corresponding billing date is larger than the next daily account date, and if so, generating a service voucher according to the service data;
if not, determining that the preset credential generation condition is not met.
5. The method according to claim 1, wherein the method further comprises:
acquiring an anti-date knot checking rule, and checking the service data according to the anti-date knot checking rule to determine whether the service data needs anti-date knot operation or not;
and if the business data is determined to need the anti-date knot operation, executing the anti-date knot operation on the date knot record.
6. A computer device, the computer device comprising:
the first judging unit is used for acquiring service data and judging whether the service type corresponding to the service data meets a preset date knot condition or not;
the first execution unit is used for executing a date knot operation on the service data to generate a date knot record if the service type corresponding to the service data meets a preset date knot condition;
the second judging unit is used for judging whether the service data meets preset credential generation conditions according to the service attribute information of the service data;
and the second execution unit is used for generating a service certificate according to the service data if the service data meets the preset certificate generation condition.
7. The computer device according to claim 6, wherein the first judging unit is specifically configured to:
judging whether a daily knot record smaller than the daily knot date exists in the target organization mark or not;
judging whether all accounts and subjects identified by the target organization are completed in a day knot of the previous day;
judging whether the date checked by the user is the same as the current date;
acquiring data that the associated account number of each service data belongs to the range of the daily account number checked by the user and the daily account date is greater than or equal to the service transaction date;
inquiring the associated certificate according to the unique identifier of the service, and judging whether the associated certificate is in a generated and pushed state;
if the target organization identifier has a date record smaller than the date of the date, all accounts and subjects of the target organization identifier have completed the date of the previous date, the date of the date checked by the user is the same as the date of the current date, and the association certificate is in a generated and pushed state, executing the date operation on the service data to generate the date record;
if the unique identifier of the service is not associated with the credential, or if the associated credential is invalidated, not pushed or failed to be pushed, determining that the service type corresponding to the service data does not meet the preset date knot condition.
8. The method of claim 6, wherein the first execution unit is specifically configured to:
filtering the service data according to preset filtering conditions to obtain target service data;
and executing the daily knot operation on the target business data to generate the daily knot record.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the method of any of claims 1 to 5 when executing the computer program.
10. A computer storage medium having instructions stored therein, which when executed on a computer, cause the computer to perform the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311592312.1A CN117635354A (en) | 2023-11-27 | 2023-11-27 | Service data date joining method, computer equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311592312.1A CN117635354A (en) | 2023-11-27 | 2023-11-27 | Service data date joining method, computer equipment and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117635354A true CN117635354A (en) | 2024-03-01 |
Family
ID=90031497
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311592312.1A Pending CN117635354A (en) | 2023-11-27 | 2023-11-27 | Service data date joining method, computer equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117635354A (en) |
-
2023
- 2023-11-27 CN CN202311592312.1A patent/CN117635354A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10546296B2 (en) | Public ledger authentication system | |
| WO2020192272A1 (en) | Blockchain-based transfer method and system, computing device and storage medium | |
| US11900271B2 (en) | Self learning data loading optimization for a rule engine | |
| US20180330342A1 (en) | Digital asset account management | |
| WO2020051154A1 (en) | Authenticated access and aggregation database platform | |
| EP3494523A1 (en) | Integration and enhancement of business systems with external services | |
| US11935036B2 (en) | Redemption and settlement transactions via smart contracts | |
| CN111738844A (en) | Resource allocation system, method and device based on block chain | |
| CN105389488B (en) | Identity identifying method and device | |
| CN112163946A (en) | Accounting processing method and device based on distributed transaction system | |
| US20220207520A1 (en) | Systems and methods for managing electronic transactions | |
| US11922383B2 (en) | Methods and systems for deconflicting data from multiple sources in computer systems | |
| US8458093B1 (en) | Systems and methods of transferring credit card charge to line of credit | |
| US11227220B2 (en) | Automatic discovery of data required by a rule engine | |
| US20160358136A1 (en) | Portal interface for establishment and management of confirmed payment account | |
| CN112950191A (en) | Service data processing method and device based on fee refunding service and computer equipment | |
| US20180218465A1 (en) | Service To Identify Class Action Settlements For Which A User Is A Class Member And Assist The User In Obtaining Settlement Damages | |
| US10217087B2 (en) | Multicomputer processing of client device request data using centralized event orchestrator | |
| US20230125814A1 (en) | Credit score management apparatus, credit score management method, and computer readable recording medium | |
| CN111737262B (en) | Data processing method and device | |
| CN117635354A (en) | Service data date joining method, computer equipment and computer storage medium | |
| KR20150054243A (en) | Method of providing loan service and server performing the same | |
| US20210295283A1 (en) | Methods and systems for blockchain digital currency stake delegation | |
| CN114757768A (en) | Account management method and related equipment | |
| CN112785380B (en) | Transaction processing method and device |
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 |