How Automated Payment Reconciliation Works: From Payment Link to Matched Invoice

Payment Automation

How Automated Payment Reconciliation Works: From Payment Link to Matched Invoice

Reconciliation is the job of proving that the bank and the books agree. The trouble is that they rarely describe the money in matching shapes. The bank shows deposits and returns, one line at a time. The books show invoices, each with its own number, customer, and balance. Someone has to connect the two, and that someone usually has a spreadsheet.

This guide follows a single payment from the moment it is requested to the moment it is recorded, and looks at where each step tends to break when it is done by hand, and what changes when the payment carries its own context along the way. It is written for finance, accounts receivable (AR), and accounts payable (AP) managers, controllers, and owners who want a clearer close without a bigger team.

Why Reconciliation Is Hard

The difficulty is not arithmetic. It is that the information needed to match a payment is spread across places and is often missing by the time someone looks for it.

• The shapes do not line up. A bank line is one amount with a short description. The books hold many invoices. A customer may pay two invoices with one transfer, or one invoice in two parts, and the bank line does not say which.
• The reference gets lost. The invoice number lives in the accounting system. By the time the money moves, it may not have traveled with it, so matching falls back on amounts and names.
• Results are not all known at once. A payment is created, then it is reported as paid or as returned.
• Exceptions hide in the volume. The few items that need judgment are buried among the many that do not, and they surface at the close.

Our guide on manual banking tasks you can stop doing lists the retyping and checking that results. This article looks at one thread of it, from payment to matched invoice, in more depth.

One Payment, Four Steps

Think of a single customer payment as moving through four steps. Each has a manual version and a connected version.

Step 1: Tie the Payment to the Invoice at Creation

Where it breaks by hand: the invoice goes out as a PDF, and the customer pays by whatever route is handy, with a transfer or a note in an email, and the invoice number may or may not be included. Someone then has to work out which invoice a payment was for.

What changes: with TIB Finance, a payment link can be generated, already tied to an invoice. TIB Finance can email the link to the customer, or return it to your software so you can send it with the invoice. When the customer pays through that link, the payment already knows which invoice it belongs to, so it can be matched to that invoice automatically. Matching stops being a detective task because the answer was attached at the start. Our guide to automating accounts receivable covers the link, and the other ways to ask for payment, in more detail.

Worth knowing: you decide how much of the matching to review. Payments can be matched to their invoices and reconciled automatically, or your team can review the matches first.

Step 2: Track the Status Through to the Result

Where it breaks by hand: the only way to know what happened to a payment is to open the bank portal and look, or to wait for the statement. A payment that looks finished may not be, and one that looks missing may simply not have been reported.

What changes: each payment has its own status, such as pending, paid, failed, or returned. You can see it in the TIB Finance portal, and it is passed on through the API and by webhook, meaning a notification when a payment's status changes. Transactions and their statuses are also available in reports. Our guide to webhook events explains how those notifications work in general.

Worth knowing: a bank payment can stay pending until the bank reports a result, so an invoice should stay open until the status says paid.

Step 3: Post the Result to Your Accounting System

Where it breaks by hand: someone types each payment into the accounting system against a customer, then works out which invoice or invoices it covers. It is slow, and a transposed digit or a wrong customer is easy to introduce and hard to find.

What changes: TIB Finance can connect to accounting and ERP systems through its API and webhooks. A connected system can receive each payment's status and record the payment against the invoice it was created for. The connection is set up as an integration, built around your systems and your process. Developers can start with the payment API integration guide.

Worth knowing: payments can be matched and posted automatically, or your team can review each one first. Both are possible, and it is up to you. Without a connection, transactions and their statuses are available in reports, and someone enters them. Either way, the accounting system stays the system of record. For the wider picture of how this fits alongside your existing software, see how payment automation helps accounting and finance teams.

Step 4: Review Only the Exceptions

Where it breaks by hand: exceptions are found at month end, when the bank lines are lined up against the invoices and a few will not match. Each one then has to be traced backward through emails and statements, when the details are hard to recall.

What changes: when payments are tied to their invoice and carry a status, there is less left to review. From the statuses and reports, your team can put together a short list of what needs a person. Typical examples:

• A returned payment. The returned status is shown against the specific payment, customer, and invoice, and the invoice can stay open. You see it in TIB Finance instead of finding it on a statement.
• A failed payment. You see which payment failed, from which customer, and for which invoice, along with the error or failed status, so it is clear that the payment did not go through, and the invoice is still waiting.

