Create an AR Remittance Mapping

Written by Uday Kumar Updated March 30, 2026 09:22

Overview

Use the AR Mapping page in SmartCustomer to create a reusable remittance mapping for a customer.

A mapping defines how the fields in a customer’s remittance file correspond to Auditoria’s standard header and line-item fields.

Before You Begin

Make sure you have:

Access to SmartCustomer
The correct ERP, Entity, and Mailbox are selected
A sample remittance file for the customer
A basic understanding of which fields in the file contain payment-level and line-level data

Sample file guidelines

Use a representative remittance file that:

Matches the customer’s actual layout
Includes the worksheet you want to extract
Contains header and line item data
Is in Excel format, such as .xlsx or .xls

Step 1: Open AR Mapping Page

To open the AR Mapping page:

In the left sidebar, select SmartCustomer.
In the top horizontal navigation bar, click AR Mapping.

The AR Mapping page opens.

Figure 1. Navigating to the AR Mapping Page

Step 2: Select Customer

In the Create a new mapping dropdown, select the customer you want to configure

The Personalize Mapping for the customer page opens.

Figure 2. Select Customer

Step 3: Upload Remittance File

In Step 1: Upload Remittance File:

Click the upload area
Select the customer’s remittance file
Confirm that the file name appears

If you selected the wrong file, upload a different file before continuing.

Figure 3. Upload Remittance File

Step 4: Select Worksheet

If the uploaded workbook contains multiple sheets:

Use the Select Sheet dropdown
Choose the worksheet that contains the remittance data

Then click Upload and Process.

The system processes the file and detects available fields.

Note: If no sheet is selected, the system may use the first sheet by default.

Figure 4. Select Worksheet

Step 5: Understand Source Fields and Auditoria Fields

After processing completes, the page displays two mapping sections:

Step 2: Customize Header Mapping
Step 3: Customize Line Items Mapping

Each section includes:

Input file fields on the left
Auditoria Fields on the right

You use these dropdowns to define how the customer’s file maps into Auditoria.

Input file fields are customer-specific

The Input file fields come directly from the uploaded customer file. These fields may vary by customer, file layout, and worksheet.

For example, one customer might provide:

Date
Invoice Date
Payment Date
Batch
Payer
Claim Number
Total Payable

Another customer may use different names for similar information.

Because customer remittance formats are not standardized, the source fields on the left side can change from one customer to another.

Auditoria fields are standardized

The Auditoria Fields are the standard target fields used by Auditoria to normalize remittance data across customers.

These fields remain consistent in the product and represent the meaning of the data Auditoria expects, such as:

Payment Date
Payment Number
Batch Number
Invoice Number
Amount To Pay

Table 1. Understanding Source Fields

Customer source field	Meaning in the customer file	Auditoria field
`Date`	Payment date	Payment Date
`Payment Dt`	Payment date	Payment Date
`Invoice Date`	If used by the customer as remittance/payment date, based on business meaning	Payment Date
`Batch`	Batch identifier	Batch Number
`Total Payable`	Amount being paid	Amount To Pay

The purpose of the mapping is to align each customer-specific source field to the correct standardized Auditoria field.

Figure 5. Review Detected Mappings

Step 6: Configure Header Mapping

Use Customize Header Mapping to map payment-level fields.

These fields typically describe the remittance as a whole.

How header mapping works

For each row:

Select a source field from Input file fields (Headers)
Select the matching target field from Auditoria Fields

Repeat until the required header fields are mapped.

Important note

The source field names may differ by customer, but the Auditoria target fields remain standardized.

For example:

A customer source field called Date may map to Payment Date
A customer source field called Payer may map to Customer Name
A customer source field called Batch may map to Batch Number

Use None when needed

If a header field should not be extracted:

select None

This is useful when:

the field does not exist in the customer file
the field is not needed
you do not want to use that value for this mapping

Auditoria Header Fields

The following table describes common Auditoria header fields available for mapping.

Table 2. Auditoria Header Fields

Auditoria field	Description	Example customer source labels
Entity	Identifies the business entity associated with the remittance.	Entity, Company, Business Unit
Batch Number	Identifies the batch associated with the payment or remittance.	Batch, Batch ID, Batch Number
Customer Name	Identifies the customer, payer, or remitting party.	Customer, Client, Payer
Currency	Currency used in the remittance or payment.	Currency, Curr, Payment Currency
Payment Date	Date associated with the payment or remittance.	Date, Payment Date, Payment Dt, Remittance Date
Payment Number	Reference number for the payment.	Payment Number, Check Number, Payment Ref
Payment Type	Type of payment, if provided.	Payment Type, Method, ACH/Check Type
Total Amount	Total payment amount for the remittance.	Total Amount, Payment Amount, Total Paid
Transaction Reference	External payment or transaction reference.	Transaction Ref, Reference, ACH Reference
None	Indicates that no value should be mapped for that row.	Not applicable

