This is a private hackathon open to Sup’Com Student participants. Please reach out to Azer if you would like to participate.

Tax fraud is the intentional act of lying on a tax return form with the intent to lower one’s tax liability. Under-reporting is one of the most common types of tax frauds. It consists of filing a tax return form with a lesser tax base. As a result of this act, fiscal revenues are reduced, undermining public investment in much-needed services.

The objective of the challenge is to detect tax fraud. This is one of the main priorities of local tax authorities which are required to develop cost-efficient strategies to tackle this problem.

Using historical data, a supervised machine learning technique that detects potential fraudulent taxpayers will increase the operational efficiency of the tax supervision process.

To read more about the Ministry of Finance of Tunisia, please visit http://www.finances.gov.tn/fr

About IEEE

IEEE Sup'Com Student Branch is a engineering club dedicated to advancing technology for the benefit of its community. It was first launched on 2011 but was the most active during the 2 past years and has held many important events that had a huge impact like IndabaX and Smart Green Tunisia. As of 2020, the student branch worked on more than 10 projects, 7 events, held many courses and gathered over 100 members.

About IEEE Computer Society Chapter

The Computer Society is one of the chapters created within the Sup'Com student branch. It has for mission to promote the different aspects of computer science within its community through conferences, educational activities, contests and IT projects. It also aims to help its members improve and become full fledged engineers that master both the technical and soft aspect of their job. Even though it was recently founded, the Sup'Com's CS chapter has already held very successful events like Google Hash code and its members are shining locally and worldwide.

About Alliance4AI Sup’Com

Alliance4AI SUP’COM Chapter is part of the african ALLIANCE4AI movement. This is a student-run club whose mission is to empower students to master Artificial Intelligence and its related technologies and also to form Africa’s future leaders through tutorials, workshops, real-world projects and non-technical events. By exposing members to the advancement and impact of AI in Africa, Alliance4AI SUP’COM’s goal is to raise the student’s awareness about what we can achieve through the use of AI.

This is a private hackathon open to Sup’Com Student participants. Please reach out to Azer if you would like to participate.

Teams and collaboration

You may participate in competitions as an individual or in a team of up to four people. When creating a team, the team must have a total submission count less than or equal to the maximum allowable submissions as of the formation date. A team will be allowed the maximum number of submissions for the competition, minus the total number of submissions among team members at team formation. Prizes are transferred only to the individual players or to the team leader.

Multiple accounts per user are not permitted, and neither is collaboration or membership across multiple teams. Individuals and their submissions originating from multiple accounts will be immediately disqualified from the platform.

Code must not be shared privately outside of a team. Any code that is shared, must be made available to all competition participants through the platform. (i.e. on the discussion boards).

The Zindi user who sets up a team is the default Team Leader. The Team Leader can invite other data scientists to their team. Invited data scientists can accept or reject invitations. Until a second data scientist accepts an invitation to join a team, the data scientist who initiated a team remains an individual on the leaderboard. No additional members may be added to teams within the final 5 days of the competition or the last hour of a hackathon, unless otherwise stated in the competition rules

A team can be disbanded if it has not yet made a submission. Once a submission is made individual members cannot leave the team.

All members in the team receive points associated with their ranking in the competition and there is no split or division of the points between team members.

Datasets and packages

The solution must use publicly-available, open-source packages only. Your models should not use any of the metadata provided.

You may use only the datasets provided for this competition. Automated machine learning tools such as automl are not permitted.

You may use pretrained models as long as they are openly available to everyone.

The data used in this competition is the sole property of Zindi and the competition host. You may not transmit, duplicate, publish, redistribute or otherwise provide or make available any competition data to any party not participating in the Competition (this includes uploading the data to any public site such as Kaggle or GitHub). You may upload, store and work with the data on any cloud platform such as Google Colab, AWS or similar, as long as 1) the data remains private and 2) doing so does not contravene Zindi’s rules of use.

You must notify Zindi immediately upon learning of any unauthorised transmission of or unauthorised access to the competition data, and work with Zindi to rectify any unauthorised transmission or access.

Your solution must not infringe the rights of any third party and you must be legally entitled to assign ownership of all rights of copyright in and to the winning solution code to Zindi.

Submissions and winning

You may make a maximum of 50 submissions per day. Your highest-scoring solution on the private leaderboard at the end of the competition will be the one by which you are judged.

Zindi maintains a public leaderboard and a private leaderboard for each competition. The Public Leaderboard includes approximately 40% of the test dataset. While the competition is open, the Public Leaderboard will rank the submitted solutions by the accuracy score they achieve. Upon close of the competition, the Private Leaderboard, which covers the other 60% of the test dataset, will be made public and will constitute the final ranking for the competition.

