The school information centre was the most afraid to get calls. It wasn't a network break, it wasn't a network slow down, but the students said:"I've been billing. The system didn't add it to me."Some schools use manual collection of a charge on the back, web logs, account balances, and then three people have reconciliations until midnight. And once the check chain is incomplete, it is unclear whether the payment for the cut-off was paid but the billing system was confiscated until the callback, whether it was transferred to the account or not, but whether it was recorded, but the student had not updated it, the entire chain of responsibility collapsed.
The core of the reconciliation is not."Check."Yes."Automation of three water lines"
The first is the flow of water on the side of payment, i.e. the amount of money withheld, which business number was seized, what the trade number was and what time it took to deduct. The second is the charging of water within the system for recording the run-off, when, which account number, how much was charged, which package was matched, and who triggered the recording operation. The third is the actual billing charge on the side of Internet behavior, how much traffic or how long the user spent from that point to that point and how much at what rate.
When real reconciliations are done, experienced schools will require manufacturers to provide an automated reconciliation module that runs every morning and pulls out these three stream lines for cross-checking. The core logic of matching is: first match the current number and billing system charging records one to one, and all that pays on the side and does not have a billing side."Lost to account"This is an anomaly of the highest priority, and it must automatically generate a work plan, make up for the student, and then find out why.——Charges are recorded at the side of the billing, and no corresponding deductions are recorded on the side of payment——It is almost impossible to see it, and if there are internal data manipulations or back door maintenance by the manufacturer, it is a security incident. As for the matching of online billing costs with account balances, it is routine audit, mainly to check whether the bill bug has resulted in over-clips or under-closes.
Several typical scenarios for mishandling and corresponding processing strategies
The first typical scenario is the loss of a callback. When a checkback is successful, the result will be passed to the billing system through a callback notice. But the callback may be lost because of network shaking, server restarting, and interface time-overtime. If the billing system relies on a roundup to confirm the chargeback, that's lost. So now it's a checkback: double-checking: the checkback triggers the entry and then the check-in for orders at every five to ten minutes, turning over the payment platform at every five to 10 minutes, and keeping the latest status as a check-up."Paid"However, transactions that do not generate a charge record are brought back to account.
The second scenario is repeated deductions. For example, in the instant of wireless drifting switching, AP reconnection leads to double postings of online time stampes; or a time-based task for the bill engine is performed twice. At this point, the reconciliation module needs to mark two identical deduction records from the same user in the end-of-day statement and automatically generate refunds. Some schools will set a tolerance threshold, such as the same user being withheld twice within one minute, and the system will be returned automatically without manual intervention.
The third scenario is the time-to-time feeder. For example, students change their 10-dollar 10G package to $20 in mid-month, and how do they convert the flow already used?
The fourth scenario is most likely to be ignored: the accounting anomalies caused by batch operations at the end of month. Many schools will harmonize their batches with graduates at the end of the month, and they will start opening up new batches. If these batch operations are not well controlled, users will have a balance when they have a user or a number to open.
Reconciliations are not just internal matters, but they're subject to audit and superior scrutiny.
The school network of public universities collects fees for education, and the accounts are subject to audit."Can you get a line from the pay-up platform to the billing system to the web log?". The campus-based system ' s reconciliation module therefore meets at least three audit requirements: first, all users of operations involved in changes in amounts can trace them and the operator, time, content and pre- and post-operational account snapshots are fully recorded in the log; second, end-of-day reconciliation reports are automatically archived and cannot be exported manually; third, the reconciliations reveal anomalies with closed processing rings, from detection to confirmation and processing to review, each step being recorded.
Practical recommendations
If you are selecting or upgrading the system, it is recommended that the following items be included in the solicitation or acceptance clause. First, the billing system must provide a positive reconciliation interface on the side of payment and not just by re-interpretation. Second, the end-of-day reconciliation report should contain cross-references to at least three current lines: pay for streaming water, charging water, Internet billing, and a missing item. Third, automatic refund mechanisms for repeated deductions must be the system ' s own capabilities and cannot be temporarily remedied by carrying a carrier. Fourth, lot operations must have pre-operation snapshots and post-operation checks, and an unapproved batch can roll back. Fifth, all accounts logs should be kept for a period of not less than three years and in a format that is understandable to outside auditors.