A category answers "what did I spend money on?" A beneficiary answers "who did I pay?" Both matter, and they matter differently.
If your Housing category shows 3,600 AZN for the quarter, that is useful — it tells you housing is your largest expense class. But it does not tell you whether that 3,600 went to one landlord, or split across a landlord, a property management company, a maintenance contractor, and a utility provider. The category groups by type; the beneficiary groups by entity. When you combine both, your transaction history becomes something you can actually query with precision.
Veridian's beneficiary field is available on every transaction type — expense, income, and transfer — and is designed to add zero friction to the logging habit. Here is how it works and when to use it.
What a Beneficiary Is in Veridian
In Veridian, a beneficiary is a named payee entity attached to a transaction. It has three fields: a nickname (required), an optional first name, and an optional last name.
The nickname is the identifier that matters day-to-day — it appears in transaction lists, search results, and the beneficiary picker. Make it recognisable and unambiguous. "Kapital Bank Loan" is better than "the bank." "ABB Mortgage" and "ABB Car Loan" are better than "ABB" for two separate loan obligations at the same bank. If you pay multiple contractors, "Ahmad Contracting" and "Leyla Electrician" are clearer than "Contractor 1" and "Contractor 2."
The optional first name and last name fields let you store the person's full legal name separately from the nickname you use in daily searching. You might nickname a client "TechCorp Invoice" but store the actual contact name in the first and last name fields for reference.
Beneficiaries are reusable across all transactions once created. Create a beneficiary once, and it is available in the picker for every future expense, income entry, or transfer.
Adding a Beneficiary to a Transaction
The Beneficiary field appears in the Add Transaction modal — on the Expense, Income, and Transfer tabs alike. It is optional and positioned below the required fields (amount, date, account, category) so it does not add steps to a quick log.
When you tap the Beneficiary field, the picker opens with a live search. Two things happen here:
Selecting an existing beneficiary: begin typing a nickname or full name. Matching beneficiaries appear immediately as you type. Tap one to attach it. The search is live — no need to type the full name.
Creating a new beneficiary inline: type a name that does not match any existing beneficiary. As you type, if there is no match, a prompt appears to use the typed text as a new beneficiary. Select it. When you submit the transaction, Veridian creates the beneficiary automatically — no detour to a settings screen, no separate step.
This means the first time you pay your gym, type "CityFit Gym" in the beneficiary field, create it inline, and submit. Every payment to that gym afterward, select "CityFit Gym" from the picker in two taps.
The how to track expenses guide covers the full transaction modal in detail, including the note field which works alongside beneficiaries.
Why Inline Creation Matters for the Habit
The most common reason people stop tagging payees in expense apps is friction: to add a new payee, you have to leave the transaction form, go to a contacts or vendors screen, create the record, come back, and resume. By the time you complete that loop — or give up and skip it — you have either lost context or decided it is not worth the effort.
Veridian eliminates that loop. The entire cycle of recognising a new payee, naming them, creating them, and attaching them to the transaction happens without leaving the transaction form. It adds roughly one extra tap to a new-payee transaction and zero extra taps for a returning payee.
The practical result: the habit of attaching beneficiaries is maintainable. It does not require discipline beyond showing up to log the transaction — the creation step is just part of the form. After a few weeks, you will have a meaningful beneficiary library built up without deliberately setting one up.
When to Use a Beneficiary — and When to Skip It
The beneficiary field is optional by design. Not every transaction benefits from one, and forcing the field on every log would slow down the habit for no gain. Here is a practical framework for where beneficiaries add value.
Always worth tagging: your landlord or mortgage lender; any contractor or service provider you pay more than once; subscriptions tied to a specific company (gym membership, annual software license, insurance premium); family members you regularly send or receive money with; clients whose income payments you want to track separately.
Usually worth tagging: hotels, airlines, and car rental companies when logging travel expenses (a single search shows every payment to that entity across all trips); vendors you may need to reconcile later (a medical provider, a government fee, a professional services firm); any entity you might need to dispute a charge with.
Usually not worth tagging: one-off cash purchases (a market stall, a street vendor); daily commodity spending (coffee, lunch, a metro ride); grocery stores unless you specifically want to track per-store spending trends.
The test is simple: "Will I ever want to know how much I have paid this entity, or when, or how often?" If yes, tag it now. Future-you will appreciate the two seconds past-you spent on it.
Searching Transactions by Beneficiary
The Transactions tab has a free-text search field that queries four fields simultaneously: category name, account name, beneficiary nickname, and note text. Typing a beneficiary's nickname surfaces every transaction tagged to them — across all accounts, all time periods, all transaction types.
This is the most practical payoff of the beneficiary system:
- Type your landlord's nickname → every rent payment, across every month, in one list with running totals visible as you scroll.
- Type a freelance client's nickname → every income payment from them, separated from the rest of your income history.
- Type a hotel chain's name → every charge across all trips, consolidated.
- Type a contractor's nickname → every invoice payment, in date order, with any notes you attached.
The search is not scoped to a time period by default — it queries your entire transaction history. If you want to constrain results to a specific period, use the type filter tabs (All / Expenses / Income / Transfers) first to narrow the transaction type, then search. For pattern analysis across periods, the understanding spending reports guide explains how the Category Breakdown and Account Summary reports complement this kind of payee-level searching.
Beneficiaries on Income Transactions
The beneficiary field is not just for tracking who you pay — it also tracks who pays you.
If you do freelance work for multiple clients, attach the client as a beneficiary to each income transaction. Log the gross amount received, select the Income category that fits (Freelance, for most cases), and tag the client. After several months, a search on that client's nickname shows every payment they have made to you — dates, amounts, running total. At the end of a tax year, searching by client gives you the complete income record for that relationship without manual reconciliation.
The same logic applies to rental income if you have multiple tenants (tag each tenant as a beneficiary on their monthly income entry), to irregular bonus or commission payments (tag the employer or payor), or to recurring transfers from a family member (tag them as a beneficiary on the income side).
Beneficiaries on Transfers
Transfers between your own accounts typically do not need a beneficiary — moving money from your bank to your cash wallet is an internal movement with no external payee. But transfers to or from an external entity do benefit from one.
If you regularly send money to a family member by bank transfer, tag them as a beneficiary on the transfer. The transaction is still categorised as a Transfer, not an expense, which keeps your spending totals accurate — but the beneficiary tag means searching that person's name shows every transfer to them over time.
The same applies to regular payments made via transfer: recurring loan repayments sent to an individual, payments to an external savings pool, or money routed to a business account you manage separately.
The Note Field as a Complement
Beneficiary and note work together as two different kinds of context for the same transaction. The beneficiary is the repeatable identity — who this entity is. The note is the transaction-specific reason — why this particular payment happened.
A few examples of how they combine:
Beneficiary: "Kapital Bank Mortgage" / Note: "March instalment — payment ref 4412"
Beneficiary: "Ahmad Contracting" / Note: "Kitchen remodel — phase 2, per invoice #018"
Beneficiary: "TechCorp Ltd" / Note: "Freelance invoice #2026-04, paid 2 weeks early"
The beneficiary gets you to the right entity fast via search. The note answers the follow-up question: what was this specific transaction for? Together they turn a transaction entry from a number with a category into a legible record you can read back months later and immediately understand.
The note field accepts up to 1,000 characters, and notes are fully searchable in the Transactions tab. A specific enough note doubles as a filter — search "invoice #018" and the Ahmad Contracting phase 2 payment surfaces directly.
A Practical Example — Tracking a Landlord
Here is how the beneficiary system looks in practice over six months of rent payments.
Month one: add an Expense. Housing category. 1,200 AZN from your AZN bank account. Tap the Beneficiary field. Type "Ali Landlord." No existing beneficiary matches. Select "Use as new beneficiary." Submit. Ali Landlord is created and attached.
Month two: same transaction setup. Tap Beneficiary. Type "Ali." The picker immediately suggests "Ali Landlord." Tap it. Submit. Five seconds extra, total.
Repeat for months three through six.
Six months later: go to the Transactions tab. Search "Ali Landlord." Six Housing entries appear — each with its date, amount, and account. No filtering by date range, no export, no spreadsheet. The total of those six entries is your rent expenditure for the period.
Open the Category Breakdown report for the year. The Housing category total includes those six rent payments alongside any other housing expenses. Tap the Housing category to drill into the individual transactions — Ali Landlord's payments are distinct from any maintenance or utility charges you also logged to Housing. Without the beneficiary tag, the category total tells you housing cost X. With the tag, you can see exactly how much of X went to the landlord specifically.
That is the second dimension categories alone cannot give you — and it is available on every transaction type in Veridian, for the cost of one extra tap per recurring payee.
For travel scenarios where beneficiary tagging across hotels and vendors becomes especially useful, the travel expense tracking guide shows how this works across a multi-currency trip.
Join the Waitlist
Veridian's beneficiary system is built and working at launch — created inline, searchable instantly, available on every transaction type. iOS and Android, coming soon. Join the waitlist to be first in.