The point is not that exceptions disappear. It is that each one comes with a status and its invoice, and your team works through a short list instead of the whole month. What happens next, whether that is contacting the customer, sending a new payment link, or collecting another way, remains a decision for your team.

The Supplier Side

A similar idea applies when you pay suppliers, in a simpler form. Supplier payments with TIB Finance run by EFT (electronic funds transfer), between two bank accounts: your bank account and the supplier's. Each one is set up as a collection initiated on the supplier's behalf, so the money is pulled from your account to theirs.

Two details help the books. You add the supplier with a name and an email address, and the supplier receives a link to TIB Finance's secure page where they enter their own bank account details, the first time only, so nobody retypes banking details. The supplier also gets a read-only view of the payment's status in the portal. You can follow the status of each payment as well, so there is less back and forth about the status of a payment. Our guide to automating accounts payable walks through that side.

What Stays With Your Team

Automated reconciliation moves work. It does not move responsibility. Two things stay as they are:

• Your accounting system stays the record. It is where invoices, balances, and aging live. TIB Finance carries out the payment and reports the result, and does not keep your books.
• Your team does the review and the close. Exceptions still need a person, and the close is still yours. The aim is a shorter list, not an empty one.

Where to Start

Start where matching is hardest. If that is customer payments for invoices, send your next set of invoices with a payment link tied to each one, and watch how matching changes. Then decide whether to connect your accounting system, or to begin with reports. For the full cycle, collections and supplier payments together, see our guide to automating the full payment cycle.

Four pieces of TIB Finance, a Canadian payment automation platform, sit behind this approach:

If month-end matching takes a lot of your team's time, contact our team to see how TIB Finance fits the way you collect, pay, and reconcile.

Common Questions

What is payment reconciliation?

Payment reconciliation is the process of confirming that the payments recorded in your accounting system agree with what the bank actually shows, and that each payment is matched to the invoice or bill it was for. It is usually done at month end, and it is where differences are found and explained.

Why is reconciling payments so time-consuming?

Because the bank and the books describe the money in different shapes. A bank line is one amount with a short description, while the books hold many invoices. When the invoice reference is not attached to the payment, matching falls back on amounts and names, and the exceptions surface only at the close.

How can a payment be matched to an invoice automatically?

By tying the payment to the invoice when it is created. With TIB Finance, a payment link can be generated already tied to an invoice, so a payment made through that link already knows which invoice it belongs to and can be matched to it automatically.

Can I review the matches, or are payments matched automatically?

Either. Payments tied to an invoice, such as those made through a payment link generated for that invoice, can be matched and reconciled automatically, or your team can choose to review the matches first. The choice is yours.

How does my accounting system learn that a payment was made?

Each payment has a status, such as pending, paid, failed, or returned. TIB Finance passes it on through its API and by webhook, which is a notification when a payment's status changes. A connected accounting system can use it to record the payment against the invoice it was created for. Without a connection, transactions and their statuses are available in reports.

Can TIB Finance connect to QuickBooks, Sage, SAP, Dynamics, or NetSuite?

Yes. TIB Finance can connect to accounting and ERP systems through its API and webhooks. The connection is set up as an integration around your systems and your process. Your accounting system stays the system of record.

What happens when a payment is returned or fails?

The failed or returned status is visible to you, in the portal and through the API and webhook, and the invoice can stay open. What happens next, such as contacting the customer, sending a new payment link, or collecting another way, is up to your team.

What stays with my team when reconciling?

Your team keeps the review and the close. Returned or failed payments are shown against the specific invoice and customer, so you can see which payment failed and for which invoice. You can choose to review the payment-to-invoice matches yourselves, or have them matched and reconciled automatically. Your accounting system stays the record, and what happens next on any exception, including a customer who pays less than the invoice amount, is a decision for your team.

How are supplier payments tracked?

Supplier payments run by EFT between two bank accounts, set up as a collection initiated on the supplier's behalf. Each payment has a status you can follow, and the supplier gets a read-only view of the status in the portal. The supplier enters their own bank account details through a secure link, the first time only.

Where should we start?

Start with customer payments for invoices. Send the next invoices with a payment link tied to each one, and see how matching changes. Then decide whether to connect your accounting system or begin with reports.