Receivables Controls

Receivables Controls has two distinct configuration layers. The upper settings form stores team preferences for collection policy, fees, communication schedule, and escalation. The Recovery policies section below it creates the active step sequence that Eigenn uses when an operator turns on Auto-chase overdue for an invoice.

Keep those layers separate. A successful Save in the upper form confirms storage. An active recovery policy with steps controls the shipped Auto-chase sequence.

Before You Start

• Select the correct team before you change settings.
• Decide who owns customer-sensitive collection decisions.
• Confirm the channels that the team can deliver: email, SMS, or in-app.
• Use a controlled test customer and invoice before you enroll real overdue work.
• Read the applicable contract, consumer-protection, late-fee, and communication rules with qualified counsel.

Open Receivables Controls

1. Open Settings.
2. Select Receivables Controls.
3. Review each settings card separately.
4. Scroll to Recovery policies to manage the sequence used by Auto-chase.

Each settings card has its own Save button. When you save one section, you do not save unsaved changes in another.

Stored Team Preferences

Autopilot Policy

Eigenn saves these values on the team record. The current Auto-chase enrollment and recovery jobs do not read them. A change to these switches does not start, stop, adapt, charge, or approve a recovery sequence.

Late Payment Policy

The page can store:

• Late fee on or off
• Percentage, flat, or tiered fee type
• Percentage choices from 0.5% through 5%
• Flat amounts from $10 through $100
• Grace periods from zero through 14 days
• Maximum fee caps from 5% through 50% of the invoice

The page labels Tiered as Coming Soon. The stored late-payment settings do not connect to Auto-chase delivery now. When you turn on late fees here, you do not add a fee to an invoice.

A recovery step applies a fee only with a separate active fee rule attached to a policy step. The current Settings page does not show fee-rule creation or attachment.

Payment Follow-up Timing

The page stores:

• Whether to send pre-due follow-ups
• A maximum of 1–20 follow-ups per invoice
• Quiet hours on or off, and the start and end time
• Weekend exclusion

The default stored preferences are pre-due follow-up on, five follow-ups, quiet hours from 21:00 to 08:00, and weekend exclusion on.

The recovery sender does not read these values now. A successful Save does not prove that active policy messages wait for quiet hours, skip weekends, or stop at the saved follow-up count.

The delivery process can respect customer-specific channel preferences and quiet hours when they exist. It can also respect policy-level quiet hours that you set on the policy. The simple Recovery policies form does not show that configuration.

Owner Review & Escalation

Enable Escalation stores whether the team prefers overdue invoices to move through review stages. It does not change the active recovery sequence now.

Policies that you create on this page use a five-step maximum. When a policy reaches that maximum, the recovery process can trigger a collections escalation. This happens even when the saved escalation switch or approval preference suggests otherwise. Keep live policies to five steps or fewer.

Recovery Policies

The Recovery policies card is the configuration that Auto-chase uses.

Create a policy

1. Enter a descriptive name such as Standard customer reminder sequence.
2. Select Create policy.
3. Confirm that the new policy shows Active.

The page creates the policy as active immediately, with a maximum of five steps. It does not offer a draft state during creation.

Add a step

1. Enter a non-negative number in Day.
2. Choose Email, SMS, or In-app.
3. Select Add step.
4. Confirm that the numbered step appears under the intended policy.

The page automatically assigns the next step number and attaches the invoice to the communication.

How Eigenn schedules Day

The Day label is compact. Eigenn schedules each step relative to sequence activity:

• The first step waits that many days after Auto-chase enrollment.
• Each later step waits that many days after Eigenn processes the step before it.

For example, take steps with Day 0, Day 3, and Day 7. Eigenn schedules them at enrollment, three days after step one, and seven days after step two. They are not necessarily due-date days 0, 3, and 7.

What Auto-chase Does

When an operator turns on Auto-chase overdue on an unpaid or overdue invoice:

1. Eigenn selects the newest active recovery policy for the team.
2. Eigenn queues a recovery sequence for that invoice and customer.
3. Eigenn schedules the first action from the enrollment time with the Day value of the first step.
4. Each step queues one communication on its configured channel.
5. The invoice details show the active step and next reminder date when the sequence record is available.
6. The sequence completes after its last executable step. It stops when you cancel it. It can also close when Eigenn processes a supported payment.

Eigenn permits only one active sequence for the same team and invoice at a time. A repeated start request must reuse the active sequence. It must not create parallel recovery work.

Channel Needs

If a customer turned off the selected channel, or Eigenn suppresses the recipient, delivery fails. Eigenn retries provider failures. Investigate the communication state before you send a second manual message.

Current Policy-Editor Limits

The Settings page can create policies and append steps. It does not give controls now to:

• Rename, deactivate, or delete a policy
• Select which active policy an invoice uses
• Edit, delete, or reorder a step that exists
• Choose a communication template or sender profile
• Attach a tone profile to a step
• Attach a late-fee rule
• Set the policy timezone or quiet hours
• Change the five-step maximum of the policy

When you create another policy, Eigenn does not deactivate the earlier one. Auto-chase uses the newest active policy. Avoid duplicates unless the team wants the newer policy to take precedence.

Tone and Template Boundary

Steps that you create in this Settings card do not include a template selector. Without a linked template, the recovery sender uses its fallback reminder content. Do not assume that a team default tone profile or an active tone experiment changes every message from this simple policy.

Tone transformation and experiments need an eligible communication workflow that has tone turned on, a template, and customer context. Confirm the outbound content before you use the sequence with customers.

Verification Checklist

After you set up the page, confirm these points:

• Every upper settings section shows the intended saved values after a refresh.
• The team understands that those values are preferences, not current delivery controls.
• Exactly one intended policy is the newest active policy.
• The policy contains one to five steps.
• Step delays produce the calendar dates that you expect from enrollment.
• Customer contact data exists for every selected channel.
• A controlled invoice can start and stop Auto-chase.
• The invoice shows the expected next step and date.
• The first test communication reaches the intended recipient and contains approved content.

Troubleshoot

A saved switch did not change Auto-chase

That is the current product boundary. The upper settings form stores team preferences. Active recovery policies and invoice-level Auto-chase control the active sequence.

Auto-chase reports that no policy exists

Create a recovery policy and confirm its Active badge. Add at least one step before you try again.

Auto-chase starts but never gets a next date

Confirm that the selected active policy contains a step and that the invoice has a customer. The start request can queue before the background sequence record appears.

Auto-chase used the wrong policy

Auto-chase now selects the newest active policy and does not show a picker. If many policies are active, contact the workspace administrator or support. Ask them to deactivate the unintended policy before you enroll more invoices.

A sixth step did not send

Policies that you create here have a five-step maximum. Keep the intended sequence to five steps or fewer. When a policy reaches the maximum, the case can move into collections escalation instead of later steps.

Quiet hours or weekend exclusion did not apply

Eigenn stores the switches in the upper settings form, but they do not connect to the sender. Stop the active sequence if the schedule is unsafe. Then correct the policy or the customer-specific delivery configuration through the supported administrative path.

A late fee was not added

The late-payment form does not attach a fee rule to a recovery step. Leave the invoice unchanged. Use a reviewed, legally valid fee workflow. Do not add a duplicate charge manually.

Related Pages

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