Documentation for the RoboTaxMaker service

Firstly, you need to register. Then you open the page with registration of RoboTaxMaker service, in the Prices section choose the required number of declarations (simple or ordinary depending on the number of transactions) and click on the Pay button.

For tax return generation, the choice of date range will depend on whether you will include the (T+) option when calculating taxes (by default it is enabled). If you choose the (T+) option, equity transactions executed on 30 December of the year preceding the reporting year will be counted on 1 January of the reporting year, and 31 December will be counted on 2 January. In turn, transactions in PFIs on 31 December of the reporting year will fall in the following year.
In addition, note that dividends are counted on a day-to-day basis, regardless of the choice of the (T+) setting.

So for the (T+) option and for a reporting year, e.g. 2020, the dates should be 30.12.2019 – 31.12.2020 inclusive.

For the option (T+) switched off and for the accounting year e.g. 2020, the dates must be 01.01.2020 – 31.12.2020 inclusive.

In some cases, it is not possible to select exactly these dates, so it is necessary to select the closest dates covering this period. If it turns out that the period exceeds 365 days (at the moment it is not possible to upload a report for a longer period), you can split it into 2 reports so that there is no overlap of dates (for example, the first report 30.12.2019 – 31.12.2019, then the second 01.01.2020 – 31.12.2020). In this
case, 2 reports are loaded into FinParser.

To generate a cash flow statement, in some cases a different date range may be used when uploading files.

First of all, only one report file should be used for each IB account. The date range regardless of the choice of option (T+) should ideally be, for example, for the 2020 tax year 01.01.2020 – 31.12.2020. If 01.01.2020 cannot be selected, then the closest available date after this date should be selected, e.g. 04.01.2020.

If the account was opened in the year for which the tax return is filed, the earliest available date should be selected as the start of the period.

Interactive Brokers uploads data on the date and amount of position opening if the position was partially or fully closed in the period being uploaded, even if it was opened in previous years (therefore it is not necessary to attach reports for all purchase years).
Freedom Finance – information about open positions in the report does not contain the date of position opening and lot sizes. This makes it impossible to build a tax return based on a report for one tax year. The lots closed in each particular transaction can be obtained only by analysing the history of transactions. Thus, in order to calculate the tax return for Freedom Finance, information for the entire trading history is required, starting from the moment of account opening (read more).

If you actually executed trades that closed positions during the reporting period, it means that you uploaded an Activity report instead of the expected Customer report. These reports represent the executed trades differently. For instructions on how to get the expected format, please refer to the corresponding help section → . Unfortunately, you will not be able to upload the correct report to the service now, as payment has already occurred for the previously uploaded Activity report.
This situation can be resolved privately. To do this, please write a message to the support email support@robotaxmaker.com with the login under which you are registered at robotaxmaker.com.

The following types of transactions are currently taken into account.

For Interactive Brokers:
Dividends (payments on ETFs) including taxes already withheld
Closing long positions
Closing short positions
Options transactions (including expiry)
Futures transactions
CFDs
Interest on balances
Bond coupons
Broker fees (inactivity fees, subscription to market data, etc.)
Warrants
Forex transactions
Corporate de

For Freedom Finance:

Dividends (payments on ETFs) including taxes already withheld
Closing long positions
Closing short positions
Transactions with IROs
Bond Coupons

List of currently supported currencies:

USD (US Dollar)
EUR (Euro)
GBP (Pound Sterling)
CHF (Swiss Franc)
JPY (Yen)
RUB (Russian Ruble)
DKK (Danish Krone)
AUD (Australian Dollar)
CAD (Canadian Dollar)
HKD (Hong Kong Dollar)
CZK (Czech Krone)
PLN (Polish zloty)
SEK (Swedish krona)
ZAR (South African rand)
TRY (Turkish lira)
SGD (Singapore dollar)
CNH (Chinese yuan)
NOK (Norwegian krone)
NZD (New Zealand dollar)
ILS (New Israeli shekel)
MXN (Mexican peso)

If the broker’s report for the declared year contains more than 1000 settlement transactions (transactions for closing positions, dividends, etc.), then when generating a file for the programme Declaration – DCX format (for example, for 2020 it is DCO), this programme will not be able to open the received DCX file and will generate the error of opening the file “Incorrect format of the declaration file, it may be corrupted” “. This is not an error of writing to the file by the service. You can try to manually enter the 1001st transaction through the Declaration programme itself and then save the result to DCX. When trying to open it, the same error will occur.
Solution: use grouping of transactions by days. All deals for each day of the year are grouped into one with indication of traded instruments. Thus, the maximum number of transactions with securities cannot exceed 365, similarly with derivative financial instruments.
For this purpose it is necessary to set the switch “Group by day” in the section “Additional parameters of calculation and commission” of the service when generating the DCX format.

If after clicking on the “Generate Reports” button nothing happens in response, neither the expected result nor an error, the first thing to do is to simply refresh the browser window (by F5).
It is possible that before generation the tab with the service was opened quite a long time ago (sometimes up to several days ago) and has not been refreshed since then. This may cause unsynchronisation of the server code and the code loaded in the user’s browser.

Check your spam folder or the promotions section in your mail.