What is the working path for card transactions into Inn-Flow?
Inn-Flow does not publish a public API, so there is no direct feed for a card platform to push transactions through. Card spend gets into Inn-Flow one of two ways: keyed in manually, or loaded through an import. Manual entry means retyping every line from card statements — dates, vendors, amounts, GL coding — for every property. An import posts the same transactions in one batch, so the real work is producing a file Inn-Flow will accept without rework.
Why is a raw card statement export not enough?
Because it carries none of the coding Inn-Flow needs. A statement export has no property assignment, no department, no GL account — just merchant strings and amounts. Someone in accounting turns that into an importable file by hand each month, splitting lines across properties and looking up codes. That spreadsheet stage is where the hours go, and it is the stage Vergo removes.
How does the Vergo workflow get transactions into Inn-Flow?
1. Spend on Vergo cards. Every transaction lands in Vergo as it settles. Cardholders — GMs, chief engineers, department heads — snap the receipt from their phone at purchase.
2. Coding during the month. Each transaction is coded in Vergo to your Inn-Flow structure: property, department, GL account. Rules handle recurring vendors automatically, so most lines code themselves.
3. Export in Inn-Flow's format. Vergo generates a custom-built CSV matched to the import format your Inn-Flow system expects — not a generic template your team has to remap.
4. Import the batch. Your accounting team loads the file into Inn-Flow as a standard import. What used to be days of coding is a review-and-import step measured in minutes.
How does this work for a multi-property group?
The property split happens at the point of spend, not at month-end. Because each card belongs to a person at a property, and coding rules follow that structure, the export arrives already divided the way your Inn-Flow books are organised. Adding a property means issuing cards, not redesigning a spreadsheet. And because Inn-Flow is a hosted platform, the accounting team can run the same import routine for every property from one place — the export carries the property split, so nothing about the process changes as the portfolio grows.
Is this an API sync?
No. Inn-Flow publishes no public API, so no card platform can honestly offer one. This is a file-based integration built to be automatic everywhere except the final import your team runs — which keeps posting control exactly where your controller wants it.
Can card transactions flow into Inn-Flow automatically?
Not by API — Inn-Flow does not publish one. The working path is Vergo's custom-built CSV export, matched to your Inn-Flow import format, which your team loads as a batch. Capture, receipts, and coding are automatic; the import is one deliberate step.
What coding does the export include?
Whatever your Inn-Flow structure uses — property, department, and GL account per line — applied in Vergo during the month, largely by rules, so the file imports without rework.
Who runs the import and how often?
Your accounting team, on whatever cycle suits your close — weekly or monthly. The import itself takes minutes because the batch arrives already coded and formatted.
What happens to receipts?
Cardholders capture them by phone at purchase, and each receipt stays attached to its transaction in Vergo — so backup is there at review time instead of being chased at month-end.
