1691 results found

1. Better management of serial prediction when publication frequency changes

   Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.

   It would save a lot of time if Alma could change the description (number, date, …) only for the items that are impacted by a new publication during the year. We would just have to fill the « Next prediction item’s information » with the new frequency.
   This enhancement would save a lot of time to catalogers.

   Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.

   It would save a lot of time if… more

   418 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Bursar integration: Additional fee statuses in Alma & Allow fee status change with job Import from Bursar

   Currently there exist in Alma only the fee statuses “open”, “transferred” and “closed”. Transferred means fee was exported to external Bursar system. When the fee is imported back to Alma, it is automatically Closed. For staff it is not possible to tell if the closed fee was paid, waived, unpaid etc. without consulting the 3rd party Bursar system.
   To give the librarians and end users more transparency about the (invoice) status of a fee, we would need more differentiated fee statuses. Also, we need to be able to set this status when importing the fees back to Alma using the job Import from Bursar.
   The optimal development would be:
   1. Have the possibility to configure ourselves in Alma which fee statuses we want to use and to have the possibility to add additional fee statuses.
   2. The Import from Bursar job must be able to set this status based on a field in the import XML file.
   If the #1 is not possible, it would be good to have the following additional fee statuses implemented:
   invoiced
   unpaid
   partial payment
   paid/closed
   storno
   write-off
   transferred to the debt collection
   e-mail not deliverable

   Currently there exist in Alma only the fee statuses “open”, “transferred” and “closed”. Transferred means fee was exported to external Bursar system. When the fee is imported back to Alma, it is automatically Closed. For staff it is not possible to tell if the closed fee was paid, waived, unpaid etc. without consulting the 3rd party Bursar system.
   To give the librarians and end users more transparency about the (invoice) status of a fee, we would need more differentiated fee statuses. Also, we need to be able to set this status when importing the fees back to Alma using the… more

   373 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   15 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Metadata editor: Enable moving up and down within a field using arrow keys

   It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.

   My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.

   Using up/down arrow keys when moving within a field would streamline cataloger’s work and help making the MDE more user-friendly.

   It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.

   My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.

   Using up/down arrow… more

   344 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Show Pickup location in the tables "Requests" and "Loans" in Patron Services

   It would be helpful ig the information “Pickup location” could be added as a column in the tables “Requests” and “Loans” in the “Patron services” in order to see the destination chosen by the Patron. Furthermore, the "Pickup location" should be displayed in Primo in the patron’s account - also in the "Loans" not only in the "Requests".

   314 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Serials: Editing of Description Needed

   When opening predicted items, the Description-Field is populated by the data provided in “Next Predicted Item´s information” and displays these data in a certain punctuation-logic. Unfortunately, this logic is not equal to the description- (and punctuation-) logic used in German speaking countries (which is following ZETA-Standard) – and there is no possibility to edit this. Since there has to be a correct description (for sorting etc.), the only way is to open and edit every single item once it is created by prediction pattern. This is causing a lot of unnecessary work to be done manually - we need the description template to be editable so that items with a correct description can be created automatically in the first place!

   Impact of Problem: Predicted items are displayed in a certain logic, for example: “V:No(Year)” [journal] or “Year: Day” [newspaper]. Format needs to be editable to suit local format (and punctuation) logic – for example “V.Year,No” [journal] or “Year,Day” [newspaper]

   When opening predicted items, the Description-Field is populated by the data provided in “Next Predicted Item´s information” and displays these data in a certain punctuation-logic. Unfortunately, this logic is not equal to the description- (and punctuation-) logic used in German speaking countries (which is following ZETA-Standard) – and there is no possibility to edit this. Since there has to be a correct description (for sorting etc.), the only way is to open and edit every single item once it is created by prediction pattern. This is causing a lot of unnecessary work to be done manually - we need the… more

   292 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. recall

   Update Lending and Borrowing Status when Recalls of Resource Sharing items are cancelled

   Currently, once an item is recalled in Resource Sharing, it stays in that status even after the recall is cancelled by the patron. If this could have the same functionality as regular Fulfillment (which can be configured to have the item's original return date applied if recall is dropped), that would be ideal.

   280 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Resource Sharing  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Batch deleting PO's

   There is currently no system job to delete PO's. These have to be done manually using the Acquisitions>Purchase Order>Delete PO function individually in ALMA.

   We have 1000's of old orders migrated from our legacy system that are no longer required. We also now only keep 7 years worth of orders in line with current financial practice and so would like to be able to set a job to batch delete at rollover into the new fiscal period.

   256 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   7 comments  ·  Acquisition - PO & POLine  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Alma - automatic warning for users about to expire with dedicated alma xml letter

   It would be useful to activate an automatic warning for users about to expire with dedicated alma xml letter.
   The customer could simply set up the amount of days before expiration and if the letter should be sent to all users or to specific user groups. A scheduled job could be activated, so that the letter is sent every day at a specific time.

   248 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   11 comments  ·  User Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Add "Description" to the "Change Physical Items" job so that this field can be edited in batch across sets of item records

   We would like to be able to edit (and delete) the "Description" field across large numbers of records without having to do it manually for each one. The "Rebuild Physical item description" job does not help here, since the content of the field is not necessarily based on Enumeration and Chronology data.
   Several fields have been added since we started with Alma (e.g. Alternative Call Number, Temporary Call Number, Inventory Number, etc.). Therefore, we hope that this field will also be available for this job in the near future. Thank you in advance!

   235 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Work Orders: package of required enhancements

    Work orders are useful but often cumbersome and don't work as required. A package of enhancements/fixes would make them much more useful and useable:

    • Adding notes when creating work orders in bulk. This would enable having fewer work order types as explanatory notes could be used instead.
    • Makes notes more (immediately) visible when scanning in (pop up message?). Again would enable fewer work order types as items could be easily catergorised according to explanatory note upon receipt at managing department.
    • Select recall/not recall at work order placement (like pick from shelf), not baked into type (and in selectable in bulk as well as individually).
    • Select/override priority level at work order placement (individual and in bulk)/make it easier to manually advance work orders in queue, AND:
    Different priority levels for different work order types.
    • Allow managing departments to manage multiple work order types (like circulation desks can) - increased versatility and flexibility.
    • Where circulation desks (and hopefully managing departments) manage multiple work order types, make it possible to view all in-process items and have work order type immediately visible.
    • Alert on scanning into work order managing department if higher priority work order/request exists.
    • Enable cancelling specific work orders/work order types in bulk (can currently only cancel all physical item requests on a set of items in bulk). This would improve versatility and flexibility.

    Realise this in not a single enhancement, but no single enhancement will make that much difference. The whole work order system needs to be looked at start-to-finish for real-world usability.

    Work orders are useful but often cumbersome and don't work as required. A package of enhancements/fixes would make them much more useful and useable:

    • Adding notes when creating work orders in bulk. This would enable having fewer work order types as explanatory notes could be used instead.
    • Makes notes more (immediately) visible when scanning in (pop up message?). Again would enable fewer work order types as items could be easily catergorised according to explanatory note upon receipt at managing department.
    • Select recall/not recall at work order placement (like pick from shelf), not baked into type (and in… more

    231 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Change currency in the order

    In the order the currency can not changed when the order is saved already. See attachment too, please.

    We need a possibility to change the currency after sending the order. Here are the reasons:

    a) During the order creation it was made a mistake.
    b) For subscriptions and standing orders the currency changes during the lifecycle. First we used British pound and than we use Euro, for example. The vendor changes the currency and we also have to be able to change that.

    • 

    230 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Acquisition - PO & POLine  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    AdminTamar Fuches (Senior product owner, Ex Libris) responded

    Dear community,

    Thanks for this idea.

    I would like to make sure that we fully understand the use case:

    1 The need is to allow users to change the currency for PO lines which were packaged and sent.

    Can you please specify the statuses in which this is needed?

    2 Upon such change, funding should be handled: disencumbrance for the original encumbered amount, and a new encumbrance on the fund with the new amount and currency. Is this correct?

    3 The POL should be removed from the original PO, and re-packed. Is this correct?

    4 Should the order be sent to the vendor again?

    Thanks,

    Tamar Fuches

    Alma product

