Finance

Payment exceptions

Allocating a mismatched payment stays with the firm.

A payment that matches can move. A payment that does not should stop.

The workflow

Payment exceptions

  1. 01
    Expect

    The instruction is already on the case.

  2. 02
    Receive

    The statement line is read.

  3. 03
    Match

    Reference and amount are compared.

  4. 04
    Queue

    A mismatch waits, with both sides shown.

Allocating a mismatched payment stays with the firm.

The problem

Payment exceptions still depends on a queue.

Unmatched payments sit on a statement until someone has time to look. Expected and received are reconciled late.

Current process

Statement lines ticked by hand.

Unmatched payments sit on a statement until someone has time to look. Expected and received are reconciled late.

The solution

A recorded workflow, with people where the decision sits.

Handled in the workflow

Expected instructions are compared with what arrived. Matches are noted. Mismatches are queued with both amounts and the reference.

  • Expect
  • Receive
  • Match
  • Queue

Your team stays in control

Allocating a mismatched payment stays with the firm.

A queue of payments that did not match.

How it works

From the queue to a recorded outcome.

Expected instructions are compared with what arrived. Matches are noted. Mismatches are queued with both amounts and the reference.

  1. 01

    Expect

    The instruction is already on the case.

  2. 02

    Receive

    The statement line is read.

  3. 03

    Match

    Reference and amount are compared.

  4. 04

    Queue

    A mismatch waits, with both sides shown.

Without it

Statement lines ticked by hand.

With UYP Systems

A queue of payments that did not match.

Allocating a mismatched payment stays with the firm.

Also in Finance

The rest of the range.

Discuss Payment exceptions.

A payment that matches can move. A payment that does not should stop.