Invoice processing for MRI Qube.
Dataforge uses AI to read the supplier invoices and utility bills that arrive for the properties you manage in Qube, predicts the property, fund and heading from your coding history, and posts approved invoices to Qube through its PL Interface. Qube returns its reference, and Qube stays your system of record.
A 20-minute walkthrough using a sample of your own invoices.
DataforgeWhat moves between Dataforge and Qube.
Matching uses the records you already keep in Qube, and every posting is tracked back to the invoice it came from. Your property accounts stay in Qube.
Check fit with your Qube setup- 01
From Qube
Supplier, property and purchase order records, used to match each invoice to the right supplier, property and PO.
- 02
To Qube
Approved invoices, posted through the PL Interface with the property, fund, schedule and heading already coded.
- 03
Back from Qube
Qube's reference, returned to the invoice history for every API posting.
- 04
When a posting fails
Posting outcomes are tracked, and errors are resolved from a dedicated inbox.
Read, matched, checked and approved first.
When confidence, checks and your approval policy allow, an invoice moves on to Qube without manual handling. Anything uncertain is held with the reason named, and reviewers see the document beside every check.
Read
AI reads every invoice, including poor scans, photos and spreadsheets, and predicts the coding from how your team has coded that supplier and property before.
Match
Property found from fragments in the agent's address, a block name, part of a postcode or a flat number, using your Qube records and supplier history.
Check
Duplicates, bank detail mismatches against your supplier master, a person on every first invoice from a new supplier, purchase orders and your posting limits.
Approve
Routed by value band and your approval matrix, through single or multi-step chains, with self-approval prevented and overdue decisions escalated.
Every posting traced back to the invoice.
What arrived, what was extracted, what changed, who approved it and the Qube reference it posted under. When a client or auditor asks why an invoice was coded to that schedule, the answer is in one history.
Deployment and control- 09:14:02RECEIVEDemail · invoices inbox · 1 page
- 09:14:03EXTRACTED14 fields · site postcode · 96%
- 09:14:03MATCHEDLS1 4AP → KWH-004 · supplier history
- 09:14:03CODEDfund SC26 · schedule SCH-03 · heading 0412
- 09:14:04HELDpossible duplicate · billed to agent
- 09:31:47REVIEWEDduplicate cleared · property confirmed · J. Patel
- 09:52:10APPROVEDvalue band 2 · S. Okafor
- 09:52:11POSTEDMRI Qube · ref PI-004812
Dataforge connects to MRI Qube through its PL Interface. Supplier, property and purchase order records come in for matching, approved invoices post back to Qube, and Qube's reference is returned to the invoice history.
No. Dataforge handles intake, extraction, checks, coding and approval before posting into Qube. Qube remains your property accounting system.
Posting outcomes are tracked for every invoice. A posting that fails lands in a dedicated inbox with the error, so your team can resolve it and post again.
Yes, when confidence levels, validation checks and your approval policy permit it. Invoices that need attention are held or blocked with a named reason for review.
Yes. Utility bills are read by AI, checked for net, VAT and total, energy VAT and Climate Change Levy, coded to the property, fund and heading, and posted to Qube like any other supplier invoice.
No. Dataforge is built and supported by Stratas. MRI Qube is a product of MRI Software. Book a walkthrough and we'll review your Qube setup with you before confirming fit.
See your own invoices posted to Qube.
In 20 minutes we'll walk through property coding, exception review and the posting route into MRI Qube, using five to ten of your own invoices and utility bills.
No commitment. We'll arrange the sample documents with you after you enquire.