How it works
Your statement, read properly.
TrakBuk does not connect to your bank. You bring the statement your bank already gives you, and it turns those rows into something you can actually read.
Export a statement from your bank
Most Nigerian banks let you download a statement from the app or internet banking, or email one on request. CSV and Excel are the most reliable. Text-based PDFs work too, as long as the text can be selected rather than scanned as an image.
Preview before anything is saved
TrakBuk reads the file and shows you what it found first: how many rows are new, how many are duplicates of something you already imported, the debit and credit totals, and the period covered. Nothing is written to your account until you confirm.
Review the categories it guessed
Every row gets a category. Anything TrakBuk could not place confidently is marked for review rather than filed silently under the wrong heading. Correcting one transaction can apply the same rule to similar ones.
What it accepts
CSV, Excel, and text-based PDF. Column names vary a lot between Nigerian banks, so TrakBuk matches on a list of known header spellings rather than expecting one fixed format — date, narration, debit, credit and balance columns are found under most of the names banks actually use.
Scanned or image-only PDFs will not work, because there is no text to read. OPay statements in PDF are refused outright with a note pointing you to the Excel export instead, rather than importing a mangled version of them. An import is capped at 5,000 rows, which covers a normal statement period comfortably.
Duplicates and overlapping periods
Statements overlap. If you pull March–May now and April–June next month, April and May appear in both files. Each row gets a fingerprint built from its date, amount, direction and narration, with a counter for genuinely repeated transactions on the same day, so importing the overlap again recognises what it has already seen instead of doubling your spending.
Checking the totals add up
Where a statement prints its own debit and credit totals, TrakBuk adds up the rows it parsed and compares. If they match, the import is marked reconciled. If they do not, it is flagged for review rather than presented as fact — usually a sign the file has a layout the parser has not seen before.
Money moving between your own accounts
Sending ₦50,000 from your savings to your current account is not income and not spending, but a naive tracker counts it as both. TrakBuk looks for transfers that appear to be between accounts you own and leaves them out of your income and spending figures, showing them separately instead. Because a guess can be wrong, each one is yours to confirm or reject.
Bank charges, added up
Stamp duty, commission, SMS alert fees, card maintenance, VAT on charges. Individually they are small enough to ignore; over a statement period they are often not. They are categorised as bank charges and totalled, so the number is in front of you rather than scattered across two hundred rows.
Where cash fits
A withdrawal shows on your statement as one line. What you actually did with that money does not. Cash tracking is kept deliberately separate so that recording those purchases does not count the same money twice. See how cash tracking works.