Skip to content
DueHello

relationship based dunning · Custom ERP integration

Relationship-based dunning for consultancies with Custom ERP integration.

Connect Custom ERP integration, encode the rules your team already follows and move every open invoice toward a documented outcome.

Map this workflow
Sourceapproved ERP or finance-system connection
Policy triggeran eligible overdue invoice enters a customer-specific policy tier
Accountable ownerengagement partner and finance lead

Operational fit

Built around how consultancies actually bill.

Invoice pattern

monthly retainers, time-based fees and milestone billing.

Relationship context

senior stakeholders expect context-aware communication.

Primary risk

a reminder can undermine an ongoing engagement or renewal conversation.

Exception route

surface commercial blockers to the engagement owner before increasing pressure.

One controlled route from signal to outcome.

adapt collection pressure to customer tier, history and active commercial context. Customer tier changes cadence; it never hides the underlying balance.

  1. 01

    Identify customer and relationship tier

  2. 02

    Apply the matching cadence

  3. 03

    Invite the account owner where required

  4. 04

    Re-evaluate after every payer signal

Custom ERP integration data contract

Use the ledger as truth. Add the decision layer it lacks.

A scoped integration supplies the minimum receivables events needed for monitoring, decisions and outcome updates. Agree source ownership, field mapping, update frequency, failure handling and security review during implementation.

Fields in scope
stable invoice and customer keys
balance and lifecycle status
dates, entity and currency
exceptions, payments and ownership

Evidence remains attached to the decision.

For this workflow, DueHello keeps relationship tier, policy version, handoff reason. The team can see what happened without reconstructing it from inboxes.

Evidence 01

relationship tier

Evidence 02

policy version

Evidence 03

handoff reason

Questions before you put it into production.

How is relationship-based dunning used by a consultancy?+

DueHello monitors monthly retainers, time-based fees and milestone billing, applies the configured receivables policy and records why each action was sent, paused or routed to engagement partner and finance lead.

What data does DueHello use from Custom ERP integration?+

The workflow uses stable invoice and customer keys, balance and lifecycle status, dates, entity and currency, exceptions, payments and ownership. A scoped integration supplies the minimum receivables events needed for monitoring, decisions and outcome updates.

What stops the relationship-based dunning workflow?+

The workflow stops or changes route when relationship context requires a pause, handoff or revised route. DueHello then surface commercial blockers to the engagement owner before increasing pressure.

Does DueHello replace the finance or account team?+

No. DueHello performs the permitted follow-up and brings exceptions to the accountable person with the context and evidence needed to decide.

Map this against real invoices.

Bring one month of monthly retainers, time-based fees and milestone billing. We will map the policy, exceptions and Custom ERP integration data route with your team.

Book a demo