Eight years of invoice automation, still running.

An industry superannuation fund processes a steady volume of supplier invoices against Oracle Financials, with a leading AP automation platform in front of it.

A fund operates under a members' best financial interests duty. Every dollar of administration cost is a dollar not returned to members, which makes manual invoice handling a recurring drag on the fund's core obligation rather than an ordinary back-office irritation.

The fund had already chosen its AP automation platform. Anything we did had to work with that decision, not around it.

Valtatech deployed Valtatech Invoice AI against the fund's existing AP automation platform, capturing supplier invoices as structured, ERP-ready data rather than documents somebody retypes into Oracle Financials.

Integration as a Service connects the flow through to the finance system, and Application Managed Services covers the platform day to day.

Exceptions are worked, not queued. Every invoice the automation cannot resolve on its own is logged against the supplier, the specific field in question and a named analyst, and chased to resolution — the same forward deployed analyst model we run on VIA and PayGuard. The fund's team sees resolved items rather than a growing list of flagged ones.

Support covers the fund's own system users and its suppliers, across technical issues, onboarding, platform walkthroughs and change requests.

Eight years is the part worth pausing on. Automation is usually judged on how it looks at go-live, when the mapping is fresh and somebody is still paying attention. What decides whether it survives is the unglamorous part — who works the exceptions in year four, and whether anyone notices when a supplier changes their invoice layout.