2025-06-06 Acquisitions Meeting notes - Encumbrances/Payments Against Upcoming Fiscal Year

2025-06-06 Acquisitions Meeting notes - Encumbrances/Payments Against Upcoming Fiscal Year

 Date

Jun 6, 2025

Recording

acquisitions-sig/2025-06-06

 Participants

Aaron Neslin

Joe Reimers

Martina Schildt

Ann Crowley

Kimberly Pamplin

Masayo Uchiyama

Dennis Bridges

Kimberly Wiljanen

Michael Hobson

Dung-Lan Chen

Kristin Martin

Molly Driscoll

Dwayne Swigert

Linh Chang

Owen Stephens

Heiko Schorde

Lisa Maybury

Scott Perry

Jackie Magagnosc

Lisa Smith

Susie Skowronek

Jean Pajerek

Lucinda Williams

Victoria Anderson

Daniel Welch

 

 

 Agenda

 

Housekeeping -

Product Council

 

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

:02

Housekeeping

Ann Crowley

:02

PC

Kristin Martin

  • 2025-05-29 Product Council Agenda and Meeting Notes

    • Discussion of Community priorities - to be continued

  • How to take priorities given by SIGs and prioritize across them

  • Development of rubric

  • Business need, criticality, impact, competitiveness, usability, alignment with FOLIO vision (need agreed upon FOLIO vision)

  • At member meeting, asked why members have chosen to be members:

    • Digital sovereignty - control over own data and product

    • Make life easier for people who use FOLIO every day

:05

Encumbrances/Payments against upcoming fiscal year

Joe Reimers

  • Features in backlog:

    • Allow encumbrances against upcoming fiscal year

    • Pay invoices against an upcoming fiscal year

  • Conceptual discussion before framing this out

  • Have already enabled support for operations in previous fiscal years

  • Electronic resource databases - multi-year commitment where vendor will give a better deal. May invoice for all three years. Library will pay current portion, but accounts payable will pay the whole amount.

    • When new fiscal year starts, would invoice in FOLIO however much it was supposed to be even though Accounts Payable has already paid for the whole thing.

  • Large prepayments out of Harrassowitz and EBSCO. Don’t use prepaid account, but prepaid object code.

  • Getting a sense there is not a lot of urgency for this?

    • Agreement

    • Don’t necessarily know what allocations will be for the funds.

  • Currently in FOLIO has to be money to encumber or pay against

  • How do you do the business logic?

    • Programming and troubleshooting perspective sounds like a nightmare

  • If you don’t know what next fiscal year budget will look like, can probably just use last year’s allocation and then adjust once known.

  • Are there circumstances where cash is all technically paid in one year, but you are allowed to spread value over balance sheet for three years?

    • Yes

  • Library budget is impacted differently. University essentially extends credit to allow library to spread this out and institution saves money from discounted rate.

  • Has any other system offered this?

  • Example of scenario on smaller scale compared to prepaid. Agreement with outside department where library’s budget was hit all in one year, but outside department is paying over a number of years. Processed as credits.

  • All linked together by the order. Is there anything problematic about doing it that way?

  • You can’t create an invoice ahead of time.

    • Maybe could, but it would be pending.

  • What’s the annoying part about having to create multiple invoices?

    • Having to remember to create them

    • Want the expense in the correct fiscal year

  • What reminds you to create invoices?

    • Spreadsheets

    • Balance prepaid object code against accounts

    • Get a report from the university accounting

  • More about workflow management and making sure things don’t get missed than actually reporting those numbers and forecasting? Or maybe some of both

  • Dependent on person handling it

  • Mixing it in with invoices may not necessarily be ideal - Catch-22.

  • What percentage of stuff is managed this way? How prevalent are these transactions?

    • Dung-Lan Chen - for our institution relatively small

    • Ann Crowley - maybe 10% of total budget

  • Is that trend increasing, decreasing, or pretty constant?

    • Cornell - Increasing this year - will be doing 5 more vendors, but not to level of other two. Not sure if this will continue, it may just be a special year.

    • Dung-Lan Chen - Stays kind of the same with the same vendors.

  • Folks that are part of Consortia, is there any kind of Consortium purchasing that is similar?

  • Kristin Martin 8:32 AM
    I think there are always opposing forces: stability and cost-savings over time vs. flexibility for the future

  • Usually commit to things where it is not expected to cancel.

  • Often for more than one year because it takes a lot of effort to do the negotiation. Doing that annually is not very feasible.

  • For Read & Publish agreements and other complicated deals trying to plot out a time horizon is helpful.

  • Molly Driscoll 8:38 AM
    I'd recommend reaching out to Slack about the topic because I know some libraries in Oceania are very interested in the multi-year spending but cannot attend this meeting slot.

:37

UAT - Orders - Unlink titles from package POLs

Dennis Bridges

  • UAT set up for Package POLs - unlinking titles

  • If you have any inventory records set up, there is an interaction there when you remove titles.

  • Plan was for this to start on Monday (6/9)

  • https://folio-org.atlassian.net/wiki/x/AQCRPQ

    • Link to environment, instructions, step-by-step guide

 

 

 

  • Reminder: UAT for lists app closes out today

:41

Expense Class Question

Dung-Lan Chen

  • Discussion regarding handling of one-time orders rolled into new fiscal year where previous year does not have expense class and need to set one up in the new year.

  • At the moment would need to go back and edit the fund distribution in the open order.