Lottery software modules

Retailer Accounting:

The lottery software performs all retailer accounting in real-time, as each transaction happens. Lottery software supports for providing accounting feeds to and accepting feeds from banking/ clearing houses system. Lottery software creates a file that the bank or clearing house uses to take the balance due from the retailer account and “sweep” it into the operator’s account. This is termed as cash-sweep. Alternatively the bank can deliver to the operator a file with the details of the remittances (deposits) made by retailers for uploading in the lottery management software for reflection on the retailer’s online account. The exact cash remittance / sweep process is customizable in lottery software as per customer requirement.

Retailer Credit Control:

Our lottery management software supports a credit control process with the retailers that allows for flexibility in granting or denying certain amounts of credit based on credit worthiness of retailers. The lottery software is configurable to set the credit limits for each retailer separately. Credit-worthy retailers may be allowed to operate with only a minimum or no security deposit with no restrictions on the amount of their sales during any invoice period. Retailers who have not established credit worthiness can be given modest to no credit limits, required them to remit funds regularly in order to continue selling. A retailer when hits their credit limit lottery software automatically disables selling, which is enabled only after retailer makes the payout.

Retailer Remittance:

Retailer remittances can be done via Automated clearing house – Lottery software generates a remittance file during EOD in the format expected by the ACH and posts the remittances automatically. In case when a transaction fails the lottery software provides an option to reverse the remittance posting through Admin interface. Bank transfer – When remittances happen through bank transfer lottery software provides for “remittance load” utility though which lottery operator can upload the transfer file received from bank. Lottery system reflects the remittances against the retailer account immediately. Cash collection through third party services – The case collection party submits the daily collections into an excel (csv) file in the format expected by the lottery system remittance load utility and loaded into the lottery system for reflecting the remittances against the retailer account. Remittances are generally credited during nightly processing, however there is a provision to enter a remittance at any time and have it reflected immediately. Lottery system keeps full ledger records of debits and credits.

Retailer Reporting:

Dusane’s retailer reporting system is available from the terminal. Retailers can obtain an up-to-date account of retailers accounting records. For invoicing periods as well as non-invoicing periods (such as daily, or week-to-date), full balance records are available showing start balance, sales, cancels, payouts, activations/settlements, commissions, adjustments, remittances, and end balance. On a game-by-game basis sales, cancels, payouts, and commissions are shown for invoice and non-invoice periods.

“Management Terminals” are standard PC’s with web browser based terminal management application. Managers, sales people, accountants, system operators, hotline, draw managers (i.e. all authorized personnel) use it to administer and control the lottery system. Using a secure login via most standard web browsers such as Microsoft Internet Explorer, users have access to the features and functions that they are authorized for.

This architecture provides several benefits over the more traditional proprietary applications of competitor systems.

  1. Central Deployment – The application is deployed on the lottery system servers and does not need to be installed on any individual desktop computers. Simply access the server via the web browser already installed. This means updates and new releases are automatically deployed to all users.
  2. Intuitive – The application is easy to use with minimal training since most people are already familiar with the user interface paradigm of web applications.
  3. Accessible – Remote users can easily access the system and reports via a secure Internet connection (virtual private network)
The lottery software supports scheduling of “buy X, get Y free”, “every Nth”, “lucky ticket”, and coupon type promotions. In “buy X, get Y” free promotions, a player is entitled to Y free bets of the specified game in exchange for purchasing X bets of a specified game. For example, “Buy 5 Lotto bets, Get 1 Keno bet for free”.

In the “every Nth” promotion, a player can win a free bet(s), cash prize, or merchandise if they purchase the lucky Nth ticket. This promotion type is multi-layered. For example, every 100th ticket wins a Coke, every 10,000th ticket wins 5 free bets, every 1,000,000 ticket wins $1000.

In “lucky ticket” promotions, the lottery system can randomly select one or more non-winning tickets to win a consolation prize.

In coupon promotions, the lottery can issue coupons which entitle the bearer to a free bet or bets.

Dusane’s lottery software provides all functions necessary for managing and controlling the lottery operations via admin interface. This includes, but is not limited to:

  • Game setup and parameters (Lotto and instant)
  • Prize plan definition
  • Retailer profile management
  • Retailer accounting
  • Draw control
  • Draw results entry
  • Prize payment
  • Hotline management functions, including ticket inquiry, pay, cancel, and stop-pay
  • Reporting
  • Terminal network management, including broadcast and unicast (sending message s to all terminals or a single terminal)
The lottery software provides all authorized users with access to various reports. Some are so-called “online” reports in that the user can specify certain query criteria, such as a date range, game(s), retailer range, retailer category, retailer region, and many others. Others are so-called “end-of-day” reports in that the system automatically generates these reports at the end of each business day and stores them for viewing at a later time.

The ADMIN module consists of a a real-time “dashboard” application that presents certain key metrics and sales figures in real time in various formats, including graphical and tabular. It provides an at-a-glance snapshot of the system such as 1) terminals connected, 2) sales by game for the day/draw, 3) peak transactions per minute, 4) average transactions per minute, 5) latest transactions per minute, 6) peak selling terminals, 7) low selling terminals, and more.

The lottery system comes with a set of standard reports. An example of some of these reports are:

  • Draw Sales and Liability Report
  • Retailer Sales Report (retailer ID range, Game(s), and date range are user selectable). Customized versions are by region, category, postcode, etc
  • Game Sales Report. For given Draw ID range lists all major Draw statistics
  • Retailer Balance Report. For given date range shows start balance, sales, payouts, commissions, remittances, end balance etc for each day
  • Daily paid/claimed ticket report
  • Daily Transaction Summary report
  • Daily Retailer Transaction Summary Report
  • Daily Cancelled Tickets Report
  • Game Transaction Summary
  • Taxable (high tier) Winning Tickets Report
  • Weekly Retailer Accounting Report
  • Weekly Sales Summary Report
  • Inactive (lazy) Retailers Report
  • Expired Unclaimed Winning Tickets Report
  • Instant Ticket Inventory Summary Report (all games)
  • Instant Ticket Inventory Detail Report
  • Instant Ticket Game Accounting Report

It is normal for custom reports to be required. Dusane will work with the various operations, sales, accounts, and other staff to deliver the reports required to support the local operation.

Dusane’s lottery software is built on a high-performance relational database platform. A separate real-time replicated MIS server is necessary only when real-time data analysis that puts a heavy load on the system is being done. Normally this sort of analysis can be done offline (i.e. not in real-time) and thus real-time replication is not required.