Pre-requisites for AR Remittances

Written by Uday Kumar Updated January 24, 2026 11:13

Before you enable and use AR Remittances in SmartCustomer, make sure the following system, data, and access pre-requisites are in place.

1. System and entitlement pre-requisites

A short description of the key system-level conditions:

Product entitlement
- Your tenant must be entitled for SmartCustomer AR and specifically AR Remittances.
- Entitlement is managed by Auditoria based on your contract and provisioning.
- If AR Remittances does not appear as an option in SmartFlow configuration, contact your Customer Success or Support representative.
Supported ERP
- AR Remittances currently supports Workday as the system of record for customer payments.
- Your Workday AR module must be active and reachable from the Auditoria tenant.

A short description of what is required on the Workday side:

Workday tenant connection configured
- A Workday Financials connector must be configured and active for your Auditoria tenant.
- The connection must include permissions for:
  - Reading customer, invoice, and entity data.
  - Creating customer payment records.
- Typically, this is set up as part of tenant onboarding, not within the AR Remittances wizard itself.
AR data availability in Workday
- The following objects should be correctly set up and in active use in Workday:
  - Customers (including contact details and appropriate entities).
  - Customer invoices (for later cash application).
  - Legal entities and currencies used in AR.
- AR Remittances relies on these records to:
  - Associate remittances with the right customer.
  - Validate entities and currencies.
  - Provide remittance advice lines that Workday can use to apply payments.

A description of what must be in place for the AR mailbox:

Dedicated AR remittances mailbox
- You must have an email mailbox (for example, ar-remittances@yourcompany.com or cashapps@yourcompany.com) that:
  - Receives customer remittance advice emails and attachments.
  - Can be connected to SmartCustomer via the standard mailbox integration (Microsoft 365, Google Workspace, or equivalent).
- This mailbox should be distinct from AP or generic AR helpdesk mailboxes to keep workflows separate.
Mailbox connection configured in SmartCustomer
- An admin (SuperAdmin / AR admin role) must:
  - Connect the AR mailbox in the platform / mailbox settings area.
  - Grant required OAuth / service account permissions so Auditoria can:
    - Read incoming emails.
    - Read attachments.
    - Apply mailbox labels/folders for AR Remittances (for example, “HereIsNewRemittance”, “NeedsHumanAttention”).
Customer routing to the AR mailbox
- Your customers must be informed to send remittance files to the connected mailbox.
- For bank or portal exports, ensure the remittance destination email is this mailbox.

A description of role/permission dependencies:

SmartCustomer user roles assigned
- At least one user must have an admin-level role for SmartCustomer AR (for example, SuperAdmin, AR Manager) so they can:
  - Configure SmartFlows.
  - Connect mailboxes and SoR.
  - Turn AR Remittances on or off.
- AR Analysts/Agents need roles that allow them to:
  - View Documents → Active Data and Written to SoR.
  - Edit fields and trigger Write to SoR (manual mode).
Record Access Control (RAC), if enabled
- If your tenant uses Record Access Control for AR, ensure that:
  - AR Remittances users have permission to see relevant customers, payments, and invoices in SmartCustomer.
  - Teams and users are mapped to the correct AR modules and mailboxes (for example, workday_ar_module, ar_mailbox).

Applies only if you plan to use the “Write to secondary destination” feature.

SFTP server provisioned by customer
- You must provision an SFTP server (owned or controlled by your organization) and provide:
  - Hostname
  - Port
  - Authentication method (user/password or key pair)
  - Target folder path for remittance CSV files
- AR Remittances only writes to this location; it does not read from it.
Generic ERP connection configured as “Destination SFTP folder”
- In the platform settings, an admin must configure a Generic ERP connection of type Destination SFTP folder.
- This connection will be selectable in the AR Remittances SmartFlow configuration as the second destination.
Zero Payment Records feature (if used)
- If your Workday configuration does not allow $0.00 customer payments and you want to use Zero Payment Records, ensure:
  - The feature flag for AR Remittances Zero Payment Records is enabled for your tenant.
  - You understand that when this option is checked:
    - Remittances with Total Amount = 0 and Amount to Pay = 0 on all lines will be written only to SFTP and not created as Workday payments.
    - Some documents in Written to SoR will have a secondary‑destination record only.

A description of what must be ready on the business/data side:

Customer master data aligned
- Customer records must be:
  - Present and active in Workday.
  - Synced to SmartCustomer (through the standard data pipeline).
- If you plan to use Autonomous Write to SoR:
  - Key customers should be enrolled for AR Remittances / AR SmartCustomer so their remittances can be processed without manual intervention.
Remittance formats identified and sampled
- For each major customer whose remittances you want to automate, you should:
  - Collect sample remittance files (PDF, CSV, Excel) that represent typical formats.
  - Document which fields are required for:
    - Workday payment headers (date, amount, currency, entity, payment type).
    - Remittance advice lines (invoice number, PO, claim ID, amounts).
- These samples are used by implementation and ML teams to:
  - Configure per-customer mappings.
  - Tune extraction for AR Remittances.
Agreement on page/volume limits
- For very large remittance documents (for example, 300–800 page PDFs), confirm:
  - Whether your tenant is configured with increased page limits per attachment.
  - Any performance or processing SLAs for large files.