Generic ERP AR Data Mapping Template

Overview

This reference reproduces the Auditoria AR business objects data mapping template for Generic ERP, one section per workbook sheet. Each table lists the Auditoria field name, field type, description, and the corresponding source-of-record field. Cells that are blank in the template are kept blank.

Note: Standard fields are mandatory. Extended fields are optional and are defined during implementation.


README – write use cases

This sheet describes how the connector writes records, including how header and line-item fields become output columns.

  • CSV files written by the Generic ERP Connector will flatten records including the Headers and "Line items" as follows:
  • Each Header field, Standard and Extended, becomes a Column header
  • Each Line Item field, Standard and Extended, becomes a Column Header
  • THIS MEANS: the CSV will have as many columns as the SUM of Standard+Extended fields across Header and Line Items

Customer

A customer is a company or person your organization sells goods or services to. The customer record holds the master data used to identify and collect from that customer, such as name, status, contacts, and assigned collections agent.

Table 1. Customer

Auditoria Customer Record Field Name (As seen in Auditoria console)Auditoria Field Type (STANDARD FIELDS ARE MANDATORY)Description (what does the field represent)Default Generic ERP Record Field Name
Customer NameStandardCustomer account name 
Status (Active/Inactive)StandardIs the Customer marked as active in SOR? Yes/No 
Customer ContactsStandardList of Contacts for Customer - contacts we do business with 
All Invoice ContactsStandard  
Collections AgentStandardEmail address of assigned Collections Agent 
Sales AgentStandardEmail address of assigned Sales Agent 
Collections ManagerStandardEmail address of assigned Collections Manager 
CSMStandardEmail address of assigned Customer Success manager 
Disputes CountStandardNOT MAPPED TO AN SOR FIELD 
Open InvoicesStandardNOT MAPPED TO AN SOR FIELD 
Delegated to AuditoriaStandardNOT MAPPED TO AN SOR FIELD 
TagsStandardNOT MAPPED TO AN SOR FIELD 
Dunning ClassificationStandardDunning Classification can be managed in AAI or in Workday. If you want to use Workday classifications, this field should be mapped. 
Invoice SubmissionStandardNOT MAPPED TO AN SOR FIELD 
NotesStandardNOT MAPPED TO AN SOR FIELD 
EntityStandardThis is the list of entities that the Customer belongs to in the SOR 

Invoice

An invoice is the document your organization sends to a customer to request payment for goods or services. The invoice record holds header data such as customer, status, due date, currency, and amounts.

Table 2. Invoice

Auditoria Customer Invoice Record Field Name (As seen in Auditoria console)Auditoria Field Type (STANDARD FIELDS ARE MANDATORY)Description (what does the field represent)Default Generic ERP Record Field Name
Customer nameStandardCustomer account name 
Status (Open/Paid/Canceled/Other)StandardWhether the invoice is Open, Paid, or partially Paid. Paid invoices are not in scope for dunning notifications. 
Due dateStandardDue date 
Foreign CurrencyStandard  
Amount PaidStandard  
Foreign Amount PaidStandard  
Delegated to AuditoriaStandardNOT MAPPED TO AN SOR FIELD 
Amount paid with Auditoria DO NOT USE 
Foreign Disputed AmountStandardNOT MAPPED TO AN SOR FIELD 
Company NameStandardThis is the entity that the Customer Invoice belongs to in the SOR 
DateStandard  
AgeStandard  
Exchange RateStandard  
Amount RemainingStandard  
Foreign Amount RemainingStandard  
Paid with Auditoria ? DO NOT USE 
Scheduled Payment DateStandardNOT MAPPED TO AN SOR FIELD 
Invoice numberStandard  
Dunning ContactsStandard  
CurrencyStandard  
Total AmountStandard  
Foreign TotalStandard  
Invoice PDF FileStandardPDF representation of this Invoice record, obtained from the SOR 
TagsStandardNOT MAPPED TO AN SOR FIELD 
Disputed AmountStandardNOT MAPPED TO AN SOR FIELD 
NotesStandardNOT MAPPED TO AN SOR FIELD 

Payment

A payment is the money your organization receives from a customer to settle one or more invoices. The payment record holds header data such as customer, currency, applied and unapplied amounts, entity, and status.

Table 3. Payment

Auditoria Customer Payment Record Field Name (As seen in Auditoria console)Auditoria Field Type (STANDARD FIELDS ARE MANDATORY)Description (what does the field represent)Default Generic ERP Record Field Name
Customer nameStandardName of customer who made the payment 
CurrencyStandardCurrency in which payment was made 
Base Unapplied AmountStandardPortion of payment not yet applied to an invoice in the payment base currency 
Applied AmountStandardThis is the applied amount in the payment currency 
CompanyStandardThis is the entity that the Customer Payment belongs to in the SOR 
Discount TakenStandardDiscount applied to payment amount for early or prompt payment 
StatusStandard[Applied, Partially Applied, Unapplied] 
Total AmountStandardTotal amount of payment made by customer in the payment currency 
Base CurrencyStandardBase or book currency 
Unapplied AmountStandardUnapplied amount in Payment currency 
Payment TypeStandardPayment method used by customer [cash, check, credit card, electronic transfer] 
Payment DateStandardDate payment was recieved from customer 
Base Applied AmountStandardPortion of payment applied to an invoice in the Base (book) amount 
Base Total AmountStandardTotal amount in book currency 
Payment CategoryStandard  
Transaction ReferenceStandardReference or memo for payment tracking or identification purposes 
Payment NumberStandardWorkday Identifier for the Payment 
Refund AmountStandardThis is the refund amount in the payment currency 
Base Refund AmountStandardThis is any amount refunded in the base currency (book currency) 
NotesStandardNOT MAPPED TO AN SOR FIELD 
Exchange RateStandardThis is the rate used to convert from payment amount to base 

Extended remittance line items

Remittance line items detail how a customer payment is applied across invoices. This sheet defines the extended fields captured for each remittance line.


Dispute

A dispute is a customer's objection to an invoice or charge, such as a billing error or short payment. In this template, dispute objects are not mapped to system-of-record fields.

  • DISPUTE objects are NOT mapped to SOR records

Status mapping

Status mapping defines how the statuses in your system of record (SOR) translate to the statuses Auditoria supports.

Table 4. Payment Status

Auditoria Supported StatusDefault Generic ERP Record Field Name Payment StatusDefault Generic ERP Application StatusMapping for Payment StatusMapping for Application Status
Canceled    
Applied    
Unapplied    
Partially Applied    

Table 5. Invoice Status

Auditoria Supported StatusDefault Generic ERP Record Field Name Invoice StatusDefault Generic ERP Record Field Name Payment StatusMapping for Invoice StatusMapping for Payment Status Status
Open    
Paid    
Canceled    
Other    

Table 6. Credit Memo Status

Auditoria Supported StatusDefault Generic ERP Record Field Name Invoice StatusDefault Generic ERP Record Field Name Payment StatusMapping for Invoice StatusMapping for Payment Status Status
Draft    
Unapplied    
Partially Applied    
Applied    
Canceled    

Table 7. Credit Memo Type

Auditoria Supported StatusDefault Generic ERP Record Field Name TypeMapping for Invoice Status
Credit Memo  
Internal  

For the complete template, download the Auditoria Generic ERP AR business objects data mapping template.

Attachments