Skip to main content

Import payments from a file

The payment importer does two jobs.

M
Written by Michael Bollinger

The payment importer does two jobs.

  • Record payments. This is its main job. Use it to record many check and cash payments at once from a spreadsheet, a bank file or a report from another system. Each new row becomes one offline payment on the owner's account, exactly like a payment you record by hand.

  • Update a few details on payments you've already imported. A row that matches a payment already in PayHOA can change that payment's method or reference number, or add a note to it. It can't change the amount, the date, the unit or the invoices. This doesn't work yet when your imports run in the background on the Payments page: there, an update file changes nothing. See Update payments you already imported.

PayHOA's AI Assistant reads the file, matches each column to a payment field and each row to a unit and an owner, and shows you every row before anything is recorded or changed.

Use something else when:

  • You have only a few payments. Record them by hand. See Record a check or cash payment.

  • You need to choose the exact invoices and amounts a payment pays. The importer can only put the invoices you name first. Record the payment by hand with Apply to specific charges.

  • The file is your Alliance Bank lockbox file. Lockbox checks have their own import. See Lockbox payments.

  • The file is a bank statement or a list of expenses. Those are transactions, not owner payments. See Import transactions from a file.

  • You're bringing in owners' starting balances. Those come in with the units and owners importer. See Import units and owners.

  • You need to change a payment's amount, date, unit or invoices. An import can't change those. Edit the payment, or delete it and record it again. See Edit, delete or fix a recorded payment.

Note: Imported payments are offline payments. Nothing is charged to an owner's card or bank account, and there are no processing fees.

Before you start

Who can use it

Admins only. The Import button shows for anyone who can edit payments, but the import pages open only for people with Admin Status. Anyone else sees You are not authorized to view the requested page. See Give board members and staff access.

Where it is

Payments in the left menu, then Import at the top right.

File types

CSV, XLS, XLSX or PDF.

File size

Up to 10 MB.

Rows

No set limit. Every row is one payment, and a single payment can't be more than $1,000,000.

Excel files

Only one sheet is read: the one that was open when the file was last saved.

Sample file

Download the sample file on the Import Payments page gives you a CSV with the columns PayHOA expects and 14 example payments.

What the AI does

It reads your column names and the first few rows to match columns to fields. It reads the names and addresses in your file to match them to your units and owners. A PDF is read in full to find the table in it. The AI can get a match wrong, so check each row before you import.

What gets created

One payment per row. A note on the payment if the row has a reference number, a memo or an Applies To value. Account credit for any overpayment. One deposit on Transactions if you ask for it.

What never gets created

Units, owners and invoices. A row whose unit or owner can't be found is left out.

What gets updated

A row that matches a payment you already have can change that payment's method or reference number, or add a note to it. Nothing else about a payment is changed by an import. This happens only when the import finishes on the import page. When it runs in the background on the Payments page, nothing is updated. See Update payments you already imported.

Emails

Owners are emailed a receipt unless you turn that off. You're emailed a summary when the import finishes.

Undo

There's no undo. To reverse an import, delete the payments. See After the import.

Your file

Each row is one payment from one unit. Your column names don't have to match the sample. PayHOA matches columns by their name and what's in them, and you can change a match before you import.

Field on the mapping page

Required?

What to put in it

Example

If it's blank or wrong

Payor (Unit)

Yes

Who paid: the unit as it's named in PayHOA, the unit's street address, or the owner's name.

101 Main Street

Blank: Payor is required. Not found: "…" does not match any unit or owner in this organization. Either way the row isn't imported.

Amount

Yes

A number with up to two decimals. A dollar sign and commas are fine. Up to $1,000,000.

350.00 or $1,234.56

Blank, zero, text or more than two decimals: the row isn't imported. A minus sign is ignored, so -50.00 is recorded as a $50.00 payment.

Owner

No

The name of the owner who paid. Only needed when a unit has more than one owner and you want to say which one.

Jane Doe

No owner column, or a blank cell: the payment goes to the unit's first owner. A name that isn't an owner on that unit: the row isn't imported.

Payment Date

No

The date the payment was made. See the formats below.

01/15/2026

Blank, or no date column: the day you run the import. A date PayHOA can't read, or a date in the future: the row isn't imported.

Reference Number

No

A check number or other reference, up to 31 characters.

1001

Blank: PayHOA gives the payment its own confirmation number. Over 31 characters: the row isn't imported.

Payment Method

No, but see the warning below

Check or Cash. See the full list below.

Check

Blank, or no method column: the payment is recorded with the method Account Credit. A method PayHOA doesn't know: the row isn't imported.

Note/Memo

No

Any text. It's saved as a note on the payment.

January assessment

Blank: no memo.

Applies To

No

Which invoices the payment is for: a month or months (Sep, Jul-Aug, Oct to Dec) or an invoice title (2026 Dues).

Jan

Blank: the payment pays the oldest invoices first.

Warning: Always include a Payment Method column with Check or Cash for money you received. A blank method is recorded as Account Credit, which is the method PayHOA uses for a credit you give an owner, not for money you took in. The owner's balance still goes down, but your books don't show the money as waiting to be deposited. See Account credit.

Dates PayHOA can read

  • 01/15/2026, 1/15/2026 or 1/15/26 (month first)

  • 2026-01-15 or 2026/01/15

  • 20260115

  • 01-15-2026

  • Jan 15, 2026 or 15 Jan 2026

A date like 01/02/2026 is read as January 2. Day-first dates are only understood when the first number can't be a month, such as 15/01/2026.

Payment methods PayHOA accepts

In your file

Recorded as

Check, Cheque, Check offline, Offline

Check

Cash, Cash offline, Zelle, Venmo, PayPal, Wire, Wire transfer, Money order

Cash

Account credit, ACH, NACHA, Bank, Bank account, Card, Credit card, Credit, Debit, or blank

Account Credit

Anything else, such as eCheck or Online

The row isn't imported: "…" is not a supported payment method.

Capitals don't matter, and a one-letter typo such as Chek is still understood.

