Isolist can reconcile data of all types, thanks to it's flexible, powerful reconciliation engine. Reconciliation with Isolist typically takes only a few seconds, however complex your matching task is. Take a look at how Isolist handles the following reconciliation tasks:

Reconcile using a single matching code

The most basic reconciliation task involves matching data using one field from each side. In Isolist, a single matching rule is used to accomplish this.

1. The matching rule defines which column from each side contains the code to be matched.
2. Once matching data rows are found, the amount associated with each one is compared to find out whether they reconcile.

Matching data using more codes

Sometimes you need to use two or more data fields to match rows precisely. Simply add more matching rules in Isolist to include more data fields in the matching process. Each matching rule compares one pair of fields and up to eight matching rules can be used in a single reconciliation stage.

As in the basic example above, once records with matching codes have been found, Isolist then compares their amounts to decide whether they reconcile.

One-to-one, One-to-many, Many-to-many

Sometimes the data you need to match is at different levels of detail. For example, you may need to match individual bank deposits on your bank statement to a single receipt posting in you bank nominal account.

Isolist can match your data records one-to-one or one-to-many or many-to-many - which ever the data demands.

Advanced Field Matching

Whether your data is clean and consistent or difficult to work with, Isolist has clever matching logic to help. Choose the appropriate match type for your data:

‘Equals’ Match Type

The standard option for use where the matching code or value on each side is required to be equal. The Equals match type in Isolist can match number-to-number, text-to-text or text-to-number

‘Proximal Date’ Match Type

This one is invaluable when you need to match transactions that have been recorded in different systems on different days. Use it, for example, when your ledger records a cash receipt on one day, but it shows up in your bank account on the next day. The Proximal Date match type lets you choose how close the dates on each side must be to count as matched.

‘Search’ Match Type

Transaction data is not always given in a clean format - sometimes the code you need to match on is buried within a longer field value. Isolist's Search match type looks for the matching code from one side within the text on the other side. The matching code doesn't need to be at a fixed position, so you can even match on data that has been hand-typed within a free-form comment field.

Multi-Stage Reconciliation

You don't have to use the same matching rules for all the transactions in your lists. Reconciliation Stages in Isolist enable you to apply different matching criteria to different rows. You might use this to:

• Define appropriate matching rules for different transaction types
• Automatically try an alternative matching strategy if some transactions fail to match in the first instance
• Use one reconciliation stage to match transactions precisely, and distinguish less precise matches with a second reconciliation stage at a lower tolerance.

Target matching rules at specified rows

Isolist provides you with filter rules to enable each matching stage to be applied only to the rows or transaction types you choose.