---
title: "Importing Customer Payments"
canonical: "https://kb.myframeworks.com.au/space/CO/30510180/Importing%20Customer%20Payments"
format: markdown
---
Import customer payments from a .csv file into Frameworks to add multiple payments at once for allocation against customer accounts, rather than entering each payment manually.

> 📝 ## Prerequisites
> 📝 
> 📝 - Customer records exist in Frameworks for every customer ID included in the import file.
> 📝 - Bank accounts to be referenced in the import file are configured in **Company Maintenance**.
> 📝 - The import file is saved as a .csv with the columns and format described in the Import File Format section.
> 📝 - Access to the **Customer Payments** screen.

## Steps

1. Click the **Frameworks Menu** and navigate to **Receivables > Transaction Processing > Customer Payments**.
2. Click **Import Payments **to open the **Customer Payments Import **window.
3. From the **Company** drop-down menu, select the company you are importing payments into, if you have access to multiple companies.
4. Click **Upload,** to open the **File Upload** window.
5. In the **File Upload** window, drag and drop the .csv file or click to browse your computer for the file, then click **Upload**.
6. In the **Customer Payment Review** window, check the imported details against the source file. Any rows with errors display a message in the **Remarks** section at the bottom of the window.
7. Resolve any errors using one of these methods:
  - Click directly into the field on the row to correct the value.
  - Click the delete icon at the end of the row to remove the payment from the import.
  - Close the window, correct the .csv file, and re-import.
8. Click **Submit** to process the payments.

## Result

The payments are created as direct credits against the customer accounts shown in the import file and are listed for allocation through the standard payment allocation process. Each payment is recorded against the bank account specified in the **Bank Account** column of the import file. Where the **Bank Account** column is left blank or contains an invalid bank account number, the payment is recorded against **Bank Account 1** as defined in **Company Maintenance**.

> ✅ ## Related Tasks
> ✅ 
> ✅ - [Allocating Payments](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30515668)
> ✅ - [Customer Payments - Overview](https://sterlandsupport.atlassian.net/wiki/spaces/fwksproau/pages/30510956)

> ✅ ## Related Information
> ✅ 
> ✅ - [Company Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28382666)
> ✅ - [Customer Payments Screen - Field Definitions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28403472)

---

## Additional Notes

### Import File Format

The import file must be a .csv with the following columns in this order:

- **Payment Date** — The date the payment was made.
- **Customer ID** — The customer code the payment is to be applied to.
- **Amount** — The payment amount.
- **Bank Account** — The bank account number the payment is recorded against. This column is optional. If left blank or if the number does not match a configured bank account, the import uses **Bank Account 1** from **Company Maintenance**. Any special characters entered in this column are automatically stripped out during import.

Validations applied to the **Bank Account** column when it contains data are the same as those applied when entering a bank account manually in the Customer Payments screen.

### Working With the Remarks Section

The **Remarks** section in the **Customer Payment Review** window lists every validation error from the import, identified by line number (for example, `Line#6 - Invalid customer ID entered [49487]`).

The **Remarks** section does not refresh as you correct errors in the grid. To confirm that all errors have been resolved before submitting:

- Copy the contents of the **Remarks** section to a notepad or text file as a reference list.
- Close the **Customer Payment Review** window, correct the errors in the source .csv file, and re-import.

Re-importing the corrected file produces a fresh **Remarks** section that reflects the current state of the data.

### Saved Import Files

If a you had previously saved an import file template without this column, re-saving the import is recommended so the **Bank Account** column is included.