How a row finds its unit and owner

  1. PayHOA looks for a unit whose name or street address is the same as the Payor (Unit) value. Capitals, extra spaces and anything in brackets at the end are ignored.

  2. If there's no exact match, it looks for a close one. The first number in the value must be the same as the unit's, so 6017 Daiquiri Bay never matches unit 6018. A plain number such as 3 matches unit 03 only when no other unit has that number.

  3. If that fails, the AI compares the value with your units' names, addresses and owners' names. It only accepts a match it's confident about.

  4. If the value is a person's name, PayHOA matches it to an owner and uses that owner's unit. The row shows the unit, then the owner in brackets, like any other row.

  5. Once the unit is known, PayHOA picks the owner. If your file has an Owner column, the name must be one of that unit's owners. If it doesn't, the payment goes to the unit's first owner: the one who was added to the unit first.

Only current owners are matched. To record a payment from a prior owner, record it by hand. This is what happens when you upload historical payments for a unit that was sold: rows that name the previous owner as the payor are rejected, because that person is no longer an owner of the unit. Leave those rows out of the file and record each one with Record payment: pick the unit, then under Attribute to owner choose the seller from the Prior owners group. See Record a check or cash payment and If the seller pays after the sale.

If a row can't be matched to a unit and an owner, it isn't imported. You can't pick a unit or owner on the mapping page. Fix the value in your file, or the unit in PayHOA, and upload again.

How payments are applied to invoices

  • With no Applies To value, the payment pays the unit's open invoices from the oldest due date to the newest.

  • With an Applies To value, the invoices it names are paid first, then the rest, oldest first. An invoice is named when its title contains the text, or when it's due in a month you named. The year isn't checked, so Sep means any September.

  • Only invoices that are already active are paid. A Future invoice is never paid by an import.

  • Anything left over becomes account credit on the unit. It pays the unit's next invoices automatically. See Account credit.

  • The Applies To text is added to the payment's note as Applies to: Sep.

You can't split one payment across particular invoices by amount. If you need that, record the payment by hand.

Rules for the whole file

  • One row is one payment. If one check paid two units, split it into two rows.

  • Headers. The first row should name the columns. If your file has no header row, clear My file has headers before you upload, and the columns are named Column 1, Column 2 and so on.

  • Two payments from the same owner, for the same amount, on the same date need different reference numbers. Without them, the second row is treated as a repeat of the first and left out.

  • Refunds, returns and reversals can't be imported. Take those rows out. See Mark a check as returned.

  • Reference number and memo. If your file has both, they're joined into one note that reads Ref# 1001 — January assessment.

Update payments you already imported

The importer is mainly for recording payments. It's also built to change a few details on payments that are already in PayHOA: the payment method, the notes and, on payments that didn't come from the importer, the reference number. It can't change anything else about a payment.

Whether an update is applied at all depends on how your association's imports run. Read the note below before you prepare a file.

Important: An import doesn't update payments when your association's imports run in the background. You're on that flow if the bar at the top of Import Payments shows two steps, Upload and Mapping, and Yes, start import takes you straight back to the Payments page with an Importing payments… card. The mapping page still marks the rows Updating and counts them in records will be imported, but they're left out when the import runs. The card ends with All 0 payments were imported., View Details opens Run details with 0 payments and Nothing matches this filter, and no payment's method, reference number or notes are changed. No message says the updates weren't applied. Make the changes by hand instead. See Edit, delete or fix a recorded payment.

Updates are applied only when your import finishes on the import page, with Importing... and then Payments Recorded. The rest of this section describes that case.

When to update with the importer

  • Fix the payment method on a batch. For example, 40 payments were imported as Cash and they were checks.

  • Add a note to many payments at once, such as a check number or a batch name you didn't have when the payments were recorded.

  • Put your own reference numbers on payments you recorded by hand, in place of the confirmation numbers PayHOA gave them.

For a wrong amount, date, unit, owner or invoice, don't use the importer. Edit the payment, or delete it and record it again. See Edit, delete or fix a recorded payment.

Steps to update payments

These steps change your payments only when the import finishes on the import page. If your imports run in the background on the Payments page, stop here and make the changes by hand. See the note at the top of this section.

  1. Get the payments into a file. Use one of these:

    • The file you imported them from. It already has the right columns.

    • An export from PayHOA. On Payments, click Filters, choose Offline under Payment source and click Apply filters. Tick the payments you want to update. The Actions button now shows how many are ticked, such as Actions (3). Click it, then Download CSV. You'll see Success Exported 3 payment(s) to CSV., and a file named payments_ and today's date, such as payments_2026-11-11.csv, is saved to your computer. See Export to a spreadsheet. The export can't be imported as it is. Change it as described in Preparing a PayHOA export for the importer.

  2. Save a copy of the file before you change it. There's no undo, and the copy shows what each payment had before.

  3. Change only the cells you want to update: the payment method, the note or the reference number.

  4. Leave the columns PayHOA uses to recognise the payment exactly as they are: the unit, the owner, the amount and the payment date. Every row needs a payment date.

  5. On payments that came from the importer, don't add or change a reference number. See the first warning under Check before you import.

  6. Make sure every row has Check or Cash in the method column, even if you aren't changing the method. A blank method is read as Account Credit: the row reads Updating and its method cell shows AccountCredit.

  7. In the notes column, leave a cell blank on every row where you aren't adding a note, or delete the column if you're adding none. Text that differs from the payment's latest note is added as a new note.

  8. Click Payments → Import and upload the file. See Import Payments.

  9. On Edit mapped payment data, read the Status column. Every row should read Updating or No changes, never New. A New row would be recorded as a second payment. If you see one, click Upload different file, then Start fresh, correct the file and upload it again. A row that reads No changes matches a payment and has nothing different. The count line adds the two together, such as 3 records will be imported • 2 updating • 1 no changes, and the buttons above the table, such as Updating (2) and No changes (1), show one kind of row at a time.

  10. Point to the orange icon in each changed cell (Value updated in the key under the table) to see Previous value: and what the payment has now. For a method, the previous value is shown as OfflineCheck, OfflineCash or AccountCredit. For a note, it's the payment's latest note. The method and notes columns are on the right of the table, so scroll it sideways to see them.

  11. To leave one value as it is, click the X beside the icon. Pointing to the X shows Keep original value on a method, and Don't apply this update on a note or on a method that was blank in your file. The orange icon is replaced by an Undo arrow, which puts the change back. If that was the row's only change, the row now reads No changes. When no row has a change left, the count line reads 3 records match your existing data. No changes will be made.

  12. Click Start import. In Payment import options, turn off Create deposit on transaction ledger if you see it. The banner counts your rows as payments ready to import, but no new payment is recorded for an Updating row. The banner's total can be wrong: when the date column comes before the amount column in your file, as it does in a PayHOA export, the total is added up from the dates. Go by the amounts on the mapping page. Click Yes, start import. See Payment import options.

  13. Open two or three of the payments on Payments and check the method and the Notes. PayHOA doesn't count updated payments on Payments Recorded or in the summary email. After an import that only updated payments, the page reads No payments needed changes. Every row already matched. If you were taken back to the Payments page instead and the card reads All 0 payments were imported., nothing was updated.

