Key takeaways
- In Yardi Voyager, an invoice is only useful for owner reporting when every line carries the right property and GL account, and often an expense category.
- Vergo reads your property, GL account and expense category structure through the interface provisioned in your Voyager environment.
- Coding is proposed by inference from your own history, and approvals route by GL account, by amount or by project, which for a portfolio usually means the property.
- Approved invoices are delivered in the Voyager import format for your provisioned interface, so coded spend reaches Voyager without re-keying.
- Access is partner-gated: the interface is provisioned in your Voyager environment, and once it is enabled Vergo does the rest.
Where should you go next?
- Learn more about Vergo AP Invoice Automation
- Vergo's Yardi Voyager integration
- Vergo for property management
How do you automate invoice coding and approvals in Yardi Voyager, step by step?
- Provision the Voyager interface. The interface is enabled in your Voyager environment once. Vergo then reads your properties, GL accounts and expense categories.
- Collect invoices in one inbox. Vendors email invoices to your AP inbox, and site staff drag and drop scans. Vergo extracts vendor, invoice number, dates, amounts and lines, and flags likely duplicates.
- Code each line. Vergo proposes the property, GL account and expense category for each line from how your team coded similar invoices, and shows why.
- Route for approval. Send each invoice to the property manager for the property, add a regional manager or asset manager above a set amount, and let routine utility bills pass on policy flags.
- Deliver to Voyager. Approved, coded invoices are delivered in the Voyager import format for your interface, ready for your payables process.
What does Yardi Voyager need on each invoice line?
Property accounting is reported by property and by GL account, because owners, lenders and investors read statements per property. Each invoice line should carry:
- Property, the building or community the cost belongs to.
- GL account from your chart of accounts, such as repairs and maintenance, landscaping or utilities.
- Expense category, where your company uses categories for budgeting or recoveries.
A landscaping vendor that services five properties often sends one invoice. Coded to one property, it overstates that property's expenses and understates the other four until someone reallocates it. Splitting the lines by property when the invoice arrives keeps each property's statement right.
How should approvals be routed for Yardi Voyager?
The property manager knows whether the work was done. Vergo routes by GL account, by amount or by project, and in a property portfolio the project is usually the property. Approvers review the invoice, the proposed property and GL account, and the reason from a phone. Common rules:
- Repairs and maintenance invoices go to the property manager for that property.
- Capital or large invoices above a set amount add a regional or asset manager.
- Recurring utility bills skip approval and rely on policy flags.
What syncs between Vergo and Yardi Voyager?
Vergo reads your property, GL account and expense category structure and delivers coded spend, including AP invoices, card transactions and reimbursements, in the Voyager import format for your provisioned interface. Yardi provisions third-party interfaces through its interface partner program. The details are on the Yardi Voyager integration page.
A practical example
A property management company receives one landscaping invoice covering four communities. Vergo reads it from the AP inbox and proposes four lines, one per property, each coded to the landscaping GL account because that is how the vendor's past invoices were coded. The invoice routes for approval by property. Once approved, the coded invoice is delivered in the Voyager import format with each property carrying its own share, so each owner statement shows the right landscaping expense.
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 Voyager properties and GL accounts. 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 into Yardi Voyager?
Vergo delivers approved, coded invoices in the Voyager import format for the interface provisioned in your Voyager environment. It reads your properties, GL accounts and expense categories so the coding matches your setup.
Can one vendor invoice be split across several properties?
Yes. Vergo codes at the line level, so an invoice covering several properties is split into lines, each with its own property and GL account.
What needs to happen before Vergo can connect to Yardi Voyager?
The interface has to be provisioned in your Voyager environment. Once it is enabled, Vergo reads your structure and handles the rest.
Who approves invoices in an automated Yardi Voyager workflow?
You decide. Vergo routes by GL account, by amount or by project, which for a portfolio usually means the property. Many teams send invoices to the property manager and add a regional manager above a set amount.
Do site staff card purchases follow the same coding?
Yes. Card spend and reimbursements are coded with the same model to the same properties and GL accounts, and delivered in the same Voyager format.
