One caseAwaiting evidence
Rate mismatch
Invoice rate differs from agreed terms.
Disputed amount
€240.00
Applicable rule
Agreed contract rate
Owner
Accounts Payable
Next action
Request supporting evidence
Disputes
Turn discrepancies into resolved disputes.
One discrepancy. One case. One documented path.
Donnerstag turns a verification discrepancy into a managed dispute with the financial impact, reason, evidence, owner and next action attached, and carries it through resolution rather than leaving it between systems and inboxes.
Part of Accounts Payable · see the full AP operation
One case, with everything attached.
The disputed amount, the applicable rule, the reason, the owner and the evidence, all on one record.
Illustrative case
Source documents
Invoice
Contract
Email
Create, manage, resolve.
A discrepancy becomes structured work rather than an email thread.
01
Create the case
A discrepancy becomes a structured case with the financial impact, reason, applicable rule and evidence already connected.
02
Manage the work
Assign an owner, track status and drive the next action across the resolution path.
03
Resolve and record
Carry the dispute to a documented outcome, preserving who decided, under which rule and on what evidence.
Prioritized by what is at stake.
Supplier and customer cases in one queue, ranked by financial impact and age.
Open cases
Value in dispute
Past SLA
Sorted by exposure
Case
Counterparty
Disputed
Age
Stage
41d
Escalated
22d
Awaiting evidence
14d
Response received
9d
Approved
3d
Raised
The whole case, summarized for you.
The system summarizes what happened and why, with every document, record and proof attached, so no one rebuilds the story from scratch.
Illustrative case
Source documents
01
Invoice
02
Contract
03
Email
What happened, in one read
The system states the discrepancy, the rule it breaks and the amount at stake, without anyone reconstructing it.
Every document attached
Invoice, purchase order, receipt, contract clause, rate card and correspondence sit on the case itself.
The proof, linked to the claim
Each piece of evidence is tied to the specific line it supports, so the argument is ready to send.
Full history preserved
Owner, status, prior actions and approvals stay on the case from first flag to final outcome.
Cases arrive typed and quantified.
With the evidence that supports the challenge already gathered.
Unsupported
Charge without basis
A surcharge or fee appears with no support in the contract or rate card.
Resolution:
Challenge the charge with the clause and rate card attached.
Variance
Quantity under-delivery
The invoice bills more than the receipt confirms was delivered.
Resolution:
Dispute the balance with the goods receipt as evidence.
Duplicate
Duplicate charge
The same charge appears twice across invoices or periods.
Resolution:
Reject the duplicate and reference the original document.
Rate
Rate mismatch
The applied rate differs from the agreed commercial terms.
Resolution:
Recover the difference once the resolution confirms it is owed.
How a case reaches resolution and write-back.
Select an action to see what it does, and the authority it runs under.
01
Open
Create the case with impact and rule attached.
02
Evidence
Gather the documents that support the claim.
03
Challenge
Notify the counterparty with the argument.
04
Approve
Route the decision to the right authority.
05
Write back
Post the outcome and preserve the trail.
Act on the case
Resolved, then written back.
Once the case closes, the outcome posts back to your ERP with the rule, decision, approver and evidence preserved behind it.
Case resolved
Outcome recorded
Approval attached
Posted to ERP
Audit trail kept
See every open case. Drill to any dispute.
An overview of disputes at operation level, then open to the case, reason, evidence and decision behind every figure.
Open cases
Value in dispute
Past SLA
Sorted by exposure
Case
Counterparty
Disputed
Age
Stage
41d
Escalated
22d
Awaiting evidence
14d
Response received
9d
Approved
3d
Raised
Keep every case answerable.
Know what is disputed, why, and what happens next.
What is disputed?
The affected item and financial lines.
Why is it disputed?
The discrepancy and applicable rule.
How much is at stake?
The financial impact of the case.
What supports it?
The relevant records and documents.
Who owns it?
The responsible person or workflow.
How did it end?
The documented final outcome.
What dispute management gains
Disputes stall when no one owns them. These are the outcomes the operation is built to produce.
Resolve disputes faster
Give each case the reason, evidence, financial impact, owner and next action required to move it forward.
Work more discrepancies
Make it practical to pursue items that previously received little attention because handling took too much manual effort.
Stronger counterparty conversations
Work from a structured case containing the amount, rationale and evidence instead of reconstructing the issue across systems.
Nothing lost between teams
Cases carry a clear owner and status, so disputes do not stall in inboxes and handovers.
Consistent resolution paths
Reason codes and workflows follow your policy, so similar disputes resolve the same way every time.
Traceable outcomes
Every resolution preserves who decided, under which rule and on what evidence.
Discrepancies start in verification.
Every dispute case originates from a flagged line in Invoice Verification, arriving with its rule, amount and evidence attached.