Note: In the Notes column, the X puts the payment's saved note back in the cell, and the row reads No changes if nothing else on it is different. To be certain no note is added, take the text out of the file and upload it again.

Preparing a PayHOA export for the importer

PayHOA has no payments export made for importing again. The CSV from Actions → Download CSV has these columns: Payor, Unit, Payment date, Deposit date, Amount, Fees, Net, Payment method, Check number, Recorded by and Note. Change it like this before you upload it:

In the export

What to do

Payor

Rename it Owner. It holds the owner's name, not the unit. Do this before you rename Unit, so that two columns never have the same name.

Unit

Rename it Payor.

Payment date

Keep it as it is. Dates are written like 11/3/2026, which the importer reads.

Amount

Keep it as it is.

Payment method

Keep the heading, or rename it Method. Change every Check (offline) to Check and every Cash (offline) to Cash. The importer doesn't accept the export's wording, and those rows aren't imported: "Check (offline)" is not a supported payment method.

Note

Delete it, unless you're adding notes. To add notes, keep the column, replace the text with the note to add on the rows you want, and clear the cell on the other rows. The export puts the payment's saved note here, such as Ref# 1001 — January assessment — Applies to: Jan.

Check number

Delete it. It's blank for payments that came from the importer: their reference number is in the Note column. To set reference numbers on payments you recorded by hand, add your own Reference Number column.

Deposit date, Fees, Net, Recorded by

Delete them.

The last two rows: a blank row and Total (3 payments)

Delete them. If you leave them in, the blank row is ignored and the total is shown as a row that won't be imported: "Total (3 payments)" does not match any unit or owner in this organization.

Rows with the method Credit Card or Bank Account

Delete them. Those are payments owners made online, and an update would relabel them Account Credit.

If you upload the export without changing it, nothing is imported. Every payment row has a warning triangle because of its method, and the count line reads, for example, 0 records will be imported • 4 invalid (skipped). Click Upload different file, then Start fresh, and prepare the file as above.

Tick the payments before you export. With nothing ticked, Download CSV gives a different file, with the owner's name and the unit in one cell, which the importer can't match reliably.

How PayHOA decides a row is an update

The check is made once, when the file is uploaded, in this order:

  1. PayHOA finds the row's unit and owner, as it does for any row. With no owner column, the owner is the unit's first owner. See How a row finds its unit and owner.

  2. It reads the row's payment date. A row with no date is never treated as an update.

  3. It looks for a payment recorded under that owner for exactly the same amount. Failed payments are ignored.

  4. It then checks the date and the reference number:

    • The row has no reference number. The payment must have the same payment date.

    • The row has a reference number. The payment must have the same reference number, on any date. Or it must have the same payment date and not have come from the importer: for example, you recorded it by hand, or the owner paid online.

If a payment is found, the row is an update. It reads Updating when its method, reference number or memo differs from the payment's, and No changes when nothing differs. If no payment is found, the row reads New.

If more than one payment fits, PayHOA picks one of them and you can't choose which. Update those payments by hand.

A row that matches. Lot 22's payment was imported as $350.00 on 01/15/2026, reference 1001, method Cash. The row Lot 22, 350.00, 01/15/2026, 1001, Check finds it by its reference number. The row reads Updating and the method becomes Check.

A row that's added as new by mistake. The same row with the reference changed to 1002, to correct the check number. No payment has reference 1002, and an imported payment with another reference number is never treated as the same payment. The row reads New and a second $350.00 payment would be recorded. The same happens if you change the amount to 355.00, or name a different owner on the unit.

What an update changes, and what it leaves alone

In your file

On an Updating row

Payment Method

Replaced with the file's method, when it's different. Only the method shown on the payment changes. The entries made in your books when the payment was recorded stay as they are.

Reference Number

Replaced with the file's value, when it's different. It's saved as the payment's confirmation number, the number on its receipt. This can only happen on a payment that didn't come from the importer.

Note/Memo

Added to the payment as a new note, when the text differs from the payment's latest note. Notes already on the payment are kept. They're never edited or removed.

Applies To

Ignored.

Payor (Unit), Owner, Amount, Payment Date

Never changed by an import. PayHOA uses them to find the payment. If you change one, the row no longer matches and reads New.

The invoices the payment paid, any account credit it created, its deposit, the entries in your books

Never changed by an import.

The owner's receipt

Not sent again, whether Email receipts to each owner associated with these payments is on or off.

Blank cells. A blank reference number or a blank memo leaves the payment as it is. A blank payment method doesn't. It's read as Account Credit, so a blank method cell, or a file with no method column, changes a Check or Cash payment to Account Credit. On the mapping page such a row reads Updating, and its method cell shows AccountCredit with the orange icon and Previous value: OfflineCheck or OfflineCash. Pointing to the X beside it shows Don't apply this update.

If you upload a file you've already imported

You'll see Updating on every row, not No changes, when the file has a memo together with a reference number or an Applies To value. PayHOA compares the memo in your file with the whole note it saved the first time, such as Ref# 1001 — January assessment — Applies to: Jan, so the two never match. The count line reads, for example, 3 records will be imported • 3 updating. The orange icon in the Notes column shows Previous value: and the saved note.

