What are the options for getting card transactions into Nimble Property?
Nimble Property is a hosted hotel accounting platform with no public API documentation, so there is no card feed or programmatic sync to switch on. Card activity gets into the books one of two ways: keyed in manually, or brought in as a file through the system's import function. Across the card volume of even one hotel — supplies, repairs, utilities deposits, travel — the file route is the only one that scales.
What does the manual workflow cost?
Without automation, each close looks like this: download statements for every card, open them in a spreadsheet, match lines to receipts collected from GMs and department heads, assign each line its account and property coding, reshape the columns into an importable layout, and run the import. Multiply by properties and cardholders, and statement-to-ledger becomes one of the slowest parts of the hotel close — with every retyped line a chance for a reconciliation break later.
How does Vergo automate the import into Nimble Property?
Vergo removes the preparation work and leaves you a clean load step:
1. Spend happens on Vergo cards. Vergo issues the corporate cards for your properties, so every transaction is captured at the moment of spend — no waiting on statements.
2. Coding happens at the point of spend. Cardholders snap receipts and code purchases from their phone; accounting sets rules so recurring vendors code themselves, with the right property and account on each line.
3. Vergo generates the import file. Vergo produces a custom-built CSV export matched to the import format Nimble Property expects, so the file loads without column-mapping or cleanup.
4. You import and review. The file runs through Nimble Property's own import routine. Accounting reviews it before loading, so nothing posts unseen.
Why does a matched export matter?
Because a generic export only automates the download. If the file from your card platform still needs a spreadsheet session before Nimble Property accepts it, the manual work has moved, not disappeared. Vergo's export is built against the structure Nimble Property imports — your accounts, your layout — so the monthly cycle collapses to two steps: export from Vergo, import into Nimble Property. Receipts, coding, and per-property distribution are already done by the time the file exists.
There is a control benefit alongside the time saved. Because accounting reviews the export before it loads, nothing posts to Nimble Property unseen — the workflow adds a checkpoint the manual statement scramble never really had. And because spend is visible in Vergo the day it happens, controllers stop discovering surprises at statement time and start catching them per property, per week, while there is still something to do about them.
Can I connect a live card feed to Nimble Property?
No. Nimble Property publishes no public API, so there is no live feed to connect. Transactions come in through its file import, and Vergo automates preparing that file.
What is in Vergo's export file for Nimble Property?
Every card transaction with its date, merchant, amount, and the account and property coding applied in Vergo — structured to match the import format Nimble Property expects, so it loads without reformatting.
Do transactions still need coding after import?
No. Coding happens in Vergo at the point of spend, with rules for recurring hotel vendors. Lines arrive in Nimble Property already distributed.
How often can I run the import?
As often as your close rhythm requires — weekly, monthly, or on demand. Vergo generates the export whenever you need it, and you control when it loads into Nimble Property.
