Expense management that works with Newstar

Key takeaways

• Vergo reads jobs and cost codes from Newstar, codes every expense by inference, and syncs coded entries back so nothing arrives as an uncoded lump at month end.
• You do not need to change cards — Vergo connects to corporate cards, fuel cards, and personal cards your business already uses.
• Card spend, employee reimbursements and AP invoices run through the same coding model and sync to Newstar the same way.
• Transactions are ready to code the moment they happen, before they clear, and approval workflows can route by GL account, amount, or project.

How the Newstar sync works

Vergo reads jobs and cost codes from Newstar, codes every expense to the right job and cost code, and pushes coded entries back so nothing arrives as an uncoded lump at month end. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into your accounting software. The structure that matters here is jobs and cost codes: every transaction is proposed with both dimensions, and reviewers see the reasoning behind each coding decision. This means your Newstar ledger stays current in real time, and reconciliation at month end confirms what has already been reviewed during the period.

Do you need to change cards?

No. Vergo does not issue cards and never asks you to switch. It connects to the cards your business already holds — corporate cards, fuel cards, personal cards used for reimbursement — and connecting your existing cards involves no card applications, no re-issuing and no banking change. The platform is card-agnostic, which means it works with whatever payment rails your business has chosen for other reasons: rewards programs, banking relationships, or simply the cards already in employees' wallets. Once connected, every transaction from those cards flows into the same coding and approval workflow, regardless of issuer.

What AI-native expense management means for job costing

Rules engines match text patterns; when a transaction does not match, a person codes it by hand. AI-native expense management 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. This applies to jobs and cost codes just as it does to GL accounts: the system learns what kind of expense belongs to which job, and every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. For mid-market construction companies running Newstar, this means the expense layer adapts to the job costing structure already in place, not the other way round.

A practical example

A project manager buys materials on a corporate card. The transaction appears in Vergo the moment it happens, before it clears the bank. Vergo proposes the vendor, GL account, job, and cost code based on the company's accounting history and the structure pulled from Newstar. The coding shows why each dimension was chosen — perhaps the vendor has been used on this job before, or the amount and merchant type match a cost code pattern. A reviewer sees the proposal, confirms it in seconds, and the coded entry syncs into Newstar. At month end, the ledger is already reconciled because every transaction was reviewed and coded in real time.

Do reimbursements and AP invoices work with Newstar too?

Yes — the same coding model handles card spend, employee reimbursements and AP invoices, and all three sync to Newstar the same way. Most tools treat these as separate products with separate coding setups; the same vendor coded two different ways is a reconciliation problem you inherit. When card spend, reimbursements, and invoices run through one coding model, the same vendor is always coded the same way, and reconciliation becomes a confirmation step rather than a detective process. Invoices are captured, coded, approved and synced — payment itself stays on the rails you already use.

How Vergo handles this

Vergo integrates with Newstar and every other ERP and accounting system. It reads your jobs and cost codes, then 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. 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, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into your accounting software. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use. Connecting your existing cards involves no card applications, no re-issuing and no banking change, and employees handle everything by text message — no app to download, no portal login.

Related questions