The exact fields available in your environment may vary slightly based on configuration.

Step 7: Configure Line Items Mapping

Use Customize Line Items Mapping to map invoice-, claim-, or detail-level fields.

These fields usually repeat across detail rows in the remittance file.

How line item mapping works

For each row:

Select a source field from Input file fields (Line Items)
Select the matching target field from Auditoria Fields

Repeat until the important line-level fields are mapped.

Important note

As with header mapping, the source field names are customer-specific, but the Auditoria target fields are standardized.

For example:

Claim No may map to Claim Number
Inv # may map to Invoice Number
Provider Payable may map to Provider Payable Amount
Total Payable may map to Amount To Pay

Use None when needed

If a line item field should not be extracted, select None.

Auditoria Line Item Fields

The following table describes the common Auditoria line-item fields available for mapping.

Table 3. Auditoria Line Item Fields

Auditoria field	Description	Example customer source labels
Amount To Pay	Amount to be applied or paid for the line item.	Amount To Pay, Total Payable, Net Payable
Bill To Customer	Customer billed for the line item, if provided.	Bill To, Billed Customer
Claim Number	Claim identifier for the line item.	Claim Number, Claim No, Claim ID
Comment	Free-text notes or comments associated with the line item.	Comment, Notes, Remarks
Copay	Copay amount for the line item.	Copay, Co-pay, Co Insurance Copay
Cost Of Treatment	Total treatment or service cost, if provided.	Cost, Treatment Cost, Cost of Service
Deductible	Deductible amount associated with the line item.	Deductible, Ded Amt
Gem Bill	Customer- or business-specific billing identifier used in the file.	Gem Bill, Bill Number
Ineligible Amount	Amount marked as ineligible or not covered.	Ineligible Amount, Non-covered Amount
Invoice Amount	Original invoice amount for the line item.	Invoice Amount, Inv Amount, Total Charges
Invoice Number	Invoice identifier used for matching.	Invoice Number, Inv #, Document Number
Invoice P P O Fee Amount	PPO-related fee amount, if provided.	PPO Fee, PPO Amount
Patient Name	Name of the patient associated with the line item.	Patient Name, Member Name
Patient Number	Identifier for the patient or member.	Patient Number, Member ID, Patient ID
Payment Amount	Amount paid on the line item, if provided separately from Amount To Pay.	Payment Amount, Paid Amount
Provider Name	Name of the provider associated with the line item.	Provider Name, Physician, Hospital
Provider Payable Amount	Amount payable to the provider.	Provider Payable, Payable to Provider
Statement Number	Statement or remittance line identifier.	Statement Number, Statement ID
Total Claim Charges	Total charges associated with the claim.	Total Claim Charges, Claim Charges
Total Payable To Olympus	Total amount payable to Olympus, if used in the customer file.	Total Payable to Olympus
Treatment Date	Date of treatment or service.	Treatment Date, Service Date, DOS
None	Indicates that no value should be mapped for that row.	Not applicable

The exact fields available in your environment may vary slightly based on configuration.

Step 8: Preview Mapping

After configuring the header and line item fields, click Preview.

The preview helps confirm that:

The correct header values were extracted
The correct line item values were extracted
Columns are mapped to the expected Auditoria fields
Amounts, dates, identifiers, and comments appear correctly

Depending on the file, the preview may show:

A source file snapshot
Header-level values
Line item values in tabular form

Figure 6. Preview Mapping

Step 9: Enter Mapping Name

After validating the preview:

In Enter mapping name, type a name for the mapping

Use a clear and recognizable name.

Naming tips

Use a name that helps identify:

The customer
The format or template
The region or business unit, if needed

Examples:

CustomerX_Claims_Format

Figure 7. Enter Mapping Name

Step 10: Save Mapping

Click Save Mapping.

After the mapping is saved:

You are returned to the AR Mapping page
The new mapping appears in the mapping list
The mapping status is shown as Active

The mapping can now be reused for future remittance files for that customer.

Figure 7. Save Mapping

If you do not want to continue creating the mapping:

Click Cancel

This exits the create flow without saving your changes.

Result

You created a reusable AR Remittance Mapping for the selected customer.

This mapping can now be used to standardize future remittance files from that customer and reduce manual interpretation effort.

After you create a mapping

After saving, you can manage the mapping from the AR Mapping page, including:

Viewing the mapping in the list
Editing the mapping if the customer’s format changes
Deleting the mapping if it is no longer needed

Next step

To work with saved mappings, see Manage AR Remittance Mappings.