Yes, you can do this with a file. When transactions already in PayHOA are missing a category, a vendor or a memo, export them, fill in the gaps in a spreadsheet and import the file. The import adds to the transactions you have and doesn't make copies of them, provided PayHOA recognizes each row by its date, amount and description. You only need those columns, the bank account and the columns you're adding. A blank cell leaves the transaction as it is.
Tip: To give many transactions the same category, you don't need a file. Tick them on Transactions and use the Actions menu. See Review many at once.
Assigning a vendor to many transactions at once (bulk or mass-assign). The Actions menu on Transactions has no bulk action for vendors or memos, so a file is the way to assign a vendor to many transactions in one go: put the vendor's name in the Vendor column on each row. A transaction rule isn't a substitute for transactions you've already approved. When you save a rule it's applied to transactions waiting on For review that have no category yet, and a rule adds its vendor only to the transactions it categorizes. See How rules work.
What you need in the file
The smallest file that works has five columns: the four that identify the transaction, and one you're adding.
Transaction Date | Description | Amount | Bank Account | Category | Vendor | Memo |
03/04/2026 | CHECK 1042 | 480.00 | Operating Checking | Landscaping | Greenway Lawn Care | Check 1042 |
03/09/2026 | ACH PMT BLUEGRASS ELECTRIC | 212.37 | Operating Checking | Utilities | ||
03/15/2026 | INTEREST PAID | -1.23 | Reserve Savings | Interest Income |
Transaction Date, Amount and Description identify the transaction. Keep them exactly as PayHOA has them, minus signs included.
Bank Account is required on every row, and must be the account the transaction is in.
Add Category, Vendor or Memo, whichever you need.
Start from PayHOA's own export to get these right: Transactions → Actions → Export CSV. It holds the rows on the page, or the ones you ticked, and the columns that are showing. Steps 2 to 4 make it ready to import. Its Type column can stay or go. Without it, PayHOA tells money in from the minus sign, and the mapping screen shows a Type (Income/Expense) column it worked out for you.
Steps
Export the transactions you're filling in, for example Filters → Status → Uncategorized. First click Columns and turn on Vendor and Memo if you're adding them. Keep a spare copy. See Export.
Fix the headings. Rename Date to Transaction Date and Account to Bank Account. Delete the Reviewed column.
Delete the rows you aren't adding to, and every transfer, split transaction, deposit of owners' payments, bill payment and journal entry. Change those one at a time in PayHOA.
Empty the placeholders. The export writes
--for no vendor or memo and Uncategorized for no category. Clear each one you aren't typing over.Type what you're adding in Category, Vendor and Memo. Copy category and vendor names exactly as PayHOA shows them. Change nothing else.
Save the file as CSV and upload it at Transactions → Actions → Import transactions. Only an Admin can open it. On Verify transaction types, choose Yes, looks correct. Never choose the swap.
On Edit mapped transaction data, check every row as described below.
Click Start import. It runs at once, with no confirmation. Import complete shows one card, Transactions updated. Its number counts every row in your file, including the ones that read No changes. Open a few transactions to check.
What you'll see before you import
Updating is what you want. Each cell you filled in has an orange info icon, whether it's a category, a vendor or a memo. Point to it: Previous value: (blank) means the transaction had nothing there. Any other value is about to be replaced.
No changes means the transaction already has what's in the row. A row you left as exported, with its placeholders emptied, reads No changes.
New means PayHOA didn't recognize the row, and importing adds a second transaction. Click Upload different file and correct the row.
A warning triangle means the row won't be imported. Point to it to see why.
A list icon with a plus in Category or Vendor means PayHOA will create a new one: New category "Utilites" will be added. The icon doesn't show what the transaction has now. Correct the name in your file, or click the X beside it to clear the cell.
Check the name shown in each cell you filled. The AI Assistant can pick a close name of yours in place of the one you typed. If it's wrong, click the X (Don't apply this update).
What gets added, and what doesn't
Case | What happens |
No category, vendor or memo yet | The file's value is added. |
A different one already | Replaced by the file's value. To fill gaps without overwriting, leave filled cells as exported, or click the X (Don't apply this update) before you import. |
A blank cell, or a column or transaction that isn't in the file | Left alone. An import never clears anything. |
Approval | Not changed. A transaction on For review stays there until you approve it. On an approved one, your books move to the new category as soon as the import finishes. |
Excluded or reconciled transactions | Stay as they are, with the added details. |
Transaction rules aren't run. A file can't change a date or an amount, reword a description, or approve anything; see Review and categorize transactions.
Watch out for
Warning: A row that isn't recognized reads New and is added as a second transaction. Keep the date, amount and description exactly as exported. If two transactions share all three, both rows change the same one; fill those in by hand.
Warning: Keep the bank account as exported. PayHOA finds the transaction in any account, then moves it to the account in the row, and an approved transaction moves without its entry in your books. An orange icon in Bank Account is the sign. See Check before you import.
Important: A name PayHOA can't match becomes a new category or vendor, and a -- left under Vendor becomes a vendor named --, which replaces any vendor the transaction has. An Uncategorized left under Category is read as a name too: PayHOA puts the closest category name you have on those transactions (for example, one called Uncategorized Charges). A Categories created or Vendors created card on Import complete means some were made.
Warning: There's no undo. Approved and reconciled transactions aren't protected, and the mapping screen doesn't say which rows are approved: a new category on an approved transaction changes your reports for that period straight away. Keep your spare copy.
Common questions
My bank transactions are already in PayHOA. Can I categorize them in a spreadsheet and import it? Yes, if you're an Admin. Export them with Transactions → Actions → Export CSV, type a category on each row, and import the file with Actions → Import transactions. A row that matches a transaction by date, amount and description adds the category to it; no second transaction is made. The export needs a few changes before you import it; see Steps.
Will it create duplicates? Not if the date, amount and description in each row are as exported. Those rows read Updating or No changes. A row that reads New would be added as a second transaction, so correct it before you click Start import.
Do I have to include every column again? No. Each row needs Transaction Date, Description, Amount and Bank Account, plus the column you're adding: Category, Vendor or Memo. A column that isn't in the file is left as it is on every transaction.
Some already have a category. Will the file overwrite it? Only where the file has a different category in that cell. A blank cell, or one left as exported, changes nothing. You can also click the X (Don't apply this update) beside a change before you import.
Does adding a category this way approve the transaction? No. A transaction on For review stays there with its new category until you approve it. An approved one stays approved, and your reports show it under the new category straight away. On the general ledger the move appears as a Recategorized transaction line.
Related
Import transactions from a file: every screen, column and message

