Piet BaudoinBy Piet Baudoin, updated September 26, 2026

How does three way matching flag an invoice that doesn't match the quote?

Three way matching lays the invoice next to the supplier's quote or order and the delivery note; your AI puts a mismatch in front of you the day it arrives, with the agreement Bombos remembers, with the reason, before you post it in QuickBooks.

Works with QuickBooks and your own project numbers.

Invoice checking is the first task; every rule from your corrections stays in one shared memory.

Book your half hour

Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →

This is how it goes now, and how it goes with Bombos.

Now

The supplier's or subcontractor's invoice does not match the quote or the delivery note, and it only shows up at month end, once nobody can retell how it happened.

Today, whenever something looks wrong, you dig up the order, delivery note and email with the agreement before posting in QuickBooks. QuickBooks Online can already read invoice details, so recognition is covered. You need to know whether the supplier charged what you agreed. A difference is not automatically a mistake, because a later email may record a change. You find that too before posting or asking the supplier.

Withbombos

The mismatch gets flagged the day the invoice comes in, before it is posted.

The difference between the invoice and the agreement is ready for you the day it arrives, before posting, with the reason attached. Your AI finds the supplier's quote or delivery note in your email and package. The supplier agreement is the starting point, not the quote to your own customer. If that agreement is missing, your AI tells you. You decide on the difference and approve before anything is posted.

After three months

After three months, you hear the same day when an invoice differs, not at month end. Every invoice is checked against the agreement, even during busy weeks. If a supplier keeps diverging in the same way, you see that alongside the earlier invoices. Every flagged difference shows which agreement it rests on.

What's ready for you then

  • Every invoice checked against the agreement
  • A mismatch flagged the day it arrives
  • Call the supplier while the job is fresh
  • Pay what you agreed, and no more

Where do you see that?

On the list of proposals you see which invoice needs attention, with the reason attached. When there is a difference with the supplier's quote or the delivery note, your check is about that difference. If information to pin down the agreement is missing, the proposal shows "waiting on your input." "Ready for you" means you can review the groundwork, not that the supplier is right.

You do not need QuickBooks open to see which invoice needs attention. The list shows what check or extra information is needed. Posting stays separate work in QuickBooks, after you have reviewed the invoice. With every proposal you see where it came from. You review the invoice, post the entry in QuickBooks, and approve any question that goes out to the supplier.

How does it start?

In the first week of the three-month pilot, we go through your invoice checking, in a setup conversation of about an hour. We look at where supplier invoices arrive and where you keep the matching quotes and delivery notes. We also discuss which agreements sit in email, and who decides when an invoice and an agreement diverge. In that same conversation we write down any verbal agreements with suppliers, so they stop living only in your head.

After the setup, your AI starts the first check with proposals. You look at what it found and correct a wrong choice or explanation. Your correction becomes the rule for the next check; Bombos keeps that explanation; without it, the memory does not hold which agreement belongs to which invoice. You keep your existing package and mailbox. Filling in settings together is enough, even if computers are not your thing. Once a task type has gone well for a while, you decide how much autonomy you give your AI, with Bombos as the memory underneath. Posting the entry and judging a mismatch both stay with you.

If a supplier keeps drifting in the same direction, your AI puts that in front of you with the earlier invoices as the reason. You decide what happens with it.

Invoice checking is the start, not the whole offer. We take you along on the first task. After that, every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed, without you having to come back to us. After three months, you hear the same day when an invoice differs from what was agreed, not at the month end close.

Sharper checks without another hire.

What happens with invoice checking is typical of a growing organization. More suppliers and jobs arrive, and checking is the first thing to start running on trust. The agreements to check against are scattered over email, quotes and QuickBooks.

Bombos is the memory layer under the AI your team already uses: Claude, Claude Code, ChatGPT, Copilot, Grok, Codex, Cursor or your own agents. One plugin gives them all one shared memory: your team's knowledge, the rules it learns from your corrections, and what is already in your email, documents and business software.

You see where every answer came from. Bombos runs in the cloud or standalone on your own server, and one person can try the plugin with their own agents first.

The pilot runs three months for €2,000 instead of €3,000, then €1,000 per month, excl. VAT. Book your half hour to talk through your situation.

What Bombos does, in three steps

  1. It reads what comes in

    An email, a message, a photo or a PDF: your AI reads it, finds the client and the details through Bombos in the systems you already have, and sees what is missing.

  2. It drafts the work, you approve it

    The proposal sits on one list with the reasoning next to it. You read it, adjust it and approve. Only then is anything sent, booked or filed.

  3. It remembers what you decide

    Every correction becomes the rule for next time. Once it has gone well for a while, you give your AI more autonomy step by step, with Bombos as the memory underneath.

What does Bombos not do here?

Bombos does not act here itself: it gives your AI the memory. Without a connection between your AI and QuickBooks, it stays a proposal.

Your AI does not decide whether a disputed invoice is justified; you approve before anything is posted. It compares against the supplier's quote or the delivery note and puts the outcome in front of you. A change agreed by phone and written down nowhere is not in the paperwork. So your AI asks you once what you agreed with the supplier on the phone, and Bombos keeps the answer, so that change ends up alongside the documents used for the check.

A proposal can still be wrong or incomplete. The content needs checking before it gets posted. You approve a message about the mismatch before it goes to the supplier, as with any outgoing message to a third party on any channel. You set that in the AI or agent itself.

Checking an invoice starts with finding the agreement again.

The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.