Noventra Automation
Payments & Collections

Payment Reconciliation

Payments matched to invoices, without the line-by-line hunt.

Money arrives in batches and invoices are settled one at a time. Somebody ends up with a payout on one screen and a list of open invoices on another, working out which settles what. It is slow work, it is easy to get subtly wrong, and it usually happens days after the money actually landed.

Live workflow
One payout, four charges
Payout received
£4,119.06 paid out4 charges, £4,182.60 gross less £63.54 in fees
£1,450.00INV-2291 · Halcyon FoodsReference and amount both agree. Marked paid.
£980.00INV-2288 · Brightwater LtdReference and amount both agree. Marked paid.
£1,200.00INV-2274 · Kesterly Group£1,200 of £1,850. Remainder left open, reminders continue.
£552.60Unmatched · No payer referenceNo invoice fits this amount. Held for a person rather than guessed at.
Nothing is marked paid on a near miss
How it works

From payment received to invoice settled, in four steps.

01Read the paymentEach payment or payout is read as it arrives: amount, date, payer, reference, and the individual charges inside a batched payout.
02Find the invoiceThe payment is matched against open invoices on reference, amount, and payer, including the case where one payment settles several invoices at once.
03Check before writingA match has to agree on more than the amount. Anything that only nearly fits is set aside rather than forced, and a payment that covers part of an invoice is applied as a part payment rather than closing it.
04Mark off, or set asideClean matches are marked settled in the accounting tool. Part payments, overpayments, and unidentified receipts are set aside with what is known about them.
Before and after

What changes after we deploy this.

TodayMatching a payout against invoices by eye
With the workflowEach payment matched to the invoice it settles
TodayInvoices still marked unpaid days after the money arrived
With the workflowMarked off the day the payment lands
TodayA part payment forced into a full match
With the workflowThe remainder left open and visible
TodayChasing a customer who already paid
With the workflowReminders stop because the invoice is genuinely settled
Where it shines

If any of these describe your business, this workflow earns its keep.

Batched payouts

A card processor pays out once a day covering many invoices, net of fees. Unpicking that by hand is the single most tedious hour in the week, and it is pure pattern work.

Steady invoice volume

Reconciliation cost scales with the number of invoices, not their value. Past a few dozen a month it stops being a task someone fits in and starts being a task someone puts off.

Chasing that outlives the payment

The worst outcome of late reconciliation is not the admin. It is a reminder going to a customer who paid last week, which costs more goodwill than the invoice was worth.

How long is it between the money arriving and the invoice being marked paid?

Send us a recent payout and a list of open invoices. We will tell you how much of it matches cleanly, and what would have needed a person.

Ask for the review
What engaging involves
It writes to your ledgerMarking an invoice settled is a real write, so the matching rules are agreed with you before anything is switched on.
Near misses are never matchedA payment that only nearly fits an invoice is set aside. The workflow would rather leave work for you than settle the wrong invoice.
It pairs with chasingReminders stop when an invoice is genuinely settled rather than when someone remembers to update it.
What it does not coverIt does not connect to a bank directly. It reads Stripe and the bank transactions your accounting tool already pulls in, and anything beyond that is a separate piece of work.
Integrations

It runs inside the tools you already use.

Xero

And 30+ others. If your tool is not listed, ask.

See every integration
Common questions

The questions we get before we build.

Still unsure? Ask us directly and we will answer before you commit to anything.

What happens when a payment does not match anything?

It is set aside with everything known about it: amount, date, payer, and any reference it carried. It is never forced onto the closest invoice. An unmatched receipt is a five-minute job for a person; a wrongly settled invoice is a customer conversation.

Can it handle one payment covering several invoices?

Yes, and that is the common case with a card payout. The payout is broken back down into the individual charges inside it, and each is matched separately, so fees and refunds do not throw the arithmetic off.

Does it connect to my bank?

Not directly. It works from Stripe and from the bank transactions your accounting tool already pulls in. A direct bank connection needs an Open Banking provider, which is a separate piece of work and a separate conversation.

What about part payments?

The part that arrived is applied and the remainder stays open, so chasing continues for the balance rather than stopping because something was paid. Closing an invoice that is only half settled is the most expensive error in this whole area.

Will it stop the invoice reminders?

If you also run reminders, yes, and that is most of the value. A reminder going to someone who paid last week costs more goodwill than the admin saved, and it usually happens because reconciliation ran days behind the money.

Does it use AI?

Only for reading unstructured references, such as a payer typing an invoice number into a free-text field. The matching itself is arithmetic and rules, so the same payment always produces the same answer.

Want to know how much of your reconciliation is mechanical?

Send us a recent payout and your open invoices. We will tell you what would have matched on its own, and what would still have needed you.

Every workflow is a managed monthly service. No credit card, and we respond within one business day.