12. Prevent change of due-date when the item is under the recalled status.

    Or have an alert message of some kind when the due date is being changed.
    Because when the due date is changed, the recalled item reverts back to its initial status making it difficult to determine if there are requests placed on the item.

    228 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Allow configuration of quick cataloguing form required fields

    We currently only use the quick cataloguing form at circulation desks to create quick records to loan items found on the shelves but not found on Alma. The items are loaned and then the work order routes them to the cataloguing team on return. All these items already have call numbers so we'd like the call number field to be a required field in the quick cataloguing form. Sometimes returned items are incorrectly returned to the shelves and if the quick catalogue record does not include the call number they are often impossible to track down.

    226 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Resource Management - General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Allow staff to override if an item type is not requestable

    We would like some books (like a reference book) to be non-requestable for a student. However, we would like for staff to be able to put in a request on a student's behalf for a reference book, or perform an override when appropriate.

    224 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Suggestions for Normalization Rules (NR) functions

    Hello,

    Please see the attached file.
    We would appreciate it if the suggested Normalization Rules functions would be developed in Alma.

    Thanks

    • 

    221 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    AdminLili Daie (Product Manager, Ex Libris) responded

    Dear all, since this idea combines various very different enhancement requests for Alma's normalization rules infrastructure, we are unable to add these to our roadmap at this time. This may change as we get more information on prioritization and needs. In the meantime, we suggest opening dedicated ideas for specific enhancements you would like to promote.

