Every cash proof rests on one question: is the cash in the bank the cash the client recorded? Answering it used to mean ticking and tying a sample of bank transactions to the general ledger (GL) by hand. Cash Proof Advanced answers it for every transaction. However your client keeps their books, Audit Sight ties each bank transaction to the GL entry that recorded it, shows you how much of the cash activity the books account for, and hands you a short list of what doesn't tie.
What matching gives you
- Every transaction, not a sample. Each matched bank transaction is tied to the GL entry that records it, for every month and every mapped bank account.
- It fits how your client keeps their books. Some clients record each deposit as it arrives. Others post a week's receipts as one entry, or a single summary entry for the month. The matching rules are built for each of these, from a check matched by its number to a payment that clears long after it was booked.
- Insight you haven't had before. Month by month and account by account, see how much of the bank activity the books explain, and exactly which transactions they don't: a fee that was never recorded, a receipt keyed in wrong, an entry with no cash behind it.
- Your time goes to the exceptions. The matching is done for you and documented in the workpaper. What's left is a short list to investigate, each item with the reason it didn't match.
- Cutoff support. Unmatched items at the start and end of the period that look like deposits in transit or outstanding checks are marked as timing differences, ready for your review. See Timing Differences: Deposits in Transit and Outstanding Checks.
- A read on the quality of the books. A high match rate means the bookkeeping follows the actual cash closely. A low rate points to summarized or irregular posting. See Understanding Cash Proof Precision Based on Your Data Environment.
- You have the final say. Create or delete a match, mark a timing difference, or adjust the matching rules for an entity. Your decisions are kept every time matching reruns.
How matching works
For each bank account, Audit Sight compares the bank transactions with the debits and credits to the GL cash account that the bank account is mapped to. When it finds the entry that records a bank transaction, the two are matched. A match can pair one bank transaction with one GL cash line, or several items on one side with one or more on the other. For example, a day's card settlements can be matched to that day's sales entry.
- Matching runs automatically every time your Cash Proof refreshes. It runs a set of matching rules in order, each one picking up what the earlier ones left. See Matching Rules: Choosing How Transactions Are Matched.
- Every automatic match is exact to the cent. Only a match you create yourself can carry a difference.
- Each transaction is matched once. Anything left over is listed as unmatched, with the reason it didn't match.
- Mapping matters. Only bank accounts that are mapped to a GL cash account are matched. See How Chart of Accounts Mapping Drives Accurate Reconciling Items.
- Reconciling items come first. Bank transactions explained by a banking-only reconciling item, such as a transfer or a sweep, are left out of matching. See Automatic Banking-Only Reconciling Items.
Where to find it
- Open the engagement, then click your Cash Proof Advanced request in its Cash Proof table. Advanced requests carry an Advanced badge.
- Under Banking, click Matching.
Matching has four tabs: Overview, Unmatched Records, Matched Records and Matching Rules. The arrow beside the Matching title takes you back to the Cash Proof's summary.
The Overview
The Overview shows how much of the bank activity was matched to the GL, month by month, for each entity in the request.
- Inflows matched and Outflows matched give the totals for the whole request. Hover over any percentage to see the counts behind it, such as "1,182 of 1,190 matched".
- Each entity has two lines, Inflows and Outflows, with one column per month and a Total. The colors follow the legend above the grid. No bank data marks a month without a bank statement.
- Click ▸ beside an entity to see each of its GL cash accounts and the bank accounts mapped to it.
- The Matches, Unmatched bank and Unmatched GL counts are links. Click one to open Matched Records or Unmatched Records with those items already filtered.
- Under each entity's name, you'll see whether its matching rules are the defaults ("Matching rules: default" or "Matching rules: 2 changed") and when matching last ran. Click the rules line to open Matching Rules for that entity.
The Overview shows the same numbers as the Bank Transaction Analysis tab of the workpaper.
What you can change
- Create a match that the rules missed, on Unmatched Records. See Creating a Manual Match.
- Delete a match that pairs the wrong transactions, on Matched Records. See Deleting a Match.
- Add or remove a timing difference on Unmatched Records. See Timing Differences: Deposits in Transit and Outstanding Checks.
- Change the matching rules for an entity on Matching Rules. See Matching Rules: Choosing How Transactions Are Matched.
Your changes belong to the entity, not only to this request. They are kept every time matching reruns, and they carry into later Cash Proof requests for the same entity.
When your changes show up
Unmatched Records and Matched Records show a change straight away. The Overview, the Cash Proof and the workpaper update once matching reruns.
- After a change, a bar at the top of the Matching screens reads Changes not yet run. You can keep working: matching reruns on its own after you stop making changes.
- To run it right away, click Rerun Matching.
- While matching runs, Refreshing shows beside the entity. When it finishes, the Overview, the Cash Proof and the workpaper update.
Matching in the workpaper
- Bank Transaction Analysis shows match rates by account and month, matches by type (exact, grouped and manual), and the comparison of bank activity with the books.
- Matched Transactions lists every match, with the bank side and the GL side next to each other. The Matching Mechanism column names the rule that made the match, or reads Manual for a match a person created.
- Unmatched Transactions lists everything left unmatched, with a Primary Reason. Timing differences also show a Secondary Reason: Deposit In Transit or Outstanding Check.
- Timing Adjustments totals the deposits in transit and outstanding checks by month.
Tab numbers depend on the engagement type. For a tour of every tab, see How to Approach a Cash Proof Review.
FAQs
Why isn't every bank transaction counted in the match rate?
Some activity isn't counted:
- transactions and bank accounts set to ignore
- bank accounts that aren't mapped to a GL account
- $0 transactions
- bank transactions that a banking-only reconciling item explains
Where a bank transaction's date or amount was corrected on Banking Data, the corrected figures are used. Entities that have only a trial balance, are waiting on data, or have no GL cash account aren't in the totals. When you open an entity on the Overview, its last line lists what wasn't counted.
Do my matching changes affect the Cash Proof?
Yes. A manual match's difference goes to the proof, and timing differences feed the proof's timing adjustments. Changes reach the Cash Proof and the workpaper after matching reruns.
What if an entity has only a trial balance?
There's nothing to match, so the Matching screens show Trial balance only for that entity. Its bank transactions are explained with reconciling items on Banking Recon Items.