Connecting Payment Processing to QuickBooks, Sage and Other Accounting Software
Table of Contents
Connecting payment processing to your accounting software means that an open invoice becomes a payment request carrying its invoice number, and that the payment's result comes back so your books can record it. The accounting software stays your book of record.
This article is for businesses that already keep their books in accounting software such as QuickBooks, Sage, Xero, or Acomba and would like payments and invoices to stop living in two places. Nothing here replaces your accounting software. It covers what moves from the software to the payment, what comes back, and what each side needs for the two to line up.
In short: an open invoice in your accounting software becomes a payment in TIB Finance, carrying the invoice number as its reference. The payment's status comes back through the API and webhooks, and your books can then record the payment or flag one that ended in an error or a cancellation. You need a reference on every invoice, a way to match customers between the two systems, and a place in your software to write results back.
Why Connect at All
Without a connection, the invoice lives in one place and its payment in another. Someone reads the amount from one screen and types it into another, looks for the matching invoice, marks it as settled, and keeps a separate note of the payments that did not go through.
Each step is small. Together they leave room for typos, for invoices that stay open after they were settled, and for customers who ask whether a payment arrived and get an answer only after someone checks. Connecting the two removes the retyping and leaves the decisions with your team. For the finance team's day-to-day view, see our article on payment automation for accounting and finance teams.
From the Invoice to a Payment Request
An open invoice in your accounting software already holds what a payment needs: the customer, the amount, the due date, and the invoice number. In a connected setup, that invoice becomes a payment in TIB Finance, and the invoice number travels with it as the payment's reference.
There are two ways to get there.
- A payment link. A payment link can be created already tied to the invoice. The customer opens it, pays, and the payment is matched to that invoice because the link was made for it.
- A payment created by your system. Through the API, your system sends the customer, the amount, the due date, and the invoice number, and the payment is created with that reference attached.
TIB Finance records the amount owed as a bill, a record with room for your own references, such as the invoice number. The amount always comes from your accounting software, so it is entered once, where the invoice was created.
A customer can settle by EFT from a bank account, including pre-authorized debit, with Interac, or by credit card. Which methods apply to a given payment depends on your setup, and all of them come back to your books the same way: with the invoice number and a status.
When the request goes out is a choice that stays with you: when the invoice is issued, or closer to its due date. Invoices that recur can be paired with payments on a schedule. For recurring bank account debits, the customer must agree first, and our guides to pre-authorized debits and recurring payments in Canada explain what that involves.
From the Result Back to the Books
The second direction matters as much as the first. A payment is only useful to your books once its result is known, and that result comes back in two ways: your system can ask for a payment's status through the API, and it can receive a webhook, which is a notification when a payment's status changes.
Each payment has a status (pending, in progress, or completed), or else ends in an error or a cancellation, with the reason given. Your books can then react to each one.
Pending or in progress
The invoice can stay open, with nothing recorded yet.
Completed
The payment can be recorded against the invoice, and the invoice marked as paid.
Error or cancellation
The invoice can stay open and be flagged, with the reason shown on the payment.
What comes back
Your reference, the amount, the status, and the reason when there is one.
How a completed payment is recorded depends on how you keep your books. The point is that it can be recorded from the payment's own result, not from a person reading it off another screen. A status can still change, for example to a cancellation after a payment showed completed, so your books can follow each update. A failed or canceled payment can be flagged in the same way, so it does not sit among open invoices looking like any other.
What to do about a flagged payment, whether to contact the customer or handle it another way, stays your decision. Matching and reconciling the results in detail is covered in our guide to automated payment reconciliation.
One Invoice, End to End
A short example makes the flow concrete. Take an invoice numbered 1042, as an illustration. It is open in your accounting software. It goes out with a payment link made for it, or your system creates the payment through the API with 1042 as its reference.
The customer pays. The payment moves through statuses such as pending and in progress until it shows completed, and each change reaches your system through the API or by webhook, still carrying 1042. Your books can then record the payment against invoice 1042 and mark it as paid.
If the payment ended in an error or a cancellation, the same reference would bring that result to invoice 1042 instead. The invoice could stay open and be flagged, with the reason beside it. In either case, nobody has to search for the invoice, because its number was there from the start.
What Each Side Needs
For the two systems to line up, three things need to be in place. They describe how the data flows, whatever the software.
A reference on every invoice
The invoice number is what ties a payment to its invoice, so each invoice needs one, and it needs to be unique. If two invoices can share a number, or an invoice has none, a payment cannot be tied to it with confidence. The same reference then comes back with the result, so your books know which invoice it concerns.
A way to match customers between the two systems
A customer exists in your accounting software and also in TIB Finance, and the two need to be recognized as the same one. Names are a weak link, since the same customer can be written two ways. A better link is an identifier of your own, such as the customer number from your software, stored with the customer in TIB Finance. Each customer is then created once, and every later payment goes to the right record.
A place in your accounting software to write results back
The results need somewhere to land. That can be the invoice status, a payment record, or a field or note on the invoice, as suits your books. Decide in advance where a completed payment goes and where a failed or canceled one is flagged, so that the same result always lands in the same place.
Seen together, the split is simple. Your accounting software keeps the customers, the invoices, and the books. TIB Finance carries the payment and its status. The reference and the customer identifier are the two threads between them.
The Same Flow Whatever Your Accounting Software
TIB Finance can connect to accounting software such as QuickBooks, Sage, Xero, and Acomba, and to other accounting software, through its API and webhooks. The flow is the same in each case: an open invoice goes out as a payment with its reference, and the status comes back to be recorded.
If your business runs an ERP instead, such as SAP Business One, Dynamics 365, or NetSuite, the pattern is the same, and our article on integrating payment processing into your ERP goes through it.
Where to Start
A connection can be tested in the sandbox, a separate environment for safe testing, starting with a handful of invoices. For each one, check that the invoice number arrives as the reference, that the customer is recognized as the right one, and that the result lands where you decided in your software. More invoices can be added once it behaves as expected.
The technical details are in the developer documentation. For the method, see the guide to testing payment integrations; for the calls themselves, the payment API integration guide. If many invoices will go through at once, managing high-volume payments looks at working only the exceptions.
Common Questions
What does connecting payment processing to accounting software mean?
It means an open invoice in your accounting software becomes a payment in TIB Finance, carrying the invoice number as its reference, and the payment's result comes back so your books can record it. The accounting software stays your book of record.
Which accounting software can TIB Finance connect to?
TIB Finance can connect to accounting software such as QuickBooks, Sage, Xero, and Acomba through its API and webhooks, and other accounting software can be connected too.
Do we have to replace our accounting software?
No. Your accounting software keeps the customers, the invoices, and the books. TIB Finance carries the payment and its status, and the result can be recorded in your software.
How does an invoice become a payment?
A payment link can be created already tied to the invoice, or your system can create the payment through the API with the customer, the amount, the due date, and the invoice number. In both cases the invoice number travels with the payment as its reference.
How is a payment matched to its invoice?
Through the reference. Because the invoice number is attached to the payment from the start, the result can be recorded against the right invoice without anyone searching for it.
What comes back to our books after a payment?
The payment's status (pending, in progress, or completed) or, if it does not go through, an error or a cancellation with the reason, along with your reference and the amount. Your system can ask for it through the API and can receive a webhook, which is a notification when the status changes.
What do we need on our side?
Three things: a unique reference on every invoice, a way to match each customer between the two systems, such as a customer number stored in both, and a place in your accounting software to write results back.
What happens if a payment fails or is canceled?
The payment shows an error or a cancellation with the reason, beside your reference, which points to the invoice it concerns. Your books can flag that invoice, and what comes next is up to you.
Can we test before connecting every invoice?
Yes. A connection can be tried in the sandbox with a handful of invoices first. Check that each reference, customer, and result lands where you expect, then add more.
Questions About Connecting Your Accounting Software?
Read the developer documentation, try the sandbox, or get in touch.
Contact TIB Finance Try the Sandbox