Automate invoice capture into IFS Cloud
AP inbox to posted invoice, in six stages.
The short answer
Post the clean matches. Ask a person about the rest.
The six stages of an invoice run
Supplier templates break as layouts change. Here an agent reads each layout, so a new supplier needs no setup.
New email in the AP inbox: invoice NC-24117 from Nordia Components
- 1 Capture the emailNC-24117.pdf, message ID kept Outlook
- 2 Read the invoice14 lines, 24,180.00 EUR Agent
- 3 Check supplier, order and duplicatesActive, PO-20447, no duplicate IFS
- 4 Create the supplier invoicePosted for approval IFS
- 5 Route any exceptionNone on this invoice Teams
- 6 Post the daily summary#accounts-payable Teams
- 1
Capture
Outlook or Gmail, the AP mailbox
Each new email starts a run. Its message ID is kept, so a forwarded copy never makes a second invoice.
- 2
Read
An agent step
The agent reads the supplier, tax ID, lines, tax and totals, and says how sure it is of each.
- 3
Check
IFS, live records
Supplier, order, totals and duplicates are checked against IFS itself, not a nightly copy.
- 4
Post
IFS, through official actions
A clean match is created in IFS with its ETag, so the posting rules IFS already has still run.
- 5
Ask
Teams, an approval
Anything unclear waits for a person, who sees the invoice and the IFS records side by side.
- 6
Report
Teams, the AP channel
Once a day: invoices posted, exceptions waiting and the oldest wait.
Four checks against IFS
Nothing posts without a clean match or a person’s decision.
| Check | Against IFS | If it fails |
|---|---|---|
| Supplier | Found by tax ID | An exception, never a guess |
| Order lines | Price and quantity within tolerance | A person decides |
| Totals | Currency matches, lines add up | The approver sees which figure is off |
| Duplicates | Same supplier, same invoice number | Stopped before anything is created |
What to have in place before the first invoice
- An AP mailbox, connected by signing in
- The companies and sites in the first wave
- Supplier records clean enough to match on tax ID
- Price and quantity tolerances, agreed with finance
- An owner for each kind of exception
- A channel where the daily summary lands
Six numbers to watch
Measure the manual baseline first.
- Touchless rate
- Invoices posted with no one touching them
- Cycle time
- Hours from the inbox to a posted invoice
- Exceptions by kind
- Where tolerances or supplier records need work
- Duplicates caught
- Overpayments that never went out
- On-time payment
- And the early-payment discounts taken
- Approval wait
- Whether people keep up with the exceptions
Questions AP teams ask
Do we need a template for each supplier?
No. Templates are what this design replaces. The agent reads each invoice the way a clerk would, whatever the layout, so a new supplier or a redesigned invoice needs no setup.
What happens when an invoice does not match the order?
It becomes an exception with an owner instead of silent rework. The approver sees the invoice and the IFS records side by side, with the reason the run stopped, and approves, corrects or rejects it. The run then carries on from where it paused.
How does an auditor trace a posted invoice?
Store a reference from each IFS invoice back to its source email and PDF. With every step of the run on the audit trail (who started it, what ran and what came back), an auditor can walk from a posted invoice to the original document.
Can this run in our own cloud?
Yes. NgageFlow runs in your own cloud, or managed by EX10, and you keep ownership of the data either way. The AI models a flow calls are the ones you connect.
Does this work on SAP or IBM Maximo too?
Yes. IBM Maximo, IFS and SAP work out of the box, through each ERP’s official interfaces, and one flow can use two of them, for example the asset in IFS and its cost in SAP. For any other application, including a homegrown one, we teach Ngage how it works in weeks. This guide uses IFS terms because it is written for IFS teams.
How quickly can we try it on our own IFS?
On IFS, a flow can be live in hours, depending on access to your test environment and the scope.
Try invoice capture on your own invoices
Describe it in a sentence or two. We run it with you, live, in a safe test setup.