CN111444003B - Multisystem day cutting preparation method and device based on credit bill and account clearing - Google Patents
Multisystem day cutting preparation method and device based on credit bill and account clearing Download PDFInfo
- Publication number
- CN111444003B CN111444003B CN202010230039.8A CN202010230039A CN111444003B CN 111444003 B CN111444003 B CN 111444003B CN 202010230039 A CN202010230039 A CN 202010230039A CN 111444003 B CN111444003 B CN 111444003B
- Authority
- CN
- China
- Prior art keywords
- transaction
- accounting
- day
- preparation
- time
- 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.)
- Active
Links
- 238000002360 preparation method Methods 0.000 title claims abstract description 119
- 238000005520 cutting process Methods 0.000 title claims description 58
- 238000000034 method Methods 0.000 claims abstract description 31
- 238000004891 communication Methods 0.000 claims description 18
- 230000007246 mechanism Effects 0.000 claims description 17
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 claims description 12
- 238000001514 detection method Methods 0.000 claims description 12
- 238000012795 verification Methods 0.000 claims description 10
- 230000001960 triggered effect Effects 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims description 6
- 230000006399 behavior Effects 0.000 description 16
- 230000008569 process Effects 0.000 description 16
- 238000010586 diagram Methods 0.000 description 9
- 230000002159 abnormal effect Effects 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
- G06F9/4887—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues involving deadlines, e.g. rate based, periodic
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- 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
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
-
- 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/03—Credit; Loans; Processing thereof
-
- 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/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a day-cut preparation method and a day-cut preparation device for a plurality of systems based on credit bill and accounting, wherein the method mainly comprises the following steps: setting a transaction deadline unified by a plurality of business systems based on the current daily cut preparation time, wherein the business systems at least comprise an accounting system, a station account system, a billing system and an accounting system; communicating the date cut preparation notice, the transaction deadline, and the next billing day to each business system; different business systems perform daily preparation according to respective business requirements. By adopting the invention, the unified transaction deadline is set through the distributed architecture, and each service system is informed, so that the billing day can be accurately judged among a plurality of systems on the premise of not stopping the service, the day cut is completed, and the user experience is improved.
Description
Technical Field
The invention relates to the technical field of financial data processing, in particular to a daily cutting preparation method and device for a plurality of systems based on credit bills and accounting.
Background
In the architecture of a distributed credit bill and accounting system, in order to unify each business system in terms of execution date and time, it is a key challenge to perform correct business data date and time. The general day cut is at the zero point of each day, the general practice is to stop the service, start the day cut again, and start the service again after the day cut is completed. However, this solution has many problems: (1) The user cannot conduct transaction during the system day-cut period, or the user timely conducts transaction, and the transaction result is not immediately displayed, so that the user experience is affected; (2) If the day cutting process is too long or abnormal occurs, the experience of a large number of users on the second day is affected, and the enterprise is further affected.
Disclosure of Invention
The embodiment of the invention provides a day-cut preparation method and device for multiple systems based on credit bills and accounting clearing, which can accurately judge the accounting day among the multiple systems on the premise of not stopping business to complete day-cut.
An embodiment of the present invention provides a day cut preparation method for a multi-system based on credit billing and accounting, which may include:
setting a transaction deadline unified by a plurality of business systems based on the current daily cut preparation time, wherein the business systems at least comprise an accounting system, a station account system, a billing system and an accounting system;
communicating a day cut preparation notification, the transaction deadline, and a next billing day to each business system;
different business systems perform daily preparation according to respective business requirements.
Further, the method further comprises:
detecting whether the last day cutting is finished;
when the fact that the last day cutting is not finished is detected, an alarm prompt is output, and the current transaction deadline setting is stopped.
And when the last day cutting is detected to be ended, continuing setting the transaction deadline.
Further, communicating a cut date ready notification, the transaction expiration time, and a next billing day to each business system, comprising:
communicating a day cut preparation notice, the transaction deadline, and a next billing day to the accounting system to cause the accounting system to perform a rationality check on the next billing day;
and after the verification is passed, carrying out communication of business systems except the accounting system.
Further, the method further comprises:
a retry mechanism is initiated when communication for the billing system and/or the ledger system fails.
Further, the method further comprises:
detecting whether the system time of a multiple retry mechanism initiated for the ledger system exceeds the transaction deadline;
and when the detection result is yes, outputting alarm information, increasing the retry frequency of the retry mechanism and expanding the time interval between the transaction deadline and the day-cut preparation time.
Further, the different service systems perform daily preparation according to respective service requirements, including:
after receiving the daily cut preparation notice, the billing system counts and sends a customer transaction event accounting for the transaction time before the transaction deadline in the transaction flow to the ledger system, and sends a cash-out event for the transaction time before the transaction deadline to the accounting system, wherein a customer transaction part does not comprise the cash-out event;
the ledger system counts the customer transaction events, uniformly cuts the transactions of customer behaviors, counts the system behavior events triggered by the customer behavior events, and sends the daily cut finishing deadline of the ledger to the accounting system after the daily cut is finished;
the accounting system judges the accounting date corresponding to the client transaction event, the cash discharge event and the line behavior event respectively according to the transaction time, the transaction expiration time and the account date cutting completion expiration time, and synchronizes accounting running water to the accounting system after judging the accounting date;
the accounting system receives the accounting running water.
A second aspect of the embodiment of the present invention provides a day cut preparation device of a multi-system based on credit billing and accounting, which may include:
the time setting module is used for setting the unified transaction deadline of a plurality of business systems based on the current day-cut preparation time, wherein the business systems at least comprise an accounting system, a station account system, a billing system and an accounting system;
the information transmission module is used for transmitting the date cut preparation notice, the transaction expiration time and the next billing date to each service system;
and the daily cutting preparation module is used for daily cutting preparation of different service systems according to respective service requirements.
Further, the device further comprises:
the date cutting detection module is used for detecting whether the last date cutting is finished or not;
and the time setting stopping module is used for outputting an alarm prompt when the fact that the last day cut is not finished is detected, and stopping the current setting of the transaction deadline.
The time setting module is specifically configured to, when detecting that the last day cut is over, continue setting the transaction deadline.
Further, the information conveying module includes:
the first order transferring unit is used for transmitting a date cut preparation notice, the transaction expiration time and the next accounting date to the accounting system so that the accounting system performs rationality check on the next accounting date;
and the subsequent communication unit is used for communicating business systems except the accounting system after the verification is passed.
Further, the device further comprises:
and the retry initiating module is used for initiating a retry mechanism when the transmission for the billing system and/or the ledger system fails.
Further, the device further comprises:
the timeout detection module is used for detecting whether the system time of the multiple retry mechanism initiated by the ledger system exceeds the transaction deadline;
and the transmission adjustment module is used for outputting alarm information when the detection result is yes, increasing the retry frequency of the retry mechanism and expanding the time interval between the transaction deadline and the day-cut preparation time.
Further, the day cut preparation module includes:
the billing system preparation unit is used for billing the customer transaction event accounting of the transaction flow, the transaction time of which is before the transaction deadline, and sending the customer transaction event accounting to the account system after the billing system receives the daily cut preparation notification, and sending the cash discharge event of the transaction time which is before the transaction deadline to the accounting system;
the ledger system preparation unit is used for the ledger system to bill the transaction event of the client, uniformly divide the transaction of the client behavior, bill the system behavior event triggered by the system behavior event, and send the ledger daily cutting completion deadline to the accounting system after the daily cutting is completed;
the accounting system preparation unit is used for judging accounting days respectively corresponding to the client transaction event, the cash discharge event and the tie-in event according to the transaction time, the transaction expiration time and the account date cutting completion expiration time by the accounting system, and synchronizing accounting running water to the accounting system after judging the accounting days;
an accounting system preparation unit for the accounting system to receive the accounting running water.
A third aspect of the embodiments of the present invention provides a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the steps of:
setting a transaction deadline unified by a plurality of business systems based on the current daily cut preparation time, wherein the business systems at least comprise an accounting system, a station account system, a billing system and an accounting system;
communicating a day cut preparation notification, the transaction deadline, and a next billing day to each business system;
different business systems perform daily preparation according to respective business requirements.
A fourth aspect of an embodiment of the present invention provides a terminal, which may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the steps of:
setting a transaction deadline unified by a plurality of business systems based on the current daily cut preparation time, wherein the business systems at least comprise an accounting system, a station account system, a billing system and an accounting system;
communicating a day cut preparation notification, the transaction deadline, and a next billing day to each business system;
different business systems perform daily preparation according to respective business requirements.
The invention has the beneficial effects that: the unified transaction deadline is set through the distributed architecture, each service system is informed, and on the premise that the service is not stopped, the billing day is accurately judged among a plurality of systems, and day cutting is completed, so that the user experience is improved.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow diagram of a method for preparing a day cut based on a credit bill and accounting system provided by an embodiment of the present invention;
FIG. 2 is an interactive schematic diagram of a day cut scheduling system provided by an embodiment of the present invention;
FIG. 3 is a schematic diagram of a day-cut scheduling flow provided by an embodiment of the present invention;
FIG. 4 is a schematic diagram of a day cut preparation device based on a plurality of credit bill and accounting systems provided by an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an information transmission module according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a day cut preparation module according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terms "comprising" and "having" and any variations thereof in the description and claims of the invention and in the foregoing drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.
Furthermore, the terms "mounted," "configured," "provided," "connected," "coupled," and "sleeved" are to be construed broadly. For example, it may be a fixed connection, a removable connection, or a unitary construction; may be a mechanical connection, or an electrical connection; may be directly connected, or indirectly connected through intervening media, or may be in internal communication between two devices, elements, or components. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art according to the specific circumstances.
It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other. The present application will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
The terminal related to the embodiment of the invention can be a mainframe computer, a PC, a tablet personal computer, a palm computer, a Mobile Internet Device (MID) and other terminal devices with data processing capability.
As shown in fig. 1, the day cut preparation method of the multi-system based on credit bill and account clearing at least comprises the following steps:
s101, setting a unified transaction deadline of a plurality of business systems based on the current day-cut preparation time.
It will be appreciated that the current day cut preparation time may be the time the day cut scheduling system starts day cut preparation daily, typically at zero daily. The transaction deadline and the day cut preparation time which are unified by each business system are arranged to have a certain time interval, for example, the time interval can be 00:05:00.
In an alternative implementation, when the transaction deadline is set, an abnormal situation may occur, to prevent the occurrence of an abnormality, whether the last day cut is ended or not may be detected before the time is set, if the last day cut is ended, the setting of the transaction deadline may be performed normally, if the next day cut is detected to be not ended, the system may issue an alarm, need to intervene to process the abnormality, and restart the preparation of the next day cut.
S102, the date cut preparation notice, the transaction expiration time and the next billing date are transmitted to each business system.
In a specific implementation, as shown in fig. 2, after the zero day cut preparation begins, each business system that can be scheduled by the day cut scheduling system can sequentially transmit day cut preparation notification, transaction deadline and next billing day to the accounting system, the ledger system, the billing system and the accounting system through the interfaces.
In a preferred implementation manner, the accounting system needs to be notified of the information first, the accounting system can perform rationality verification on the next billing day of notification, if verification is not passed, the next day is not triggered, and the system should alarm and perform artificial intervention; and after the verification is passed, other business systems except the accounting system can be notified.
It should be noted that, when other service systems are notified, an abnormal situation may occur, which may cause a system to fail to prepare for daily cutting. If the abnormal situation causes the failure of daily cutting preparation of the notification billing system, the situation does not affect the daily cutting accuracy of the service data, and the scheduling system initiates a retry mechanism; if the day-cut preparation of the accounting system is informed to fail, the dispatching system can initiate retry, but if the system time exceeds the transaction deadline after multiple retries, the day-cut data can be wrong, the accounting data which should belong to the next day is accounted for in the last accounting day, and aiming at the situation, the system can send out an alarm, and set high-frequency retry and enlarge the interval of the day-cut preparation starting time and the transaction deadline.
It can be understood that the day cut scheduling system considers that day cut can be started only after all systems are confirmed to receive day cut preparation notification, and further coordinates the smooth progress of day cut among different service systems.
S103, different service systems perform daily cutting preparation according to respective service requirements.
In a specific implementation, after receiving the day cut preparation notification, the billing system may bill and send the customer transaction event with the transaction time before the transaction deadline in the transaction flow to the ledger system, and send the cash discharge event with the transaction time before the transaction deadline to the accounting system. In the above process, the transaction of the billing system is not stopped, and the transaction of the user can be sent to the accounting system and the ledger system in real time. Accounting of the cash-out event can not be stopped, and the accounting system can compare the transaction time of the cash-out event to distinguish different accounting days according to the transaction deadline
In a specific implementation, the ledger system accounts for the customer transaction (except for the cash discharge transaction) event, and uniformly segments the transaction of the customer behavior, so that the billing day error is avoided.
Further, the ledger system processes transaction flow of customer behavior, the system itself triggers a series of system behavior events (such as first clear calculation, second clear calculation, month end calculation, etc.), these events should belong to the last billing day on business, but the transaction time is after the day-cut transaction deadline, so the ledger system can send a ledger system day-cut completion deadline to the accounting system after day-cut is completed, the accounting system judges the billing time of non-paying event, and the transaction time and the ledger day-cut completion deadline are compared to judge the billing day.
In an alternative implementation, a situation may occur in which the ledger system day cut preparation cannot end all the time, in which case when the day cut does not end, an alarm may be given to prompt the operation and maintenance personnel to process, but the process does not affect the transaction behavior of the user.
In one specific implementation, the primary function of the accounting system preparation phase is to determine the billing day of the transaction flow. Because billing for two different events, namely customer transaction (including customer transaction event and cash discharge event) and system transaction, needs to be processed, transaction flow transmitted by a billing system and a station account system is judged that the billing day mode is not identical.
And judging whether the paying event of the billing system is counted and other client transaction counts transmitted by the machine account are counted, comparing the transaction time of the original band of the billing system with the transaction deadline, counting the last billing day before the deadline, and counting the subsequent transaction as the next billing day. And the accounting of other events is to judge the accounting date by comparing the transaction time with the expiration time of the cutting of the ledger date.
In one particular implementation, because accounting date of the accounting system is determined by accounting, accounting running water is synchronized to accounting system accounting. Thus, the accounting system preparation phase is simply that the day cut preparation start and the transaction expiration time are received, and no operation is performed.
In the embodiment of the invention, the unified transaction deadline is set through the distributed architecture, and each service system is informed, so that on the premise of not stopping the service, the billing day is accurately judged among a plurality of systems, and the day cutting is completed, thereby improving the user experience.
In another embodiment of the present application, a day cut scheduling process is shown in fig. 3, and specifically may include the following steps:
1. day cut time notification.
1.1, notifying the core of day-cut preparation, namely notifying a billing system of day-cut preparation.
1.2, notifying the preparation of the ledger daily cutting.
1.3, notifying the daily cutting preparation of the accounting.
1.4, notifying the preparation of the daily cut of the accounting.
2. And pushing the service data.
And 2.1, notifying the core service data to push.
2.1.1, pushing customer account time.
2.1.2, push order change running water.
And 2.2, notifying the account service data to push.
2.2.1, push customer account, two clear, and out event.
And 2.3, notifying the accounting business data to push.
2.3.1 pushing all accounting vouchers.
3. Confirm that the day cut preparation is all completed.
4. And executing daily cutting.
5. Checking is performed.
5.1, bill-account reconciliation.
And 5.2, checking the account of the standing book.
And 5.3, checking internal balance of the accounting.
5.4, accounting-accounting reconciliation.
5.5, checking the internal balance of the accountant.
It should be noted that, in the present embodiment, step 1 and step 2 are a process of performing day-cut preparation, and specific implementation processes may be referred to the description in the above embodiment, and steps 3 to 5 in the present embodiment are day-cut processes, where the day-cut process performed by each service system is a process of aggregating day-cut data of each service system, and a process of mutually checking accounts of different service systems or an internal balance verification process.
In the embodiment of the invention, the unified transaction deadline is set through the distributed architecture, and each service system is informed, so that on the premise of not stopping the service, the billing day is accurately judged among a plurality of systems, and the day cutting is completed, thereby improving the user experience.
The following describes in detail a day cut preparation device based on a plurality of systems for credit billing and accounting according to an embodiment of the present invention with reference to fig. 4 to 6. It should be noted that, the day cut preparation device shown in fig. 4-6 is used to execute the method of the embodiment shown in fig. 1-3, and for convenience of explanation, only the relevant parts of the embodiment of the present invention are shown, and specific technical details are not disclosed, please refer to the embodiment shown in fig. 1-3 of the present invention.
Referring to fig. 4, a schematic structural diagram of a day cut preparation device based on a plurality of credit bills and accounting systems is provided in an embodiment of the present invention. As shown in fig. 4, the day cut preparation device 10 according to the embodiment of the present invention may include: a time setting module 101, an information transmission module 102, a day cut preparation module 103, a day cut detection module 104, a time setting stop module 105, a retry initiation module 106, a timeout detection module 107, and a transmission adjustment module 108. The information transmission module 102, as shown in fig. 5, includes a first transfer unit 1021 and a subsequent transmission unit 1022; the day cut preparation module 103 includes, as shown in fig. 6, a billing system preparation unit 1031, a ledger system preparation unit 1032, an accounting system preparation unit 1033, and an accounting system preparation unit 1034.
The time setting module 101 is configured to set a transaction deadline unified by a plurality of service systems based on a current day-cut preparation time, where the plurality of service systems includes at least an accounting system, a billing system, and an accounting system.
In an alternative embodiment, the day cut detection module 104 is configured to detect whether the last day cut is ended.
And the time setting stopping module 105 is used for outputting an alarm prompt when the fact that the last day cut is not ended is detected, and stopping the current setting of the transaction deadline.
The time setting module 101 is specifically configured to, when detecting that the last day cut is over, continue setting the transaction deadline.
The information transmission module 102 is used for transmitting the date cut preparation notice, the transaction expiration time and the next billing date to each business system.
In a preferred implementation, retry initiation module 106 is configured to initiate a retry mechanism when communication fails for the billing system and/or ledger system.
A timeout detection module 107, configured to detect whether a system time of the multiple retry mechanism initiated by the ledger system exceeds a transaction deadline.
The transmission adjustment module 108 is configured to output an alarm message when the detection result is yes, increase the retry frequency of the retry mechanism, and enlarge the time interval between the transaction deadline and the day cut preparation time.
And the date cutting preparation module 103 is used for performing date cutting preparation according to respective service requirements by different service systems.
In alternative embodiments, the information communication module 102 may include the following elements:
the first transfer unit 1021 is used for transmitting the date cut preparation notice, the transaction expiration time and the next billing date to the accounting system so that the accounting system can carry out rationality check on the next billing date.
And a subsequent communication unit 1022 for communicating business systems other than the accounting system after the verification is passed.
In an alternative embodiment, the day cut preparation module 103 may include the following elements:
the billing system preparation unit 1031 is configured to, after receiving the day-cut preparation notification, bill and send a customer transaction event accounting for a transaction time before a transaction deadline in the transaction flow to the ledger system, and send a cash discharge event for a transaction time before the transaction deadline to the accounting system.
The ledger system preparation unit 1032 is configured to make the ledger system account for the transaction event of the customer, make unified segmentation for the transaction of the customer behavior, make account for the event of the system behavior triggered by the ledger system, and send the cut-off time of the ledger system to the accounting system after the cut-off is completed.
The accounting system preparation unit 1033 is configured to determine accounting days corresponding to the client transaction event, the payment event and the tie action event according to the transaction time, the transaction expiration time and the account day cutting completion expiration time, and synchronize the accounting running water to the accounting system after determining the accounting days.
The accounting system prepares unit 1034 for the accounting system to receive the accounting running water.
It should be noted that, the detailed execution process of each unit and module in the above system may be referred to the description in the above method embodiment, and will not be repeated here.
In the embodiment of the invention, the unified transaction deadline is set through the distributed architecture, and each service system is informed, so that on the premise of not stopping the service, the billing day is accurately judged among a plurality of systems, and the day cutting is completed, thereby improving the user experience.
The embodiment of the present invention further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are adapted to be loaded by a processor and execute the method steps of the embodiment shown in fig. 1 to 3, and the specific execution process may refer to the specific description of the embodiment shown in fig. 1 to 3, which is not repeated herein.
Referring to fig. 7, a schematic structural diagram of a terminal is provided in an embodiment of the present invention. As shown in fig. 7, the terminal 1000 may include: at least one processor 1001, such as a CPU, at least one network interface 1004, a user interface 1003, a memory 1005, at least one communication bus 1002. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display (Display), a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface, among others. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may also optionally be at least one storage device located remotely from the processor 1001. As shown in fig. 7, an operating system, a network communication module, a user interface module, and a day cut preparation application program may be included in a memory 1005 as one type of computer storage medium.
In terminal 1000 shown in fig. 7, user interface 1003 is mainly used for providing an input interface for a user, and acquiring data input by the user; the network interface 1004 is used for data communication with a user terminal; and the processor 1001 may be configured to call a day cut preparation application program stored in the memory 1005, and specifically perform the following operations:
setting a transaction deadline unified by a plurality of business systems based on the current daily cut preparation time, wherein the business systems at least comprise an accounting system, a station account system, a billing system and an accounting system;
communicating the date cut preparation notice, the transaction deadline, and the next billing day to each business system;
different business systems perform daily preparation according to respective business requirements.
In some embodiments, the processor 1001 is further configured to:
detecting whether the last day cutting is finished;
when the fact that the last day cutting is not finished is detected, an alarm prompt is output, and the current transaction deadline setting is stopped.
And when the last day cutting is detected to be ended, continuing setting the transaction deadline.
In some embodiments, the processor 1001, when communicating the day cut preparation notification, the transaction expiration time, and the next billing day to the business systems, specifically performs the following:
communicating the date cut preparation notice, the transaction expiration time and the next billing day to the accounting system to enable the accounting system to conduct a rationality check on the next billing day;
and after the verification is passed, carrying out communication of business systems except for the accounting system.
In some embodiments, the processor 1001 is further configured to:
a retry mechanism is initiated when communication fails for the billing system and/or ledger system.
In some embodiments, the processor 1001 is further configured to:
detecting whether the system time of a multiple retry mechanism initiated by a ledger system exceeds the transaction deadline;
when the detection result is yes, outputting alarm information, increasing the retry frequency of the retry mechanism and expanding the time interval between the transaction deadline and the day-cut preparation time.
In some embodiments, the processor 1001, when controlling different service systems to prepare for day cutting according to respective service requirements, specifically performs the following operations:
after receiving the daily cut preparation notice, the billing system accounts a customer transaction event accounting for the transaction time before the transaction deadline in the transaction flow and sends the customer transaction event accounting to the ledger system, and sends a cash-out event for the transaction time before the transaction deadline to the accounting system, wherein the customer transaction piece does not comprise the cash-out event;
the account system counts up the customer transaction event, uniformly cuts the transaction of the customer behavior, counts up the system behavior event triggered by the account system, and sends the account date cutting completion deadline to the accounting system after the date cutting is completed;
the accounting system judges the accounting days respectively corresponding to the client transaction event, the paying event and the line behavior event according to the transaction time, the transaction expiration time and the account date cutting completion expiration time, and synchronizes the accounting running water to the accounting system after judging the accounting days;
the accounting system receives accounting running water.
In the embodiment of the invention, the unified transaction deadline is set through the distributed architecture, and each service system is informed, so that on the premise of not stopping the service, the billing day is accurately judged among a plurality of systems, and the day cutting is completed, thereby improving the user experience.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in the embodiments may be accomplished by computer programs stored in a computer-readable storage medium, which when executed, may include the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like.
The foregoing disclosure is illustrative of the present invention and is not to be construed as limiting the scope of the invention, which is defined by the appended claims.
Claims (9)
1. A method for preparing a day cut based on a plurality of systems for credit billing and accounting, comprising:
setting a transaction deadline unified by a plurality of business systems based on the current daily cutting preparation time, wherein the business systems at least comprise an accounting system, a standing account system, a billing system and a accounting system;
communicating a day cut preparation notification, the transaction deadline, and a next billing day to each business system;
different service systems perform daily cutting preparation according to respective service requirements; wherein the method comprises the steps of
The different service systems perform daily cutting preparation according to respective service requirements, and the daily cutting preparation comprises the following steps:
after receiving the daily cut preparation notice, the billing system counts and sends a customer transaction event accounting for the transaction time before the transaction deadline in the transaction flow to the ledger system, sends a cash-out event for the transaction time before the transaction deadline to the accounting system, wherein the customer transaction part does not comprise the cash-out event,
the ledger system counts the customer transaction event, uniformly cuts the transaction of the customer behavior, counts the system behavior event triggered by the transaction system, sends the ledger daily cutting completion expiration time to the accounting system after daily cutting is completed,
the accounting system judges the accounting date corresponding to the client transaction event, the cash discharge event and the system behavior event respectively according to the transaction time, the transaction expiration time and the account date cutting completion expiration time, synchronizes accounting running water to the accounting system after judging the accounting date,
the accounting system receives the accounting running water.
2. The day cut preparation method according to claim 1, further comprising:
detecting whether the last day cutting is finished;
when the fact that the last day cutting is not finished is detected, outputting an alarm prompt, and stopping the setting of the current transaction deadline;
and when the last day cutting is detected to be ended, continuing setting the transaction deadline.
3. The day cut preparation method according to claim 1, wherein communicating day cut preparation notice, the transaction deadline, and a next billing day to each business system comprises:
communicating a day cut preparation notice, the transaction deadline, and a next billing day to the accounting system to cause the accounting system to perform a rationality check on the next billing day;
and after the verification is passed, carrying out communication of business systems except the accounting system.
4. A day cut preparation method according to claim 3, further comprising:
a retry mechanism is initiated when communication for the billing system and/or the ledger system fails.
5. The day cut preparation method according to claim 4, further comprising:
detecting whether the system time of a multiple retry mechanism initiated for the ledger system exceeds the transaction deadline;
and when the detection result is yes, outputting alarm information, increasing the retry frequency of the retry mechanism and expanding the time interval between the transaction deadline and the day-cut preparation time.
6. A multi-system day cut preparation device based on credit billing and accounting, comprising:
the system comprises a time setting module, a time counting module and a time counting module, wherein the time setting module is used for setting the unified transaction deadline of a plurality of business systems based on the current day-cut preparation time, and the business systems at least comprise an accounting system, a standing account system, a billing system and a accounting system;
the information transmission module is used for transmitting the date cut preparation notice, the transaction expiration time and the next billing date to each service system;
the daily cutting preparation module is used for daily cutting preparation of different service systems according to respective service requirements; wherein the method comprises the steps of
The different service systems perform daily cutting preparation according to respective service requirements, and the daily cutting preparation comprises the following steps:
after receiving the daily cut preparation notice, the billing system counts and sends a customer transaction event accounting for the transaction time before the transaction deadline in the transaction flow to the ledger system, sends a cash-out event for the transaction time before the transaction deadline to the accounting system, wherein the customer transaction part does not comprise the cash-out event,
the ledger system counts the customer transaction event, uniformly cuts the transaction of the customer behavior, counts the system behavior event triggered by the transaction system, sends the ledger daily cutting completion expiration time to the accounting system after daily cutting is completed,
the accounting system judges the accounting date corresponding to the client transaction event, the cash discharge event and the system behavior event respectively according to the transaction time, the transaction expiration time and the account date cutting completion expiration time, and synchronizes accounting running water to the accounting system after judging the accounting date;
the accounting system receives the accounting running water.
7. The day cut preparation device according to claim 6, further comprising:
the date cutting detection module is used for detecting whether the last date cutting is finished or not;
the time setting stopping module is used for outputting an alarm prompt when the fact that the last day cutting is not finished is detected, and stopping the current transaction deadline setting;
the time setting module is specifically configured to, when detecting that the last day cut is over, continue setting the transaction deadline.
8. The day cut preparation device according to claim 6, wherein the information communication module comprises:
the first order transferring unit is used for transmitting a date cut preparation notice, the transaction expiration time and the next accounting date to the accounting system so that the accounting system performs rationality check on the next accounting date;
and the subsequent communication unit is used for communicating business systems except the accounting system after the verification is passed.
9. The day cut preparation device according to claim 8, further comprising:
and the retry initiating module is used for initiating a retry mechanism when the transmission for the billing system and/or the ledger system fails.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010230039.8A CN111444003B (en) | 2020-03-27 | 2020-03-27 | Multisystem day cutting preparation method and device based on credit bill and account clearing |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010230039.8A CN111444003B (en) | 2020-03-27 | 2020-03-27 | Multisystem day cutting preparation method and device based on credit bill and account clearing |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111444003A CN111444003A (en) | 2020-07-24 |
CN111444003B true CN111444003B (en) | 2024-03-01 |
Family
ID=71649087
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010230039.8A Active CN111444003B (en) | 2020-03-27 | 2020-03-27 | Multisystem day cutting preparation method and device based on credit bill and account clearing |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111444003B (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112988800B (en) * | 2021-03-31 | 2022-09-27 | 建信金融科技有限责任公司 | Data processing method and device based on distributed environment |
CN113761064B (en) * | 2021-08-27 | 2023-06-30 | 成都质数斯达克科技有限公司 | Block chain-based day cut account checking method, device and equipment and readable storage medium |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109598604A (en) * | 2018-11-20 | 2019-04-09 | 中国银行股份有限公司 | Day cuts judgment method and device |
CN110264328A (en) * | 2019-06-14 | 2019-09-20 | 深圳前海微众银行股份有限公司 | Account checking method, device, equipment, system and computer readable storage medium |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101807286A (en) * | 2010-02-05 | 2010-08-18 | 南京联创科技集团股份有限公司 | Method for realizing exact reconciliation of telecommunication multisystem in transaction scene of 7*24 h |
-
2020
- 2020-03-27 CN CN202010230039.8A patent/CN111444003B/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109598604A (en) * | 2018-11-20 | 2019-04-09 | 中国银行股份有限公司 | Day cuts judgment method and device |
CN110264328A (en) * | 2019-06-14 | 2019-09-20 | 深圳前海微众银行股份有限公司 | Account checking method, device, equipment, system and computer readable storage medium |
Non-Patent Citations (1)
Title |
---|
肖薇 ; .多样化支付模式下医院对账系统设计.电脑知识与技术.2020,(第04期),全文. * |
Also Published As
Publication number | Publication date |
---|---|
CN111444003A (en) | 2020-07-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111444003B (en) | Multisystem day cutting preparation method and device based on credit bill and account clearing | |
CN110232565B (en) | Resource clearing method, device, computer equipment and storage medium | |
WO2019157776A1 (en) | Processing method and system for reconciling discrepancies | |
CN109255706B (en) | One-key financial product combined purchase flow control method and system | |
CN101329795B (en) | System and method for implementing bank card agent authorization | |
CN111353841B (en) | Document data processing method, device and system | |
WO2019117746A1 (en) | Method for automatically crediting deposited funds in the event of fault occurrences | |
CN101950452B (en) | Bank card core system and bank card stand-in authorization system data synchronous processing method | |
WO2023197917A1 (en) | Payment security management method and apparatus and payment system | |
CN110675247B (en) | Unknown transaction processing method and system, peripheral system and core bank system | |
CN109493230B (en) | Supplementary recording method and device for unilateral transaction | |
US20060174218A1 (en) | Method for controlling software modules | |
CN112732733B (en) | Data checking processing method and device | |
CN115271694A (en) | Order payment method and system | |
US11176785B1 (en) | Detection of dispensing errors in automated teller machines | |
CN102447798B (en) | Recharge-for-recovery method and device | |
US20190147422A1 (en) | Automated transaction machine, communication terminal, automated transaction system, and program | |
JP2013145426A (en) | Failure detection system, failure detection method, program and automatic transaction device | |
CN112634049A (en) | Method and device for preventing repeated posting of receipt and payment transactions | |
CN111582851B (en) | Platform money printing method and device based on big data, electronic equipment and storage medium | |
CN111192113A (en) | Order processing method, device, equipment and storage medium | |
JP4100217B2 (en) | Transaction processing system and information terminal | |
JP7000549B1 (en) | Information processing equipment, methods and programs | |
CN114465974B (en) | Push message processing method and device, processor and electronic equipment | |
JP5827597B2 (en) | Fault response system, automatic transaction apparatus, fault response method, and fault response program |
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 | ||
GR01 | Patent grant | ||
GR01 | Patent grant |