If you are in the top 5 at the time the leaderboard closes, the host of this hackathon will reach out to you to submit your code for code review. You have 48 hours to submit your code following the submission guidelines detailed below. Failure to respond will result in disqualification.

If two solutions earn identical scores on the leaderboard, the tiebreaker will be the date and time in which the submission was made (the earlier solution will win).

If the error metric requires probabilities to be submitted, do not set thresholds (or round your probabilities) to improve your place on the leaderboard. In order to ensure that the client receives the best solution Zindi will need the raw probabilities. This will allow the clients to set thresholds to their own needs.

You acknowledge and agree that Zindi may, without any obligation to do so, remove or disqualify an individual, team, or account if Zindi believes that such individual, team, or account is in violation of these rules. Entry into this competition constitutes your acceptance of these official competition rules.

Zindi is committed to providing solutions of value to our clients and partners. To this end, we reserve the right to disqualify your submission on the grounds of usability or value. This includes but is not limited to the use of data leaks or any other practices that we deem to compromise the inherent value of your solution.

Zindi also reserves the right to disqualify you and/or your submissions from any competition if we believe that you violated the rules or violated the spirit of the competition or the platform in any other way. The disqualifications are irrespective of your position on the leaderboard and completely at the discretion of Zindi.

Please refer to the FAQs and Terms of Use for additional rules that may apply to this competition. We reserve the right to update these rules at any time.

• Reproducibility of submitted code
• If your submitted code does not reproduce your score on the leaderboard, we reserve the right to adjust your rank to the score generated by the code you submitted.
• If your code does not run you will be dropped from the top 10. Please make sure your code runs before submitting your solution.
• Always set the seed. Rerunning your model should always place you at the same position on the leaderboard. When running your solution, if randomness shifts you down the leaderboard we reserve the right to adjust your rank to the closest score that your submission reproduces.
• We expect full documentation. This includes:
• All data used
• Output data and where they are stored
• Explanation of features used
• A requirements file with all packages and versions used
• Your solution must include the original data provided by Zindi and validated external data (if allowed)
• All editing of data must be done in a notebook (i.e. not manually in Excel)
• Environment code to be run. (e.g. Google Colab or the specifications of your local machine)
• Expected run time for each notebook. This will be useful to the review team for time and resource allocation.

Data standards:

• Your submitted code must run on the original train, test, and other datasets provided.
• If external data is allowed, external data must be freely and publicly available, including pre-trained models with standard libraries. If external data is allowed, any data used should be shared with Zindi to be approved and then shared on the discussion forum. Zindi will also make note of the external data available on the data page.
• Packages:
• You must submit a requirements file with all packages and versions used.
• If a requirements file is not provided, solutions will be run on the most recent packages available.
• Custom packages in your submission notebook will not be accepted.
• You may only use tools available to everyone i.e. no paid services or free trials that require a credit card.

Consequences of breaking any rules of the competition or submission guidelines:

• First offence: No prizes or points for 6 months (probation period). If you are caught cheating, all individuals involved in cheating will be disqualified from the challenge(s) you were caught in and you will be disqualified from winning any competitions or Zindi points for the next six months.
• Second offence: Banned from the platform. If you are caught for a second time your Zindi account will be disabled and you will be disqualified from winning any competitions or Zindi points using any other account.
• Teams with individuals who are caught cheating will not be eligible to win prizes or points in the competition in which the cheating occurred, regardless of the individuals’ knowledge of or participation in the offence.
• Teams with individuals who have previously committed an offence will not be eligible for any prizes for any competitions during the 6-month probation period.

Monitoring of submissions

• We will review the top 20 solutions of every competition when the competition ends.

We reserve the right to request code from any user at any time during a challenge. You will have 24 hours to submit your code following the rules for code review (see above). Zindi reserves the right not to explain our reasons for requesting code.

If you do not submit your code within 24 hours you will be disqualified from winning any competitions or Zindi points for the next six months. If you fall under suspicion again and your code is requested and you fail to submit your code within 24 hours, your Zindi account will be disabled and you will be disqualified from winning any competitions or Zindi points with any other account.

The evaluation metric for this challenge is Root Mean Square Error.

Your submission file should look like:

client_id        target
test_Client_0    0.957
test_Client_1    0.996
test_Client_10   0.612

1st Place: 100 TND

Competition closes on 13 september 02:00 GMT

Final submissions must be received by 02:00 GMT

We reserve the right to update the contest timeline if necessary.