Skip to content
DueHello

invoice dispute workflow · Exact Online

Dispute and exception routing for architecture firms 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 triggera reply, ledger note or team member flags an exception
Accountable ownerproject architect and practice finance

Operational fit

Built around how architecture firms actually bill.

Invoice pattern

design stages, planning milestones and additional services.

Relationship context

the client relationship spans approvals, revisions and delivery phases.

Primary risk

scope revisions can make a standard overdue sequence inappropriate.

Exception route

route scope and approval questions to the project owner before another touch.

One controlled route from signal to outcome.

separate operational exceptions from ordinary late payment and assign ownership. No collection sequence continues while a qualifying dispute is open.

  1. 01

    Classify the exception

  2. 02

    Pause the affected action

  3. 03

    Assign an accountable owner

  4. 04

    Resume only after a recorded resolution

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 exception category, owner and timestamps, resolution note. The team can see what happened without reconstructing it from inboxes.

Evidence 01

exception category

Evidence 02

owner and timestamps

Evidence 03

resolution note

Questions before you put it into production.

How is dispute and exception routing used by a architecture firm?+

DueHello monitors design stages, planning milestones and additional services, applies the configured receivables policy and records why each action was sent, paused or routed to project architect and practice finance.

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 dispute and exception routing workflow?+

The workflow stops or changes route when the exception is resolved, rejected or moved to an agreed owner. DueHello then route scope and approval questions to the project owner before another touch.

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 design stages, planning milestones and additional services. We will map the policy, exceptions and Exact Online data route with your team.

Book a demo