Write to Another Destination

Written by Uday Kumar Updated

Who this is for. Administrators who send payment data from AR Remittances to a second system. Only the SuperAdmin role can change the setting.

Availability. Only where the system of record (SoR) is Workday. AR Remittances must be enabled for your organization. See Roles and Access.

Overview

Write to another destination also sends the payments written to Workday to a second destination, as CSV files. The destination is a Universal Connector connection of the SFTP type, with an outbound folder set. An S3 connection does not receive the files.

A payment goes to the destination after its Workday write succeeds. A zero payment record goes there without a Workday write, as Zero payment records in Write to SoR explains. The agent sends the files on a schedule. You choose how often:

  • 1 hour, the default
  • 4 hours
  • 12 hours
  • 24 hours

Each payment written to Workday becomes its own CSV file. On the schedule you choose, the agent sends the files created since the last send. AR Remittances writes to Workday in the same way with or without a second destination.

Before you start

  • Turn on AR Remittances for the instance. Settings shows how.
  • Have a Universal Connector connection for the destination that no other SmartCustomer or AR Helpdesk instance uses as its destination. Without one, the option does not appear.
  • Sign in with the SuperAdmin role.

Set up the second destination

  1. Open the Settings step in the configuration of the instance.
  2. Under the AR Remittances options, select Write to another destination. Two lists appear beside it, with no labels.
  3. In the first list, choose the destination. The list shows the names of the Universal Connector connections you can use.
  4. In the second list, choose how often the agent sends files.
  5. Select Continue.
  6. Complete the Save and Run step.

From then on, each payment written to Workday becomes a CSV file. The agent sends it at the next scheduled time.

Write to another destination selected, with a destination list, a 1 hour frequency list, and the Zero Payment Records checkbox

Figure 1. Write to another destination with its destination and frequency lists

File contents

Each file is a CSV file with a header row. The headers are the field names as the console shows them. Each row is one line item, with the payment record fields repeated on each row. The file name includes the Workday ID of the payment. A zero payment record has no Workday ID, so its file name carries the document ID.

Auditoria sets up which fields the file carries for your organization. To change them, contact your Customer Success Manager or Auditoria support with the fields you need.

Variations

Changing the destination or the schedule

You can change the destination or the schedule on a running instance. Open the configuration, change the list, and complete the Save and Run step.

Turning the option off

Clear Write to another destination, and complete the Save and Run step. AR Remittances goes on writing payments to Workday. The Zero Payment Records option disappears with it.

Zero payment records

With Zero Payment Records selected, zero payment records go to this destination only. Their total is 0.00, and their line amounts add up to 0.00. They create no payment in Workday. Zero payment records in Write to SoR describes the option.

One destination per instance

An instance sends files to one destination. The first list takes one connection. A destination that one instance uses is not offered to another.

Sending files before the scheduled time

To send the waiting files before the scheduled time, open System Settings. On the connection card of the destination, select the sync icon. Its tooltip reads Initiate Sync Now.

Troubleshooting

When Write to another destination is missing

Your organization has no Universal Connector connection, or another SmartCustomer or AR Helpdesk instance uses each one as its destination. The option also needs Turn on AR Remittances selected, on a Workday connection.

When a payment is not in the destination

The Documents tab does not show which payments reached the destination. To check an upload, open Administration > Audit Logs and select System. Each uploaded file has an entry named SFTP CSV files Uploaded. A failed upload has its own entry. While the destination cannot be reached, the files wait and go out at the next sync.

A payment's file goes out at the next scheduled send after its Workday write succeeds. A zero payment record goes out without a Workday write.

Related information