• ALERTS / ANNOUNCEMENTS

    ALERTES / ANNONCES

    ALL BRANCHES:  Please note that the automatic GL coding of laundry, waste management, coffee supplies that BPTS was programmed in 2022 has been turned off.  All invoices are uploaded to the branch Pending GL queue.  Please identify all transactions that should be in Ariba that may not have the IND PO on the image and follow the process noted below.  Continue to work on generating a blanket PO for recurring expenses and move entries to Ariba.  Thank you.

    CINTAS laundry invoices: due to the volume and multiple lines of these large invoices please continue to process in BPTS. 


    All Invoices with a CSS PO# or no PO# and an Ariba vendor # will start to be rejected now.

    Branches:  Please do not code / approve invoices until you determine it is not paid or uploaded to another system. A PO is critical to ensure we are not issuing duplicate payments.  Cummins is starting to being notified of Duplicate payments.  Invoices paid by any other system are not to be processed in BPTS.  

    Do not submit invoices paid or to be paid in:  Ariba; Mihlfeld; PCard; Concur


    All Indirect purchases with an Ariba vendor# must be processed in Ariba.  Please follow the process below in how to handle indirect invoices.

    Please have your teams monitor the system and make sure all entries in BPTS have a BMS PO for direct purchases.  You can task to our AP team with the BMS PO and we can add that PO# to the file so it does not get voided. 


      REMINDER:  PURCHASE ORDERS ARE TO BE GENERATED AT TIME OF ORDER AND THAT # MUST BE PROVIDED TO THE VENDOR.  INVOICES ARE NOT TO BE USED TO CREATE PO'S AFTER THE FACT. THIS POLICY APPLIES TO BOTH DIRECT PO'S GENERATED IN BMS AND INDIRECT PO'S GENERATED IN ARIBA.

      ARIBA Procurement system transactions:

      Invoices:

      1. - branches are to identify all INDIRECT invoices that DO HAVE or SHOULD HAVE a PO in ARIBA that the vendor HAS NOT INCLUDED on the invoice.
      2. - branches are to task these invoices to the Canada AP team requesting the invoice be voided in BPTS and you must provide the Ariba IND PO#.  (Note: branches are not to use the BPTS system to obtain invoices to create an IND PO after the fact to then send to Ariba)
      3. - branches are to contact the vendor to update their invoice with the Ariba PO# and resubmit to canada.supplier.invoices@cummins.com to route to the Ariba invoice intake system.
      NOTE:  BMS INDIRECT VENDORS ARE SCHEDULED TO BE DEACTIVATED. DO NOT CONTINUE TO ORDER INDIRECT PURCHASES OUTSIDE OF ARIBA.  EXCEPTION IS WHEN YOU ARE WAITING FOR AN EXISTING VENDOR TO BE MIGRATED TO ARIBA AND THEN ALL ORDERS AFTER MUST BE GENERATED IN ARIBA.   

      - Branches are responsible to ensure only one system is being used to approve invoices to prevent duplicate payments.**  All indirect are to be in Ariba and should not be coded or approved in BPTS when there is an Ariba PO.

      - Do not generate a BMS PO for an INDIRECT purchase.  Internal WO's for indirect spends are no longer to be used

      **Please note to prevent duplicate payments this also applies to invoices paid through other Cummins payment teams:  Mihlfeld, Cushman, PCard, Concur.

      Credits:

      1. - branches are to identify Credits for indirect PO's for invoices that are being processed in Ariba
      2. - branches are to task these Credits to the Canada AP team requesting the credit be voided in BPTS. You must provide the Ariba IND PO# and if in Open or Closed status and the GL code assigned to the original invoice
      3. - Canada AP will void the credit in BPTS and add the GL code to the image to email to the CBS Accounts payable team to enter into the BOLT payment system.

    • .