An overhead view of a team around a table with laptops
IFS · Accounts Payable · Hub

AI Agents for IFS
Accounts Payable

On a project ledger the bottleneck is coding, not approval. The person who knows the project, activity and cost element does not work in finance.

Key takeaways
  • An IFS invoice needs a project, an activity and a cost element, and the person who knows all three is the project manager. Routing unresolved coding to finance is why the queue moves slowly.
  • Resolve the project from the purchase order first, then the document, then how the supplier was coded before. Return a confidence per field, because vendor, amount, tax and project reference fail independently.
  • In a worked population of 168 held invoices, 135 were somebody else's decision. They age in the finance queue because that is where invoices land.
  • Report incurred, committed and certified cost as three figures. Collapsing them into one cost to date is how a project looks fine until the month it does not.
  • A failed integration message is a missing invoice and it is invisible in the ledger. Reading the message layer is how an agent tells that from an invoice never sent.

AI agents for IFS accounts payable read through the published IFS Cloud interfaces, resolve each invoice to a project, activity and cost element, match against the purchase order and receipt, and hand every posting to a named person. ChatFin returns a confidence per field rather than per document, and routes what it cannot resolve to the person who can answer it rather than to the finance queue.

The distinctive problem on IFS is not approval, it is coding. On a cost centre ledger an invoice needs an account and a department. Here it needs a project structure that only the project manager fully knows, which means the majority of held invoices are somebody else's decision sitting in finance's queue. In a worked month of 168 held invoices, 135 of them were exactly that.

IFSIFS CloudAccounts payableProject accountingCommitted costAccrualsSubcontractor applicationsCodingAI agents for finance
01

On a project ledger the bottleneck is coding, not approval

A cost centre invoice needs an account and a department. An IFS invoice usually needs a project, an activity and a cost element, and the person who knows all three is the project manager rather than anyone in finance. That single fact reorders the whole process.

1

Resolve from the purchase order first

Where a purchase order exists, the project and activity are already on it. Highest confidence path, and it should always be tried before extraction.

2

Then the document, then history

A project reference in the invoice text, then how this supplier was coded for similar work on the same project before. Both are proposals, not decisions.

3

Return a confidence per field

Vendor, amount, tax and project reference fail independently. One score for a whole invoice tells a clerk nothing about what to check.

4

Route unresolved coding to the project manager

Not to finance. Finance cannot answer which activity a cost belongs to, and routing it there is why the queue moves slowly.

5

Hold anything that breaches the approved project value

Committed cost passing the approved value is a commercial question and it should stop before it posts, not after.

The metric to watch is not invoices processed. It is the share coded to a project without a person choosing, and the share of coding questions reaching the right owner first time.
In ChatFin

ChatFin proposes coding with the purchase order, the prior treatment and the per field confidence visible. Where none of the three paths resolves the project, it asks rather than guessing.

02

What an agent reads on IFS

IFS Cloud exposes functionality as OData style projections through its API gateway, with IFS Connect handling integration messaging. That gives a documented read path that does not depend on driving the Aurena screens. Confirm the projection set in your own release before scoping, because it differs between releases.

AreaWhat payables needs from itWhy
Supplier invoice header and linesAmounts, tax, currency, authorisation stateThe authorisation state matters as much as the amount
Purchase order and receiptOrdered, received, and the project on the orderThe project reference is usually already there and unused
Project, activity and cost elementThe coding structure in force for that dateStructures change mid project and historic coding must still resolve
Supplier masterTerms, tax registration, payment detailResolution target. Duplicates here cause most downstream mess
Integration messagesFailed and pending messagesA failed message is a missing invoice, and it is invisible in the ledger

The last row is worth dwelling on. Where systems are integrated, a document that never arrived looks identical to one that was never sent. Reading the message layer is how an agent tells the difference.

In ChatFin

ChatFin reads through the published interfaces rather than the Aurena screens. Screen automation breaks the first time a page layout changes, and it breaks silently.

03

A worked exception population, 168 invoices held

A month of intake leaves 168 supplier invoices held. Sorted by value that is 168 decisions. Grouped by cause it is six, and only two of them belong to finance.

CauseInvoicesOwner
No project reference resolvable from any source54Project manager
Receipt not booked against the purchase order38Site or requisitioner
Price above the order, outside tolerance24Procurement
Would breach the approved project value19Commercial
Tax treatment unclear on a cross border supply18Finance
Supplier resolved to more than one master record15Finance, master data

One hundred and thirty five of the 168 are somebody else's decision. They sit in the finance queue because that is where invoices land, and they age there while the person who can resolve them never sees them.

An overhead view of a team around a table with laptops
Routing by cause rather than by value is the change that moves cycle time on a project ledger.
04

Accruals and committed cost on a project

Project reporting needs committed cost, not just incurred cost, and the two are assembled from different places.

Received not invoiced is calculable exactly. Receipts with no matching supplier invoice at the cut off, priced from the purchase order rather than an average.
Ordered not received is a commitment, not a cost. Reporting it as accrued overstates the position and it is a common error on long projects.
Subcontractor applications are neither. An application for payment is a claim until it is certified, and certifying it is not a finance decision.
Retentions have their own timing. They sit outside the ordinary ageing and get forgotten until a project closes.
The number worth reporting per project is incurred, committed and certified as three separate figures. Collapsing them into one cost to date is how a project looks fine until the month it does not.
In ChatFin

