Ask the receiving department what it needs to do with each transferred record. Then ask IT and Ellucian to confirm whether the proposed source and target support that transfer. Keep unanswered questions in the interface specification until a named person can confirm the method and approve the test result.
Start with the receiving department's task
Ask the Registrar, admissions team or other receiving department to describe the task the interface must support. For an enrollment report, have the report owner identify the student population, effective date and fields staff need.
Ask the integration lead to write the actual source product, deployment, version and receiving system beside that requirement. Distinguish Banner Student on-premises from the contracted Ellucian Student target. Include systems that will stay in place during the move.
Confirm the proposed access with Ellucian
If Ethos Integration is proposed, ask Ellucian to confirm the resource and version relevant to this environment. Compare its confirmed fields and operations with the receiving department's requirements. Do not assume that a resource name establishes access to every required value.
Ask IT to record the accounts and permissions required for the approved transfer. Have Ellucian confirm any applicable access conditions, limits and supported method in the current documentation or a written response.
Ask the receiving-system vendor to confirm how it accepts those records. If a required field or operation is unconfirmed, leave that part of the specification open. Do not substitute an unapproved database read or claim that an extension will solve it.
Check the required volume and transfer time
Ask the department when it needs the records and how many it expects during an ordinary period and a busy one. Separate any initial transfer from later changes so the integration lead can test both requirements.
Ask Ellucian and the receiving vendor to confirm the limits that apply to the proposed method. Then have IT run a permitted test with an agreed set of records and record when it starts, when it finishes and which records arrive.
Compare the measured result with the department's deadline. If it does not meet the requirement, ask the vendors about supported alternatives or ask the department whether the requirement can change. Record that decision before accepting the design.
Compare record contents, not just successful transfers
Have the records owner choose approved sample records and expected values. Include the history and local codes needed for the task, and confirm how the proposed method will provide them. Do not infer historical access from a current-record test.
Ask the integration lead to compare the sent and received counts. Have the receiving department check record contents, dates and code meanings against the agreed samples. Record each missing or changed value and who will investigate it.
If the transfer uses a mapping, name the person who approves it and keep the approved version with the specification. Retest affected records when that mapping changes.
Test rejection, retry and support
Ask IT to test a permitted record that the receiving system rejects. Confirm that the responsible staff member can find the rejection, understand it and decide whether to correct the source or change the transfer.
Test a retry after a failed transfer. Compare the receiving records before and after the retry to check that it has not created duplicates. Record the results; do not assume that the proposed method prevents them.
Have the records owner confirm who may correct a record. Have IT confirm who investigates a transfer failure and who contacts Ellucian or the receiving vendor. Put the agreed contact and escalation arrangements with the test record.
Ask the department approver to review the counts, sample contents, rejected records and retry results. Record whether the interface is accepted, needs correction or should wait.
Reconfirm the interface when the environment changes
Before a move to SaaS or another deployment, ask Ellucian and the receiving vendor to confirm support for the actual target. An interface that works in the current environment is not automatically approved for the new one.
Repeat the agreed transfer and permission tests in the proposed environment. The receiving department should approve the result before the old transfer is retired. Keep unresolved product questions with a named person and a date for the next answer.

