Two questions account for an outsized share of every AP team's inbox: "Did you receive my invoice?" and "When am I getting paid?" They're reasonable questions. They're also almost entirely mechanical to answer — the status is sitting in your ERP — yet they get answered by a person, one email at a time, all day long.
We've written before about why this matters strategically in the AP work before the invoice. This post is the narrow, practical version: how you actually automate the status reply itself, and why the hard part isn't the reply — it's knowing the real answer.
Why a templated auto-reply isn't enough
The temptation is to bolt a canned auto-responder onto the AP mailbox: "Thanks, we've received your email." That's worse than nothing. It doesn't answer the supplier's actual question, so they email again — or call. You've added noise, not removed it.
A useful auto-reply has to do two things a template can't:
- Understand what the email is actually asking. Is this a status query? A fresh invoice? A duplicate of one already in flight? A statement? A sales order that should just be deleted? Each needs a different response.
- Look up the truth. "When am I paid?" only has a real answer if you can read the invoice's live status out of the ERP at the moment the email arrives.
Get either wrong and you've automated a confident, useless reply. The value is entirely in the accuracy.
Step one: classify the inbound email
Before anything can be answered, the message has to be understood. The classifier reads the email and its attachment and decides what it is — a status enquiry, a new invoice (with or without a PO), a duplicate, a statement, a credit note, or junk to discard. Status queries and duplicates are the two that route into the payment-status flow; the rest go their own way.
The distinction that drives everything downstream is who's asking. A supplier asking about an invoice and an internal team member asking about the same invoice should get differently worded answers, even when the underlying status is identical. Same fact, different audience.
Step two: read the real status from Oracle
Once an email is identified as a status question (or a duplicate of an invoice already submitted), the system queries Oracle for that invoice and maps the result to one of three states:
- Not processed — Oracle has no validated record of it yet, or it's mid-pipeline.
- Validated — processed and approved, sitting in the queue for the next payment run.
- Paid — the payment has gone out.
That mapping is the whole game. It's the difference between "we're processing it" and "that was paid last Tuesday." Both are true at different moments; only the live lookup tells you which one applies right now.
Step three: reply with the real answer
With the status in hand, the reply writes itself — and it's phrased for the audience:
- Not processed → "Your invoice is being processed." If it's a duplicate, that becomes a gentle "This is a duplicate — please don't resend; we're currently processing your invoice."
- Validated → "This invoice is processed and scheduled to be paid on our next payment run."
- Paid → "This invoice was paid on [date]" — and for a supplier, the system fetches the remittance advice for that transaction and sends it to the remittance email on file. That single step preempts the next three emails.
There's also an honest failure mode. If the supplier references an invoice number that doesn't exist in Oracle, the right reply isn't silence — it's "That invoice number isn't valid; please provide a valid invoice number." Asking a clear clarifying question is itself an automated, useful answer.
Why this only works ERP-native
Notice that every branch above depends on a live read from Oracle. A bolt-on email tool that can't see invoice status can only ever send templates. The accuracy — and therefore the entire value — comes from the auto-reply being wired into the same system that holds the invoice's real state. Pull the status at the moment the email lands, and the reply is correct by construction. Cache it, guess it, or template it, and you're back to a person checking the ERP and typing the answer.
This is also why "did you get my invoice?" is such a good first target for AI email exception prevention. It's high-volume, the answer is unambiguous, and resolving it upstream means the supplier conversation never becomes a phone call, a follow-up, or an exception sitting in someone's queue.
Where EZ Cloud fits
EZ Cloud reads invoice status live from Oracle — EBS or Fusion — and answers supplier and internal status enquiries automatically, with remittance advice attached when an invoice has paid. The AP team stops being a lookup service for the supplier base and gets that time back for work that actually needs judgment. If the loudest thing in your AP inbox is "any update on my invoice?", that's exactly the noise this is built to remove.