Supplier invoices in Sage 50 and 200: control

By Nicolau Matarrodona, founder · Published 3 May 2026 · Updated 24 October 2026

Before posting a supplier invoice in Sage 50 or Sage 200, three things need checking that entering the invoice does not check on its own: that the price is the purchase order price, that the quantity is what arrived according to the delivery note, and that the invoice has not already been posted. ininvoice performs those checks line by line before Sage and hands it the approved invoices as a CSV or Excel file; it has no native Sage connector.

What entering an invoice does not check

Entry route	What it solves	What it leaves unchecked
Typing the invoice by hand	Getting the data in	Everything else: what is typed is what is posted
Invoicing against a purchase order already recorded	Not retyping purchase order prices and quantities	Whether what was invoiced arrived, when the receipt is not recorded
Digitising the PDF to propose the entry	Saving keying	Whether price and quantity match purchase order and delivery note
Importing a file	Volume: many invoices at once	Whatever was not checked before generating the file

Two invoices before they reach Sage (synthetic data)

Supplier and invoices are made up for the example.

Invoice	What ininvoice finds	Amount at stake	Result
"FV-2026/0042" from an electrical supplies vendor, EUR 1,284.00	It had already received "FV 2026 0042" from the same supplier: the same number written differently	EUR 1,284.00	Held as a possible duplicate
"FV-2026/0057", 40 reels at EUR 18.40 (purchase order at EUR 17.90)	Price above the purchase order: (18.40 − 17.90) × 40 = EUR 20.00, 2.8% of the line	EUR 20.00	Held for a price difference

Had both invoices been typed or imported directly, the first would have been paid twice and the second EUR 20.00 too much. Neither reaches the file for Sage until a person decides.

Want to see it with your own invoices? Request a demo with your own invoices

The flow with Sage

Invoices arrive in the invoice mailbox connected to ininvoice (read-only) or are uploaded by hand; purchase orders and delivery notes, as PDF, image or spreadsheet.
ininvoice reads every document line by line, validates tax ID, base, VAT, withholding and reverse charge, and matches the invoice with purchase order and delivery note.
Invoices that do not match, and possible duplicates, are held for a person to approve, reject or ask for clarification.
Approved invoices are exported as CSV (one row per line) or Excel (columns to choose).
The file is imported into Sage, which posts, settles taxes and pays.

Sage and Spain's 2027 e-invoicing

According to the Spanish Tax Agency, B2B e-invoicing is mandatory from 6 October 2027 for businesses above EUR 8 million of turnover and from 6 October 2028 for the rest. Received invoices will then arrive as structured messages, but checking them against purchase order and delivery note will still be needed. ininvoice reads PDF, image, scan, photo and spreadsheets today; reading XML e-invoices is in development.

Frequently asked questions

Does ininvoice replace Sage?

No. Sage remains the ERP or accounting software: it posts, settles taxes and pays. ininvoice works before it, checking every supplier invoice against the purchase order and the delivery note.

Does ininvoice have a native Sage connector?

No. The hand-over to Sage is a CSV or Excel file with the approved invoices, imported into Sage. There is no direct writing into Sage.

Does it work with Sage 50 and Sage 200?

Yes, because it does not depend on the version: ininvoice reads the documents and delivers a file. The mapping between the file's columns and each Sage version's fields is defined once.

Does it detect an invoice already posted in Sage?

ininvoice compares each invoice with the ones it has already received: same number from the same supplier (even if written with different hyphens or spaces), same amount and date, and same file. Invoices posted in Sage by another route, without going through ininvoice, are not visible to it.