Skip to content
DueHello

relationship based dunning · Xero

Relationship-based dunning for consultancies with Xero.

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

Map this workflow
SourceXero organisation
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

Xero data contract

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

DueHello monitors receivables from the connected organisation and evaluates each next action against the configured policy. Connect the organisation, choose the accounts and invoice states in scope, then validate sender and approval rules.

Fields in scope
contact and invoice number
currency, total and amount due
issue date and due date
status and organisation

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 Xero?+

The workflow uses contact and invoice number, currency, total and amount due, issue date and due date, status and organisation. DueHello monitors receivables from the connected organisation and evaluates each next action against the configured policy.

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 Xero data route with your team.

Book a demo