Configure the Parchment-Banner integration using the Ellucian eTranscript API connector, establishing SFTP key-based authentication to the Parchment SFTP server
Define the trigger in Banner Self-Service or Banner workflow: when a student submits a transcript request, generate a transcript request record with recipient details in the Banner integration table
Export the request record to a delimited file or invoke the web service endpoint that Parchment has provisioned for your institution, passing student ID, recipient address, hold-for-degree flag, and rush indicator
Parchment processes the request, generates the official transcript PDF, and delivers it electronically or by mail to the recipient; a status event is returned to the SIS
Poll the Parchment status endpoint or receive an SFTP drop file with delivery confirmations and map confirmation codes back to Banner transcript request records
Update the Banner transcript request status to 'sent' and notify the student via Banner workflow or email
Known gotchas
Parchment's integration model is institution-specific: some institutions use direct SFTP file exchange while others use the Ellucian eTranscript web service API; implementation steps differ materially between the two approaches
Hold-for-grades and hold-for-degree flags must be evaluated in Banner before the request is exported; Parchment will not block fulfillment based on SIS holds unless the integration explicitly withholds the request
Transcript delivery confirmations may arrive hours to days after the initial send depending on recipient institution's intake process; design the status reconciliation process to handle delayed confirmations without timing out
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp