Know Which Invoices Each Payment Pays

At Qvery, we help finance teams spend less time matching, with custom AI agents that pair payments with invoices. We build them around your own files and rules. The first working result comes in about two weeks. A wrong match is worse than a slow one: it sends someone chasing a customer who already paid. So each proposed match carries its evidence: the amount, the reference, the line in the email. Payments it can't explain go to your team with a drafted question.

The agent reads the customer's payment email and looks through your open invoices for the amounts that add up to the deposit. It handles short payments and credit notes too. When more than one set of invoices fits, it shows them all next to each other, with the reason for each. Where it can't tell, it says ambiguous instead of picking one. Your team decides which set is right and records the payment as it does now. Each proposal lists every invoice with its amount, so the total is easy to check. Short payments are proposed with the amount left open.

The agent tries the customer's open invoices and recent credit notes, and it looks for the amounts that add up. A single fitting set is proposed with the amounts that add up. A short or missing bank reference doesn't stop it, because it also reads the amount and the payer. If nothing explains the deposit, it goes on a separate list with a drafted question for the customer. Your team asks the customer, then decides. A large payment is where a wrong match costs the most, so it gets the most evidence.

For the free try, export your open invoices as a spreadsheet and send your bank statement. In your build, we connect it to your accounting system and bank feed. Each morning, it then reads the new deposits and your open invoices directly. Your team records the payments in your accounting system, as it does now. Nothing about how your team records payments has to change. In the free try, the statement and invoice list you send are enough.

No. It proposes matches with the evidence for each one. That is the amounts that add up, the reference that agrees or the line in the email. Your team reviews the proposals and the questions for customers. They decide which invoices each payment covers. Then they record every payment in your own system, as they do now. The agent never records anything itself. A proposal is a suggestion until your team confirms it.

Yes. Send your statement as a document or a spreadsheet, with your open invoices and any payment emails. That's the free try. The agent reads the amount, the payer and the bank reference on each deposit. That reference is often short or missing, so the amounts and the emails carry more weight. Your team gets the proposed invoices for each deposit, each with its reason. A document or a spreadsheet both work, so there is nothing to convert.

An agent for this job costs about $25,000 to build, then roughly $400 a month to run. The $25,000 is a one-time build, and the monthly figure covers running it. The calculator above shows what that means against your team's time on payments. Put in your own numbers, and the result updates as you type. It counts the people on this job and the share of their week it takes.

The agent reads only the statements, exports and inbox you connect it to, and it changes nothing in your books. You decide where it runs and how long anything is kept. It reads a payment email only to find the line that says what the customer paid. Your team still records every payment in your own system. Credit notes and open invoices are read to find what a payment can cover.

We deliver a working agent in about two weeks. Each morning, it reads the new deposits on your bank statement: the amount, the payer and the bank reference. It runs on your real deposits beside your team first, so you see its proposals before you rely on them. Then it takes over the morning matching, and your team works on the payments it can't explain. Where nothing fits, it says not found instead of guessing. A morning's deposits are matched before your team opens the list.

It sends back the invoices each payment covers, with the reason. It also shows the payments that fit more than one set of invoices, next to each other. The payments to ask about come with drafted questions. You send your bank statement, your open invoice list and any remittance emails or PDFs. The result comes from vlad@qvery.ai within 15 minutes, and we delete your files as soon as it is sent. A sample is a wholesaler's deposit statement with its open invoices. Each payment shows the evidence behind its proposal.