Skip to main content
Skip table of contents

Finance Information

This page outlines the financial settings and behaviors of QuickPay.

Batch Selection

iMIS Quickpay first attempts an invoice payment without an explicit batch. This allows iMIS EMS to automatically select or create the appropriate batch using internal iMIS business logic.

This scenario accounts for over 99% of all payments.

How can I identify an iMIS auto-created batch?

Auto-created batches will have a “Description” of Auto-Created for XXXX, replacing “XXXX” with the username of your CSI Cloud Background Account. The “Created By” field will also be set to this user.

In rare cases, it is possible that iMIS cannot automatically select or create a new batch. In these cases specifically, iMIS QuickPay will look for a batch that matches the following settings:

  • Batch is open

  • Batch date is today (UTC)

  • Description is “iMIS QuickPay Auto-Created Batch“

  • Created by the Background Account username

If no batch is found in iMIS matching these criteria, a new one is created.

This batch will be used with the invoice payment (“order”).

iMIS QuickPay does not auto-post this batch for you. Ensure that your finance team is aware that these batches will need to be processed manually.

A Note on Cash-based Dues Invoices

QuickPay reads invoices from iMIS by the Bill To ID (iMIS ID) and the invoice reference number.

For cash-based dues (invoices where the reference number starts with Cash-), it is possible to have multiple invoices with the same reference number.

Currently, iMIS QuickPay supports paying these types of invoices only if there is a single invoice with an outstanding balance.

For cases where there are multiple invoices for a given Bill To ID that have the same reference number, and two or more of these invoices have open balances, iMIS QuickPay is not able to pay these invoices at this time.

Payment Methods and Payment Method Sets

iMIS QuickPay requires a single payment method to be selected for its transactions.

Payment method sets (and the payment method set dropdown) are not supported at this time, and using a split payment method per credit card is also not supported.

Additionally, it is not currently possible to limit the card type(s) accepted by specifically QuickPay. If you do not want to accept certain credit card types, you will need to work with ASI to apply this preference globally to your iMIS Pay account.

Our recommendation for iMIS Pay payments is to create a single payment method in iMIS of type “Credit Card”, called “QUICKPAY” or “QP”, and use this for your iMIS QuickPay payments. This will allow you to create an IQA query to identify which transactions specifically were entered into iMIS via QuickPay.

To build an IQA query for QuickPay specific payments, use the PaymentSummary business object and in the “Payment Method ID” enter the selected payment method set.

Because we use the iMIS Pay Central SDK, we have no control over the credit card number, credit card type, or how it’s authorized and processed.

CSI_QuickPay_Invoice - Invoice ID vs Invoice Number

Do note that the difference in these fields is due to how iMIS is configured

Invoice Number is the number that you are used to seeing in iMIS. For example, cash-based dues are "CASH-12345", some invoices are "R12345", etc. Invoice Number is what you can see when you go to Finance--> Invoices.

Invoice ID is an internal unique identifier for invoices because the reference number is NOT unique. InvoiceID is often "behind the scenes", not something displayed on-screen usually; usually a combination of Invoice Number plus Billing Log Key or Generated On Date. Invoices for Cash-based dues will have the same reference number but may be in a format like CASH-12345:2023, CASH-12345:2024, etc for uniqueness.

You could have the same Invoice Number for different individuals, but Invoice ID will always be unique.

Since Invoice ID is unique, when building reports in your iMIS Environment we suggest joining on Invoice ID (if possible), but that depends on the business object you are linking to.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.