Confirm the Table Boundaries

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

Confirm is the fourth step of the mapping editor. The editor shows it as Step 4 of 6 · Confirm.

The table boundaries tell the mapping which rows hold the column headings and which rows are real data. The step proposes them for each sample, and you correct them and confirm. Every future file from this customer is read against what you confirm here.

Field mapping and Test and validate stay locked until you confirm. When this step is done, go to Review the field mappings.

Row markers

The row-number column of the grid marks each row. The following table lists the markers.

Table 1. Row markers on Confirm

Example: a remittance with a subtotal and a total

Figure 1 shows the Northwind Traders sample. It has a header block and a table, followed by a subtotal and a total. The step reads it like this:

• Rows 1 to 5 hold the header block, from the title to the cheque number. The block also gives the client, the payer, and the payment date.
• Row 6 is empty, so it is marked ○.
• Row 7 holds the column headings, from Invoice Number to Status. It is marked H.
• Rows 8 to 12 hold the five invoice lines. Row 8 is marked F and row 12 is marked L.
• Row 13 holds Subtotal and row 15 holds Total Paid. Both are marked !.

A warning above the grid reads 2 rows with values aren't part of any table (highlighted below). Mark them into a table, or they'll be skipped. Here, leave both rows outside the table, because they are not invoice lines. The header block still feeds header fields such as Payment Date. The totals come from rules on Field mapping.

Figure 1. Table boundaries with the subtotal and total rows outside the table

Confirm the boundaries

The grid shows the primary sample first. To see another sample, select its name above the table. To add a sample, select + beside the names.

1. Review the table for the file shown.
2. Review the markers in the row-number column.
3. To move a marker, point to the row. Then select Header, First, or Last.
4. Review the rows marked !. Mark a row into a table only if it holds data you want read as a line. To mark a row under the table, point to it and select Last. It becomes the table's last row, and the warning counts one row fewer.
5. On the Structure view, select Confirm boundaries. The button is not on the Tables view.

The page locks while the mapping is set up. Setting up your mapping reads Reading every sample file against the boundaries you just confirmed. It lists these stages:

• Detecting this customer’s formula rules
• Matching your master fields to the columns
• Learning how to find the tables in future files
• Reading the email samples for the fields that come from them

It notes that this usually takes a few seconds. Then Field mapping opens. On this step and on Field mapping, Expand to full window gives the grid the whole window.

Figure 2. The mapping being set up after Confirm boundaries

Confirm a sheet with more than one table

A sheet can hold more than one table, such as invoice lines followed by credit notes. Each table has its own markers. The help text above the grid reads Select a table above, then hover any row to mark it as that table's header, first, or last data row. Every table's range stays highlighted, and the selected one is brightest.

In the Northwind Traders example, Table 1 holds three invoice lines and Table 2 holds two credit notes.

1. On the Structure view, find Tables in this sheet. It lists each table found, such as Table 1 and Table 2. The Tables button counts them, for example Tables (2).
2. If the sheet has a table that the list misses, select Add a table. A new table joins the list, for example Table 3 (shared header). The count goes up, for example to Tables (3).
3. Select a table, for example Table 2. Its range becomes the brightest.
4. Check the selected table's markers. In the example, Table 2 has its header on row 14 and its data on rows 15 and 16.
5. To move one of its markers, point to the row. Then select Header, First, or Last. The other tables keep their markers.
6. Repeat steps 3 to 5 for each table.
7. If a table holds rows you do not need as line items, such as credit notes, remove it. A line item field shows Error when a table has no column for it. Select its remove icon, for example Remove table 2. The table is removed at once, with no confirmation. Its rows then show !, as rows outside every table, and are skipped.
8. Select Tables to check the rows of each table. With both tables kept, each table shows its row count, for example Table 1 · 3 rows and Table 2 · 2 rows.
9. Select Structure, then select Confirm boundaries. The list of steps then shows, for example, 2 tables · 1 file under Confirm.

The mapping reads line items from every table. In the example, both tables are kept. The test counts 5 line items: 3 from Table 1 and 2 from Table 2.

A line item field looks for its column in each table. If a table has no such column, the field shows Error on Field mapping. Table 2 in the example has no Invoice Date or Invoice Amount column. So Invoice Date and Invoice Total Amount show errors, such as Column "Invoice Date" not found in this table. Activate then shows, for example, Resolve 2 field errors before activating.

In the example, removing Table 2 before you confirm leaves Tables (1). No field then shows an error, and the test counts 3 line items with No field errors.

