relationship based dunning · Xero
Relationship-based dunning for creative agencies with Xero.
Connect Xero, encode the rules your team already follows and move every open invoice toward a documented outcome.
Map this workflowOperational fit
Built around how creative agencies actually bill.
deposits, production stages and final delivery invoices.
the next brief often depends on the same buyer relationship.
approval feedback and payment follow-up can cross in the same inbox.
pause when delivery approval or usage rights remain unresolved.
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.
- 01
Identify customer and relationship tier
- 02
Apply the matching cadence
- 03
Invite the account owner where required
- 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.
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.
relationship tier
policy version
handoff reason
Questions before you put it into production.
How is relationship-based dunning used by a creative agency?+
DueHello monitors deposits, production stages and final delivery invoices, applies the configured receivables policy and records why each action was sent, paused or routed to producer and finance owner.
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 pause when delivery approval or usage rights remain unresolved.
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 deposits, production stages and final delivery invoices. We will map the policy, exceptions and Xero data route with your team.
Book a demo