Skip to content

Receivables Desk ​

Investigate asset exceptions, examine cohorts, and preserve the decision.

Start with a question ​

“Which obligations are blocked by missing evidence?” “What changed since the last file?” “Which completed line items could form a distinct cohort?” The desk should return a bounded set of assets and a reason for each result.

Workflow ​

  1. Choose the existing local source.
  2. State the question or open the work queue.
  3. Inspect the assets, evidence, and reason for the suggested action.
  4. Review a suggested classification or package.
  5. Save the decision and its source. External messages or system changes require a separate enabled action.

Agent jobs ​

JobInputReviewable output
Exception investigatorSource records and supporting filesA bounded issue list with exact IDs and missing evidence.
Cohort researcherObligations and definition rulesSuggested groups with membership and a source-backed rationale.
Change analystTwo explicitly chosen snapshotsAdded, removed, and changed records with their source differences.

Scope each task ​

Use these workflow patterns to define the input, evidence, and reviewable output. Start with the local source and an exact question. A saved finding must identify the records that support it.

Build acceptance ​

Every finding must resolve to exact records. A suggested group must show its rule and members. Source records remain unchanged. A new snapshot must not rewrite an earlier result. Any cloud step must identify the data it sends.

MINT · Product documentation