The importer does two jobs:
It adds transactions. Bring a batch of bank transactions into PayHOA from a spreadsheet: for example, a year of history for an account that isn't linked to your bank, or a month your bank feed missed. New transactions arrive on For review, where you check and approve them like any others.
It updates transactions you already have. Export your transactions, fill in or change the category, vendor or memo in a spreadsheet, and import the file to change them all in one go. A row that matches a transaction already in PayHOA changes that transaction instead of adding a second one. See Update existing transactions with the importer.
Either way, PayHOA reads your file, matches each column to a transaction field, and shows you every row, marked New, Updating or No changes, before anything is saved.
Use something else for:
An account that's linked to your bank. Its transactions arrive on their own. See Connect and manage bank accounts.
One or two transactions. Add them by hand, or open them and edit them. See Add a transaction or journal entry by hand and Review and categorize transactions.
Owners' payments. A deposit you import here isn't applied to anyone's account. Use Import payments from a file or record the payments, then link them to the deposit. See Link owner payments to deposits.
The list of categories itself, or starting balances. See Import the chart of accounts.
Before you start
Who can use it | An Admin of the association. Someone on custom permissions can't run this importer, even with Write on Transactions. They see Import transactions in the menu, but PayHOA sends them back to the dashboard with You are not authorized to view the requested page. See Give board members and staff access. |
Where it is | Transactions in the left menu → Actions → Import transactions. |
File types | CSV, XLS or XLSX. PDFs aren't accepted. |
File size | Up to 10 MB. There's no separate limit on the number of rows. |
Sample file | Yes. On the Import Transactions page, click Download the sample file. |
Bank accounts | Every bank account named in your file must already exist in PayHOA. The importer never creates bank accounts. |
AI | PayHOA's AI Assistant reads your column headers and the first rows to match columns to fields. It also matches the category, vendor and bank account names in your file to the ones you already have. It can get a match wrong, so you check every match on the mapping screen before you import. |
What it creates | New transactions. New categories and new vendors, when a name in your file doesn't match one you have. |
What it updates | A row that matches a transaction already in PayHOA (same date, same amount, same or very similar description) updates that transaction instead of adding a second one. The category, vendor, memo, description and bank account are set from your file. See Update existing transactions with the importer. |
What it leaves out | Rows with a problem, such as a bank account PayHOA can't match or a date it can't read. They're listed for you. |
Emails and charges | Nothing is sent to owners or vendors, and nothing is billed. PayHOA emails you, the person who ran the import, a summary titled Transactions Import Complete. |
Undo | There's no undo button. You can delete the imported transactions afterwards. A transaction that was updated keeps its new values, so save a copy of your export before you update. See "After the import" below. |
Your file
Start from the sample file, or use your bank's export. The first row must hold the column names. Your headers don't have to match the sample: PayHOA matches columns by their name and contents, and you can change any match before you import.
Columns
Field on the mapping screen | Sample file header | Required? | What to put in it | Example | If it's blank or wrong |
Transaction Date | Transaction Date | Yes | The date the transaction posted. Accepted: 01/15/2024, 1/15/24, 2024-01-15, 01-15-2024, Jan 15, 2024, 15 Jan 2024. When a date could be read two ways, the month comes first: 03/04/2024 is March 4. The year must be 1900 or later. | 01/15/2024 | The row isn't imported: Transaction date is required. or Transaction date could not be parsed. |
Description | Description | Yes | What the transaction was. Up to 255 characters. | Landscaping Services - January | The row isn't imported: Description is required. or Description is 300 characters. It must be 255 characters or fewer. |
Amount | Amount | Yes | A number. PayHOA understands 1250.00, $1,250.00, -25.50, (25.50), 25.50-, 25.50 CR and 25.50 DR. See "Money in or money out?" below. | 1250.00 | The row isn't imported: Amount is required. or Amount could not be parsed. |
Bank Account | Bank Account | Yes | The Bank account name exactly as it appears in PayHOA (capitalization doesn't matter), or the last four digits of the account number if PayHOA has it, such as ...1234. | Operating Checking | The row isn't imported: Bank account is required. or No matching bank account found. Bank accounts are not created by the transaction importer. |
Type (Income/Expense) | Type | No | Income or Expense. PayHOA also understands Credit, Deposit, In, Receipt and CR as income, and Debit, Payment, Out, Withdrawal and DR as expense. | Expense | Blank, or any other word: PayHOA uses the sign of the amount instead. |
Category | Category | No | The name of an income or expense category in your chart of accounts. | Utilities | Blank: the transaction comes in with no category. No match: PayHOA creates a new category with that name. |
Vendor | Vendor | No | The vendor's name. | Duke Energy | Blank: no vendor. No match: PayHOA creates a new vendor with that name. A new vendor's name can be 40 characters at most; longer, and the row isn't imported. |
Memo | Memo | No | A note. Up to 255 characters. A good place for a check number. | Check 1001 | Blank: no memo. Too long: the row isn't imported: Memo is 300 characters. It must be 255 characters or fewer. |
Any other column in your file, such as a running balance or a reference number, is left out. There are no custom fields for transactions.
Money in or money out?
PayHOA decides whether each row is income or an expense like this:
Your file has a Type column. The type decides. The sign of the amount is ignored, so 350.00 with Income is money in.
Your file has no Type column. The sign decides: a negative amount is Income (money in) and a positive amount is an Expense (money out). Many bank exports do the opposite and show deposits as positive. That's what the Verify transaction types step is for: it shows you a few rows, and you can swap income and expense for the whole file in one click.
Your file has separate debit and credit columns. Combine them before you upload. The importer takes one Amount column; it doesn't work out the direction from which column a number is in. If you upload the file as it is, PayHOA matches both columns to Amount, but it doesn't combine them: the rows with a debit come in as Expense, and the rows with only a credit are left out with missing required field: Amount. (Verify transaction types shows every row as Expense before that.) The simplest fix is to make one Amount column and add a Type column that says Expense on the rows from the debit column and Income on the rows from the credit column.
Rules for the whole file
One row is one transaction in one bank account. You can mix several bank accounts in one file, as long as each row names its account.
The header row comes first. Delete any title lines, account details or blank rows above it. If your file has no header row at all, clear My file has headers when you upload; the columns are then called Column 1, Column 2 and so on.
Excel files: PayHOA reads one worksheet, the one that was open when the file was last saved.
One column per field. Each field takes one column, and each column feeds one field. (A file with separate debit and credit columns is the one case where PayHOA matches two columns to the same field, and it doesn't work; see "Money in or money out?" above.)
No transfers. A transfer between two of your accounts comes in as two ordinary transactions, one per account. Turn them into a transfer afterwards. See Record transfers between accounts.
No splits, attachments or check images. Add those to the transaction afterwards.
Check numbers have no field of their own. Map that column to Memo, or leave it out.
How PayHOA matches what you already have
Bank accounts are matched by name, or by the last four digits of the account number. The AI Assistant may also match a close name, such as Operating to Main Operating Account. If nothing matches, the row can't be imported.
Categories and vendors are matched by name (capitalization doesn't matter). The AI Assistant may also match a name that means the same thing, such as Electric to your Utilities category, or ABC Landscaping LLC to your vendor ABC Landscaping. The mapping screen marks every matched name, exact or close, with a green icon so you can reject it. If nothing matches, PayHOA creates a new category or vendor. A new category is an income category when only income rows use it, and an expense category otherwise.
Transactions already in PayHOA are matched on three things together: the same date, the same amount, and the same description (or one that's about three-quarters the same, when no other transaction on that date and amount is as close). PayHOA looks across all your bank accounts, including transactions that came from a linked bank, ones you've approved and ones you've excluded. A matching row updates that transaction instead of adding a duplicate.
That last rule is what lets you update transactions on purpose; see Update existing transactions with the importer. It's also the only protection against duplicates, and it's partial:
If a linked account already brought in the same transaction with a different description, the row doesn't match, and you get a duplicate. Bank feeds often word descriptions differently from a downloaded file.
Two identical rows in the same file both come in.
A transaction you deleted isn't matched, so its row comes in as new.
Importing the same file twice doesn't duplicate anything: the second time, every row matches the first import and shows No changes.
Important: Don't import a period that a linked account has already brought in. If you must fill a gap, cut the file down to the missing dates first.
Tip: Leave out transactions dated on or before the account's Balance as of date. They're already part of its Starting Balance, so importing them counts them twice. See Transactions: common questions.
Update existing transactions with the importer
The importer isn't only for new transactions. When a row in your file matches a transaction that's already in PayHOA, importing it changes that transaction. So you can export your transactions, edit them in a spreadsheet, and import the file to change them all at once.
When to use it
Categorizing a backlog. Export a few hundred uncategorized transactions, type a category on each row, and import the file.
Adding vendors or memos in bulk. For example, put the vendor on a year of utility payments, or a check number in each memo.
Small corrections to descriptions, such as a typo. A description you rewrite completely no longer matches; see "How PayHOA decides a row is an update" below.
Use it for the Category, Vendor and Memo columns. It can't change a date or an amount.
Only filling in what's missing? For a short recipe, see Add categories, vendors or memos to transactions from a file.
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 and categorize transactions.
Steps
Find the transactions. On Transactions, pick the bank account and the tab, then narrow the list to the ones you want to change: type part of the description in the Search box, or use Filters, for example Status → Uncategorized. A transaction you've deleted can't be updated this way: the Transactions page has no list of deleted transactions to export, and a deleted transaction is never matched, so a row for one would be added as a new transaction.
Show the columns you need. Click Columns. Keep Date, Description, Amount, Category and Bank Account showing. Turn on Vendor and Memo if you want to change them. They're hidden to start with, and the export only holds the columns that are showing.
Export. Raise Items per page at the bottom of the list, up to 1000, so the transactions are all on one page. Then click Actions → Export CSV. If you tick some rows first, only those are exported, and the menu shows how many: Actions (8) → Export CSV (8). A green message confirms it, such as Exported 8 row(s) to CSV., and your browser saves a file named transactions_ followed by today's date. If you have more than 1000, export and import one page at a time. See Find, filter and export transactions.
Save a copy of the export and leave it alone. It's your record of how things were. Work in a second copy.
Get the file ready for the importer. The export can't be imported exactly as it is, because of the placeholder values described in step 6. Its header row reads Date, Description, Type, Amount, Category, Account, Vendor, Memo, Reviewed. (Vendor and Memo are there only if you turned them on. Reviewed is always there, even when that column is switched off.) In a spreadsheet:
Rename the header Date to Transaction Date, and Account to Bank Account. If you upload an export without renaming them, PayHOA usually still matches Date to Transaction Date and Account to Bank Account. But the AI Assistant does that matching, and the sample file's names leave it nothing to guess. Leave the headers Description, Type, Amount, Category, Vendor and Memo as they are. The Type column's expense and revenue are understood as they are: revenue is read as income.
Delete the Reviewed column, and the BillPayment column if it's there. (If you leave Reviewed in, it appears on the mapping screen with nothing chosen in its list, and it isn't imported.)
Delete the rows you aren't changing. Always delete the rows for transfers, split transactions, deposits of owners' payments, bill payments and journal entries. The importer doesn't leave these out for you, and for some of them the Category cell isn't a real category (a transfer's reads Transfer to …). Change those one at a time in PayHOA.
Make your changes in the Category, Vendor and Memo columns only.
Type category and vendor names as they appear in PayHOA, including the number in front if your categories have one, such as 4010 - Assessments / Dues. A name PayHOA can't match becomes a new category or a new vendor.
Empty every cell that holds
--, and every Category cell that holds Uncategorized, unless you're typing a real value over it. The export writes these where a transaction has nothing. Left in, PayHOA reads them as real values. It would create a vendor named -- and put it on every one of those transactions, and set the memo to --. For Uncategorized it picks the closest category name you have (for example, a category called Uncategorized Charges), or creates a category named Uncategorized if nothing is close.A category that Gable has only suggested (the one with a sparkle icon and an AI confidence percentage on For review) isn't on the transaction yet. The export shows Uncategorized for it. Empty the cell to leave the suggestion as it is, or type the category you want.
Leave Transaction Date, Description, Amount, Type and Bank Account exactly as they were exported. PayHOA uses the date, the amount and the description to recognize each transaction, and every row must name its bank account.
Upload the file. Save it as CSV, open the importer and upload it. See 1. Open the importer and 2. Import Transactions: upload your file.
On Verify transaction types, the rows your export calls expense show an expense badge and the ones it calls revenue show an income badge. Money in keeps the minus sign the export gave it, such as -1.23. Choose Yes, looks correct, then click Continue. Don't choose the swap. It reverses every amount, and then no row matches.
On Edit mapped transaction data, check the field above each column, especially Bank Account and Memo.
Check that every row reads Updating, and none reads New. The summary line counts them, such as 9 records will be imported • 2 new • 4 updating • 3 no changes, and the New, Updating and No changes buttons above the table show each kind on its own. No changes is fine: that row is already the same. A New row was not recognized, and importing it adds a second copy of the transaction. If you see one, don't import. Click Upload different file, fix the file and upload it again.
Check the changes. Click Updating to see those rows on their own. Each cell that will change has an orange info icon (Value updated in the legend under the table). Point to it to see what's there now, such as Previous value: 4010 - Assessments / Dues, or Previous value: (blank) when the transaction has nothing in that field. To leave one cell out of the update, click the X beside it (Don't apply this update). The orange icon is replaced by a curved arrow. The cell goes on showing the value from your file, but that value isn't saved: when you import, the transaction keeps what it has now. If that was the only change on the row, the row changes to No changes and the counts at the top change with it. Click the curved arrow (Undo) to put the change back.
Look for the list icon with a plus in the Category and Vendor columns. It means PayHOA will create a new category or vendor (point to it: New vendor "--" will be added), which in an update file is usually a typing mistake or a
--you didn't empty. Fix the file and upload it again, or click the X (Don't create this vendor) to clear the value on that row.Click Start import. There's no "are you sure" step. Import complete shows one card, Transactions updated, with the number of rows that matched a transaction. That number counts every row in the file, including the ones that read No changes, so it can be higher than the number of transactions that changed. For example, a file of four rows (two Updating, two No changes) ends with Transactions updated 4.
Check the result. Go back to Transactions, find the transactions again, and look at a few. Each one is on the tab it was on before, with its new values.
If you upload the export without getting it ready. Here is what the mapping screen can show for an export of eight transactions, uploaded as it is: six of the eight rows read Updating although nothing has been edited. Every -- in the Vendor column has the list icon with a plus (New vendor "--" will be added), the Uncategorized cells have become the closest category name, such as Uncategorized Charges, and a -- memo is marked as a change. Importing that file would put a vendor named -- on six transactions. A placeholder also replaces a value that's already there: on the mapping screen, Uncategorized is set to replace a category a transaction already has (Previous value shows it), and -- is set to replace an existing vendor, with only the new-vendor icon to show for it. Click Upload different file, clean the file as in step 6, and upload it again.
If you import the same file a second time, every row reads No changes and nothing is added or changed. Uploading your own file twice by accident is harmless.
How PayHOA decides a row is an update
For each row in your file, in this order:
PayHOA finds the transactions in your association with the same date and the same amount, in the same direction (money in or money out). It looks in every bank account and on every tab: For review, Reviewed and Excluded all count. Deleted transactions are left out. The bank account in the row plays no part.
Of those, it takes one whose description is the same as the row's. Capital letters and extra spaces are ignored.
If none is the same, it scores each description from 0 to 100 on how much of the text is the same as the row's. It takes the closest one if that scores 75 or more and no other transaction comes within 15 points of it.
If nothing qualifies, the row is New.
For example, PayHOA has an expense of 1,250.00 on 01/15/2024 described as Landscaping Services - January:
Row in your file | Result |
01/15/2024, 1250.00, LANDSCAPING SERVICES - JANUARY | Matches. Only the capitals differ. |
01/15/2024, 1250.00, Landscaping Service - January | Matches, because the description is close enough. The description is replaced with the file's wording. |
01/15/2024, 1250.00, January mowing contract | Doesn't match. The row is New, and importing it adds a second transaction. |
01/16/2024, or 1205.00, with the original description | Doesn't match. The row is New. |
So the date and the amount can never be changed by an import, and the description only slightly.
What an update changes, and what it leaves alone
On the transaction | What an update does |
Category | Replaced with the category in your file. A name that matches none of your categories creates a new category. |
Vendor | Replaced with the vendor in your file. A name that matches none of your vendors creates a new vendor. |
Memo | Replaced with the memo in your file. |
Description | Replaced with the file's wording. This only happens when the wording is still close enough to match. |
Bank Account | Replaced: the transaction moves to the bank account named in your file. With an exported file the account is the same, so nothing moves. If the transaction is approved, only the transaction moves. Its entry in your books stays in the old account; see the warning under Check before you import. |
Date, Amount and whether it's income or an expense | Stay as they are. A row only matches when these are the same. |
Approved or not, excluded or not, reconciled or not | Never changed by an import. The transaction stays on the tab it was on. |
Attachments, splits, linked owner payments and transfers | Never changed by an import. |
A blank cell never clears anything. A blank Category, Vendor or Memo leaves the value the transaction already has. (Bank Account can't be blank.)
Approval and rules. An update doesn't approve a transaction, and it doesn't un-approve one. A transaction on For review stays there with its new category, waiting for you to approve it. A transaction on Reviewed stays approved, and your books and reports move to the new category as soon as the import finishes, with nothing else to click. On the general ledger the move shows as a Recategorized transaction line, dated the same day as the transaction. Your transaction rules aren't run on an updated transaction; they run when a transaction first arrives.
What you can't update this way
The date or the amount. A row with a different date or amount doesn't match, so it's added as a new transaction. Open the transaction and edit it. See Review and categorize transactions.
A description you want to reword. Small corrections go through; a new wording doesn't match. Edit the transaction instead.
Emptying a field. A blank cell keeps what's there. To remove a category, vendor or memo, edit the transaction.
Approving, excluding or deleting. See Review and categorize transactions and Exclude, delete or fix duplicate transactions.
Transfers, split transactions, deposits of owners' payments, bill payments and journal entries. Change these one at a time. See Record transfers between accounts, Split a transaction and Link owner payments to deposits.
Two transactions with the same date, amount and description. PayHOA can't tell them apart, so both rows update the same one. Change those by hand.
Moving an approved transaction to another bank account. The importer moves the transaction but leaves its entry in your books in the old account. Open the transaction and change the account there, so your books are updated with it. See the warning under "Check before you import" below.
The categories and vendors themselves, such as their names or details. See Import the chart of accounts and Import vendors.
Check before you import
Warning: There's no undo. An updated transaction keeps its new values, and PayHOA doesn't store the old ones. Keep the untouched copy of your export. Preparing and importing that copy in the same way puts back the categories, vendors and memos it holds, but it can't empty a field that was empty before.
Warning: Approved and reconciled transactions aren't protected. An Updating row changes them like any other, the mapping screen doesn't say which rows are approved, and a new category on an approved transaction changes your reports for that period straight away. Don't run an update over a period you've already reconciled or reported on unless you mean to.
Warning: Don't use an import to move an approved transaction to another bank account. The transaction moves, but your books don't. On Transactions it shows under the new account, while the Account register report and each account's Ledger balance still count it in the old one. PayHOA doesn't warn you: the row reads Updating like any other, with an orange icon in the Bank Account column. Move an approved transaction by hand instead: open it and change the Account there. If an import has already moved one, import that row again with the original bank account to put it back.
Important: A row can match a transaction in a different bank account, because the bank account plays no part in matching. Say your operating and reserve accounts each have a Service Charge of 5.00 on the same date. Both rows in your file match the same one of the two, and the row that names the other account moves it there. On each Updating row, look for an orange icon in the Bank Account column. If you didn't mean to move that transaction, take the row out of your file and upload the file again.
Important: Changing a column's field on the mapping screen doesn't re-check which rows are New and which are Updating. PayHOA decides that once, when it reads the file. If a column was matched to the wrong field, don't correct it on the screen. Click Upload different file, fix the header in your file (use the names in step 5) and upload it again.
Important: If the same category name is spelled two ways in your file, or differently from PayHOA, you get new categories. After the import, check your chart of accounts for categories you didn't expect. See Add, edit, nest, delete and restore categories.
The import, screen by screen
1. Open the importer
What you see. The Transactions page. In the Actions menu, below Export CSV, is Import transactions. When a tab has no transactions to show, the empty page (Waiting for new transactions) also has an Import transactions button.
What to do.
Click Transactions in the left menu.
Click Actions → Import transactions.
What happens next. The Import Transactions page opens. A progress line at the top shows the three steps: Upload, Mapping and Complete. If you left an import unfinished, you see You have an import in progress first (below).
2. Import Transactions: upload your file
What you see.
The title Import Transactions and the line Upload your file and AI Assistant will automatically map your columns.
A Quick guide card with an AI-powered mapping badge and three steps:
Upload a CSV or Excel file. Under it: Not sure how to lay it out? and the link Download the sample file.
AI analyzes your import data: Review column mappings and be sure it all looks right.
Finish the import.
The Upload your file box: Drag & drop your file here, or click to browse, with a Browse files button. Under it: CSV, XLS or XLSX, up to 10 MB.
The My file has headers checkbox, ticked to start with.
A back arrow at the top left, which returns you to Transactions.
What to do.
If you want the layout, click Download the sample file. It's a CSV named payhoa-sample-transactions.csv with eight columns (Transaction Date, Description, Amount, Bank Account, Type, Category, Vendor, Memo) and 18 example rows. Replace the examples with your own rows, and put your own bank account name in the Bank Account column.
Leave My file has headers ticked if the first row of your file holds column names. Clear it if the first row is a transaction.
Drag your file into the box, or click Browse files and choose it.
What happens next. PayHOA starts reading the file straight away. Nothing has been added to your transactions yet. If the file is the wrong type, too big or empty, a red message appears and the file isn't uploaded; see "If something goes wrong".
You have an import in progress
This dialog appears when you open the importer and you have a transaction import you started but didn't finish.
What you see. The heading You have an import in progress and the question Would you like to pick up where you left off, or start a new import? Then four facts: Import type (Transactions), Records (the number of rows, such as 6 rows), Current step (Mapping) and Last updated. Two buttons: Start fresh and Resume import. There's no close button; you have to pick one.
What to do.
Click Resume import to go back to the mapping screen, with your column choices as you left them.
Click Start fresh to throw the unfinished import away. PayHOA confirms with Previous import cleared. Ready for a new file! and leaves you on the upload page.
What happens next. Either way, nothing has been added to your transactions. Only the person who started an import is offered it again.
Note: A resumed import doesn't show Verify transaction types again. Check the Type (Income/Expense) column on the mapping screen instead. If income and expense are the wrong way round, click Upload different file and upload the file again.
3. Reading your file
What you see. A small window with a sparkle icon and a heading that changes as PayHOA works: Uploading your file…, Reading your columns…, Finding your headers…, then Reading your file…, Lining up your columns… and Getting every row ready to match…. Your file's name is underneath. A progress bar is labelled Step 1 of 2 · Uploading, then Step 2 of 2 · Reading & mapping your file, with a percentage on the right. On a long wait the heading may change to Taking a little extra care with this one… or Big file, careful work. Hang tight….
What to do. Wait. Even a six-row file takes 10 to 20 seconds; a file with thousands of rows takes longer. The window has no buttons and can't be closed.
What happens next. PayHOA has now saved your file and a working copy of its rows as an unfinished import. Your transactions haven't changed. Then one of three things happens:
Verify transaction types opens (the usual case).
A red message says what's wrong with the file, and you're back on the upload page. See "If something goes wrong".
If PayHOA couldn't find an Amount column, it skips Verify transaction types and goes to the mapping screen, where you pick the column yourself.
4. Verify transaction types
What you see.
The heading Verify transaction types.
Your file's name and how many rows it has, such as 6 transactions detected.
The note We detected Income and Expense classifications for your transactions. Please verify they look correct.
A table of the first five rows of your file that have an amount, with Date, Description, Amount and Type. Amounts are shown as they are in your file, so a negative amount keeps its minus sign. Type shows how PayHOA will treat each row, as an income or expense badge: taken from your file's type column if it has one, or worked out from the sign of the amount.
The question Do these types look correct? with two choices:
No, swap Income & Expense — Flip all types before importing
Yes, looks correct — Continue with these types
Cancel and Continue. Continue is greyed out until you pick a choice.
What to do.
Look at a row you recognize. Is a deposit shown as Income, and a payment as Expense?
If yes, choose Yes, looks correct. If they're the wrong way round, choose No, swap Income & Expense.
Click Continue.
What happens next. If you chose to swap, PayHOA flips every row in the file, not only the five shown, and confirms with Swapped Income/Expense for 6 transactions. Then the mapping screen opens.
Cancel, or the X, closes the dialog and leaves you on the upload page. The unfinished import is kept; you'll be offered it the next time you open the importer.
Note: The swap is all or nothing. If only some rows are wrong, fix them in your file: add a Type column and upload it again.
5. Columns need your input (sometimes)
This window appears on top of the mapping screen when your file has a column PayHOA couldn't match to a transaction field and thinks you may care about. Often it doesn't appear at all.
What you see. The heading 1 column needs your input (or 2 columns need your input) and We analyzed the values and have recommendations. Choose how to handle each column. Each column has a card with its name, a few of its values, and a list. For transactions the list has one choice: Skip this column. At the bottom: Skip — I'll map manually and Continue.
What to do.
Click Continue to leave those columns out of the import.
Click Skip — I'll map manually if one of them is really a transaction field, such as your memo column. You can then pick the field for it on the mapping screen.
What happens next. The window closes and you're on the mapping screen. Either way, a column with no field isn't imported.
6. Edit mapped transaction data: check the columns and the rows
This is where you check everything. Nothing is added to your transactions until you click Start import.
What you see, top to bottom.
The heading Edit mapped transaction data.
A purple tip: AI analyzed the file, formatted your data, and matched columns. Review column mappings and see which records are new vs updates.
Warnings, when they apply (see "Rows and columns with problems" below).
Filter buttons, when your file has more than one kind of row: All records, New, Updating, No changes, Skipped and Invalid, each with a count, such as All records (6), New (2), Invalid (4). Only the kinds your file has are shown.
A Search rows box, and a summary line such as 6 records will be imported • 4 new • 1 updating • 1 no changes. Rows that won't be imported are counted in orange at the end: • 2 invalid (skipped). If every row matches a transaction that's already the same, the line reads 6 records will be imported • 6 no changes; importing then changes nothing.
The table: a Status column, then one column for each column in your file. Each column heading shows your file's header, an arrow, and a list holding the PayHOA field it's matched to. Required fields have an asterisk. Values are shown as they appear in your file.
If your file has no type column, PayHOA adds a Type (Income/Expense) column after Amount, showing Income or Expense for each row. Its list is greyed out because it isn't a column from your file.
Upload different file and Start import.
A legend under the table that explains the icons in use.
The Status column.
Status | What it means | What happens when you import |
New | No transaction like this is in PayHOA. | A new transaction is added. |
Updating | The row matches a transaction that's already in PayHOA, and something differs: the category, vendor, memo, description or bank account. Cells that differ have an orange info icon; point to it to see Previous value. | The existing transaction is changed to match your file. A blank Category, Vendor or Memo cell leaves the existing one alone. This is the result you want when you're updating; see Update existing transactions with the importer. |
No changes | The row matches a transaction that's already the same. | Nothing changes. No duplicate is added. |
Skipped | PayHOA couldn't read this row from the file. | It isn't imported. |
A warning triangle, with no badge | The row has a problem. The row is greyed out and crossed through. Point to the triangle to see why. | It isn't imported. |
Icons in the cells.
Icon | Legend text | What it means | What you can do |
Green info icon | Mapped to existing entity | PayHOA matched the name in your file to a category, vendor or bank account you already have. It appears on exact matches as well as the AI Assistant's close ones. The cell shows your existing name, not the file's. | If the match is wrong, click the X beside it. For a category or vendor (Use original value and create new category), PayHOA will create a new one with the name from your file instead. For a bank account (AI mapping incorrect — don't import this row), the row is left out of the import. |
List icon with a plus | New entity to be created during import | No category or vendor matched, so PayHOA will create one. Point to it: New category "Landscaping" will be added. | Click the X (Don't create this category or Don't create this vendor) to clear the value on that row instead. If the AI had suggested a match and you rejected it, the X reads Use AI-matched vendor instead. |
Orange info icon | Value updated | On an Updating row, this cell differs from the transaction in PayHOA. | Point to it to see Previous value, such as Previous value: 4010 - Assessments / Dues or Previous value: (blank). Click the X (Don't apply this update) to leave that cell out of the update. The orange icon gives way to a curved arrow, and a row with no other change becomes No changes. The cell goes on showing your file's value, but it isn't saved: the transaction keeps the value it has. Click the curved arrow (Undo) to put the change back. |
Empty-set icon (a circle with a line through it) | Required field could not be matched. Row will be skipped. | The bank account in this row doesn't match any account in PayHOA. | Fix the name in your file and upload it again. |
Warning triangle | Row won't be imported. Hover the icon for the reason. | See "Rows and columns with problems". | Fix the row in your file and upload it again. |
What to do.
Check the field above each column. To change one, open the list and pick the right field. The fields are grouped as Transaction (Transaction Date, Description, Amount, Memo) and Classification (Type (Income/Expense), Category, Vendor, Bank Account). A field already used by another column is greyed out and marked (mapped); free it first by setting the other column to something else.
To leave a column out, pick Skip column (do not import), the first choice in the list. A column with nothing chosen in its list, such as a reference number PayHOA didn't recognize, is also left out.
Check the Type (Income/Expense) column against a few rows you know.
Check every green and plus icon in the Category, Vendor and Bank Account columns, and reject any match that's wrong.
Use the filter buttons to look at Updating rows on their own. Each one changes a transaction that's already in PayHOA to match your file. When you're updating on purpose, these are the rows you expect: point to the orange icons to check each change. When you're adding new transactions, an Updating row means PayHOA already has that transaction, so make sure the change is one you want. Either way, look closely at any row with an orange icon in the Bank Account column: importing it moves the existing transaction to the bank account in your file. If that transaction is approved, your books aren't moved with it; see Check before you import.
Use Invalid to see the rows that won't be imported, and point to each triangle for the reason.
When it all looks right, click Start import.
Each change you make to a column is saved as you make it. While PayHOA re-checks the rows, the table shows grey placeholder bars for a moment.
You can't type into the cells. To change a value, such as a date or an amount, fix it in your file and upload the file again.
What happens next. Start import is the point of no return: PayHOA starts adding and updating transactions at once, with no "are you sure" step.
To leave without importing:
Click Upload different file (see below) to throw this import away.
Or just go to another page. The import is kept as it is, and the next time you open the importer you'll see You have an import in progress.
Rows and columns with problems
A required field has no column. A yellow warning reads Required fields are not mapped — The following required fields need to be mapped: Bank Account (or whichever are missing). Every row is greyed out and crossed through, and the summary line is hidden. Start import is greyed out, and pointing to it shows Map all required fields before importing. Pick the field above the right column. If your file has no such column, for example no bank account column, add it to the file and upload it again.
You have no bank accounts. A red message reads Add a bank account before importing transactions — Bank Account is required on every transaction and must match an existing bank account — this importer never creates them. Create a bank account in your organization, then start this import again. Start import stays greyed out. Add the account first. See Connect and manage bank accounts.
A row has a problem. The row is greyed out and crossed through, and shows a warning triangle instead of a status. Point to it to read the reason, which starts This row won't be imported —. The reasons are listed under "If something goes wrong". You can still click Start import: the rows that are fine are imported, and the rows with problems are left out and listed on the last screen.
Important: If more than half of the rows have a problem, the import ends with Import failed, even though the good rows have been imported. It's cleaner to fix the file first: click Upload different file, correct the rows, and upload it again.
You changed a column and the problems changed. That's expected. PayHOA checks every row for problems again each time you change a column's field. It doesn't work out again which rows are New and which are Updating; that's decided once, when the file is read. If the Transaction Date, Amount or Description column was matched to the wrong field, fix the header in your file and upload it again.
Upload different file?
What you see. After you click Upload different file: the heading Upload different file? and This will discard your current import progress. You can start fresh with a new file. Buttons: Cancel and Start fresh, and an X that does the same as Cancel.
What to do. Click Start fresh to throw the import away, or Cancel to stay on the mapping screen.
What happens next. Start fresh deletes the unfinished import and its rows. After a few seconds you're back on the upload page, with a green Cleared message: Previous import cleared. Ready for a new file! Your transactions haven't changed.
7. Importing
What you see. The table is replaced by a card with a spinner, the heading Importing... and Please wait while we process your records. This may take a few moments.
What to do. Wait, and keep the page open. Six rows can take about five seconds; a bigger file takes longer.
What happens next. One of two screens: Import complete, or the mapping screen again with a red Import failed message.
8. Import complete
What you see.
A tick icon and the heading Import complete.
A green pop-up at the top left: Import Complete — Your data has been imported successfully. It goes away after a few seconds, or when you click its X.
If some rows were left out, a red box: Some rows could not be imported. It lists the first ten with the reason, such as Row 3: Amount is required., then And 2 more. Row 1 is the first transaction in your file, so with a header row, Row 3 is line 4 of your spreadsheet.
Cards with the totals. Only the ones above zero are shown:
Card: New transactions added What it counts: Transactions created.
Card: Transactions updated What it counts: Rows that matched a transaction already in PayHOA. This includes rows that showed No changes.
Card: Categories created What it counts: New categories made from names in your file.
Card: Vendors created What it counts: New vendors made from names in your file.
Card: Transactions skipped What it counts: Rows PayHOA couldn't read from the file.
Card: Transaction imports failed What it counts: Rows left out because of a problem.
Return to Transactions.
What to do. Note any rows that were left out, then click Return to Transactions.
What happens next. You're back on Transactions. PayHOA also emails you the summary, Transactions Import Complete, with the failed rows and their reasons.
Import failed
What you see. You're back on the mapping screen, with a red box above the table: Import failed, followed by the reason. The usual one is Import failed: 4 of 6 rows failed (66.7% failure rate exceeds 50% threshold). A red Import Error pop-up at the top left repeats it. The table looks as it did before, with the good rows still marked New.
What it means. More than half of the rows had a problem. The rows that were fine have been imported; they aren't undone. The rows with problems were left out.
What to do.
Go to Transactions → For review and see what came in.
Fix the remaining rows in your file.
Open the importer and upload the corrected file. The failed import is closed, so you get the upload page, not You have an import in progress. The rows that already came in show No changes, so they aren't added twice.
Don't click Start import again on the same screen. That import is finished, and PayHOA answers Cannot transition from failed to reviewing.
After the import
Where the transactions are. New transactions are on Transactions, on the For review tab, under the bank account named in each row. They aren't approved, so they aren't in your books or reports yet. See Review and categorize transactions.
Transactions you updated are on the tab they were on before. An update doesn't approve anything or send anything back to For review, and your transaction rules aren't run on it. See Update existing transactions with the importer.
What PayHOA did for you.
Rows with a category arrive with that category, waiting for you to approve them. Your transaction rules don't change a category that came from your file.
Rows with no category are handled like any new transaction. A matching transaction rule is applied first; a rule set to approve will approve it. Otherwise PayHOA copies the category from a transaction with the same description that you approved before, or Gable suggests one. Gable's suggestion is there within seconds: the row shows a category with Gable's sparkle icon and an AI confidence percentage, and it still waits for you to approve it. See Set up transaction rules.
New categories and vendors were created where a name didn't match.
You were emailed the summary.
What PayHOA didn't do.
It didn't approve anything (unless one of your rules approved a new transaction).
It didn't post anything to the general ledger. That happens when a transaction is approved.
It didn't record transfers. Both sides of a transfer are ordinary transactions until you convert them. See Record transfers between accounts.
It didn't apply any deposit to an owner's account or mark any invoice paid.
It didn't mark anything reconciled.
What to check.
Open For review, pick the bank account, and compare the number of transactions and a few amounts with your file.
Check that deposits show as income and payments as expenses.
Look for duplicates, especially if the account is linked to your bank. See Exclude, delete or fix duplicate transactions.
Check the new categories in your chart of accounts, and rename, nest or merge them as needed. See Add, edit, nest, delete and restore categories.
Check the new vendors. They have a name and nothing else. See Add, edit and delete vendors.
Approve the transactions.
Reconciling. Imported transactions appear in a bank reconciliation for their account like any others, as Unmatched until you tick them. Finishing a reconciliation approves the ticked ones that have a category. The importer doesn't check your finished reconciliations: a new transaction dated inside a finished period is added without being reconciled, and that period's reconciliation isn't changed. An Updating row changes a reconciled transaction like any other; it stays reconciled. See Reconcile a bank account.
Fixing a mistake.
One transaction is wrong: open it and fix the category, vendor, memo, description, date or amount. See Review and categorize transactions.
The whole import is wrong (wrong account, income and expense swapped, wrong file): delete the imported transactions, fix the file, and import again. On For review, pick the bank account, tick the transactions, and choose Actions → Delete. See Exclude, delete or fix duplicate transactions. Deleting doesn't stop you importing the same rows again from a file.
Categories or vendors you didn't want: deleting the transactions doesn't remove them. Delete them yourself.
A transaction that was updated by mistake: there's no way to put the old values back automatically. Edit the transaction. If you kept the export you started from, you can import it to put back the categories, vendors and memos it holds. See Update existing transactions with the importer.
You can't tell what came in: contact PayHOA support with the date and time you ran the import.
If something goes wrong
The import worked, but I can't find the transactions
If you uploaded a file (a bank activity export, for example), saw Import complete, and the transactions aren't on Transactions, in reports or in a bank reconciliation, they are almost certainly in PayHOA but not where you're looking. Uploading the same file again and seeing every row marked No changes confirms it: PayHOA already has those rows. Check these in order:
The For review tab. New imported transactions wait on For review, under the bank account named in each row. They aren't on Reviewed, in reports or in the account's Ledger balance until you approve them.
The bank account. Each row went to the account in its Bank Account column, which may not be the account you have open. Choose All accounts in the account menu.
The dates. A transaction whose date was read differently from what you meant sits outside the dates you're looking at, and outside the period of any reconciliation or report. This happens with two-digit years and with day-first dates: 1/15/24 is read as January 15, 2024, and 03/04/2024 as March 4. To find them, open All transactions, click Filters, set Timeframe to All time and click Apply filters, then type a description or an amount from the file in Search. Look at the date on the rows you find.
The summary email. The person who ran the import was emailed a summary of what it did.
If the dates came in wrong, fix them in one of two ways. For a few transactions, open each one and correct the Date. For a whole file, delete the imported transactions (tick them and choose Actions → Delete), change the file to four-digit years in a format such as 01/15/2024, and import it again. Don't re-import a corrected file without deleting first: a row with a different date doesn't match the earlier one, so you'd have both.
If you still can't find them, contact PayHOA support with the date and time you ran the import, the bank account, and one row from the file (its date, amount and description).
Messages about the file
Message | What it means | What to do |
Unsupported file type. Please upload a CSV, XLS, XLSX file. | The file isn't a CSV or Excel file. | Save it as CSV, XLS or XLSX. A PDF statement or a Google Sheets link won't work; download the sheet as CSV or Excel first. |
File is too large. The maximum file size is 10MB. | The file is over 10 MB. | Split it into smaller files, for example one per year, and import them one at a time. |
That file is empty. Please upload a file that contains data. | The file has nothing in it. | Check you picked the right file. |
Could not detect column headers in the file. Please check the file format. | PayHOA found no header row. | Make sure the first row holds the column names, or clear My file has headers. |
No data rows found in the file. Please check the file contains data. | There are headers but no transactions under them. | Add your rows. In Excel, make sure the sheet with the data is the one that was open when you saved. |
The first row of this file looks like data, not column headers. Add a header row naming each column, or uncheck "My file has headers", then upload it again. Otherwise that first record would be lost. | The first row is a transaction, not column names. | Do what the message says. |
Failed to read CSV headers. or Excel file is empty. | The file couldn't be read. | Open it, check it has a header row and data, save it again and retry. |
Failed to process file. Please try again. or Failed to process file. Check the file type and size, then try again. or Failed to upload file. Please try again. | Something went wrong while PayHOA read the file. | Try again. If it keeps happening, try a smaller file, then contact PayHOA support with the file and the time you tried. |
Session expired. Please refresh and try again. | You've been signed out. | Refresh the page, sign in and upload again. |
You do not have permission to import transactions for this organization. or You are not authorized to view the requested page | You aren't an Admin of this association. | Ask an Admin to run the import. |
Messages on the mapping screen
Message | What it means | What to do |
Required fields are not mapped — The following required fields need to be mapped: … | Transaction Date, Description, Amount or Bank Account has no column. | Pick the field above the right column, or add the column to your file and upload again. |
Map all required fields before importing | The tooltip on a greyed-out Start import, for the same reason. | As above. |
Add a bank account before importing transactions | Your association has no bank accounts in PayHOA. | Add one, then start the import again. See Connect and manage bank accounts. |
Failed to load mapping data | The screen couldn't load. | Refresh the page. If you're asked, click Resume import. |
Failed to save mapping or Failed to save change | Your last change wasn't saved. | Make the change again. |
Failed to swap transaction types. Please try again. | The swap on Verify transaction types didn't go through. | Upload the file again and choose the swap again. |
No matching records found | Your search or filter matches no rows. | Clear the Search rows box or click All records. |
Reasons a row won't be imported
On the mapping screen these follow This row won't be imported —. On Import complete they follow the row number.
Reason | What it means | What to do |
No matching bank account found. Bank accounts are not created by the transaction importer. | The Bank Account value doesn't match any account in PayHOA. | Use the Bank account name as it appears in PayHOA, or add the account first. See Connect and manage bank accounts. |
Bank account is required. | The row's Bank Account cell is empty. | Fill it in on every row. |
Bank account match was rejected. Bank accounts are not created by the transaction importer. | You clicked the X on a bank account the AI Assistant had matched, to say the match was wrong. | Put the right account name in your file and upload it again. |
Transaction date is required. | The date cell is empty. | Add the date. |
Transaction date could not be parsed. | PayHOA can't read the date, such as 13/45/2026 or last Tuesday. | Use a format like 01/15/2024. |
Amount is required. | The amount cell is empty. | Add the amount. |
Amount could not be parsed. | The amount has no number in it, such as N/A. | Use a number like 1250.00. |
Description is required. | The description cell is empty. | Add a description. |
Description is 300 characters. It must be 255 characters or fewer. (also Memo) | The text is too long. | Shorten it. |
Vendor is 52 characters. A new vendor name must be 40 characters or fewer. Shorten it or match an existing vendor. | The vendor doesn't exist yet and the name is too long for a new one. | Shorten the name, or use the name of a vendor you already have. |
This row could not be read from the file and was skipped. | The row is damaged in the file. It shows as Skipped. | Retype the row in your file. |
missing required field: Amount. (or fields:) | A required cell is empty on this row. You also get this on the credit rows of a file with separate debit and credit columns. | Fill it in. For debit and credit columns, see "Money in or money out?" above. |
Messages when the import runs
Message | What it means | What to do |
Import failed or Import Error — Import failed: 4 of 6 rows failed (66.7% failure rate exceeds 50% threshold) | More than half the rows had a problem. The good rows were still imported. | See "Import failed" above. |
Cannot transition from failed to reviewing. or This import session can no longer be run — it may have already completed or failed. Upload the file again to start a new import. | You clicked Start import on an import that had already finished or failed. | Check For review for what came in, then upload the file again. |
Import failed with no other detail, or a technical message | Something unexpected stopped the import. In this case nothing from it is kept. | Check For review to be sure, then upload the file again. If it repeats, contact PayHOA support. |
Some rows could not be imported. | The import finished, and the rows listed were left out. | Fix those rows in your file and import again; the rows that already came in show No changes. |
Common questions
My bank's file has separate debit and credit columns. What do I do? Combine them into one Amount column and add a Type column: Expense for the debits, Income for the credits. See "Money in or money out?" above.
Everything came in as income (or as expense). The file's signs are the opposite of what PayHOA expected, and the swap wasn't chosen on Verify transaction types. Delete the imported transactions, then import the file again and choose No, swap Income & Expense. If only some rows are wrong, add a Type column to the file instead.
Can I import into an account that's linked to my bank? The importer doesn't stop you, but you'll usually get duplicates, because the bank feed words descriptions differently. Only do it to fill a gap, and cut the file down to the missing dates first. To bring back a long stretch a linked account missed, re-link the account instead. See Connect and manage bank accounts.
Can I import a PDF bank statement? No. The importer takes CSV, XLS or XLSX. Download a spreadsheet export from your bank's website. If you only have the PDF, start a bank reconciliation with Reconcile with Gable: Gable reads the statement and lets you add the transactions that are missing. See Reconcile a bank account.
Does the importer create bank accounts? No. Add each account first, with the name you'll use in the file. See Connect and manage bank accounts.
How many transactions can I import at once? There's no row limit, only the 10 MB file size. PayHOA reads the whole file in one go, so a very large file takes longer. If it doesn't finish, split it by year.
Can I change the category, vendor or memo on many transactions at once? Yes. Export the transactions, change those columns in a spreadsheet, and import the file. Rows that match a transaction already in PayHOA update it. See Update existing transactions with the importer.
My transactions are already in PayHOA. Can I import a file just to add categories, vendors or memos? Yes. Export the transactions, fill in the empty Category, Vendor or Memo cells, and import the file. Each row that matches a transaction by date, amount and description adds the detail to it, and no second transaction is made. A blank cell leaves the transaction as it is. See Add categories, vendors or memos to transactions from a file.
Will importing my file again create duplicates? Not if the date, amount and description in each row are unchanged. Those rows match what's already in PayHOA and show Updating or No changes, never New. Importing the very same file twice changes nothing. A row whose date or amount you changed, or whose description you reworded, is added as a new transaction. See "How PayHOA decides a row is an update" in Update existing transactions with the importer.
Can I fix dates or amounts by importing a corrected file? No. A row with a different date or amount doesn't match the original, so you'd get a second transaction. Edit the transaction instead. See Review and categorize transactions.
Will my reports change as soon as I import? Not for new transactions. They wait on For review and reach your books when you approve them. An update is different: a new category on a transaction you've already approved changes your reports as soon as the import finishes.
Can I import (upload) journal entries? No. The importer adds bank transactions only; journal entries can't be imported or uploaded from a file. Add them with Actions → Add journal entry, where Copy from existing entry and Create multiple entries at once save retyping. See Add a journal entry.
Can I import transfers between my accounts? Not as transfers. Import both sides as ordinary rows, then convert one to a transfer and remove the other. See Record transfers between accounts.
Where do check numbers go? There's no check number field. Map that column to Memo.
Can I undo an import? There's no undo. Delete the imported transactions from For review (Actions → Delete). Categories and vendors the import created stay until you delete them. Transactions the import updated keep their new values; keep a copy of your export so you can put the old ones back.
I closed the page halfway. Is anything saved? No transactions are added until you click Start import. Your unfinished import is kept; open Import transactions again and choose Resume import or Start fresh.
Who gets the email? Only the person who ran the import. Owners and vendors aren't told anything.
Is the importer different on the older accounting version? No. It works the same on both. What differs is afterwards: on the older version, click Actions → Update general ledger once you've approved the transactions. See Accounting V2 and V1.


















