GPO supplier report and invoice reconciliation
GPO reconciliation automation checks supplier sales and admin-fee reports and invoices against your contracts, member rosters and expected revenue as they arrive, maps revenue, and tracks compliance and contract adherence, so gaps surface when the report arrives, not at audit time.
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.
Supplier reports and invoices arrive by email in every format, and someone re-keys them into a spreadsheet to check against contracts and rosters.
Missing reports and duplicates are hard to spot, and tier or member mismatches surface late, at audit time.
- Allied FastenersReconciledReported $18,240Expected $18,240
Matches contract and member roster
- Beacon LightingShortReported $9,860Expected $11,420
Purchases by 3 members missing from the report
- Cortland SafetyDuplicate flaggedReported $5,130Expected $5,130
Same report received twice; counted once
- Delmar PackagingNot reportedReported NoneExpected $4,750
No report received for the quarter
- Everline MedicalReconciledReported $7,080Expected $7,080
Matches contract and member roster
Follow up before audit time. Each gap links back to the supplier report, the contract, and the member roster used to compute it.
02 / How it runs
The workflow, step by step.
- Collect
Reports arrive by email as PDFs or spreadsheets, and Runtara tracks who has reported this period.
- Read
A model step reads each supplier's format with your own model credentials. Duplicates count once.
- Reconcile
Sales and admin fees are checked against your contracts, member rosters and expected revenue.
- Follow up
Short, missing or mismatched reports go to your team with the evidence side by side.
Separate a real shortfall from a reporting difference, and follow up while the period is open.
03 / Under control
What stays under control.
Gaps surface when the report arrives
Reports are reconciled on arrival, so a short fee shows up now, not in a later audit.
Every number has its evidence
Each figure links back to the report, contract and roster it came from.
Only the access it declares
Each step can only call the connections it declares, so a read-only reconciliation cannot write.
04 / Systems
Systems it connects.
Examples from the supported connections. Other systems are scoped during implementation.
- Supplier reports and invoices by email, as PDFs or spreadsheets
- Your accounting system or ERP, including QuickBooks and Business Central
- Database tables your team can review and export
05 / Questions
Common questions.
Our suppliers all send reports in different formats. Is that a problem?
No. Each supplier's format is read into the same fields, whether it arrives as a PDF, a spreadsheet, or in the body of an email.
Can it tell which suppliers have not reported?
Yes. Runtara tracks which suppliers have reported for each period and flags duplicate submissions, so missing and repeated reports are visible as soon as the period closes.
Can it tell a real shortfall from a reporting difference?
That is what the reconciliation step is for: spend below the contract and a mismatch in supplier-reported values are flagged differently, so each gets the right follow-up.
How long until it is live?
Live in two weeks once access is in place: access to the mailbox the reports arrive in, your contracts and member roster, and your accounting system or ERP.
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.