Start a project
22:40 · Invoice guard

Forty invoices due Thursday. One pays the wrong account.

Invoice checks before the payment run, on SAP or any ERP

Obhur Builders (example): a contractor on SAP, paying hundreds of supplier invoices a month in a Thursday payment run.
How it worksQuestionsTry it

Before and after

Today

Every number is right, so it gets paid

An email from albina-steel.co asks for invoice INV-2026-1191 to be paid to a new account. The order, the goods received and the VAT all match, so 128,800 leaves on Thursday's run. It is found when the real Al Bina Steel asks to be paid.

With it

Matched, and still held

Before money moves, every invoice is checked three ways: is it real, is it right, is it normal. This one passes the first two and fails the third, so the payment is blocked in SAP until someone calls the supplier on the number already on file.

The demo's result, Tuesday 22:40:05
Invoice
Al Bina Steel · INV-2026-1191
Real?
Yes: stamp verified, VAT and commercial registration match
Right?
Yes: order and goods received match
Normal?
No: new account, lookalike sender
Thursday's run
128,800 held · payment block in SAP

What it reads, writes and never touches

What comes inYour systems
What comes in
Invoices mailboxsupplier emails and their e-invoice files, as they land
Your approvalthe same weekly sign-off you give today
Monolith invoice check
  • Real: verifies the ZATCA stamp; checks VAT and commercial registration numbers and duplicates
  • Right: matches the invoice to the order and goods received
  • Normal: compares bank, sender and amount with the supplier's history
Your systems
SAP supplier recordsread-only
SAP purchasingorders, goods receipts, paid invoices · read-only
SAP supplier invoicesposted by your AP team, as today
Reads

The email and its ZATCA XML, the supplier records, orders, goods receipts and the invoices already paid

Writes

A payment block on the supplier invoice when a check fails; on your approval, the block is lifted so it joins the next payment run. Nothing else.

Never touches

Paying, posting an invoice, or changing a supplier's bank account. Those stay with your staff.

How it works, step by step

  1. 122:40:01 · demo time

    Is it real?

    The e-invoice file inside the email is read, its stamp is verified against the invoice, and the seller is matched to your own supplier records. Then it is compared with every invoice already paid this year.

    Checks on the invoice
    ZATCA stamp
    verified against the invoice
    VAT no. 310122458700003
    matches your supplier records
    Commercial registration 4030219876
    matches your supplier records
    Duplicate or near-duplicate
    none among 1,412 invoices paid this year
  2. 222:40:02 · demo time

    Is it right?

    The invoice is matched to the purchase order and the goods receipt in SAP: the same quantity, the same price, and VAT that adds up.

    Invoice against SAP
    Purchase order
    4500000991, with its goods receipt
    Quantity: invoice, order, received
    40 t, 40 t, 40 t
    Price: invoice, order
    2,800 per t, both
    Net + VAT 15%
    112,000 + 16,800 = 128,800
  3. 322:40:05 · demo time

    Is it normal?

    The pattern is compared with the supplier's history in SAP. Here the money would go to an account asked for tonight, from a lookalike address, and never paid before, so a payment block is set in SAP at 22:40:05.

    Against the supplier's history
    Sent from
    albina-steel.co
    Supplier's own domain
    albinasteel.com.sa
    Pay to: supplier records → invoice
    account ending 7731 → account ending 1234
    Payments ever made to the account ending 1234
    none
    Amount against this supplier's history
    in the usual range

Rules you set

Approval limit25,000 for one approver; above it, a second approver
A new bank accountHeld until someone calls the number already in your supplier records
A bill split under the limitCoastline Freight, 2 × 21,620, 3 minutes apart: to the second approver
A duplicate with a new numberINV-2026-1176-A, paid on 21 Oct as INV-2026-1176: refused, with the payment reference

Values are examples from the demo

Connect or build

Connect to yours

We read SAP's supplier records, purchasing and posted supplier invoices through its standard interfaces. Your invoices mailbox is reached through Microsoft 365 or Google Workspace, with your admin's consent.

Or we build it

If you have no ERP, or one that can't hold a payment for review, we build what is missing.

Oracle, Microsoft Dynamics and Odoo connect through the interfaces they offer; which ones yours has is checked at the start. Each system is reached through a technical user your IT creates and can revoke.

The questions that decide it

Does it pay anything by itself?

No. It checks and holds, and nothing is paid without your approval. The call to the supplier uses the number already on file, never the one in the email.

What if the bank change is genuine?

Then the person who called records it, a second approver signs off because it is above the 25,000 limit, the block is lifted and it is paid on Thursday to the new account. The call is logged with the name of the person they spoke to.

Will it slow down ordinary invoices?

No. An invoice that passes all three checks gets no block and joins Thursday's run, as Dhahab Cement's does in the demo, with no one matching it by hand.

Want every invoice checked before it is paid?

Tell us your ERP, how supplier invoices reach you and when you run payments. We will tell you what we connect to and what we build.

Start a project
We reply by email. Quotes come by email or WhatsApp.