Importing that file again doesn't record the payments twice, and no receipts are sent. What happens to the Updating rows depends on where your import finishes:

  • On the import page: each payment gets one more note, with just the memo text from your file. Nothing else changes.

  • In the background, on the Payments page: the rows are left out. Nothing changes. The card reads All 0 payments were imported., and Run details lists nothing.

If you only uploaded the file to check it, click Upload different file, then Start fresh.

What you can't update this way

  • The amount, the date or the text of a note already on the payment. On Payments, click ⋯ on the payment → Edit. See Edit a payment.

  • The unit, the owner or the invoices the payment paid. Delete the payment and record it again. See A payment went to the wrong invoice or unit.

  • The reference number of a payment that came from the importer. Add the right number as a note instead, with a notes column and no reference number column.

  • A payment recorded as Account Credit that was really money received. Changing the method here doesn't correct your books. Delete the payment and import the row again with Check or Cash. See After the import.

  • Which deposit a payment belongs to. See Link owner payments to deposits.

  • A returned check or a refund. See Mark a check as returned and Refund an owner's payment.

  • Sending a receipt again. On Payments, click ⋯ on the payment → Send receipt. See Receipts.

Check before you import

Warning: Don't add or change a reference number on a payment that came from the importer. The row stops matching, reads New, and a second payment is recorded for the same money. Never click Start import on an update file while any row reads New.

Warning: Every row needs Check or Cash in the method column. A blank method, or a file with no method column, changes the payments it matches to Account Credit.

Warning: Check that each Updating row is the payment you mean. PayHOA matches on the owner, the amount and the date. If an owner paid the same amount twice on one day, or paid online on the day you're updating, the row can match the other payment and change its method or reference number.

Important: Changing a column's match on the mapping page doesn't check the rows again. Rows keep the New or Updating status they were given when the file was uploaded. If a column was matched wrongly, rename its heading in your file and upload the file again. See Changing a column's match.

Important: There's no undo. Keep the copy of the file you started from, so you can see what each payment had before.

Note: An update never emails a receipt. Turn off Create deposit on transaction ledger when your file only updates payments. No updated payment is added to a deposit, so the deposit would be empty.

The import, screen by screen

The Payments page

What you see: The Payments page, with Import and Record payment at the top right. Both are greyed out while another batch of payments is still being recorded.

What to do:

  1. Click Payments in the left menu.

  2. Click Import.

What happens next: The Import Payments page opens. If you started an import earlier and didn't finish it, you're asked whether to carry on with it first.

Import Payments

What you see:

  • A bar across the top with the two steps of the import, Upload and Mapping, and a back arrow that returns to Payments.

  • The heading Import Payments 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 from your payment processor, AI analyzes your import data (Review column mappings and be sure it all looks right.) and Finish the import. Under the first step is Not sure how to lay it out? and the link Download the sample file.

  • The Upload your file box, with Browse files and the hint Drag & drop your file here, or click to browse. Below it: CSV, XLS, XLSX or PDF, up to 10 MB.

  • The My file has headers checkbox, ticked.

What to do:

  1. If you want a starting point, click Download the sample file. Replace the example rows with your own, or use your own spreadsheet.

  2. Leave My file has headers ticked if the first row of your file names the columns. Clear it if the first row is a payment.

  3. Drag your file into the box, or click Browse files and choose it.

What happens next: The upload starts as soon as you choose the file. To leave without importing, click the back arrow.

You have an import in progress

This dialog appears when you open Import Payments and you have an unfinished payment import in this association.

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? Below it: Import type (Payments), Records (the number of rows in the file), Current step (Mapping) and Last updated.

What to do:

  • Click Resume import to go back to the mapping page for that file.

  • Click Start fresh to throw that import away and upload a file. You'll see Cleared Previous import cleared. Ready for a new file!

Tip: Units and owners are matched when the file is uploaded. If you've added or changed units or owners since then, click Start fresh and upload the file again so the rows are matched against today's records.

Only you see your unfinished import. Another admin opening Import starts their own.

Reading your file

What you see: A dialog with a line of text that changes as PayHOA works, such as Uploading your file… and Reading your file…, your file's name, and a progress bar labelled Step 1 of 2 · Uploading, then Step 2 of 2 · Reading & mapping your file, with a percentage beside it. There are no buttons.

What to do: Wait. A short file takes a few seconds. A long file, or a PDF, takes longer because every payor is matched to a unit and an owner before the next page opens.

What happens next: The Edit mapped payment data page opens. If the file can't be read, the dialog closes and an Upload Error message says why. See If something goes wrong.

Edit mapped payment data

This is the one page where you check everything. Nothing has been recorded yet.

What you see:

  • The heading Edit mapped payment data.

  • A tip: AI analyzed the file, formatted your data, and matched columns. Review column mappings and see which records are new vs updates.

  • A notice: Double-check owner matches. Owners are matched to your file by name using AI, which can occasionally get a match wrong. Please review the matched owner on each row before importing.

  • A Search rows box. Type any text to show only the rows that contain it. If nothing matches, the table shows No matching records found.

  • A count line, such as 6 records will be imported • 6 new. It can also show how many rows are updating, no changes, skipped and invalid (skipped).

  • Filter buttons above the table, when your file has more than one kind of row: All records, New, Updating, No changes, Skipped and Invalid, each with a count. Only the kinds your file has are shown.

  • The table. It has a Status column, then one column for each column in your file.

  • At the top of each column: your column's name, an arrow, and a drop-down showing the PayHOA field it's matched to. An asterisk marks a required field.

  • Upload different file at the bottom left and Start import at the bottom right.

  • A key under the table explaining the icons that appear in it, such as Mapped to existing entity.

The table is wider than the page. Scroll it sideways to see the columns on the right.

The Status column shows what will happen to each row:

Status

What happens when you import

New

A payment is recorded.

Updating

The row matches a payment you already have. When the import finishes on the import page, that payment's reference number or method is changed, or a note is added to it. When the import runs in the background on the Payments page, the row is left out and nothing is changed. Either way, no second payment is recorded. See Update payments you already imported.

