Why is file import the way into NewStar?
NewStar publishes no public API or developer documentation, so no card platform can push transactions into it directly. Spend reaches NewStar the way the system supports: as an imported file. The job is producing a file NewStar's importer accepts first time, with job-cost coding already on every line.
What does the manual version look like for a homebuilder?
Without tooling, the accounting team downloads card statements, works through each charge in a spreadsheet — which job, which cost code — chases superintendents for receipts weeks after the purchase, reshapes columns to what NewStar's importer expects, and uploads. Uncoded field spend is the recurring problem: by month-end, nobody remembers which lot the lumber run was for.
How does Vergo automate the import?
Vergo moves the coding to the point of purchase and removes every step except the upload. Field staff spend on Vergo cards; the transaction is captured instantly and coded from their phone — job, cost code, category — with the receipt photographed on the spot. Vergo then generates a custom-built CSV export matched to NewStar's import format. Your accounting team downloads it and imports it into NewStar. No re-keying, no end-of-month coding interviews, and no pretence of an API sync — NewStar publishes none, and the matched file does not need one.
What lands in NewStar?
Each transaction arrives as an importable line — date, amount, vendor, job, and cost code — while receipts stay attached to the transaction in Vergo as the audit trail. Job costs land exactly where they belong, from an upload that takes minutes.
What does setup involve for a builder?
A one-time exercise. Vergo matches its export to the import format your NewStar installation expects, and your jobs and cost codes are reflected in Vergo so field staff code purchases against the same structure your job-cost reports use. Nothing is required from Constellation and nothing is installed alongside NewStar — the file is the interface, which is the point for an ERP with no published API. From then on the rhythm holds: field spend on Vergo cards, job and cost code applied at the point of purchase, receipts photographed on the spot, and a matched CSV imported by accounting on your cadence. Verify the first import against a handful of known purchases; after that the file shape is proven and current job costs stop waiting for month-end.
Can I connect a card feed directly to NewStar?
No — NewStar publishes no public API. Card transactions come in by file import, and Vergo's custom CSV exports are matched to NewStar's import format.
Do transactions arrive coded to jobs and cost codes?
Yes. Field staff code each purchase in Vergo at the point of sale, so the exported file carries job and cost-code detail on every line.
How often should we import into NewStar?
Whenever fits your close — weekly keeps job costs current, and the export is available on demand. The import itself takes minutes.
Where do receipts go?
They are photographed at purchase and stay attached to each transaction in Vergo, giving you a searchable audit trail alongside the entries imported into NewStar.
