Page Comparison

...

NOTE:  THESE PROCEDURES ARE IN DRAFT STATUS AND ARE SUBJECT TO CHANGE PRIOR TO GO-LIVE.

Procedure Directory

Background

Some CSU libraries export user fine/fee data to campus bursar systems. Creating an automated process allows for greater efficiency and provides the opportunity for integration of online payment through a campus payment processing system.  Alma's existing Bursar integration exports fines and fees data to an ERP system such as PeopleSoft, but upon export, the fines become closed and the user's record becomes active again.  The functionality desired by many campuses would enable fines and fees to be retrieved from Alma, payable by Credit Card through CashNet, with resulting confirmation of payment received by Alma and potentially by email to circulation desk staff.

User fine and fee data is available to 3rd party systems through Alma's External Systems Integration Profile, the User API, and the Analytics API. The first option utilizes Alma's built-in export functionality to extract patron fine/fee data and S/FTP to a campus server. Fines and fees exported via this method are considered closed in Alma, since they are handled by the campus bursar system.

...

Import of user fine/fee payment updates to Alma is available only via the User API method. However, any export method may be used with the payment update import process. Updates to user accounts are made on a per user basis. With PeopleSoft it is possible to utilize a reporting query or a query by an external script to retrieve fine/fee payment data for specific users. 

...

Supporting Documents:

• CashNet Products by Campus

Procedure Statement

This policy applies to the implementation considerations and system configuration required for exchanging user fine/fee data with a campus bursar system. 

...