EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

Configure Receivables Controls

Save team collection preferences, build the active recovery sequence, and test Auto-chase with a controlled invoice.

This guide sets up Receivables Controls. Do not confuse the 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 schedules messages.

Prerequisites

  • You can open Settings → Receivables Controls for the correct team.
  • The team 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 that you test.
  • A controlled unpaid or overdue test invoice exists.
  • You connected and set up the necessary delivery providers.
  • You do not enroll a production invoice until the test is complete.

1. Record the Policy Decision

Before you edit the page, write down:

  • whether collection is manual or automated
  • which invoices are eligible
  • the permitted communication channels
  • intended delays between messages
  • who examines disputes and sensitive accounts
  • whether the law and the contract permit fees
  • what evidence must exist before escalation

The current page does not enforce every saved preference. This decision about operations stays 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 a reviewed payment workflow manages customer authorization and saved payment methods.
  4. Set Collections Approval to the intended owner-review preference.
  5. Select Save in Autopilot Policy.
  6. Refresh the page.
  7. Confirm that the values remain.

Eigenn stores these values as team preferences. At this time, they do not 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 to record Enable Late Payment Fees.
  2. Select Percentage of Invoice or Flat Amount when a fee policy exists.
  3. Set the rate or amount, grace period, and maximum fee cap.
  4. Do not select Tiered (Coming Soon) for a live operations policy.
  5. Select Save in Late Payment Policy.
  6. Refresh the page.
  7. Confirm that the values remain.

This form does not apply a fee. Do not test it with a manual charge. A live fee needs an active fee rule on a recovery step. This page does not show that fee rule.

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 the page.
  7. Confirm that the values remain.

At this time, the recovery sender does not enforce these values. 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 the page.
  4. Confirm that the value remains.

At this time, this switch does not intercept the active recovery sequence. The policies that you create below use a five-step maximum. That maximum can trigger collections escalation when the sequence reaches it.

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. Confirm the Active badge.
  4. Do not create a second policy unless you want the newer one to take precedence.

The new policy is active immediately. Auto-chase uses the newest active policy. It 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 you confirm the content and the delivery of the first step.
  3. Add later SMS or in-app steps only after you confirm the necessary customer data and provider setup.

Eigenn numbers each step automatically. Each step 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 that you create from this page have a five-step maximum. Do not add a sixth live step. When the sequence reaches the limit, it can escalate the recovery case. It does not send a later step.

8. Examine the Editor's Missing Controls

Before you test, confirm that you can accept these current limits:

  • you cannot edit, reorder, or delete the policy and the steps from this page
  • you cannot rename or deactivate the policy from this page
  • you cannot select the template, sender, fee rule, tone profile, timezone, or policy quiet hours here
  • every created step attaches the invoice

If a step is wrong, do not compensate with contradictory steps. Pause the production rollout. 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 that the customer and the recipient are test-safe.
  3. Find Auto-chase overdue.
  4. Turn it on.
  5. Confirm that the switch stays on while the request waits in the queue.
  6. Refresh until the recovery step and next reminder date appear.
  7. Confirm that the date matches enrollment plus the delay of the first step.

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

10. Confirm the First Communication

Confirm all of the items that follow before you expand the test:

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

The steps that you create in Settings do not select a template. Eigenn can use fallback reminder content. A default tone profile or experiment does not necessarily affect this message.

11. Test Stop and Recovery

  1. Turn off Auto-chase overdue on the test invoice.
  2. Confirm that the sequence is not active.
  3. Wait past any immediate scheduled job.
  4. Confirm that the canceled sequence sends no customer message.
  5. Correct the policy before you enroll another invoice.

The stop action changes the recovery state. A scheduled recovery check can still run. That check then skips the inactive sequence.

Acceptance Checklist

Configuration is ready for a limited rollout when:

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

Troubleshoot

I created the wrong policy

The page does not show rename, deactivate, or delete. Find which policy must stay active before you create a replacement. The newest active policy takes precedence.

I added the wrong step

On this page you cannot edit, remove, or reorder a step. Stop the production enrollment. Correct the policy through the supported administrative path.

Auto-chase says no active policy exists

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

Auto-chase starts but the sequence never appears

Confirm that the policy has at least one step. Confirm that the invoice has a customer. Wait for Eigenn to process the request. Refresh the page. Contact support if the sequence stays absent.

The communication ignored quiet hours

Eigenn stores the upper quiet-hours preference. The recovery sender does not read it. Stop the sequence. Correct the policy-level or customer-specific schedule before you continue.

The test email or SMS failed

Check the customer address or phone, the opt-out state, the suppression state, and the provider credentials. Let the retries finish before you send a manual duplicate.

Related Pages

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

Configure Notifications and Branding

Set personal alert channels, confirm a custom sender domain, and test which brand settings reach customer output.

Connect Transaction Records

Connect a bank feed or import a clean transaction history, then check the records that Eigenn uses.

On this page

Prerequisites1. Record the Policy Decision2. Save Autopilot Preferences3. Save the Late-Payment Preference4. Save Communication Preferences5. Save the Escalation Preference6. Create One Recovery Policy7. Add No More Than Five Steps8. Examine the Editor's Missing Controls9. Test Auto-chase10. Confirm the First Communication11. Test Stop and RecoveryAcceptance ChecklistTroubleshootI created the wrong policyI added the wrong stepAuto-chase says no active policy existsAuto-chase starts but the sequence never appearsThe communication ignored quiet hoursThe test email or SMS failedRelated Pages

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesAssistant AutomationAssistant Command CenterBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionDocument VaultFinancial Analytics and ReportsFinancial OverviewInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewReceivablesReceivables AnalyticsReceivables ControlsSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow PausesWorkflowsWorkspace Inbox and Approvals
OverviewBuild and Review a ForecastBuild Your First WorkflowConfigure Assistant OperationsConfigure Notifications and BrandingConfigure Receivables ControlsConnect Transaction RecordsCreate and Manage CustomersCreate and Send InvoicesDeveloper API SetupFirst Cash ReviewInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsReview a Customer Finance RecordRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Your First Command Center ReviewSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsRemote Tracker API StatusTracker Categories APITracker Entries and Timers APITracker Projects APITransactions APIWebhooks API StatusWorkflows API Status
Overview
Overview