What is AR Remittance Mapping?
AR Remittance Mapping lets you define how a customer’s remittance file maps to Auditoria’s standard remittance fields.
Customers often send payment remittances in different Excel layouts, with different column names, sheet names, and field structures. Because these formats are not standardized, AR teams may otherwise need to manually interpret each file to identify payment details and invoice-level line items.
AR Remittance Mapping provides a self-service way to configure those customer-specific formats so they can be used consistently in Auditoria.
Once a mapping is created, it can be reused for future remittances from that customer. If the customer changes their remittance format later, the mapping can be updated without requiring backend metadata changes or a deployment.
Why use AR Remittance Mapping?
Use AR Remittance Mapping to:
- Standardize customer-specific remittance layouts
- Reduce manual interpretation of remittance files
- Improve extraction accuracy for payment and invoice details
- Reuse mapping configurations for future remittances
- Update mappings more quickly when customer formats change
This helps AR teams process remittances more efficiently and with fewer errors.
How AR Remittance Mapping works
At a high level, the mapping workflow is:
- Select a customer in AR Mapping
- Upload a sample remittance file
- Select the worksheet to process
- Let the system detect available input fields
- Map customer file fields to Auditoria fields
- Preview the mapped output
- Save the mapping for reuse
The saved mapping is then available for future remittance processing for that customer.
What can be mapped?
AR Remittance Mapping supports two types of remittance data:
Header fields
Header fields are payment-level values that apply to the remittance as a whole.
Examples include:
- Customer name
- Currency
- Payment date
- Payment number
- Batch number
- Total amount
- Transaction reference
Line item fields
Line item fields are invoice-, claim-, or detail-level values.
Examples include:
- Invoice number
- Claim number
- Invoice amount
- Amount to pay
- Comment
- Deductible
- Copay
- Provider name
- Provider payable amount
- Treatment date
- Patient number
- Patient name
When should you create a new mapping?
Create a new mapping when:
- A customer is being onboarded for the first time
- A customer’s remittance format does not match an existing mapping
- The customer begins using a new worksheet layout or template
- Different remittance formats are used for different business units, regions, or payment methods
If a customer already has a mapping but changes their file structure, you can update the existing mapping or create a new one, depending on your business process.
Who typically manages AR Remittance Mapping?
AR Remittance Mapping is typically managed by:
- SuperAdmin
Self-service mapping vs. manual mapping
Before the self-service AR Mapping tool, customer remittance mappings often had to be prepared manually using sample files and backend metadata configuration. This required internal technical setup and was more time-consuming to maintain.
With the self-service AR Mapping tool in SmartCustomer, users can:
- Upload a sample file directly in the application
- Select the appropriate worksheet
- Configure header and line item mappings themselves
- Preview the extraction results
- Save and reuse mappings without backend deployment
This makes onboarding and maintaining customer remittance formats faster and more scalable.
Key benefits
AR Remittance Mapping helps:
- Reduce onboarding time for new customer remittance formats
- Improve consistency of remittance extraction
- Minimize manual mapping effort
- Support ongoing changes to customer file formats
- Enable reusable, customer-specific mapping templates
Next step
To start creating or maintaining mappings, see Access the AR Mapping page.