How can we help today?

Tag manually You can set a Field value anywhere you see the transaction: From a table. Each active Field has its own column in Cards, Banking, and Accounting. Select the cell, then pick an option or start typing to search. With permission, you can create a new option right from the picker From the details drawer. Open any transaction and set its Fields in the details panel. This works the same in the mobile app In a payment or invoice flow. Transfers, wires, checks, bills, and invoices carry the same Fields; set them during creation or afterward from the transaction's detailsLet cards do it automatically Give a card a default option for any Field (during card creation or in card settings). Every transaction on that card inherits the default automatically and shows an AUTO indicator. Anyone with edit permission can override it per transaction, and the override wins. Defaults are the recommended way to track spend by person or team: one setting per card, zero per-transaction work. Split a transaction across options Open the transaction's details and select Split transaction Add a line per portion and give each line an amount and an option. For example, a $5,600 bill can go $5,100 to Sales, $200 to Marketing, and $300 to Engineering under one Field Line amounts must add up to the transaction total Require a Field with expense policies Expense policy rules can require a Field to be set (for example, require Category on every card transaction over $50). Build this under your expense policy rules the same way you would require a receipt or note. Fields in exports and accounting Every transaction CSV export includes one column per active Field, and split transactions export one row per split line with its amount and option. Fields are also available in accounting mapping rules, so options can drive how transactions map to your general ledger.

Create a Field Go to Settings › Fields Select New field (or Use starter Category if you have no Fields yet and want the suggested set) Name the Field. Use the question you want answered on every transaction: Category, Project, Client Choose the input type: Predefined list (your team picks from options you define) or Free text (your team types a value per transaction, good for job numbers or client codes) For a predefined list, add your options. Type them one at a time, or paste comma-separated values to add several at once Your new Field appears immediately as a column on transaction tables and as a row in the transaction drawer. You can have up to 7 active Fields at a time. Add or edit options In Settings › Fields , open the Field Select Add value to append an option, or use the row actions to rename an option Users with the "edit field values" permission can also add a new option on the fly from any place they apply the Field, so the list can grow as your business does Renaming an option updates it everywhere it has been applied, including past transactions. Add options in bulk Type or paste comma-separated values into the option input and each one becomes its own option (for example: Marketing, Travel, Legal). Duplicates of existing options are skipped. Archive an option or a Field Archiving removes something from pickers going forward without touching history. Archive an option from its row in the Field editor. Past transactions keep the option; nobody can apply it to new ones Archive a Field from the Field's header row. Its column leaves your tables, and it stops counting toward the 7-Field limit If an expense policy rule requires a Field you archive, that requirement stops being enforceable, so review your expense policies after archiving.

Understanding Fields in Rho What makes up a Field Name. What the Field is called: Category, Project, Client, Job Number. This is the column header you will see on your transaction tables. Options. For a predefined-list Field, the set of choices your team picks from. You can add options one at a time, or in bulk by pasting comma-separated values into the option input. Input type. Predefined list (pick from options) or free text (type a value per transaction, useful for things like job numbers). Each transaction takes one option per Field. If one payment covers several things, you can split the transaction and give each portion its own option and amount. You can have up to 7 active Fields. Archived Fields do not count toward the limit, and archiving never deletes historical data. The starter Category Field New accounts start with a suggested Field named Category , pre-filled with 10 common options: Software & Subscriptions, AI & Compute, Marketing, Travel, Food & Meals, Office & Supplies, Equipment, Contractors, Legal, and Other. You can rename it, edit the options, or skip it and build your own. It exists so you can start tagging spend on day one without configuring anything. Where Fields appear Fields are available on every transaction type: card transactions, banking transactions, payments, bills, reimbursements, and invoices. They also live on cards, where a default option applies automatically to that card's transactions. Every transaction CSV export includes your Fields as columns. One deliberate exception: people. Fields apply to money movement, not to users, so you will not see Fields anywhere in user management. Your account does not include a Reporting tab. That tab houses the Departments and Labels pages used by longer-tenured accounts. Your spend views live directly on the transaction tables: one column per Field, filters by Field, and CSV export. Fields-native reporting views are on the roadmap. Fields and cards Every card can carry a default option for each Field. New transactions on that card inherit the default automatically and show an AUTO indicator until someone overrides them. This is the easiest way to track spend by person or team: give each teammate's card a default, and their spend rolls up with no per-transaction work. A note on card repayments Card repayments do not carry Fields. A repayment moves money from your account to pay your card balance; the spend itself was already categorized on the original card transactions, so categorizing the repayment would double-count it. Card purchase refunds do carry Fields. Who can do what Field access follows your role in Users › Roles: Permission What it allows View fields See Fields and applied options on transactions you have access to Edit field values Apply options to transactions and cards you have access to Manage field configuration Create, rename, and archive Fields and their options in Settings Related articles: How to Set Up and Manage Fields · How to Apply Fields to Transactions