ChatFin assembles the three separately with the source documents attached to each line, and prepares the accrual for a named person to release.

05

Duplicates on a project ledger have their own shape

The usual duplicate tests still apply. Two additional patterns are specific to project work and neither is caught by vendor, amount and reference.

The same work claimed under two activities. A subcontractor invoices against activity 210 in one month and 215 the next for overlapping work. Both look legitimate on their own line.
The application and the invoice. An application for payment followed by an invoice for the same valuation, entered separately, is the project ledger's classic double count.
The reissued invoice after a project renumbering. A restructured project leaves cost on the old identifier and a reissued document on the new one.
In ChatFin

ChatFin tests against the receipt and the certified valuation, not only against the reference. A held invoice costs a conversation. A paid duplicate costs the money and the recovery.

06

Retentions and the money that goes missing at project close

Retention is withheld cash with a release date attached, and it is the single most commonly lost item on a project ledger because nothing prompts anyone about it.

ItemWhy it goes missingWhat an agent should report
Retention withheld from a subcontractorSits outside the ordinary ageingBalance by project with the contractual release date on each line
Retention due for releaseNo system prompt when the date passesA dated release list, monthly, whether or not anyone asked
Retention on a project already closedThe project stops being reviewedClosed projects with a non zero retention balance, as a standing exception
Defects liability period expiringTracked in contracts, not in financeThe expiry date read from the contract, matched to the balance

The same applies in the other direction on receivables. Retention held by a customer is cash owed with a date, and it ages differently to an ordinary invoice.

A standing report of retention balances on closed projects usually finds money the first time it is run. It is one query and almost nobody runs it.
In ChatFin

ChatFin reports retention by project with release dates read from the contract, and flags closed projects carrying a balance as a standing exception.

07

Where this underperforms on IFS

Three, and all three should be tested before a pilot.

API access is not opened. Without governed access to the IFS Cloud projections the alternative is screen automation, which is a liability rather than a workaround. The honest answer is then no.
Project structures differ between business units. Where one unit uses activities and another does not, portfolio level automation cannot work until the structures agree. That is an organisational decision, not a technical one.
Purchase orders do not carry the project. If the project reference is not on the order, the highest confidence coding path is unavailable and everything downstream degrades.
In ChatFin

ChatFin reports the share of invoices it can code from the purchase order before it reports an automation rate. A high rate on a narrow population is not a solved process.

Deeper in IFS payables

Three use cases sit under this hub, in build and shown rather than linked.

Worked on this page
Vendor follow up for missing invoices · AP inbox automation · Invoice intake and document extraction

Covered as sections here
Project and activity coding · 3 way matching · Duplicate detection · Approval routing · Accruals from open orders · Committed cost

Questions IFS payables teams ask first

Why do so many invoices get held on a project ledger?

Because coding needs knowledge finance does not have. An IFS invoice needs a project, an activity and a cost element, and in a worked month of 168 held invoices only 33 were genuinely finance decisions. The rest were unresolvable project references, missing receipts, price differences and approved value breaches, all owned by project managers, sites, procurement or commercial. ChatFin groups them by cause and routes each group to the owner who can resolve it.

How does an agent decide the project coding?

In descending confidence. The purchase order first, because the project and activity are usually already on it. Then a project reference in the document itself. Then how the same supplier was coded for similar work on the same project before. Each is a proposal with a stated source, not a decision. Where none of the three resolves it, ChatFin asks rather than defaulting, because a confident wrong project code is invisible in the totals.

What should be reported for committed cost?

Incurred, committed and certified as three separate figures. Received and not invoiced is calculable exactly and should be priced from the purchase order. Ordered and not received is a commitment rather than a cost and reporting it as accrued overstates the position. A subcontractor application for payment is a claim until certified, and certifying it is not a finance decision. ChatFin assembles all three separately with documents attached.

How ChatFin works in IFS payables

168 held invoices become six queues with six owners.

ChatFin resolves project coding from the purchase order, the document and prior treatment, returns a confidence per field, and matches against the receipt before proposing anything.

Exceptions are grouped by cause and routed to the person who can answer them. Incurred, committed and certified cost are assembled separately, and ChatFin posts nothing.

Bring one month of held invoices. The comparison takes an hour.

Book a demo
AM
Ashok Manthena
CEO and co founder, ChatFin

Ashok Manthena is the CEO and co founder of ChatFin, an AI agent platform for enterprise finance that runs across NetSuite, Acumatica, JD Edwards, SAP and Dynamics 365. He works with CFOs and controllers on governed automation of the close, payables, receivables and reporting. Connect on LinkedIn.

Image credits. Header photograph: an overhead view of a team around a table with laptops, sourced from Pexels and used under the Pexels licence.
All images are served from the Pexels content network. No third party product screenshots, vendor logos or licensed media are used on this page.
Get started

Bring one month of held invoices.

We will run the same population through ChatFin, group it by cause and owner, and tell you the share we can code straight from the purchase order.

✓Coding resolved from the order first, with the source stated
✓Confidence per field, not per document
✓Exceptions routed by owner, not by value
Request a demo
Confidential & private