.png)
Most AR teams set up one collections workflow and apply it to everyone. A reminder goes out at 7 days past due, another at 15 days, escalation at 30 days. Clean, simple, completely wrong for about 60% of your customer base.
The problem isn't the workflow design. It's the assumption that all customers should be treated identically. A Fortune 500 company with a 60-day payment cycle doesn't need the same reminder cadence as a small business paying net 30. A customer who consistently pays 5 days late but always pays shouldn't trigger the same escalation as someone who's 45 days overdue for the first time.
Centime's platform offers two fundamentally different approaches to collections automation: customer-level workflows and invoice-level workflows. Understanding when to use each one will determine whether your automation actually improves collection efficiency or just generates more noise.
See Centime in action
Our innovative AR, AP and business banking solutions are powerful alone, and even better together.
Schedule a tailored demo with a Centime expert.
How Customer-Level Workflows Actually Work
Customer-level workflows treat the relationship as the unit of management, not the individual invoice. When you enroll a customer in a customer-level workflow, the system looks at their entire outstanding balance and payment behavior across all invoices to determine communication timing and content.
This matters most for customers with ongoing relationships. If you're invoicing someone monthly for managed services, they might have 3-4 open invoices at any given time at different stages of their payment cycle. Sending separate reminder sequences for each invoice creates email chaos. The customer receives multiple messages about different invoices, often within the same day, each with slightly different tones depending on how overdue each one is.
Customer-level workflows consolidate this. The system evaluates the customer's total exposure, identifies which invoices need attention, and sends one communication that addresses everything at once. Your customer gets a clear picture: "You have three outstanding invoices totaling $15,400. Here's the breakdown and payment options."
The January 2025 platform release added enhanced workflow collaboration features, including shared team views that let AR and sales teams coordinate on customer-level strategies. This addresses a real pain point: sales needs visibility into collection status without getting bombarded with individual invoice alerts. Customer-level workflows give them a single source of truth per customer rather than a scattered list of invoice-specific actions.
When Customer-Level Makes Sense
High-volume, recurring relationships are the obvious fit. SaaS companies, professional services firms, distributors with standing orders, and anyone billing the same customers repeatedly should default to customer-level workflows. If you're generating more than one invoice per customer per quarter, you're probably creating unnecessary complexity with invoice-level approaches.
One services company moved 80 of their top customers from invoice-level to customer-level workflows and saw email volume drop by 60% while collection effectiveness actually improved. The customers were paying faster because they weren't getting overwhelmed by separate reminder streams for every open item.
Relationship-sensitive accounts benefit from customer-level treatment. When you're working with strategic partners, key accounts, or customers where the sales relationship matters more than the transactional payment, you want collections to feel coordinated and professional. Customer-level workflows let you maintain consistent messaging tone and ensure you're not accidentally escalating on one invoice while the customer is paying down others.
According to AFP's 2025 Payments Fraud Report, maintaining strong customer relationships through professional collections practices directly correlates with payment reliability. Customers who view their suppliers as partners rather than adversaries pay 18% faster on average.
Complex payment terms often require customer-level logic. Customers with payment plans, negotiated schedules, or credits/adjustments across multiple invoices need workflow rules that can evaluate the whole picture. Invoice-level workflows process each item independently and can't factor in whether the customer is meeting their overall payment obligations even if individual invoices appear late.
See Centime in action
Our innovative AR, AP and business banking solutions are powerful alone, and even better together.
Schedule a tailored demo with a Centime expert.
The Invoice-Level Alternative
Invoice-level workflows treat each invoice as an independent collection event. The moment an invoice is created, it enters a workflow sequence based on its due date and terms, regardless of what else is happening with that customer.
This approach works best for transactional, low-frequency relationships. If you're invoicing a customer once or twice per year, there's no relationship rhythm to disrupt. Each invoice stands alone. A construction subcontractor billing for a specific project completion, a consultant invoicing for a one-time engagement, or a retailer selling to infrequent buyers are all good invoice-level candidates.
High-value, one-off transactions often need invoice-specific attention. A $500,000 equipment sale shouldn't be bundled into a general "you have outstanding invoices" message alongside routine $2,000 monthly charges. Invoice-level workflows let you create specialized sequences for specific transaction types or amounts.
Invoice-level also makes sense when payment responsibility varies by invoice. Some companies have different departments or subsidiaries handling payments for different types of purchases. When your contact for invoice A is completely different from your contact for invoice B (even though both are technically the same customer in your ERP), invoice-level workflows ensure the right message reaches the right person.
The Hybrid Approach Most Companies Actually Need
Here's what happens in practice: you need both.
Set up customer-level workflows as your default for about 70% of your customer base (regular, repeat customers with ongoing relationships). Then carve out specific invoice-level workflows for edge cases: high-value transactions above a certain threshold, specific product lines that require specialized collection treatment, or customer segments where you don't have established payment patterns yet.
Centime's workflow settings let you layer these approaches. You can establish a customer-level workflow as the baseline, then create invoice-level exceptions that trigger when certain conditions are met. For example, most invoices for Customer X follow the customer-level sequence, but any single invoice over $50,000 automatically enters a specialized high-value invoice-level workflow with different timing and messaging.
The shared views feature released in January 2025 makes this hybrid approach manageable. You can create filtered views that show: all customers in customer-level workflows with balances over $10,000, all invoices in specialized invoice-level sequences, customers with mixed workflow types, and exceptions requiring manual review. Different team members can subscribe to the views relevant to their role without drowning in the full dataset.
See Centime in action
Our innovative AR, AP and business banking solutions are powerful alone, and even better together.
Schedule a tailored demo with a Centime expert.
Segmentation Strategies That Actually Work
The most effective collections operations segment customers into tiers before assigning workflow types. Research from SSON's AR Trends & Insights Market Report found that companies using customer segmentation in their AR processes reduce DSO by 10-15% compared to one-size-fits-all approaches.
Start with payment behavior, not just invoice volume.
Tier 1: Strategic accounts with excellent payment history. These customers pay consistently, communicate proactively about timing issues, and represent significant ongoing revenue. Put them in customer-level workflows with gentle, relationship-focused messaging. Your first reminder might not go out until 10 days past due, and the tone should assume good faith. Something like: "We wanted to make sure this invoice didn't get lost in the shuffle" rather than "Your payment is overdue."
Tier 2: Standard customers with generally good payment patterns. They occasionally pay a few days late but nothing concerning. Customer-level workflows with standard timing (reminder at 3 days past due, follow-up at 10 days, escalation at 20 days). This is probably 60-70% of your customer base.
Tier 3: Inconsistent or new customers. Either they don't have enough payment history for you to assess reliability, or their track record is spotty. Use invoice-level workflows here because you want tighter monitoring of each transaction. If a new customer's first invoice goes 15 days past due, you need to know immediately and address it specifically, not wait for a consolidated customer-level review.
Tier 4: Problem accounts. Customers with multiple past-due invoices, history of disputes, or collection issues. These might need specialized workflows (either customer-level or invoice-level depending on the situation) with faster escalation timing and possibly direct AR manager involvement rather than automated messages.
You can also segment by invoice characteristics rather than customer attributes. Create invoice-level workflows for: invoices over a certain dollar threshold, specific product categories that have higher dispute rates, international invoices with different payment timing expectations, or invoices flagged for specific payment terms during the sales process.
See Centime in action
Our innovative AR, AP and business banking solutions are powerful alone, and even better together.
Schedule a tailored demo with a Centime expert.
Communication Frequency and Email Fatigue
One benefit of customer-level workflows that doesn't get enough attention: they naturally throttle communication volume. When you're sending one consolidated message per customer instead of separate messages per invoice, you dramatically reduce the risk of email fatigue.
Industry data shows that collection email effectiveness drops by 35% after the fifth reminder, according to research on accounts receivable statistics. Invoice-level workflows can easily trigger this when a customer has multiple open invoices. You might send 3 reminders per invoice × 4 open invoices = 12 emails in a two-week span. At that point, your messages are just noise.
Customer-level workflows consolidate this into 3-4 total messages covering all open items. The customer gets a manageable volume of communication and can address their entire obligation in one action rather than sorting through individual invoice requests.
That said, invoice-level workflows have a place when you want high-frequency, invoice-specific follow-up. A contractor waiting on payment for a completed project milestone might prefer targeted messages about that specific invoice rather than bundled statements. The key is matching communication strategy to customer expectations and relationship dynamics.
Technical Implementation: How to Set This Up
In Centime, customer-level workflows require some upfront customer configuration. You need to establish customer-level receivables settings that define how that customer should be treated: workflow assignment, communication preferences, payment terms, and any custom rules that apply.
Start by exporting your customer list and adding a "workflow type" column. Go through your top 50 customers by revenue and manually classify each one: customer-level standard, customer-level strategic, invoice-level, or needs custom treatment. This sounds tedious but it's worth it. These 50 customers probably represent 70-80% of your AR balance.
For the remaining customers, create classification rules based on observable criteria: customers with 6+ invoices in the past 12 months → customer-level standard, customers with 2-5 invoices in the past 12 months → evaluate case by case, customers with 0-1 invoices in the past 12 months → invoice-level.
Once you've made initial assignments, set up workflow monitoring to track performance by workflow type. You want to measure: average days to payment for each workflow type, number of reminders sent per dollar collected, escalation rate (what percentage of invoices require manual intervention), and customer satisfaction scores if you collect feedback.
The January 2025 update to Centime's collaboration features means you can create shared views for different stakeholders. Your AR manager might want a view showing all customers in specialized workflows with pending collection actions. Your CFO might want a high-level view showing total exposure by workflow type. Sales might want to see their accounts flagged for possible escalation before it happens.
See Centime in action
Our innovative AR, AP and business banking solutions are powerful alone, and even better together.
Schedule a tailored demo with a Centime expert.
When to Override Your Workflow Defaults
Automated workflows are powerful, but they're not gospel. You need clear override protocols for situations that warrant manual intervention.
Material changes in customer circumstances require reassessment. If a strategic customer-level account suddenly has layoffs, leadership changes, or public financial distress, you might temporarily shift them to tighter invoice-level monitoring until the situation stabilizes. Conversely, if a Tier 3 customer consistently pays early for six months, promote them to customer-level treatment.
Large, unusual transactions might justify pulling a specific invoice out of the standard workflow. If a customer who normally buys $5,000 monthly suddenly places a $50,000 order, that invoice probably deserves specialized attention regardless of their usual workflow assignment.
Relationship events can trigger manual overrides. If your sales team is negotiating a major contract renewal, you probably don't want automated escalation messages firing at the same time. Temporarily pause or modify workflows for customers in active sales discussions, dispute resolution, or contract negotiations.
According to VersaPay's research on AR collections best practices, companies that maintain open communication channels between AR and sales teams resolve payment issues 40% faster than those operating in silos.
Measuring What Actually Matters
The point of workflow segmentation isn't to have elegant categorization. It's to collect more money, faster, with less effort.
Track these metrics separately for customer-level and invoice-level workflows:
Collection effectiveness index (CEI): This measures how much of the collectable AR you actually collected in a period. Calculate it as (Beginning AR + Period sales - Ending AR) / (Beginning AR + Period sales - Ending AR over 90 days) × 100. Your customer-level workflows should show higher CEI because you're maintaining relationship continuity and catching issues earlier through consolidated monitoring.
Days sales outstanding (DSO) by workflow type: Customer-level workflows typically reduce DSO by 8-12 days compared to treating the same customers with invoice-level approaches. If you're not seeing this improvement, your customer-level messaging might be too gentle or your timing too slow.
Research from HighRadius on AR automation trends indicates that companies implementing workflow segmentation strategies achieve 10-15% DSO improvements within the first year, with the gains concentrated among their highest-volume customer relationships.
Cost to collect per dollar: This should be substantially lower for customer-level workflows due to reduced message volume and less manual intervention. If it's not, you might be enrolling too many high-touch customers in automated flows.
Customer satisfaction impact: Survey a sample of customers about their experience with your collections process. Customer-level workflows generally score higher for "professional" and "easy to understand" while invoice-level workflows score higher for "clear and specific." Neither is better; they serve different purposes.
The Strategic Decision Point
Choosing between customer-level and invoice-level workflows is really a question about how you view accounts receivable. If you see AR primarily as a transactional function (invoices go out, payments come in, manage exceptions), invoice-level workflows align with that model. Each invoice is a discrete task to complete.
If you see AR as a relationship management function (customers buy from us repeatedly, payment is one touchpoint in an ongoing relationship, collection strategy should reinforce rather than damage the relationship), customer-level workflows match that philosophy better.
Most mid-market companies are transitioning from the first view to the second as they mature. Early-stage companies treat each invoice as a separate event because they don't have enough repeat business to need relationship-level thinking. As revenue becomes more predictable and customer lifetime value extends beyond single transactions, customer-level approaches deliver better outcomes.
According to the 2026 B2B Payments Outlook from Bottomline, finance leaders are increasingly prioritizing relationship preservation alongside collection efficiency, recognizing that overly aggressive collections tactics cost more in lost future revenue than they gain in immediate payment acceleration.
The workflow strategy you choose reflects where you are in that maturity curve. And if you're somewhere in the middle, mixing both approaches based on customer segmentation, that's probably exactly right.