Key takeaways
- DoorLoop records an expense in one step: pay-from account, payee, property, optional unit, category and amount.
- Its bank sync uses Plaid to connect bank accounts and credit cards, with automatic categorisation and matching.
- AI Expense Capture, which fills an expense from a dropped receipt, requires DoorLoop's AI Add-on.
- Vergo proposes property, unit and category from history, texts for receipts and records expenses paid by credit card through the API.
Where should you go next?
- Vergo's DoorLoop integration
- What expense management software integrates with DoorLoop?
- Get started with Vergo
How do you automate expense management in DoorLoop, step by step?
- Connect DoorLoop. Vergo connects through DoorLoop's public API, reads your GL accounts and vendors, and records each coded card purchase as a DoorLoop expense paid by credit card, with property and account on each line.
- Connect your existing cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
- Collect receipts by text. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.
- Code property, unit and category. Vergo proposes each value for every receipt line.
- Record the expense. Confirmed spend becomes a DoorLoop expense, so the synced card line has something to match.
What does DoorLoop need on each card transaction?
- Pay from account: the credit card account.
- Property: the property incurring the expense.
- Unit: optional, for unit-level tracking.
- Category: the expense account.
- Attachment: the receipt.
Where does bank sync stop and automation start?
DoorLoop's bank sync brings card transactions in and sorts them into categories. A category is only half the answer in property management; the property and unit decide whose statement the cost lands on. Vergo reads the receipt itself, line by line, and predicts the GL account from what was actually bought, not just the vendor name on the header, and proposes the property and unit from where that staff member usually works and how similar items were coded.
A practical example
A leasing agent buys cleaning supplies for a turnover at one building and a lockbox for a vacancy at another. Vergo texts for the receipt, proposes the cleaning category on the first property's unit and the supplies category on the second property, and the bookkeeper confirms. Two DoorLoop expenses are recorded with the receipt attached.
How Vergo handles this
Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. In DoorLoop, that means learning which technicians work which properties and how turnovers are categorised. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Approval workflows are optional and fit how you already control spend: route by GL account or by amount — or skip approval flows entirely and let policy flags catch only what breaks a rule.
Frequently Asked Questions
Does Vergo record DoorLoop expenses itself?
Yes, through DoorLoop's public API, as expenses paid from the credit card account.
Can Vergo code to units?
Yes. Vergo proposes the unit when similar spend was tracked at unit level.
Do we need the DoorLoop AI Add-on?
Not for Vergo. Vergo reads receipts itself.
Does DoorLoop have expense claims?
DoorLoop's documentation covers expenses as accounting transactions; it does not describe employee claims or approvals.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
