Overview
This article contains a detailed description of the manual payment batch module.
Manual Payment Batch is designed to be a complimentary feature for service providers who subscribe to automated payments and who collect payments using direct debit. To be used, customers must have direct debit as their nominated payment method. It gives service providers the ability to:
- Generate a list of customers who are due to make a payment.
- They must have an outstanding invoice whose payment is falling due and their preferred payment method is set to direct debit.
- Create payments for those customers
- When a batch is created, all the payments are created in the system automatically.
- Download a bank compliant export file from Cumulus
- Mark the payments as Complete or Failed.
A list of supported banks is on this page.
This file can then be uploaded to the service provider's bank and will initiate payment to be taken from the customer. Once a response from the bank is received, the payment can be marked in Emersion as Complete or Failed. Once all payments are resolved, the user can closed the batch and the ledger journal is updated.
While the Manual Payment Batch page is accessible to all Emersion subscribers, users cannot create a manual payment batch or download an export file unless the following prerequisites are met.
If you have checked that these requirements are being met and the Manual Payment Batch is still not returning any customers, please raise a support ticket.
If part of an invoice, is covered by a payment plan, the part of the invoice not covered will be picked up and put into a batch.
Payments for Payment plans have a separate predefined payment schedule and are also excluded.
if the invoice due date from/to is chosen, invoices due in those dates will be used irrespective of if they are due in the future or not.
Requirements
Users cannot create a manual payment batch and generate an export file unless the following requirements are met.
Service Provider Requirements
- A payment gateway for direct debit that is supported by Manual Payment Batch is enabled and mapped to your service provider account.
If you are not sure if a gateway is enabled, please raise a support ticket. Service Providers do not have visibility into which payment gateways are configured, but our customer service team will be happy to provide that to you.
Customer (End User) Requirements
All of these requirements must be met:
- The customer's payment method is set to Direct Debit and the Automated payment status is Enabled.
- The customer's bank account details are saved.
- The customer owes a payment by way of an invoice that is due or overdue.
- The customer owes a payment that is greater than the EPS minimum payment amount.
The EPS (Emersion Payment System) Minimum Payment Amount is the minimum threshold to trigger a payment. The customer must owe at least this much money in order to trigger an automated payment, or to be direct debited. A default amount can be set for all customers and overridden at the customer level if required.
Customer (End User) Bank Account Number Requirements (for Australian Bank)
All of these requirements must be met:
- The BSB number must comprise 6 numbers (integers).
- The Bank account number must comprise of no more than 10 numbers (integers). While Cumulus supports the use of hyphens in the bank account number field, if the total number of numbers + hyphens => 10, the hyphens will be stripped when the number is saved.
For example;
- 12-123-123 will be saved as 12-123-123
- 12-123-1234 will be saved as 121231234