No changes

The row matches a payment you already have, and nothing is different. The row is left out.

Skipped

The row couldn't be read from the file and is left out. Retype that row in your file and upload again.

A warning triangle

The row has a problem and is left out. Point to the triangle to see why.

PayHOA adds up to two columns of its own:

  • Owner, when your file has no owner column. It sits straight after the payor column and shows the owner each payment will be recorded under. An info icon beside the name shows Mapped to existing entity.

  • Payment Date (Default), when your file has no date column. Every row shows today's date with a small calendar icon. Point to it to see Defaulted to today (no payment date in file).

You can't change the match on these two columns.

In the Payor (Unit) column, a matched row has an info icon. Point to it to see Matched to existing unit. When that column is the first one in your file, the cell shows what PayHOA matched instead of your text: the unit, then the owner in brackets, such as Lot 22 (Rachel McAdams). A row whose payor is an owner's name looks the same: the cell shows that owner's unit, then the owner in brackets.

The other columns show the text from your file as it is. A method such as Money order is shown as Money order here.

If your file has both a reference number and a memo, Combined into Note appears under both column headings.

What to do:

  1. Read across the column headings. Check that your unit column is matched to Payor (Unit) and your amount column to Amount, and that the date, method, reference and memo columns are matched to the right fields.

  2. Read down the Payor (Unit) and Owner columns. Check that every row has the right unit and the right owner.

  3. Check the Amount and date on each row.

  4. Look for warning triangles. Point to each one to see why that row won't be imported.

  5. When everything is right, click Start import.

You can't type in the table. To change a value, correct your file and upload it again.

What happens next: Start import opens the Payment import options dialog. Nothing is recorded until you confirm there.

Leaving this page: If you close the tab or go to another page, the import is kept as it is. Next time you click Payments → Import, you're asked whether to resume it or start fresh.

Edit mapped payment data: changing a column's match

What you see: Opening the drop-down above a column lists:

  • Skip column (do not import).

  • Payment: Payor (Unit) and Amount, both required.

  • Owner: Owner.

  • Optional: Payment Date, Reference Number, Payment Method, Note/Memo and Applies To.

A field that another column already uses is greyed out and marked (mapped). The field this column is matched to has a tick. The list is longer than the menu, so scroll inside it to see every field. A column PayHOA couldn't match shows Select a field... and is ignored unless you pick a field for it.

What to do:

  1. Open the drop-down above the column.

  2. Pick the right field, or Skip column (do not import) to leave the column out.

  3. Wait a moment while the table reloads.

If Payor (Unit) or Amount has no column, a warning appears: Required fields are not mapped. The following required fields need to be mapped: Payor (Unit), Amount. Start import stays greyed out, and pointing to it shows Map all required fields before importing.

Important: Units, owners and row problems are worked out once, when the file is uploaded. Changing which column is Payor (Unit), Owner or Amount on this page doesn't match the rows again or clear their warnings. If one of those columns was matched wrongly, rename the column heading in your file to something clear, such as Unit, Owner or Amount, and upload it again.

Edit mapped payment data: rows with problems

What you see:

  • A warning triangle in the Status column of each row that won't be imported. The rest of the row is greyed out and crossed through. Point to the triangle to read the reason, which starts This row won't be imported —.

  • A crossed-circle icon in the Payor (Unit) cell when the unit wasn't found (Could not match to a unit in your system), or in the Owner cell when the owner wasn't found (Could not match to an owner on the matched unit).

  • The count line ends with the number of rows that are invalid (skipped), such as 3 records will be imported • 3 new • 3 invalid (skipped).

  • Filter buttons above the table, such as All records (6), New (3) and Invalid (3). Click Invalid to see only the rows with problems.

  • In the key under the table: Value updated, Mapped to existing entity, Required field could not be matched. Row will be skipped. and Row won't be imported. Hover the icon for the reason.

What to do:

  1. Click Invalid to list the rows with problems.

  2. Point to each warning triangle and note the reason. The reasons are listed in If something goes wrong.

  3. Choose one of these:

    • Fix and upload again. Correct the rows in your file, or fix the unit or owner in PayHOA. Then click Upload different file, Start fresh, and upload the corrected file.

    • Import the good rows now. Click Start import. The rows with problems are left out. Later, upload a file with just the corrected rows.

Note: Some reasons end select one manually or select them manually. There's nowhere on this page to pick an owner. Fix the owner in your file or on the unit, and upload again.

Edit mapped payment data: rows that match a payment you already have

When the file is uploaded, PayHOA compares each row with the payments already recorded for that owner. A row is treated as a payment you already have when the owner and the amount are the same, and one of these is true:

  • The row has a reference number, and the existing payment has the same one. The dates don't have to match.

  • The row has no reference number, and the existing payment has the same date.

  • The row has a reference number, and the existing payment has the same date and wasn't itself imported. For example, you recorded it by hand, or the owner paid online.

What you see:

  • No changes on a row that matches and has nothing new. If every row is like this, the count line reads 6 records match your existing data. No changes will be made.

  • Updating on a row that matches and has a different reference number, payment method or memo. This is the normal result when you're updating payments on purpose. An orange icon in the changed cell (Value updated in the key) shows Previous value: and what the payment has now. Click the X beside it to leave that value alone. The count line reads, for example, 3 records will be imported • 3 updating, even though no new payment will be recorded.

  • Updating also appears when you upload a file again and nothing in it has changed, if the file has a memo together with a reference number or an Applies To value. PayHOA compares the memo in your file with the whole note it saved the first time, such as Ref# 1001 — January assessment — Applies to: Jan, so the two never match. The Previous value: in the Notes column is that saved note.

What an Updating row changes, what it leaves alone, and when the change is applied are in Update payments you already imported.

What to do: Check that each No changes and Updating row really is the same payment. If an owner made two payments of the same amount on the same day, give each a different reference number in your file and upload again, so that both are recorded.

