Juno Spend Account

The Juno Spend Account is a dedicated bank account for paying for all guest travel and expenses.

Like a traditional business bank account, you can move money in and out of the Juno Spend Account at any time, and funds are FDIC insured. Juno partners with Stripe Payments Company for money transmission services, with funds held at Fifth Third Bank N.A., Member FDIC.

Unlike a traditional account, every transaction is automatically categorized and enriched with travel and expense data, policy compliance data, and your configured custom fields (e.g., cost center, department).

This enables a consolidated, fully reconciled monthly statement, reducing the time required to book transactions in your accounting system.

How It Works

Onboarding

During onboarding, we collect basic compliance data to meet banking partner requirements.

Funding

Once your account is opened, transfer an initial balance into your JSA to start purchases.

Paying Vendors

As travelers make in-policy purchases and submit approved expenses, Juno pays vendors, reimburses expenses, and maintains a complete data trail.

Reconciling

Each month, you receive a fully reconciled statement for travel and expense transactions, plus a transaction-level CSV for journal entries.

Topping Up

Each month, top up your JSA via bank transfer to continue purchases and reimbursements.

Behind the Scenes: How Vendors and Guests Get Paid

For airline and hotel purchases, Juno generates single-use virtual cards for each purchase made on the Juno platform. These cards are transmitted directly to the respective vendors, so travelers don’t need to pay out of pocket for these expenses.

For Uber vouchers, your spend account will be billed directly by Uber via an ACH draw for each voucher.

For approved guest out-of-pocket expenses, Juno will handle reimbursement to your guests via their preferred method, including ACH transfers, a mailed check, and other international money movement options. Once guests have been reimbursed, Juno will debit the funds from your spend account.

Automated Reconciliation

Juno helps streamline the monthly reconciliation of your JSA purchases and expenses by automatically tracking transactions and generating unified reports. Juno tracks and reports on several types of travel-related financial data:

This page describes reconciliation for the Juno Spend Account. If your organization also pays for guest travel with credit cards, each credit card has its own per-card transaction history, CSV export, and (when Juno is the merchant of record) downloadable receipts. Credit card transactions are not included in the JSA monthly statement.

Booking Data

Flight reservations and changes
Hotel bookings and payments
Ground transportation (Uber vouchers)
Cancellations and refunds

Policy Data

Policy compliance flags
Approval details

Approval notes in invoice transaction CSVs

Invoice transaction CSVs include an Approval Notes column so you can see why an exception was approved. It contains internal notes from the linked booking or expense’s latest request only when that request is approved, either manually or automatically. Missing or blank notes, or a latest request that is pending, denied, or canceled, leave the column blank; guest-facing reasons are not substituted.

If one payout row covers multiple expenses, its cell combines the distinct notes from those expenses’ approved requests. These notes appear in the CSV export, not the invoice PDF.

Expense Data

Receipt uploads and AI-parsed information
Expense categorization and amounts

Payment Information

Virtual card transactions for flights and hotels
Ground transportation invoices
Traveler reimbursements

Reimbursement Currency Details

For reimbursement payout rows, the invoice PDF and transaction CSV include the original requested amount and currency, the approved expense value, and the expense-date reference conversion. They also show the amount and currency sent to the guest, the Wise rate when applicable, and the USD amount charged to your organization. Use these values together to reconcile what the guest submitted, what they received, and what your organization paid.

The USD amount charged to your organization is recorded when the reimbursement is funded, along with any applicable processing fee, and it isn’t recalculated when Juno later collects it. It’s based on what Juno actually paid out, so it can differ from the expense-date reference conversion, which is shown for comparison only.

Older payouts may not include expense-date reference rates. When that historical conversion evidence is unavailable, the report leaves those details blank instead of calculating them using a current rate.

Refund Credits in the Developer API Transactions Report

This section applies only if your organization reads transactions through the Developer API transactions report. It doesn’t change your monthly statement, transaction CSV, or dashboard views, and it doesn’t change which purchases can be refunded.

When a vendor refunds a purchase, the report shows the refund as its own transaction with positive amounts. The original charge stays in the report unchanged, so the charge and its credit together net to what your organization paid.

Refunds Juno passes back to you. For purchases Juno paid on a Juno virtual card, a refund appears after Juno has credited your organization — to your credit account, your card, or your Juno Spend Account — and after the original charge appears in the report. Its date is the date the vendor issued the refund. It belongs to the same booking and payment method as the original charge.
Refunds on your own Conferma cards. When a vendor refunds a charge it made directly to your organization’s Conferma card, the refund appears with the card issuer’s posting date and statement reference for the credit, without waiting for the original charge.

The credit amount is what your organization received. If part of a refund went back to a guest who paid a share of the booking, that share isn’t included. Refund credits don’t include a processing fee refund.

A refund might not appear in the report yet. For example, the credit to your organization might still be processing, or the original charge might not be in the report yet. These refunds appear automatically once the credit completes and the original charge is reported. Juno doesn’t guess at refunds it can’t match to one original charge, or at refunds that together exceed the original purchase amount before its processing fee (which would mean part of the fee was refunded). Those stay out of the report until they’re reviewed. If a credit is canceled after it’s reported, the reported refund stays in place and Juno reviews it.