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. Decide the Automated-Send Stance

Open Settings → Receivables Controls.

Leave Autopilot Collections off until steps 3 through 8 are complete and you have reviewed the message content with a controlled test.

The switch is the master opt-in for automated collection messages. Eigenn sends nothing automatically while it is off, whatever the recovery policy contains. Manual reminders from an invoice and transactional email are unaffected.

When you are ready to send:

  1. Set Autopilot Collections on.
  2. Select Save in Autopilot Policy.
  3. Refresh the page.
  4. Confirm that the value remains on.

Eigenn requires the value to be explicitly saved as on. An unsaved or unreadable setting pauses automated sends.

3. Save the Communication Window

  1. Set Enable Quiet Hours and the intended start and end time.
  2. Set Exclude Weekends.
  3. Select Save in Payment Follow-up Timing.
  4. Refresh the page.
  5. Confirm that the values remain.

The defaults are quiet hours from 21:00 to 08:00 and weekend exclusion on.

These values are the team default. A customer-specific preference and a policy-level quiet window both take precedence over them.

There is no late-fee card on this page. Late fees come from fee rules attached to a recovery policy step.

4. 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.

5. 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.

6. 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.

7. Test Auto-chase

  1. Confirm that Autopilot Collections is on. Enrollment alone sends nothing while the master switch is off.
  2. Open the controlled unpaid or overdue invoice.
  3. Confirm that the customer and the recipient are test-safe.
  4. Find Auto-chase overdue.
  5. Turn it on.
  6. Confirm that the switch stays on while the request waits in the queue.
  7. Refresh until the recovery step and next reminder date appear.
  8. 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.

8. 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.

9. 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.

Confirm the Result

Configuration is ready for a limited rollout when:

  • the Autopilot Policy and Payment Follow-up Timing cards keep the values that you set, after a refresh
  • Autopilot Collections is on only after the content and recipients were reviewed
  • 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 invoice is enrolled but nothing was sent

Confirm that Autopilot Collections is explicitly saved as on. The switch is opt-in and fails closed, so an unsaved value pauses every automated send.

The communication ignored quiet hours

A customer preference or a policy-level quiet window overrides the team default. Check the customer record and the recovery policy before you change the team setting.

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 Planning Time and Actuals

Set the model range and granularity, place the last actual date, verify source periods, and roll the forecast forward safely.

Connect Planning Data and Actuals

Add a supported planning source, refresh it, import actuals, and verify the model against source records.

On this page

Prerequisites1. Record the Policy Decision2. Decide the Automated-Send Stance3. Save the Communication Window4. Create One Recovery Policy5. Add No More Than Five Steps6. Examine the Editor's Missing Controls7. Test Auto-chase8. Confirm the First Communication9. Test Stop and RecoveryConfirm the ResultTroubleshootI created the wrong policyI added the wrong stepAuto-chase says no active policy existsAuto-chase starts but the sequence never appearsThe invoice is enrolled but nothing was sentThe communication ignored quiet hoursThe test email or SMS failedRelated Pages

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesApproval PoliciesAssistant AutomationAssistant Command CenterAssistant Workspace and Saved WorkBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer FieldsCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionFiles and Document VaultFinancial Analytics and ReportsFinancial OverviewInbox and ApprovalsInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewPlanning Data and DimensionsPlanning Models and FormulasPlanning Time and ActualsPlanning UncertaintyPlanning Versions and CollaborationPlanning Views and ExportsReceivablesReceivables AnalyticsReceivables ControlsScenario PlanningSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransaction CodingTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow OutcomesWorkflow PausesWorkflows
OverviewBuild a Driver-Based Planning ModelBuild and Review a ForecastBuild Your First WorkflowCollaborate on a Planning ModelCompare and Share Planning ScenariosConfigure Approval PoliciesConfigure Assistant OperationsConfigure Customer FieldsConfigure Notifications and BrandingConfigure Planning Time and ActualsConfigure Receivables ControlsConnect Planning Data and ActualsConnect Transaction RecordsCreate and Manage CustomersCreate and Send InvoicesCreate Your First Planning ModelDeveloper 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 RecordReview, Restore, and Export a Planning ModelRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Planning Uncertainty AnalysisRun Your First Command Center ReviewSave and Share Assistant WorkSet 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
Overview
Overview