Skip to content
vokse.

Bringing it with you

Your history arrives intact.

Years of numbers should not be the reason you stay where you are. Bring a file from your bank, or a whole budget from YNAB, and read what will happen before anything is written.

Start freeSee the comparison
The import screen in vokse, with the prepared file ready to review
The prepared import, before a single row is written

Upload, read, done.

Three moves, and the middle one is the point: nothing enters your household until you have seen it.

  1. Upload the file

    A CSV, OFX or JSON export from your bank, or your YNAB budget by file or by connecting the account.

  2. Read what will happen

    vokse prepares the import and shows it back: which accounts it found, which payees it recognised, what it will create and what it will skip.

  3. Confirm, and it lands

    Only then do the rows arrive, dated and categorised. Send the same file twice and the second one changes nothing.

The shop becomes a name you recognise.

A bank line reads like a receipt printer wrote it. On the way in, vokse turns it into the payee you already know, and remembers the spelling for next time.

  • One name, many spellings

    The same shop written four ways lands on one payee, and the other spellings stay attached to it.

  • Your rules start working

    Because imported lines carry a real payee, the rules you wrote for it file them from day one.

  • Written down, not guessed at

    Every payee vokse creates while importing is recorded, so you can see later where a name came from.

vokse next to YNAB, row by row
The payees screen in vokse, with merchants grouped under the names people use

What each source can carry.

Different exports hold different things. This is what actually survives the trip, not what we wish it did.

  1. YNAB

    By file or by connecting the account

    Categories
    Comes across
    Payees
    Comes across
    Transfers
    Comes across
    Flags
    Comes across
    Receipts
    Does not come across

  2. CSV file

    Categories
    Does not come across
    Payees
    Comes across
    Transfers
    Card payments pair up
    Flags
    Does not come across
    Receipts
    Does not come across

  3. OFX file

    Categories
    Does not come across
    Payees
    Comes across
    Transfers
    Card payments pair up
    Flags
    Does not come across
    Receipts
    Does not come across

  4. JSON file

    Categories
    Does not come across
    Payees
    Comes across
    Transfers
    Card payments pair up
    Flags
    Does not come across
    Receipts
    Does not come across

  5. Bank connection

    Ongoing, once a bank is linked

    Categories
    Through your rules
    Payees
    Comes across
    Transfers
    Card payments pair up
    Flags
    Does not come across
    Receipts
    Does not come across

Receipts are never in an export: you attach them afterwards, from a photo or from the tray.

Nothing lost, nothing doubled.

The awkward parts of a migration, handled before you notice them.

  • Nothing lands unread

    The prepared import is a proposal. Until you accept it, your household is exactly as you left it.

  • The same file twice is still one import

    Rows already in your household are recognised as such instead of arriving again.

  • Your own rows keep their place

    When the bank later sends a payment you had already typed, the two become one row rather than two.

  • Old pending rows are swept up

    A hand-typed row still waiting on a bank-fed account after two weeks is pointed out, not left to rot.

Keep exploring

Bring the last few years with you.

Start with a file or a bank connection, read the proposal, and keep the history you already wrote.

Start free