Brokers

BUX Zero portfolio tracker: benchmark your BUX Zero portfolio against the S&P 500

We read a BUX Zero transaction export and turn the many small orders in it into one history with a return you can compare. The file is picked up by our BUX profile, which looks for the transaction time, the transaction category and the asset name among the headings. That profile is built on the documented layout rather than on a large pile of real files, so the first import is worth one comparison against what the app shows you.

What the file contains

The export is a single flat table of events. Each row carries the time of the transaction, a category saying what happened, the name of the asset and its identifier, the number of units and the amount of money involved together with its currency. Because the identifier field holds an ISIN, holdings are matched on the instrument rather than on a name that can be rewritten.

Two features of an app broker file shape the arithmetic. Quantities are fractional, often to four decimal places or more, so a position is rarely a round number of shares. And orders are many and small, because a monthly habit produces a long file. Both turn into advantages once the file is loaded: fractions keep the position exact, and every dated purchase adds another point to the cash flow timeline the index comparison replays.

The export comes as CSV or XLSX, and we read the file as it is: no renaming, no reformatting, no cleaning up in a spreadsheet first. The columns we look for in this export are Transaction Time (CET), Transaction Category, Asset Name, Asset Id, Asset Amount, Transaction Amount and Transaction Currency.

How the import works for BUX Zero

BUX Zero is recognised through a column profile: we know the header names its export uses. That profile follows the documented format rather than a large set of real files, so if a header has been renamed you point at the column once and we save the mapping.

Our BUX export guide points to the documents, statements or reports area of the app, and to a machine readable export in preference to a statement as PDF. The full route is in our BUX Zero export guide.

Take the whole period and check the categories. A history that begins halfway leaves sales with no matching purchase, and the cost basis that follows is wrong in a way that looks entirely reasonable on screen. It is also worth confirming that dividend credits are inside what you downloaded, because a file of orders alone understates your return permanently rather than temporarily. If you have used more than one product under the same brand over the years, treat each one as an account of its own, export both and upload them together.

What to watch for with BUX Zero files

Fractional quantities. Positions in this file are rarely whole shares, and a quantity such as 2.4137 is ordinary. The decimals are kept exactly as they are, because trimming one changes the holding by a real amount.

A time, not only a date. The transaction time is recorded to the minute in central European time. Only the date is used for the return, but the time is what lets two orders on the same day be told apart.

Currency on every row. Each row carries the currency of its own amount, so a transaction settled in something other than euros is not quietly treated as euros.

Statements are not data. Monthly statements as PDF are a record of what happened rather than a table. Where a machine readable export exists anywhere in the app, that is the file to upload instead.

What you see after the upload

Your file becomes a verdict first: your time-weighted return next to the S&P 500 and the Nasdaq 100 over the same period, with your own deposits replayed into the index so both sides carry the same timing. Under it sit your positions with their cost basis, the dividends you received and the income your holdings are expected to pay, your allocation across positions and currencies, and a year report you can keep for your records.

With a BUX Zero history loaded, the dividend view usually looks different from the app, because payments spread thinly across a year are hard to add up on a phone screen.

You can look at all of that on the demo portfolio before you upload anything of your own. The first two weeks are free and no card is asked for.

Frequently asked questions

Which file does the profile recognise? A transaction export whose headings include the transaction time, the transaction category and the asset name. When those are present the columns are read without asking you anything. If your file has another layout, nothing is lost: you assign the columns once and the assignment is stored for later uploads from the same broker.

Why does the first import need checking? Because this profile is based on the documented format rather than on a large collection of real user files. It is deliberately cautious: when the headings do not match, the file falls through instead of being read wrongly. Comparing the resulting positions with the app once tells you whether the match was right, and a mismatch is worth reporting to us.

Can I upload PDF statements instead? Not usefully. A statement is a rendered document and the numbers in it cannot be recalculated without guessing at the structure. Where a spreadsheet or comma separated export exists anywhere in the app, that is the one to take, and it also saves you from collecting twelve documents every year.

Do fractional shares confuse the return? No, as long as the file keeps them intact. Fractions are treated as ordinary quantities and the cost basis works from the amount paid rather than from a whole number of shares. The failure mode here is human: opening the file, rounding a quantity for tidiness and saving it before the upload.