16. Overriding and/or deleting a continuous POL at the item level

    As a cataloger at a large research library, we frequently receive gap-fill purchases of periodical issues from third-party vendors or as gifts from donors—including for subscriptions that are still open.

    We know that we can associate a POL at the holding level, but this is undesirable for these situations where we need to trace the POL/method-of-acquisition to an individual item. Also, if you change a continuous POL at the item level, Alma changes the POL for every item attached to that same holding.

    Often we have many items purchased with different (or no) POLs—subscription, firm order, gift—together on one holding, and these items need to be on the same holding to clearly reflect what we hold, sequentially, to our users.

    It would be highly useful if Alma allowed catalogers and acquisitions staff to override a hyperlinked (continuous) POL at the item level to accommodate these very common occurrences of gifts (with no POL) and gap-fills (with differing POLs).

    With thanks for your consideration! :’)

    As a cataloger at a large research library, we frequently receive gap-fill purchases of periodical issues from third-party vendors or as gifts from donors—including for subscriptions that are still open.

    We know that we can associate a POL at the holding level, but this is undesirable for these situations where we need to trace the POL/method-of-acquisition to an individual item. Also, if you change a continuous POL at the item level, Alma changes the POL for every item attached to that same holding.

    Often we have many items purchased with different (or no) POLs—subscription, firm order, gift—together on one holding,… more

    219 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Acquisition - PO & POLine  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Indication that shows I edited an open record

    Icons in MD-Editor only show if a record has been saved or not. I would like to have an indication to see if the record has been edited by me after I opened it.

    209 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Alma overlap analysis tool to include different identifiers in one comparison

    We would find it useful if the overlap analysis tool compare a list that includes different identifiers. i.e. ISSN, EISSN, ISBN, EISBN, TITLE in one comparison.
    Currently it only allows you to compare overlap within just one identifier. This is very important with collections from vendors that include different kinds of material.
    Being able to conduct this kind of overlap analysis is important for us in terms of making purchasing decisions and we feel that including this kind of feature in the overlap analysis tool would make this a more efficient process within Alma.

    207 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Library opening hours for more than 3 years

    When setting standard opening hours in library calendar Alma automatically sets the field "Valid to" for 3 years. But the opening hours do not change very often. This setting also does problems by long term loans, because now the opening hours are valid to october 2024 but the library wants to loan documents to january 2025 (documents bought from some grants and the academic staff is working with these documents for a long time). In would be nice to have a possibillity to set somewhere that library opening hours should be valid for more than 3 year e.g. for 5 years or more.

    When setting standard opening hours in library calendar Alma automatically sets the field "Valid to" for 3 years. But the opening hours do not change very often. This setting also does problems by long term loans, because now the opening hours are valid to october 2024 but the library wants to loan documents to january 2025 (documents bought from some grants and the academic staff is working with these documents for a long time). In would be nice to have a possibillity to set somewhere that library opening hours should be valid for more than 3 year e.g. for 5… more

    200 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Stop the practice of showing funds for 'in review' invoices as expenditure.

    Current Alma practice is that EDI invoices automatically load into Alma and expend from a fund whilst still 'in review' and before the 'approval' stage.

    Below are some examples where the practice of expending a fund whilst the invoice is still 'in review' is causing us issues:

    1. We have full end-to-end invoice integration from our suppliers, via Alma and into Agresso. We don't send through manual invoices for payment. Our invoice data is automatically transferred through to Agresso every evening once an invoice has been approved. Only those invoices that have moved out of review are included in the export. Any invoices 'in review' will not be in the export but will be showing as expended on our system. This means that Agresso and Alma will always be out of step whilst we have invoices 'in review'. This makes it impossible to reconcile Alma and Agresso.

    2. Some invoices have over 200 lines and it may take us some days to work through each transaction. There may be issues with incomplete or inaccurate data. We have to make a few manual amendments in order to ensure that the Agresso transfer completes successfully. Only once all of that is done do we 'approve'. Whilst this is happening our Alma and Agresso systems are out of sync. What is the point of the approval step?

    3. We are working with IT on enabling the accrual accounting functionality so that our Finance Team don't have to maintain a separate spreadsheet of prepayments and meet monthly to reconcile. There is little benefit to be gained from working on this functionality if, once again, the two systems are always out of sync. We can't reliably turn up to meetings to discuss our accounts when the Alma reported expenditure includes invoices that aren't yet paid.

    4. If an invoice arrives that doesn't have an Alma PO number on it, the transaction amount is expended but because there is no PO to match to the amount remains encumbered too.

    Any 'in review' invoices should remain as 'encumbrance' until they have been 'approved' or have another 'pending expenditure' type invoice status.

    Current Alma practice is that EDI invoices automatically load into Alma and expend from a fund whilst still 'in review' and before the 'approval' stage.

    Below are some examples where the practice of expending a fund whilst the invoice is still 'in review' is causing us issues:

    1. We have full end-to-end invoice integration from our suppliers, via Alma and into Agresso. We don't send through manual invoices for payment. Our invoice data is automatically transferred through to Agresso every evening once an invoice has been approved. Only those invoices that have moved out of review are included in the export.… more

    198 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    7 comments  ·  Acquisition - Invoices  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close