Parchment and California Legislation on Transcripts and Financial Holds
Parchment Staff •
Dec 20, 2019 •
Blog
We’ve heard many questions from our members on the recently passed California legislation, Assembly Bill No. 1313 Educational Debt Collection Practices Act, which has a direct impact on those that are responsible for transcripts at their institution. If you haven’t taken the time to do so, push pause on reading this blog post and take a minute to review AB 1313 for yourself here.
Here is an extracted excerpt of the bill: …a school shall not do any of the following:
(a) Refuse to provide a transcript for a current or former student on the grounds that the student owes a debt. (b) Condition the provision of a transcript on the payment of a debt, other than a fee charged to provide the transcript. (c) Charge a higher fee for obtaining a transcript, or provide less favorable treatment of a transcript request because a student owes a debt. (d) Use transcript issuance as a tool for debt collection.
Given the number of Parchment members in California, the number of questions that we’ve received, and our commitment to the community, we took some time to sit down with an industry expert on how their institution is handling AB 1313.
We’ve approached this as a Q&A, at the end of the post you’ll have the opportunity to submit additional questions; we’ll either get back to you individually, or post the answer by updating this post.
Give us some background and context on your institution. Loma Linda University is a faith-based health sciences institution located in southern California. We are mainly a graduate/professional institution and 100% of our students are transfer (no first-time freshmen). Our more than 4,400 students in eight schools share the campus with six hospitals where they receive hands-on training, along with opportunities in local and international clinics.
Erin, did you know about AB 1313 before it was passed by the California legislature? Yes. It was on the radar of our Director of Student Finance and between him and our Director of Financial Aid we were kept apprised of where it was in the legislative process.
Once Assembly Bill 1313 passed, who did you start talking within your organization? Within two weeks of the signing of the bill on October 18 we held a general meeting and invited Student Finance (Bursar and Campus-based loans), IT, University Records, and our CFO to talk through the implications of losing the ability to collect debts via transcript holds.
Is there any particular processes at your institution that AB 1313 impacts? Yes. We have multiple holds added to student accounts to help students and alumni follow up on financial obligations. These holds currently prevent the fulfillment of requests for academic transcripts, degree verifications, and diplomas.
As of January 1, 2020, AB 1313 states these holds can no longer prevent a transcript request from being fulfilled. As other institutions may have also recognized, this legislation mostly impacts our campus-based loans, as that is an institutional liability that can no longer be mitigated by withholding transcripts. In the past, we have been able to encourage payment plans and other options to get alumni back on track with loan repayment, but now there needs to be other ways of recouping debt. We are still in conversation about what we will do in that vein.
The first step was to identify all of the holds in the system that (1) are used for financial reasons and (2) prevent the release of transcripts. This was a larger list than we anticipated as some holds are administered by the schools, some by the university, and some by financial officers. We then reviewed the list and set up a process with IT to mark those holds as “null” for all academic transcript requests starting January 1, 2020.
A key understanding we came to was that we are still going to add the holds to the student accounts in our usual practice to ensure other processes work as needed, we just need to turn off the hard stop for transcript requests. Because this process affects how holds work, it was highly important for IT to be at the table and part of the conversation.
This legislation is specific to transcripts, are you changing anything for diplomas and verifications? No, we are only changing the way financial holds affect requests for academic transcripts. We’re going to change the information we send to Parchment to ensure transcripts are not held for financial reasons. Again, an important role for our incredible IT team to fill.
Is this institution specific or student specific? We are taking a read of AB 1313 that because we are in California, it is applicable to all students. That makes it pretty cut and dry for us.
Will you be creating a new hold type for “California Residents”? No, since we are located in California we are treating all transcript requests the same regardless of state residence.
So let’s turn the table, what questions do you have for Parchment.
What have you heard from other member institutions and how they are approaching a solution to AB 1313? We have heard from several institutions who are taking different approaches. Some are taking no action at all. Others are removing financial holds for students and alumni who have an address in California. Our recommendation stands that institutional leaders should review the policy with campus general counsel.
What principles come to mind for Parchment in the context of AB 1313? The number one goal is ease of use, installation, configuration, and maintenance for our members. Our member institutions maintain full control and continuity of their transcript processes. In the same way, the member institution SIS remains the ultimate authority and custodian of their learner records.
How do the Parchment Connectors work? At the highest level they function as a broker between the Parchment platform and your SIS. Hold checks can occur pre or post ordering, but regardless, Parchment works to configure the system to fit the business workflows in place. This includes respecting any transcript impacting holds. In the event the connector locates a hold, the learner is notified and the order is not processed. It’s common to maintain a number of different hold types with specific messaging regarding remediation steps for learners.
As it relates to AB 1313, is Parchment changing anything in its process to circumvent any financial holds on the student record in the SIS? No, we are not changing processes as it relates to AB 1313. If a transcript impacting hold is removed in your SIS, the connector simply won’t locate the hold and insert the request for standard processing.
Where do I go if I have more questions for Parchment about AB 1313? Please submit those questions to info@parchment.com
In summary, review the legislation here, talk to key stakeholders on campus, determine your institutional policy in response to the aforementioned legislation, and as applicable make updates your student information system. There are no configuration requirements required to the Parchment Connectors.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
__cf_bm
30 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
__sharethis_cookie_test__
session
ShareThis sets this cookie to track which pages are being shared and by whom.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
lang
session
LinkedIn sets this cookie to remember a user's language setting.
li_gc
5 months 27 days
This is a cookie from LinkedIn and is used for storing visitors' consent regarding the use of cookies for non-essential purposes
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
liveagent_oref
1 year
This cookie is set by LiveAgent to allow Live Chat assistance for existing customers.
liveagent_ptid
1 year
LiveAgent sets this cookie to link previous chats and transcripts from a single visitor.
liveagent_sid
session
LiveAgent sets this cookie to capture a unique pseudonymous ID when a user requests a chat during an active session.
liveagent_vc
1 year
This cookie is set by LiveAgent to allow Live Chat assistance for existing customers.
NextPage
past
This cookie tracks the previous page to allow users to go back and forth between pages using the user interface buttons.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
X-Salesforce-CHAT
session
This cookie is set by LiveAgent to allow Live Chat assistance for existing customers.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
aka_debug
session
Vimeo sets this cookie which is essential for the website to play video functionality.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-essential
1 year
The cookie is set by the GDPR Cookie Consent plugin to record the user consent for the cookies in the category “Necessary”.
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
STYXKEY_api_token
1 hour
AWS Cloud API
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
vuid
2 years
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
webinarVideo
never
Recursive support screen share session tracking cookie
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Cookie
Duration
Description
__jid
30 minutes
Cookie used to remember the user's Disqus login credentials across websites that use Disqus.
AWSALB
7 days
AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_clck
1 year
Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
_clsk
session
Connects multiple page views by a user into a single Clarity session recording.
_ga
2 years
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_ga_N0Q7GW0J6L
2 years
This cookie is installed by Google Analytics.
_gat_gtag_UA_335339_11
2 hours
Set by Google to distinguish users.
_gat_UA-*
1 minute
Google Analytics sets this cookie for user behaviour tracking.
_gat_UA-335339-11
1 minute
A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to.
_gcl_au
3 months
Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid
1 day
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
AnalyticsSyncHistory
1 month
No description
ANONCHK
10 minutes
The Microsoft Clarity ANONCHK cookie, indicates whether MUID is transferred to ANID, which is a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0 indicating not for advertising.
CLID
1 year
Used by Microsoft Clarity. The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
CONSENT
2 years
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
disqus_unique
1 year
Set by Disqus to record internal statistics for anonymous visitors.
loglevel
never
Collects data on visitor interaction with the website's video-content - This data is used to make the website's video-content more relevant towards the visitor.
SM
session
This Microsoft Clarity cookie is used in synchronizing the MUID across Microsoft domains.
SRM_B
1 year 24 days
Used by Microsoft Clarity as a unique ID for visitors.
ti_
2 years
This cookie is set by Triblio to track the way a visitor uses the website and to monitor the performance of marketing campaigns.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_fbp
3 months
This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
bito
1 year 1 month
This cookie is set by Beeswax for advertisement purposes.
bitoIsSecure
1 year 1 month
Beeswax sets this cookie for targeting and advertising. The cookie is used to serve the user with relevant advertisements based on real time bidding.
fr
3 months
Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE
1 year 24 days
Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
MUID
1 year 24 days
Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations.
NID
6 months
Google sets the cookie for advertising purposes; to limit the number of times the user sees an ad, to unwanted mute ads, and to measure the effectiveness of ads.
S
1 hour
Used by Yahoo to provide ads, content or analytics.
test_cookie
15 minutes
The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
tuuid
2 years
The tuuid cookie, set by Demandbase via BidSwitch, stores an unique ID to determine what adverts the users have seen if they have visited any of the advertiser's websites. The information is used to decide when and how often users will see a certain banner.
tuuid_lu
2 years
This cookie, set by Demandbase via BidSwitch, stores a unique ID to determine what adverts the users have seen while visiting an advertiser's website. This information is then used to understand when and how often users will see a certain banner.
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devices
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-id
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextId
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requests
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.