Key takeaways
- MRI Software reports by entity or property and GL account, and uses job codes to track project spend such as capital work and tenant improvements.
- Vergo reads your ledger accounts and job codes from MRI, so proposed coding uses values that exist in your database.
- Coding is proposed by inference from your own history, and approvals route by GL account, by amount or by project, which in a portfolio usually means the property.
- Approved invoices post into MRI through MRIAPInvoiceCreate, and new suppliers are created as AP vendors.
- Access is partner-gated: API access sits in your MRI environment, your IT team enables it once, and Vergo does the rest.
Where should you go next?
- Learn more about Vergo AP Invoice Automation
- Vergo's MRI Software integration
- Vergo for property management
How do you automate invoice coding and approvals in MRI Software, step by step?
- Enable API access. Your IT team enables MRI API access in your environment once. Vergo reads your ledger accounts and job codes.
- Collect invoices in one inbox. Vendors email invoices to your AP inbox and property teams drag and drop scans. Vergo extracts vendor, invoice number, dates, amounts and lines, and flags likely duplicates.
- Code each line. Vergo proposes the entity or property, GL account and, where relevant, job code for each line from how your team coded similar invoices, and shows why.
- Route for approval. Send invoices to the property manager, route capital invoices with a job code to the project or asset manager, and add a second approver above a set amount.
- Post to MRI. Approved invoices post as AP invoices through MRIAPInvoiceCreate, ready for your payment run. Vergo reads AP payments back.
What does MRI need on each invoice line?
MRI users report operating expenses per property for owners and investors, and track capital projects separately so they can be budgeted and, where leases allow, recovered. Each line should carry:
- Entity or property, so the expense lands in the right set of books.
- GL account from your MRI chart of accounts.
- Job code, for spend that belongs to a capital project or tenant improvement.
- Vendor, matched to an existing AP vendor or created for a new supplier.
A roofing contractor's invoice that mixes a repair at one building with work on a capital project at another has to be split. Coded to one line, it overstates operating expense at the first property and leaves the capital project short. Line-level coding at intake keeps both right.
How should approvals be routed for MRI Software?
Vergo routes by GL account, by amount or by project, and approvers review the invoice image, the proposed coding and the reason from a phone without an MRI login. Common rules:
- Operating invoices go to the property manager for the property.
- Invoices carrying a job code go to the project or asset manager for that job.
- Recurring utility and service contract bills skip approval and rely on policy flags.
What syncs between Vergo and MRI Software?
Vergo reads ledger accounts and job codes, creates, reads and updates AP vendors, posts AP invoices through MRIAPInvoiceCreate and GL journal entries through IRESMRIGLJournalCreate, and reads AP payments. MRI documents these calls in its MRI API integrations guide. The connection is partner-gated. The specification is on the MRI Software integration page.
A practical example
A commercial landlord receives an HVAC contractor invoice with two lines: a service call at one office building and a unit replacement that belongs to a capital job at another. Vergo proposes the repairs GL account and the first property for the service call, and the capital job code for the replacement, based on how the contractor's past invoices were coded. The property manager approves the service call and the asset manager approves the replacement. The invoice posts into MRI through MRIAPInvoiceCreate with both lines coded, so operating expense and capital spend are separated before anyone runs a report.
How Vergo handles this
Vergo is an AI-native, card-agnostic spend platform that runs AP invoices, card spend and employee reimbursements through one coding model against your MRI ledger accounts and job codes. Proposals come from your own history, with the reason shown, and new vendors are coded on first sight. Approval flows are optional, and payment stays on the rails you already use.
Related questions
Frequently Asked Questions
Does Vergo post invoices directly into MRI Software?
Yes. Vergo posts approved invoices into MRI through the MRIAPInvoiceCreate API, with property, GL account and job code on each line. GL journal entries post through IRESMRIGLJournalCreate.
Can Vergo create new vendors in MRI?
Yes. Vergo creates, reads and updates AP vendors through MRI's API, so a first-time supplier's invoice does not wait on manual vendor setup.
How does Vergo separate capital spend from operating expense?
Vergo reads your MRI job codes and proposes one on lines that belong to a capital project, based on how similar invoices were coded before. Those lines can route to the project or asset manager for approval.
What does IT need to do to connect MRI?
API access sits in your MRI environment. Your IT team enables it once, and Vergo handles the rest.
Is this the same integration as MRI Qube PM or Strata Master?
No. MRI Qube PM and MRI Strata Master have their own integration pages. This page covers MRI Software, where Vergo posts AP invoices through MRIAPInvoiceCreate.
