Skip to main content
Share / Export

AR Customers

Company Tracker action: implementation-setup-ar-customers Milestone: Accounts Receivable / Module Setup (milestone_id=7, core_milestone_id=2) Order: 3 Estimated duration: 1 hour Typical owner: Controller / Billing

Purpose​

Load the customer master used on contracts, invoices, cash receipts, and statements so go-live billing and open/YTD AR tie out.

Prerequisites​

  • HQ Payment Terms and tax codes exist when used as defaults.
  • AR Receivable Types exist when assigned at customer level.
  • AR Company Parameters email / statement settings ready if statement delivery is in scope.
  • Open contracts and year-to-date activity customers identified for the minimum load.

Vista configuration article​

See the detailed Vista guide:

Setting Up AR Customers

Field meanings and form steps live there. Do not restate them on this page.

Implementation guidance​

  • Load scope: Many clients import customers used in the past one or two years (same idea as AP vendors). Customer lists are often smaller, so most clients bring the full list. At minimum, load every customer on open contracts and any with year-to-date activity.
  • Addresses: Include mailing and billing. Billing address defaults on invoices and can be overridden on the contract and/or invoice.
  • Payment terms: Keep terms accurate on the customer — they drive due-date defaults on invoices. Required for clean AR entry.
  • Tax code: Optional customer default when the customer always uses the same code. More often tax is driven at the contract (billing) level — leave customer tax blank when that is the case.
  • Statement delivery: Fill email when statements will be emailed. Add a recipient on the customer (used for the send). Most important: check Print/Email Statements or that customer is excluded from statement delivery.
  • Receivable type: Optional on the customer; when contracts are in play, contract JB Info usually wins (see Receivable Types).
  • Accept means Controller/Billing confirms go-live customers, terms, addresses, and statement flags for every bill-to that must receive statements.

Tips and gotchas​

  • Minimum load = open + YTD activity customers; full list is common because AR masters are smaller than AP.
  • Billing address is the invoice default; override lives on contract/invoice.
  • Statement email needs recipient + Print/Email Statements checked — email alone is not enough.
  • Terms on the customer matter for due dates; tax more often lives on the contract.

Done when​

  • Open and YTD (or full) customer set is loaded with mailing/billing addresses as needed.
  • Payment terms accurate on go-live bill-tos.
  • Statement recipients and Print/Email Statements set for every customer in statement delivery.
  • Tax/receivable type defaults documented (customer vs contract) when used.