Manage Customers

Customers list with editable customer records

Create and maintain customer records so invoicing, payment follow-up, and customer-specific receivables workflows start from clean setup data.

When to use this

Use this guide when you need to add, update, search, import, or review customer records before creating invoices, receiving customer payments, or assigning customer context to money-in bank activity.

Before you start

  • You can open the Customers page.
  • You know the customer name.
  • If you plan to use customer defaults for invoicing, you know the income account, payment terms, or credit settings you want to apply.
  • You understand whether this customer should use standard terms, restricted credit handling, or manual review before invoicing.

Steps

  1. Open Customers.
  2. Decide how you want to work with the list:
    • Use New to add one customer from the drawer.
    • Use Import if you already have customer data in a spreadsheet or CSV file.
    • Use More > Enable Grid Mode if you want to make several edits in one pass, or turn on Grid Edit default in Preferences if you want supported pages to open that way automatically.
  3. When creating or editing a single customer, complete the core record details:
    • Name is required.
    • Company, Email, and Phone support billing and follow-up workflows.
    • Address fields help complete the customer profile when you need them.
  4. If you want invoices for this customer to start from a consistent sales setup, set Default Income Account.
  5. If you track customer payment expectations, open Payments & Credit and review the available settings:
    • Credit limit
    • Credit status
    • Terms
  6. Decide whether this customer needs setup beyond the basic record:
    • Keep the record simple if you only need contact details.
    • Add payment terms when invoices should usually follow a standard due-date pattern.
    • Add credit settings when your team wants a visible review signal before opening new invoices.
  7. Save the customer.
  8. Use the page tools to manage or review the list after setup:
    • Search by name, company, email, or phone.
    • Filter for Active or Inactive customers when cleaning up the list.
    • Open row actions for an existing customer when you want to create an invoice, create a payment, or jump into that customer’s AR Aging report.
  9. If the customer will be invoiced often, pair this setup with saved item records and invoice account review before the first live invoice.
  10. In Banking, customer names can also help money-in review:
    • Pending bank rows can offer customer choices alongside vendor choices where the current UI exposes grouped parties.
    • Banking import preview can resolve Customer, Customer ID, or shared Customer/Vendor style columns for inflow or sale rows.
    • Add unknown customers (n) creates setup records from unique unresolved customer names in the current import preview batch when you choose to use it.
  11. When importing customers from QuickBooks Desktop data, review billing address fields after import.
    • QuickBooks-style BADDR1 through BADDR5 values can be preserved as structured billing address data.
    • SPRK can place the first billing line into address line 1, keep remaining non-city lines in address line 2, and parse a final City, ST ZIP line into city, state, and postal code when it is recognizable.
    • Review any address that does not follow that pattern before using it on customer-facing invoices.
  12. Use Grid Edit when post-import cleanup or repeated customer-field updates will be faster than opening one drawer at a time, then review the changed-cell count before selecting Apply Changes.

What happens next

The customer is saved and available for invoice selection, payment workflows, Banking party assignment, search, import cleanup, and customer-specific receivables follow-up.

Assigning a customer to a bank row adds party context. It is not the same as matching the bank row to an open invoice payment; use the Banking match workflow when the row should receive an invoice payment.

If something looks wrong

What You See What To Check What To Do Next
Two similar workflows or fields are easy to mix up Treating Credit status as a payment record It is a setup signal, not the same thing as receiving money