Finance

Billing exceptions

The checks, and any override, are the firm’s.

Most invoices are routine. The cost is the one that should not have gone out.

The workflow

Billing exceptions

  1. 01
    Read

    The invoice is taken from the billing run.

  2. 02
    Test

    Rate, duplicate and approval checks run.

  3. 03
    Hold

    A failure stops that invoice only.

  4. 04
    Release

    The rest of the run continues.

The checks, and any override, are the firm’s.

The problem

Billing exceptions still depends on a queue.

Invoices are checked by sampling, or not at all. A wrong rate, a missing approval or a duplicate is found by the client.

Current process

A sample, or a complaint.

Invoices are checked by sampling, or not at all. A wrong rate, a missing approval or a duplicate is found by the client.

The solution

A recorded workflow, with people where the decision sits.

Handled in the workflow

Each invoice is tested against the checks the firm defines. Failures are held with the failed check. Passed invoices continue.

  • Read
  • Test
  • Hold
  • Release

Your team stays in control

The checks, and any override, are the firm’s.

Every invoice, the same checks, holds only where they fail.

How it works

From the queue to a recorded outcome.

Each invoice is tested against the checks the firm defines. Failures are held with the failed check. Passed invoices continue.

  1. 01

    Read

    The invoice is taken from the billing run.

  2. 02

    Test

    Rate, duplicate and approval checks run.

  3. 03

    Hold

    A failure stops that invoice only.

  4. 04

    Release

    The rest of the run continues.

Without it

A sample, or a complaint.

With UYP Systems

Every invoice, the same checks, holds only where they fail.

The checks, and any override, are the firm’s.

Also in Finance

The rest of the range.

Discuss Billing exceptions.

Most invoices are routine. The cost is the one that should not have gone out.