Overview
In the Settings step, the Write to SoR section controls how AR Remittances creates payment records in your ERP and whether it also sends data to a secondary destination.
What is “Write to SoR”?
Write to SoR means “write to System of Record”.
For AR Remittances, the System of Record (SoR) is your ERP (typically Workday), where official customer payment records are stored.
When AR Remittances “writes to SoR,” it:
Takes the data extracted from a remittance file (customer, entity, date, currency, amounts, and lines).
Creates a customer payment in the ERP for that customer and entity.
Links the remittance document in SmartCustomer to the created payment record (using the ERP’s external ID).
This is the key step where automation turns incoming remittance advice into real payments in your finance system.
Write to SoR Mode
Write to SoR automatically
Select this option if you want AR Remittances to create customer payments in the ERP without manual review for eligible documents.
Use this when:
Formats and mappings are stable and tested.
You trust the extraction quality for your enrolled customers.
Your goal is to maximize automation and speed up cash application.
For example, if a major customer emails a consistent daily bank remittance file, “Write to SoR automatically” lets those payments post automatically, with only exceptions needing human review.
Write to SoR manually
Select this option if you want a user to review and approve each remittance before a payment is created.
Use this when:
You have strict internal controls or audit requirements.
You are still tuning extraction, mappings, or customer enrollment.
Different teams must review remittances for different customer groups.
In this mode, remittances stay in Active Data until an authorized user opens a document and clicks Write to SoR. Only then is a payment created in the ERP.
Write to Another Destination
Write to another destination
Select this checkbox if you want AR Remittances to also send payment data to a secondary destination, such as an SFTP folder.
When enabled:
Destination – Choose a pre‑configured SFTP destination (for example, a folder used by your data warehouse or analytics platform).
Frequency – Choose how often AR Remittances sends CSV files (for example, every 1 hour, 4 hours, or daily).
This is useful when downstream systems (for example, reporting, analytics, or custom integrations) need a feed of all payments created by AR Remittances, in addition to the official records in the ERP.
Zero Payment Records
Zero Payment Records
Select this checkbox if you want AR Remittances to handle zero‑amount remittances specially.
Typical usage:
Your ERP discourages or blocks $0.00 payments.
You still want to capture “informational” remittances (for example, full offsets or adjustments) for reporting.
When enabled, your configuration can allow zero‑amount remittances to be exported only to the secondary destination, without creating a zero‑amount payment in the ERP.
Important:
How zero‑amount remittances behave depends on your specific tenant configuration. Confirm with your implementation or finance team before enabling this option.
Why Write to SoR Matters
It is the authoritative step where remittance data becomes an official customer payment in your ERP.
The mode (automatic vs manual) defines how much human oversight you have.
The secondary destination option lets you reuse the same payment data in analytics or downstream systems, without changing the ERP.