Remove a table after you confirm

After you confirm, the step is locked. It reads Boundaries confirmed for every file and sheet — rule detection and auto-mapping ran against these. Add a table is unavailable.

Caution: Confirming again runs the first pass again, so the field mappings can change. The number of rules can change too. In the example, Rules 2 became Rules 4. Note how each field is mapped before you start, and review every field before you test. See Update a mapping for a new file layout in Manage AR remittance mappings.

1. In the list of steps, select Confirm. Then select Structure.
2. Select Unlock. No confirmation is asked. The remove icons, Add a table, and Confirm boundaries come back.
3. Select the table's remove icon, for example Remove table 2.
4. Select Confirm boundaries. The mapping reads every sample again, and Field mapping opens.
5. Run Test and validate again.

In the example, the two column errors are gone after the second confirm. The test then counts 3 line items with No field errors.

Confirm a workbook with more than one sheet

A sample workbook can hold several sheets, and each sheet has its own tables and markers. The Northwind Traders workbook in this example has three sheets: Remittance, Credit Notes, and Notes. Selecting Confirm boundaries once confirms the tables of every sheet.

1. On the Structure view, read the banner above the grid. It reads One mapping spans sheets with different roles · detected by AI, then lists each sheet with its role. Here the roles are Remittance · data, Credit Notes · lookup, and Notes · notes. The banner adds Each field can be sourced from any sheet — set “From sheet” in a field’s editor.
2. In Sheet, choose a sheet, for example Credit Notes. The grid shows that sheet's own tables and markers. The line beside Sheet counts its rows, for example 3 rows in sheet.
3. Review the sheet's tables and markers, as in Confirm the boundaries on this page.
4. Repeat steps 2 and 3 for each sheet.
5. On the Structure view, select Confirm boundaries. The list of steps then counts the tables of all the sheets, for example 3 tables · 1 file.

On Test and validate, the test reads the data sheet. On Field mapping, a line item field's panel offers From sheet, with a list of the sheets. See Field sources and rules.

After you save and reopen such a mapping, From sheet is no longer offered. For what that changes, see Known limitations in AR remittance mapping messages.

If a saved mapping already covers the format

If a sample matches a mapping you already saved, the step shows A saved mapping already covers this format. The banner gives a match percentage. It names the saved mapping and its customer. It also names the sheet that matched and the mapping's status.

Select why? to see the evidence. It can cover these points:

• the column headings
• the labels above the table
• the column types
• the layout
• the file name pattern
• the customer

Select hide why to close it.

For example, suppose you build a second Northwind Traders mapping from a copy of the same file. The banner then shows 100% match with the saved draft. Its evidence includes headers 6/6 matched and customer matches the file (Northwind Traders).

A weaker match reads the same, with a lower percentage. Its evidence shows partial counts, such as header labels 4/5 matched. Other close mappings follow also close: at the end of the banner.

Caution: The saved mapping can be the customer's live mapping. Saving it with Save draft makes it a draft and takes it out of service. If you leave without saving, it stays as it was.

• To keep building this mapping, select Dismiss.
• To work on the saved mapping instead, select Use this mapping. The saved mapping opens on Field mapping, with the file you uploaded as its only sample. Its table boundaries stay confirmed.

Figure 3. A sample that matches a saved mapping, with the evidence shown

Structure and Tables views

Two views sit above the grid. Structure shows the sheet with its markers. Tables shows each table found in the sheet, with a count such as Tables (1). Sheet shows the sheet you are viewing, and a line beside it counts the rows in the sheet. In a workbook with more than one sheet, Sheet lists every sheet. See Confirm a workbook with more than one sheet on this page.

In the Tables view, each table is listed with its rows and a row count, such as Table 1 · 5 rows.

Tables in this sheet lists each table found, such as Table 1 and Table 2. Before you confirm, each table has a remove icon when the sheet has more than one. Add a table adds another. After you confirm, select Unlock first. See Confirm a sheet with more than one table on this page.

A banner above the grid shows how the mapping treats the sheets. For samples with one layout, it reads Same mapping applies to every data sheet · detected by AI. For a workbook whose sheets differ, it lists each sheet with its role.

If no two samples share their columns, a warning reads These files are not the same format. Build a separate mapping for each layout. See Messages on Confirm in AR remittance mapping messages.

Figure 4. The Tables view with one table found in the sheet

Related information

• Choose the master fields
• Review the field mappings
• AR remittance mapping overview
• AR remittance mapping messages