Before You Start

Written by Uday Kumar Updated October 13, 2026 07:07

Who this is for. Administrators who set up AR Remittances for the first time. Only the SuperAdmin role can use AR Remittances and do this setup, as Roles and Access explains.

Availability. Only where the system of record (SoR) is Workday. AR Remittances must be enabled for your organization and turned on for a SmartCustomer instance.

Overview

Several things must be in place before AR Remittances can process a remittance. The groups on this page follow the order of setup, from your organization's setup to the configuration.

Organization and system of record

AR Remittances needs Workday as the system of record. The function must also be enabled for your organization.

Table 1. Organization and system of record requirements

Requirement	Details
AR Remittances enabled for your organization	Without it, Turn on AR Remittances does not appear on the Settings step. Auditoria enables it for your organization. If the option is missing on a Workday instance, ask your Customer Success Manager, or see Contacting Support.
Workday as the system of record	The option appears only when the instance's ERP is Workday.
A Workday connection	You choose it in the ERP field on the Connection step. A SuperAdmin adds the connection under Administration > System Settings > Add New Connection. For the Workday permissions it needs, see Setting Up an Integration System User (ISU) for Auditoria SmartCustomer Products.
Customers synchronized from Workday	The agent matches each remittance against these customers. They appear on the Customers tab. For how often this copy refreshes, see The SmartCustomer Console.

The connected mailbox

AR Remittances reads one mailbox: the one connected to its SmartCustomer instance.

Table 2. Mailbox requirements

Requirement	Details
A mailbox connected to Auditoria	You choose it in the Mailbox field on the Connection step. A SuperAdmin connects the mailbox under Administration > System Settings > Add New Connection > Mailbox.
A mailbox that no other SmartCustomer or AR Helpdesk instance uses	The Mailbox field does not offer a mailbox that another SmartCustomer or AR Helpdesk instance already uses.
Remittances sent to that mailbox	Your customers' remittance emails must reach this mailbox.
Remittance details in an attachment	The agent reads attachments only. It does not extract details from the email body.

File types and limits

The File Types: setting on the Settings step offers four types. All four are selected by default, and at least one must stay selected.

Table 3. Limit or behaviour for each item

Item	Limit or behaviour
PDF	Up to 150 pages per email, across all its attachments. Each spreadsheet counts as one page.
XLS and XLSX	Up to 60 columns and 500 rows. A workbook with more than one sheet gives every document from its email the status Multi Tab File Please Review. The agent reads only the first sheet.
CSV	Up to 60 columns and 500 rows.
Hidden and empty columns	They count toward the column limit.
A file over a limit	The email's documents are still processed. Every document from that email gets the status Large File Please Review. If the email also holds a workbook with more than one sheet, they get Large & Multi Tab File Please Review. So a file can carry one of these statuses because of another attachment in the same email.
Other file types	Not processed. The setting offers only the four types.
A file type you do not select	Not extracted, and no document is created for it.
Password-protected files	A password-protected PDF, XLS, or XLSX file is classified as Others. Its status is Record is not a Customer Remittance. AR Remittances extracts no field from it. A CSV file that cannot be read is handled the same way.
Languages	Tested with remittances in English, French, and Spanish.
Currencies	If the file shows no currency, the agent uses USD. Check the currency before you write.

Customer enrolment

Enrolment decides whether a matched document reads Known or Unenrolled. A user can write a document only when it reads Known. Enrolment is per function. Enrolling a customer for AR Helpdesk does not enrol it for AR Remittances.

Table 4. Where enrolment happens and when it applies

Where or when	Details
Customers tab	The Enroll or unenroll control opens Select SmartFlow Skill to Enroll or unenroll, with one checkbox per function. It applies to the customers you selected.
Customer page	The Enrollment row has one switch per function, and Save.
Enrolled column	One icon for each function the instance runs, such as AR Helpdesk and AR Remittances. Each tooltip reads Enrolled in or Unenrolled from and the function, such as Enrolled in AR Remittances.
A document with an Unenrolled customer	The details page offers Enroll beside Customer Match Status.
When a change applies	For how enrolment affects writes without review, see Write to SoR. Enrolling from a document page also makes that customer's open documents Known at once, so you can write them. Unenrolling does not change documents that are already Known.

Configuration and roles

The configuration needs AR Remittances turned on. Each other setting in the table has a default or is optional.

Table 5. Configuration and role requirements

Requirement	Details
Turn on AR Remittances on a SmartCustomer instance	Selected on the Settings step. For the steps, see Configuration Workflow.
A Write to SoR option	Collaborative Mode, Autonomous, or Configurable at Customer Level. See Write to SoR.
A Date Format	MM/DD/YYYY, DD/MM/YYYY, or DD-MMM-YYYY. See Settings.
Optional: Write to another destination	Needs a Universal Connector connection that no other SmartCustomer or AR Helpdesk instance uses as its destination. The connection is of type SFTP, with an outbound folder set. A SuperAdmin adds it in System Settings. Without one, the option does not appear. See Write to Another Destination.
Optional: Zero Payment Records	Needs Write to another destination. See Zero payment records in Write to SoR.
A role that can configure	SuperAdmin.
The role for the people who review documents	SuperAdmin. See Roles and Access.