Connections to configure

• Applicant identity or intake system. Configure the chosen source separately and agree how staff identify the intended applicant and assessment. A readable applicant name must not substitute for the organization’s identity process.
• Payment or treasury system. Agree the source of the payment reference, what it identifies and how Benefits Officer inspects actual payment confirmation. Benefit status progression preserves the amount and does not write monetary actuals.
• Accounting system. Keep expense verification distinct from the external payment event that supports Paid. Agree the monetary convention and how confirmation evidence is retained.
• Evidence and reporting sources. Establish the source of milestone, expense and outcome attachments and verify access for the intended reader. Map reporting periods and measure definitions before importing outcome inputs.

Program Manager agrees program and criteria ownership with the responsible source owner. Benefits Officer defines the payment-reference handoff, Finance Officer defines external expense confirmation and Monitoring Officer checks the reporting basis.

Identify the exact assessment or program before importing linked records. Inspect existing planned benefits and kickoff work before repeating a creation action. A reference supplied by another system needs an agreed interpretation and access to the supporting evidence.

Rehearse an unavailable payment reference, an assessment without a usable date and an outcome with no denominator before release. Review implementation with the people responsible for each side of the connection.