Who this is for. SmartCustomer users with the SuperAdmin role.
Availability. The AR Mapping tab appears in SmartCustomer when AR Mapping is enabled for your organization.
Overview
Master fields is the third step of the mapping editor. The editor shows it as Step 3 of 6 · Master fields.
Master fields are the standard header and line fields that every customer's remittance is normalized to. They come from your Payment record, so their names match the document view. On this step, you review the fields the mapping fills. For each field, you also choose whether its value comes from the file or from the email.
When this step is done, go to Confirm the table boundaries.
Header and line fields
The list has two kinds of field:
- Header fields hold one value per document. Examples are Payment Number, Payment Date, and Total Amount.
- Line fields hold one value per row of the table. Examples are Invoice Number and Invoice Date.
Above the list, a line counts the payment fields in your Payment record, for example 29 payment fields from your Payment record. The count depends on your Payment record.
To show only one kind of field, select Header or Line. To show every field, select All. To find a field by name, type in the search box. The box shows Search fields… until you type. If no field matches, the list shows No fields match your search.
Field details
Selecting a field opens its details beside the list. The following table describes what the details show.
Table 1. Parts of the field details
| Part | What it shows |
|---|---|
| Name and tags | The field name, its tag (Header or Line), and its data type. Then the field's key, such as paymentNumber
|
| Source | Where the mapping reads the value: File or Email |
| Section | Whether the field is a header field or a line field, for example Header — one value per document |
| Data type | The kind of value, for example Text |
| Description | What the field holds, from your Payment record |
Under the details, a note reads Name, section and data type come from your Payment record, so they match the document view. Change them there, not here. The details also show an In this mapping check box, which is unavailable.
Set the fields that come from the email
Email is offered only after you add an email sample on Email samples. Until then, Source offers only File, and its note reads Read from the remittance file. Add an email sample on step 2 to read a field from the email instead.
- Select a field to see its details.
- If the customer states this value in the email, set Source to Email. The field then shows an Email badge in the list. If you later switch a mapped field back to File, Field mapping shows it as Not mapped. Switching it to Email again leaves it Not mapped until you select its value there.
- Repeat steps 1 and 2 for each field that comes from the email.
- Select Next.
With an email sample, each choice has its own note under Source:
- File: Read from the remittance file. Choose Email when this customer states it in the email instead.
- Email: Read from the email’s subject or body. Field mapping offers what the email samples state, and you can highlight anything it missed.
For example, in Figure 1 Payment Number is set to Email. The Northwind Traders email states the payment reference, and the file holds only the cheque number. For how that field is then mapped, see Add email samples.
Figure 1. A master field set to come from the email
Limits of this step
You cannot add or remove fields on this step. Add field is unavailable, and so is the check box beside each field.
To keep a copy of the field list, select Export master fields. It downloads the list as master-fields.json.