Development build — sample configuration

Approve payment proofs and match payments to the bank statement

Check the transfer, deposit or mobile wallet proofs customers send, then import the bank statement and match every credit to a recorded payment.

Updated on

Customers who pay outside the app send a proof, which staff check with the bank before the money reaches the account; the imported statement then shows which credits still need an explanation. Approving, rejecting and matching need the Owner, Administrator, Finance or Billing clerk role; read-only roles see the lists without the buttons.

Before you start#

  • The utility has payment methods configured.
  • To import, you have the bank statement as a CSV file with the columns value_date (YYYY-MM-DD), amount, reference and description, in that order.
  • To record a payment from a statement line you also need access to Accounts.

Step 1: Review the proofs#

  1. In the Payments group of the menu, open Payments and pick the Payment proofs tab.
  2. Filter by Under review and open a row. The panel shows the Declared amount, Payment method, Reference, Payment date, the account and the attached file.
  3. Check with the bank or wallet that the money arrived, then click Approve and record payment. In the Approve proof dialog, correct Amount received or Reference if the bank shows different values, add a Note (optional) and click Approve.
  4. If you cannot find the transaction, click Reject, write the Reason and confirm with Reject.

Step 2: Import the statement#

  1. Open the Bank reconciliation tab and click Import statement.
  2. Fill in Bank account, Statement reference and Statement date.
  3. Under File, choose the CSV, or paste the lines into Content, and click Import.

Step 3: Settle what stayed unmatched#

  1. Choose the statement from the list and filter by Unmatched.
  2. Open a line. Under Match with a payment, choose the Payment and click Match.
  3. If the money arrived but no payment exists, use Record a payment from this line: choose the Account and click Record payment.
  4. For a bank fee or any movement that needs no payment, click Ignore line, give the Reason and confirm with Ignore.

What happens next#

An approved proof becomes Approved, creates a payment on the customer's account that is applied to the oldest invoices first, and issues its receipt. A rejected proof becomes Rejected; the customer sees your reason and can send a new one.

During import, a credit line is matched on its own when its reference equals the provider reference or receipt number of a payment with the same amount. Without a reference match, it is matched only when exactly one bank transfer of that amount falls within three days of the value date. The payment becomes Reconciled and the line Matched, and the Lines, Matched, Unmatched and Unmatched amount figures summarise the chosen statement.

Common problems#

  • The proof was already reviewed. Someone else approved or rejected it in the meantime. Reload the list; the earlier decision stands.
  • The reference was used for a different payment. Approval is refused so the same money is not recorded twice. Check the bank and reject the duplicate proof.
  • A CSV line is refused. The message gives the line number with a bad date or a missing amount. Fix that line and import again.
  • The chosen payment will not match. The payment amount must equal the line amount and the payment must be Posted. A line matched by mistake goes back to the queue with Undo match.

Start today. Set up your utility in minutes.