Skip to content
DueHello

relationship based dunning · Exact Online

Relationship-based dunning for business suppliers with Exact Online.

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

Map this workflow
SourceExact Online administration
Policy triggeran eligible overdue invoice enters a customer-specific policy tier
Accountable owneraccounts receivable and sales owner

Operational fit

Built around how business suppliers actually bill.

Invoice pattern

purchase orders, deliveries and repeat account billing.

Relationship context

the payer is often also an important repeat customer.

Primary risk

purchase-order and goods-received mismatches can masquerade as late payment.

Exception route

distinguish process mismatch from refusal to pay 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

Exact Online data contract

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

DueHello reads receivable status from the connected administration and keeps the accounting record as the source of truth. Connect the administration, select the entities in scope and map the sender identity before activating a playbook.

Fields in scope
invoice number and customer
issue date, due date and open amount
payment and credit status
administration and reference

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 business supplier?+

DueHello monitors purchase orders, deliveries and repeat account billing, applies the configured receivables policy and records why each action was sent, paused or routed to accounts receivable and sales owner.

What data does DueHello use from Exact Online?+

The workflow uses invoice number and customer, issue date, due date and open amount, payment and credit status, administration and reference. DueHello reads receivable status from the connected administration and keeps the accounting record as the source of truth.

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 distinguish process mismatch from refusal to pay 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 purchase orders, deliveries and repeat account billing. We will map the policy, exceptions and Exact Online data route with your team.

Book a demo