What this means for importing a file twice: Importing the same file again doesn't record the payments twice. Every row shows No changes or Updating, never New. There are three exceptions:

  • A file with no dates. Its rows always show New, because a row with no date isn't compared with your payments until the import runs. Those payments are dated the day you import. On the same day, the repeats are left out when the import runs. If you import the file again on a later day, and the rows have no reference numbers, the dates no longer match and the payments are recorded again.

  • A row you changed. If you change the amount or the date in the file, it's a different payment and is recorded as new.

  • A reference number you added or changed. On a payment that came from the importer, a different reference number makes the row a different payment, and it's recorded as new. See Check before you import.

Upload different file?

What you see: After you click Upload different file, a dialog asks Upload different file? This will discard your current import progress. You can start fresh with a new file.

What to do: Click Start fresh to throw this import away and go back to Import Payments, or Cancel to stay on the mapping page.

What happens next: You'll see Cleared Previous import cleared. Ready for a new file! Nothing was recorded.

Payment import options

This is the last step before payments are recorded.

What you see:

  • The heading Payment import options.

  • A banner: 6 payments ready to import · $240.69 total. The count leaves out rows with problems. The total is right when the amount column comes before the date column in your file. When the date column comes first, the total is added up from the dates and is wrong: three payments of $10.50, $11.22 and $12.34 dated 11/3, 11/2 and 11/2 showed $33.00 total. Go by the amounts on the mapping page.

  • Configure how you'd like to process these payment records:

  • A switch: Email receipts to each owner associated with these payments. It starts on.

  • A switch: Create deposit on transaction ledger. It starts on. Under it are Deposit date, which starts as today, and Deposit account, which starts as the first account in your list. You only see this switch if your association has no bank account linked to PayHOA and doesn't use the PayHOA financial account.

  • Cancel and Yes, start import, and an X at the top right.

What each choice does:

Choice

On

Off

Email receipts to each owner associated with these payments

Each new payment's receipt is emailed to the owner it's recorded under, with a copy to that owner's additional email addresses. Owners with no email address get nothing. Rows that are left out, and payments that are only updated, send no receipt.

No owner is emailed. You can send one later: on Payments, click ⋯ on the payment → Send receipt.

Create deposit on transaction ledger

One deposit called Offline Payment Deposit is added to Transactions in the Deposit account, dated the Deposit date, for the total of the payments recorded. Every imported payment is linked to it.

No deposit is added. Link the payments to the bank deposit yourself later. See Link owner payments to deposits.

There's nothing in this dialog for the payment date, the payment method or which invoices are paid. Those come from your file. See Your file.

What to do:

  1. Turn Email receipts… off if you don't want owners emailed, for example when you're entering old payments.

  2. If you see Create deposit on transaction ledger: leave it on when all these payments went to the bank as one deposit, and set the Deposit date and Deposit account. Turn it off when they went in as several deposits, or the deposit is already on Transactions.

  3. Click Yes, start import.

Important: Yes, start import records the payments. There's no undo. To back out, click Cancel or the X: you go back to the mapping page and nothing is recorded.

If Yes, start import is greyed out, the deposit switch is on but there's no deposit account to choose. Turn the switch off.

If you don't see the deposit switch, link the payments to the bank deposit when it reaches Transactions. See Link owner payments to deposits.

What happens next: The payments are recorded. Depending on how PayHOA has set up your association, either you stay on this page and see Importing, or you're taken straight back to the Payments page while the import runs in the background. Both are described below.

Importing

You see this if your association's imports finish on this page. If you were taken back to the Payments page instead, skip to Importing payments on the Payments page.

What you see: A spinner, Importing... and Please wait while we process your records. This may take a few moments.

What to do: Wait, and keep the page open.

What happens next: The Payments Recorded page opens. If the import can't finish, you go back to the mapping page with an Import failed message.

Payments Recorded

What you see:

  • A check mark and the heading Payments Recorded.

  • A sentence such as 6 payments totaling $240.69 have been recorded. If receipts were sent: 6 email receipts were sent to homeowners.

  • Cards with counts: Payments created, Units matched, Payments skipped (rows with problems that were left out) and Payment imports failed. Only counts above zero are shown.

  • If some rows failed while being recorded, a notice: Some rows could not be imported. It lists up to 10 as Row 3: … with the reason, then And 2 more. Row 1 is the first payment in your file, so with a header row, Row 3 is line 4 of your spreadsheet.

  • If no payment was recorded because every row matched a payment you already have: No payments needed changes. Every row already matched.

  • Return to Payments.

What to do: Read the counts. If any rows failed or were skipped, note which ones. Then click Return to Payments.

Rows that matched a payment you already have aren't counted on this page. They're listed as Duplicates Skipped in the email you get.

Import failed

What you see: You're back on Edit mapped payment data, with a notice: Import failed and a reason, such as Import failed: 4 of 6 rows failed (66.7% failure rate exceeds 50% threshold).

This appears when more than half of the rows that should have imported failed while being recorded.

Important: The rows that didn't fail have still been recorded. Nothing is taken back. No receipts are emailed for this import.

What to do:

  1. Open Payments and see which payments were recorded.

  2. Fix the rows that failed in your file.

  3. Click Upload different file, then Start fresh, and upload the file again. Payments that already went in show as No changes and aren't recorded twice.

Don't click Start import again on the same page. That import can't be run a second time, and you'll see Cannot transition from failed to reviewing.

Importing payments on the Payments page

You see this instead of Importing and Payments Recorded if your association's imports run in the background.

What you see:

  • You're back on the Payments page. Import and Record payment are greyed out until the import finishes.

  • A card: Importing payments… with a progress bar and This runs in the background. You can leave the page and it keeps going, and we'll notify you when it finishes. On a longer import the card also shows a count such as 3 of 6 payments. A file of three payments finishes in about ten seconds.

  • When it finishes, the card reads All 6 payments were imported. If some failed: 4 of 6 payments were imported. 2 couldn't be imported. Retry them below, or contact support if this keeps happening.

  • If every row matched a payment you already have (rows marked Updating or No changes), the card reads All 0 payments were imported. Nothing was recorded and nothing was changed.

  • View Details and Dismiss.

