Customer account fields
Under Customers → Accounts.
The Acts column is the one to read. A field marked records is stored and displayed, and nothing in Yessort reads it — see what an account decides.
Identity
| Field | Acts | Notes |
|---|---|---|
| Account name | — | The business's name |
| Code | — | Your short identifier for it. Required |
| Organisation | Yes | Which of your organisations holds the relationship |
| Type | Partly | Trade, Inter-company or Reseller. See account types and statuses |
| Status | Yes | Whether you are currently trading with them |
Commercial
| Field | Acts | Notes |
|---|---|---|
| Currency | Yes | The currency of the account's orders |
| Payment terms (days) | Yes | First fallback after the customer's own terms — see payment terms |
| Credit limit | No — records only | Nothing checks it. No order is blocked, held or flagged for exceeding it |
| Invoicing strategy override | Yes | Channel default, Per-order invoice, Daily summary or Deferred. Overrides the channel |
| Fulfilment policy | No — records only | Strict (whole-line only) or Partial allowed. Nothing reads it; picking behaves the same either way |
| Xero contact id | Yes | The reference used when posting this account's documents |
The two that only record
Credit limit. The name implies enforcement and there is none. An account with a £5,000 limit can place a £50,000 order and nothing stops it. Useful as a note of your arrangement; not a safeguard.
Fulfilment policy. Describes an intention about sending part of a line when the whole cannot be sent. Nothing acts on it.
Both are worth setting if they record something a colleague should know. Neither will enforce it.
Invoicing strategy override
| Value | Meaning |
|---|---|
| Channel default | Do not override. The channel decides |
| Per-order invoice | Each order gets its own |
| Daily summary | A day's orders combined into one |
| Deferred | Settled later rather than invoiced per order |
This beats the channel's setting. One thing beats it in turn: an order paid by more than one payment method always gets its own invoice. See invoicing strategies.
Not on the account
A price list. An account cannot be given its own from the Yessort screens — there is no field for it. See sales price lists.