Invoice processing
Invoice processing automation turns supplier invoices into ERP records: Runtara extracts the fields, matches each line against the purchase order and goods receipt, and holds any variance for a person to approve before it is posted.
In use by a Runtara customer: automated reconciliation of supplier reports and invoices against contracts and expected revenue for a GPO.
01 / The problem
Why it is still manual.
Invoices arrive as PDFs and emails, but your ERP needs structured records. Someone reads each one, finds its purchase order, compares it, and keys it in.
Matching is the easy part. The line that does not match needs the right person, the evidence, and an ERP write only after they decide.
02 / How it runs
The workflow, step by step.
- Receive
Invoices arrive by email, PDF, EDI, SFTP or API. Each one starts a run that records what arrived.
- Extract
A model step reads the fields and line items with your own model credentials.
- Match
Each line is checked against the purchase order and goods receipt in your ERP.
- Hold
Variances wait for a person, with the document, ERP record and difference side by side.
- Post
Approved values are written to the ERP, with the decision and who made it kept on the run.
Finance sees the document, the ERP record and the variance together, then the approved values carry on.
03 / Under control
What stays under control.
The model only has the tools you gave it
In the example run, a request to change a vendor bank account is denied: that tool was never compiled in.
Approvals can wait
A held run waits as long as the approver takes, then resumes without repeating finished steps.
One query answers "what happened?"
Events, the approval and the ERP write sit together, so an auditor reads one result, not stitched logs.
04 / Systems
Systems it connects.
Examples from the supported connections. Other systems are scoped during implementation.
05 / Questions
Common questions.
Does a person have to approve every invoice?
No. Lines that match continue under the rules agreed for the workflow. Only the variances and exceptions you define are held for a person.
What happens when an approval takes days?
The run waits at its last committed step and resumes from there once the person answers. Completed steps, including model calls and ERP reads, are not repeated.
Which model reads the documents, and who pays for it?
You choose the model provider and endpoint. Model calls use your credentials and are billed directly to your provider account, on Runtara-managed Cloud and on customer-managed deployments.
Can this run with no internet access?
Yes, on a customer-managed deployment. A fully air-gapped installation has no route to Runtara; your model endpoint and business systems must be reachable inside that environment.
How is it priced?
Start with a paid pilot of this one process on Cloud. Each process has a one-time implementation fee, quoted from the systems, rules, and exception paths involved, plus the plan subscription. There are no per-task fees or run-count limits. Enterprise includes one agreed process.
Bring us the process.
Show us the systems involved, the records that move between them, and the exceptions your team handles. We will map the steps and scope a first workflow.