What to do:

  1. Carry on with other work if you like. The import keeps going if you leave the page or close the tab.

  2. When the card shows the result, click View Details to open Run details. At the top it reads Payment import, the date and time, and the number of payments. Two cards show the total and count that were Recorded and Not recorded. Below them are the buttons All, Not recorded and Recorded, a search box (Search by payer, unit, status, or reason), and one card for each payment with the owner's name, the Amount and the Status, such as Recorded. If any failed, the reason is shown and you can click Retry 2 payments to try them again. Click Export run (CSV) to download the list, and Close when you're done. After an import in which no payment was recorded, Run details reads 0 payments, both cards show $0.00 and the list reads Nothing matches this filter.

  3. Click Dismiss to clear the card. The totals at the top of the Payments page update once the import has finished.

If the card reads We've lost track of this run., the import is very likely still going. Click Check again. Don't start the import a second time.

In this flow:

  • Each payment is recorded on its own. One that fails doesn't stop the others, and there's no Import failed page.

  • Receipts are emailed as each payment is recorded.

  • A row marked Updating on the mapping page is left out. The payment it matched isn't changed, and nothing on the card or in Run details says so. To change those payments, edit them by hand. See Update payments you already imported.

After the import

Where the payments are. On the Payments page, with the method Check (offline) or Cash (offline) and the source Offline, dated with each row's payment date. Recorded by shows the person who ran the import. Each one is also on its unit's Account history. See Find, filter and export payments.

What was done for you:

  • Each unit's invoices were marked paid, oldest first or as Applies To said, and the owner's balance went down.

  • Any overpayment became account credit on the unit.

  • A note was added to each payment with its reference number, memo and Applies To text, such as Ref# 1001 — January assessment — Applies to: Jan. Click a payment and open Notes to see it.

  • Receipts were emailed, if you left that switch on.

  • You were emailed a summary titled Payments Import Complete, or Payments Import Completed with Errors. It lists the rows that were skipped and the rows that failed, with the reason for each.

What wasn't done:

  • No late fees were removed. A late fee that was already charged stays on the unit.

  • Future invoices weren't paid.

  • If you didn't add a deposit, the payments aren't linked to a bank deposit yet.

In your books. A Check or Cash payment reduces what the owner owes straight away. On accrual reports, the money sits in Undeposited Funds until the payment is linked to a bank deposit. On cash-basis reports, it only counts as income once it's linked to a deposit and that deposit is approved. See Link owner payments to deposits and Cash vs accrual and the fiscal year. A payment recorded as Account Credit isn't treated as money received. See the warning under Your file.

What to check:

  1. On Payments, find the new payments and compare the count and total with your file. They're dated with the payment dates from your file, not the day you imported.

  2. Open two or three units and check Account history: right owner, right amount, right invoices paid.

  3. Check the Method of the new payments. If any show Account Credit that should be Check or Cash, delete them, add a method to those rows and import them again.

  4. Open Transactions and look for an Offline Payment Deposit. There should be one only if you asked for a deposit, in the account you chose, dated with your deposit date, for the total of the payments recorded. If you asked for one and it isn't there, link the payments to your bank deposit yourself.

Fixing a mistake:

  • One payment is wrong. Edit its amount, date or note, or delete it and record it again. Imported payments can be edited and deleted like any payment you recorded. A payment that's linked to a deposit must be unlinked first. See Edit, delete or fix a recorded payment.

  • A payment went to the wrong unit or owner. Delete it and record it on the right one.

  • The whole import is wrong. On Payments, tick the imported payments and choose Actions → Delete payment(s). If the import added a deposit, unlink the payments from it first, then delete the empty deposit on Transactions. See Exclude, delete or fix duplicate transactions.

  • Check and Cash are mixed up, or a note is missing, on many payments. If your imports finish on the import page, correct the file and import it again as an update. If they run in the background on the Payments page, an import won't change them: edit each payment. See Update payments you already imported.

  • Some rows were left out. Fix them and import a file with just those rows. Importing the full file again is also safe: the payments that already went in show as No changes or Updating, not New.

  • A check bounced. Don't delete it. See Mark a check as returned.

If something goes wrong

Before or during the upload

Message

What it means and what to do

You are not authorized to view the requested page

You don't have Admin Status. Ask an admin to run the import or to give you access.

Unsupported file type. Please upload a CSV, XLS, XLSX, PDF file.

Save the file as CSV, XLS, XLSX or PDF. A Google Sheets link or a Numbers file won't work: download it as CSV or Excel first.

File is too large. The maximum file size is 10MB.

Split the file and import the parts one at a time.

That file is empty. Please upload a file that contains data.

The file has nothing in it. Check you chose the right one.

Could not detect column headers in the file. Please check the file format.

PayHOA found no column names. Add a header row, or clear My file has headers. In a PDF, this means no table was found: use a spreadsheet instead.

No data rows found in the file. Please check the file contains data.

The file has column names but no payments under them.

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.

Do what it says.

Failed to read CSV headers. or Excel file is empty.

The file is blank or damaged. Open it, check it has your payments, save it again and upload it.

Failed to extract data from PDF: …

The AI couldn't read a table from the PDF. Export the data as CSV or Excel instead.

Failed to process file. Please try again. or Failed to process file. Check the file type and size, then try again.

Something went wrong while the file was being uploaded or read. Refresh the page and try again. If it keeps happening, contact PayHOA support with the file and the time you tried.

You do not have permission to import payments for this organization.

Your access changed. Ask an admin.

On the mapping page

Message

What it means and what to do

Required fields are not mapped The following required fields need to be mapped: Payor (Unit), Amount

No column is matched to the field named. Pick it above the right column. See the Important note under Changing a column's match.

Map all required fields before importing

The tooltip on a greyed-out Start import. Same fix.

Failed to load mapping data

The page couldn't load the import. Refresh. If it still fails, click Payments → Import and choose Start fresh.

Failed to save mapping

Your change to a column's match wasn't saved. Try again.

Reasons a row won't be imported

Point to a row's warning triangle to see these. Each starts This row won't be imported —.

Reason

What to do

"…" does not match any unit or owner in this organization

