Advanced Invoice Settings: Past Due Invoices & Hiding Credits

Written by Kay Depper

Last published at: June 10th, 2026

Customize how your automated billing infrastructure interacts with outstanding ledger items and account credits. These account-level configurations are found within your Invoice Integrations settings. If you want to change these configurations, please contact your Account Manager or our Support team.

AutoPay Past Due Invoices

By default, AutoPay automatically manages both current and past due invoices. While the system processes invoices matching the current day's due date, it also expands its scope to capture all open, unpaid invoices outstanding from the last 90 days, or from your initial AutoPay creation date, whichever window is closer to the current run date. 


This built-in safeguard ensures that if you just launched AutoPay last week, the system won't scan deep into your history and inadvertently draft old payments. 


How the Look-Back Window Behaves:

  • Scenario A (Established Account): If a customer's AutoPay profile was established on March 1st, 2024, and an automated daily run executes, the system will look back up to 90 days to automatically capture any missed or open invoices.
  • Scenario B (Newly Created Account): If a customer's AutoPay profile was created just last Monday, the system will safely isolate its look-back boundary to last Monday, capturing only the open invoices generated since that creation date.


Delete

Critical Balance Compliance

To ensure past-due invoice processing operates flawlessly, it is imperative that your integrated management system is kept completely up to date. Our platform contains automated duplication filters that detect and block duplicate charges for any invoices processed natively through our platform (whether via a manual Payment Page or an automated AutoPay run). 

However, if an invoice is paid off-platform (such as via a physical paper check sent to your office) and your team does not mark that invoice as paid within your management system, our platform cannot detect the off-platform collection, which may result in an unintended automated charge.


NOTE: This feature is available upon request if it is not already enabled on your account. Please reach out directly to your Account Manager or our Support team to activate it. 


AutoPay Hide Credits


By default, this option is turned off. Under standard operating parameters, ePayPolicy runs a safety check for outstanding ledger credits before charging a customer. If a payer has a negative balance or an active ledger credit that is larger than the total of their due invoice, AutoPay identifies the credit and stops the automated charge from executing.


When the AutoPay Hide Credits is enabled all active AutoPay schedules on your account will deliberately ignore this safety check. This allows automated billing to process uninterrupted, pulling funds even if the customer's ledger holds an outstanding credit balance greater than the invoice total.


Credit Handling Examples:

  • When Toggle is "No" (Standard Safety On): An account possesses a $100 ledger credit and a new $50 invoice. AutoPay evaluates the balances, notes that the credit exceeds the invoice total, and skips the automated run.
  • When Toggle is "Yes" (Credits Hidden): An account possesses a $500 ledger credit and a new $50 invoice. AutoPay completely ignores the $500 credit balance and automatically processes the $50 collection from the customer's bank account or card as scheduled.


While this setting is highly effective for business structures with long-standing, specialized ledger credits that should not disrupt regular monthly automated billing cycles, it does bypass traditional credit-checking safeguards. Dashboard administrators must remain aware that customers will be charged as scheduled even if they have available funds sitting on their account ledgers.


We recommend consulting with your onboarding integration team to determine if your specific business model requires credits to be fully exhausted before an AutoPay triggers, or if payments should process regardless of credit status.


Was this article helpful?