Receivables and disputes
Prepares collection context with current dispute and relationship information; no payment moves.
Run the firm
The saved work
A reconciliation query, with the uncertainty intact
The supplied assertions reconcile deterministically to one invoice assertion, INV-NORTH-01, for AUD 100. They also contain a AUD 20 received-payment assertion, PAY-NORTH-01, followed by an exact AUD 20 reversal for that same payment. The payment’s net asserted effect is therefore AUD 0. The supplied reconciliation consequently reports matched receipt assertions of 0 and an asserted balance of AUD 100, labelled “No matching receipt.” No unmatched assertions or held reversals are supplied.
This is not a cash, billing, collection, or legal conclusion. The stated fictional terms make invoice eligibility conditional on explicit acceptance of report12/scope1. The available acceptance material is a simulated sponsor-receipt scenario and expressly does not establish an actual message, signature, acceptance, send, or payment. Accordingly, the actual contract condition and any real invoice eligibility remain unresolved.
A related local example. It shows the stated part of the work, not every step in this design. Read it in saved outputs
- Starts when
- Finance review due or dispute received
- What it works from
- Accounting receivables, terms, disputes and prior contact
- What it prepares
- Exception list and contextual follow-up brief
- What your team decides
- Finance/client owner chooses collection action; no payment movement
What this helps your team do
This path has been checked in the fictional local build.
Responsibilities connected
See what each agent is responsible for preparing in this workflow. These are designs and local examples, not a set of independently running agents.
When it stops and asks
Stale/missing finance, people or effort data remains unknown; the owner receives bounded options rather than an invented operational fact.
Supported scope, source access and authority are agreed for each installation.