Configure Receivables Controls

This guide configures Receivables Controls without confusing saved policy preferences with the active Auto-chase sequence. Complete the upper settings cards for team intent, then build and test the recovery policy that actually schedules messages.

Prerequisites

• You can access Settings → Receivables Controls for the correct team.
• The team has approved its reminder, late-payment, escalation, and customer-contact policy.
• A test customer has a valid email, phone, or in-app account for the channel being tested.
• A controlled unpaid or overdue test invoice exists.
• Required delivery providers are connected and configured.
• No production invoice will be enrolled until the test is complete.

1. Record the Policy Decision

Before editing the page, write down:

• whether collection should be manual or automated
• which invoices are eligible
• allowed communication channels
• intended delays between messages
• who reviews disputes and sensitive accounts
• whether fees are legally and contractually permitted
• what evidence must exist before escalation

The current page does not enforce every saved preference, so this operating decision remains important.

2. Save Autopilot Preferences

Open Settings → Receivables Controls.

1. Set Autopilot Collections to the team's intended default.
2. Set Adaptive Cadence to the intended preference.
3. Leave Due-Date Autopay off unless customer authorization and saved payment methods are managed through a reviewed payment workflow.
4. Set Collections Approval to the intended owner-review preference.
5. Select Save in Autopilot Policy.
6. Refresh and verify the values remain.

These values are stored team preferences. They do not currently start collection, change cadence, charge a card, or insert an approval into the active recovery sequence.

3. Save the Late-Payment Preference

1. Decide whether Enable Late Payment Fees should be recorded.
2. Choose Percentage of Invoice or Flat Amount if a fee policy exists.
3. Set the rate or amount, grace period, and maximum fee cap.
4. Avoid Tiered (Coming Soon) for live operating policy.
5. Select Save in Late Payment Policy.
6. Refresh and verify the values remain.

This form does not apply a fee. Do not test it by adding a manual charge. A live fee requires an active fee rule attached to a recovery step, which this page does not expose.

4. Save Communication Preferences

1. Set Send Pre-Due Follow-ups to the team's preference.
2. Set Max Follow-ups Per Invoice from 1 through 20.
3. Set Enable Quiet Hours and the intended time window.
4. Set Exclude Weekends.
5. Select Save in Payment Follow-up Timing.
6. Refresh and verify the values remain.

These values are not currently enforced by the recovery sender. Do not schedule a live policy on the assumption that the saved quiet hours, weekends, or maximum will suppress a message.

5. Save the Escalation Preference

1. Set Enable Escalation to the team's intended policy.
2. Select Save in Owner Review & Escalation.
3. Refresh and verify the value remains.

This switch does not currently intercept the active recovery sequence. Policies created below use a five-step maximum that can trigger collections escalation when reached.

6. Create One Recovery Policy

Scroll to Recovery policies.

1. Enter a precise name, such as Test — three-step email sequence.
2. Select Create policy.
3. Verify the Active badge.
4. Do not create a second policy unless the newer one is intentionally meant to take precedence.

The newly created policy is active immediately. Auto-chase uses the newest active policy and does not ask the operator to choose.

7. Add No More Than Five Steps

For a controlled initial test, use a short sequence. For example:

1. Add Day 0 · Email.
2. Add Day 3 · Email only after the first step's content and delivery are verified.
3. Add later SMS or in-app steps only when the required customer data and provider configuration are confirmed.

Each step is numbered automatically and attaches the invoice.

The Day value is a relative delay:

• Day 0 starts at enrollment time.
• A later Day 3 waits three days after the prior step.
• A later Day 7 waits seven more days after that.

It is not an absolute number of days after the invoice due date.

Policies created from this page have a five-step maximum. Do not add a sixth live step. Reaching the limit can escalate the recovery case instead of sending a later step.

8. Review the Editor's Missing Controls

Before testing, confirm you can accept these current limits:

• policy and steps cannot be edited, reordered, or deleted from this page
• policy cannot be renamed or deactivated from this page
• template, sender, fee rule, tone profile, timezone, and policy quiet hours cannot be selected here
• every created step attaches the invoice

If a step is wrong, do not compensate by adding contradictory steps. Pause production rollout and ask the workspace administrator or support to correct the active policy through the supported administrative path.

9. Test Auto-chase

1. Open the controlled unpaid or overdue invoice.
2. Confirm the customer and recipient are test-safe.
3. Find Auto-chase overdue.
4. Turn it on.
5. Verify that the switch remains on while the request is queued.
6. Refresh until the recovery step and next reminder date appear.
7. Confirm the date matches enrollment plus the first step's delay.

If the first step is Day 0, monitor the delivery system immediately.

10. Verify the First Communication

Confirm all of the following before expanding the test:

• the intended policy was selected
• the message used the expected channel
• the recipient is correct
• the invoice attachment is correct
• the content is approved
• the provider reports sent or delivered rather than only queued
• no duplicate communication exists
• the invoice shows the expected next step

Settings-created steps do not select a template, so fallback reminder content can be used. A default tone profile or experiment is not guaranteed to affect this message.

11. Test Stop and Recovery

1. Turn off Auto-chase overdue on the test invoice.
2. Verify the sequence is no longer active.
3. Wait past any immediate scheduled job and confirm no customer message is sent from the canceled sequence.
4. Correct the policy before reenrolling another invoice.

Stopping changes the recovery state. A scheduled recovery check can still occur and then skip the inactive sequence.

Acceptance Checklist

Configuration is ready for a limited rollout when:

• all four settings cards retain intentional values after refresh
• the team understands those values are not current enforcement controls
• one intended policy is the newest active policy
• the policy has one to five reviewed steps
• every delay is understood as relative to enrollment or the previous step
• channel prerequisites are verified
• the test invoice starts, reports progress, and stops correctly
• the actual outbound content and attachment are approved
• provider delivery evidence is visible
• the team has an owner for failed sends, disputes, and escalation

Troubleshooting

I created the wrong policy

The page does not expose rename, deactivate, or delete. Do not create several replacements without first resolving which policy should remain active, because the newest active policy takes precedence.

I added the wrong step

Existing steps cannot be edited, removed, or reordered here. Stop production enrollment and correct the policy through the supported administrative path.

Auto-chase says no active policy exists

Confirm that the policy creation succeeded and the Active badge is visible for the current team.

Auto-chase starts but the sequence never appears

Confirm the policy has at least one step and the invoice has a customer. Wait for processing, refresh, and contact support if the sequence remains absent.

The communication ignored quiet hours

The upper quiet-hours preference is stored but not read by the recovery sender. Stop the sequence and correct policy-level or customer-specific timing before continuing.

The test email or SMS failed

Verify the customer address or phone, opt-out state, suppression state, and provider credentials. Allow retries to finish before sending a manual duplicate.

Related Pages

• Receivables Controls
• Invoice Collection Workflow
• Receivables
• Tone Profiles and Experiments
• Invoices