PayHOA couldn't find that unit or owner. Use the unit's name exactly as it is in PayHOA, or add the unit first. See Add a unit.

Payor is required

The row has no unit. Fill it in.

"…" matched an owner with no unit — payments need a unit to post to

The name matched a person who isn't on a unit. Put the unit in the row instead.

"Jane Doe" is not an owner on unit 101 (owners: John Smith). Fix the owner in the file or select one manually

The Owner column names someone who isn't an owner of that unit. Correct the name, clear it to use the unit's first owner, or add the owner to the unit. See Add or remove owners on a unit.

Unit 101 has no owners. Add an owner to the unit, then select them manually

Add an owner to the unit, then upload the file again.

Unit 101 has owners but none with a name. Add the owner's name, then select them manually

Give the owner a first or last name on their profile, then upload again.

No owner could be matched on the unit. Select an owner manually

Put the owner's name in an Owner column and upload again.

Payment amount is required

The amount is blank.

"abc" is not a valid payment amount or Payment amount is invalid

The amount isn't a plain number. Remove text, brackets and extra decimals.

Payment amount cannot be $0

Take the row out, or correct the amount.

Payment amount $1,500,000.00 exceeds maximum allowed ($1,000,000)

Check the amount. If it's right, split it into more than one payment.

"13/45/2026" is not a valid payment date

Use one of the date formats under Your file.

Payment date cannot be in the future

Correct the date. Payments can't be dated after today.

"eCheck" is not a supported payment method

Use Check or Cash, or another value from the list under Your file.

Reference number is 40 characters. It must be 31 characters or fewer

Shorten it, or move the extra text to the memo column.

missing required field: Amount

The row has nothing in a required column. Fill it in.

When the import runs

Message

What it means and what to do

Import failed Import failed: 4 of 6 rows failed (66.7% failure rate exceeds 50% threshold)

More than half the rows failed. The rest were still recorded. See Import failed.

Some rows could not be imported. Row 3: No owner matched for this payment. Please select an owner manually.

The unit's owner couldn't be worked out. Add an Owner column, or fix the owner on the unit, and import that row again.

Row 3: Owner ID … not found or does not belong to this organization.

The owner was removed from the unit after you uploaded the file. Upload it again.

Row 3: Unsupported payment method "…" — only offline payments (check, cash, account credit) can be imported.

Use Check or Cash on that row and import it again.

Row 3: Matched payment could not be found to update.

The payment this row matched was deleted after you uploaded the file. Upload it again.

This import session can no longer be committed. or 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.

This import has already finished or failed. Click Upload different file, then Start fresh, and upload the file again. Payments already recorded are left out as No changes.

A message that mentions Http failure or a time-out

The page lost touch with PayHOA while the payments were being recorded. Open Payments and check whether they're there before you try again. Then upload the file again: anything already recorded shows as No changes.

Common questions

Do owners get an email when I import payments? Yes, by default. Each owner gets a receipt for their payment. Turn off Email receipts to each owner associated with these payments in the Payment import options dialog if you don't want that.

Does importing charge the owner's card or bank account? No. An import only records payments you've already received. Nothing is collected and no processing fees apply.

Can I change many payments at once? Only a few details, and only when your import finishes on the import page. There, an import can change the payment method on payments you already have, add a note to them, and set a reference number on payments you recorded by hand. It can't change amounts, dates, units or invoices. When imports run in the background on the Payments page, an import doesn't change existing payments at all. See Update payments you already imported.

I already recorded these payments. Can I import a file to add the check numbers or memos? Only if your import finishes on the import page, with Payments Recorded. There, a row that matches a payment you already have can add a note to it, change its payment method, and set a reference number on a payment that didn't come from the importer. If your imports run in the background (Yes, start import takes you back to the Payments page with an Importing payments… card), the matching rows are left out. Nothing is added, the card reads All 0 payments were imported., and no message says why. In either case an import can't add or change an amount, a date or the invoices a payment paid. To add a check number or a memo yourself, click ⋯ on the payment → Edit and type it in Notes, for example Check #1042. The method can't be edited; to correct it, delete the payment and record it again. See Edit a payment and Update payments you already imported.

Will importing my payments again create duplicates? Not if the unit, owner, amount and date in each row are unchanged and every row has a date. Those rows show Updating or No changes, and no second payment is recorded. A row that shows New will be recorded as a second payment, which happens if you change an amount or a date, or add or change a reference number on a payment that came from the importer. See How PayHOA decides a row is an update.

I imported the same file twice. Are the payments doubled? No, as long as the rows have dates. The second time, every row shows No changes or Updating instead of New, and no second payment is recorded. If your file has no date column and no reference numbers, and you imported it on two different days, the payments were recorded twice: delete the extra ones. See Edit, delete or fix a recorded payment.

An owner paid more than they owed. Where did the extra go? It became account credit on the unit and pays the unit's next invoices automatically. See Account credit.

Can I choose which invoice a payment pays? Partly. Put a month or the invoice's title in an Applies To column, and that invoice is paid first. You can't set an amount for each invoice. For that, record the payment by hand with Apply to specific charges.

The payment went to the wrong owner on a unit with two owners. With no Owner column, the payment goes to the unit's first owner. Delete the payment, add an Owner column with the right name, and import that row again, or record it by hand.

Can I edit or delete an imported payment? Yes, the same as a payment you recorded by hand. See Edit, delete or fix a recorded payment.

Why do my imported payments show the method Account Credit? Those rows had no payment method, or a method such as ACH or Card. See Payment methods PayHOA accepts.

Can I import payments owners made online somewhere else? Yes. They're recorded as offline payments. Rows labelled ACH, Card or similar are recorded with the method Account Credit. See Payment methods PayHOA accepts.

Is this the same as importing lockbox payments? No. The lockbox import reads the file Alliance Bank sends and has its own page and settings. See Lockbox payments.

Can I import a PDF? Yes, if it contains a table of payments. The AI reads the table out of the PDF, so check every row with extra care. A spreadsheet is more reliable.

Can two admins import at the same time? Each admin has their own unfinished import. If both import the same payments, the second import leaves them out as payments you already have.

What's next

Did this answer your question?