Skip to content
Finance team reconciling hospitality payments across properties on a unified ledger.

Payment-to-ERP automation

From settlement to your books — automatically.

Juno Financial Suite takes settlements from your acquirers, processes every transaction and commission, reconciles them against what was actually paid out, and posts clean data to your ERP — from bexio and Xero to SAP, Business Central and NetSuite.

Reconciled and posted

Every transaction matched to every payout, then posted to the system you already run — so month-end stops being a manual job.

How it works

Four steps from payout to posted.

01 · Ingest

Settlements in

Juno pulls settlements from your acquirers automatically — every payout, every fee.

02 · Process

Transactions & commissions

Each transaction and commission is processed and enriched, line by line.

03 · Reconcile

Matched to reality

Processed transactions are matched against what was actually settled — and, for enterprise, against your bank statements too.

04 · Post

Into your ERP

Clean, reconciled data flows straight into your financial system. No re-keying.

The Juno pipeline
Acquirers
Settlements & fees
Juno
Process · Reconcile
ERP
Clean, posted data

Capabilities

Everything finance needs between the acquirer and the ledger.

Settlement processing

Ingest settlements from any acquirer and process every transaction and commission, line by line — no manual import, no missing fees.

Reconciliation

Match every processed transaction — integrated or standalone terminal — against what was actually settled. Discrepancies surface automatically.

Post to any ERP

Send reconciled data straight to your financial system, from SME tools to enterprise platforms.

Reporting

Commissions by brand, by transaction, DCC reports, delayed-payout reports and more — the detail finance actually asks for.

Reconciliation

Reconciliation that goes all the way to the bank.

Juno compares every transaction it processed — whether captured through an integrated system or a standalone terminal — against the payments your acquirers actually settled. Mismatches, missing payouts and fee differences surface automatically, before they reach your books.

Standard — transactions vs. settlements

Match what Juno processed against what was settled. Every terminal, integrated or standalone.

Enterprise — three-way reconciliation

Add your bank and financial statements. Juno matches transactions, settlements and statements together — so nothing slips between processing, payout and the bank.

Three-way match
TransactionsMatched
SettlementsMatched
Bank statementMatched
Reconciled by Juno

Post to any ERP

Your numbers, in the system you already run.

Once reconciled, Juno posts clean financial data directly into your ERP — from small-business accounting to enterprise platforms. No exports, no re-keying, no copy-paste at month-end.

bexio
Xero
SAP Business ByDesign
SAP Business One
MS Dynamics 365 Business Central
Oracle NetSuite

…and a growing ecosystem.

Reporting

The full picture, broken down however finance needs it.

A wealth of reports across your payment estate — built for the people who own the numbers.

Commissions by brand

See exactly what each brand or property is costing and earning.

Commissions by transaction

Drill down to the line.

DCC reports

Track Dynamic Currency Conversion (DCC) volume and associated revenue share.

Delayed-payout reports

Flag settlements that haven't arrived on time.

600+
Active payment locations
14
Years in hospitality payments
43
Certified integrations
PCI DSS L1
Security compliance

Close the books with confidence.

See how Juno reconciles every transaction to every payout — and posts it straight to your ERP.

Knowledge

Juno Financial Suite — questions answered

Transactions Settlements Bankstatements Reconciliationmatch & flag discrepancies ERP Standard = transactions + settlements · Enterprise adds bank statements
Transactions, settlements and bank statements feed reconciliation, which posts to the ERP.

Quick facts

Purpose
The suite within Juno that automates the path from acquirer settlement to posted ledger entry — processing, reconciling and posting payment data to the ERP.
Target customers
Hospitality finance teams, from SME operators to enterprise hotel groups.
Inputs
Settlement files and fees from acquirers, and processed transactions from integrated or standalone terminals.
Reconciliation modes
Standard (transactions vs. settlements) and Enterprise three-way (transactions, settlements and bank statements).
Supported ERPs
bexio, Xero, SAP Business ByDesign, SAP Business One, Microsoft Dynamics 365 Business Central, Oracle NetSuite, and a growing ecosystem.
Reporting
Commissions by brand, commissions by transaction, DCC reports, delayed-payout reports.
Deployment model
A suite within Juno; works with payments captured through Juno or through standalone terminals.

Frequently asked questions

What is the Juno Financial Suite?

The Juno Financial Suite is the suite within Juno that automates the financial back office for hospitality payments. It takes the settlements paid out by a property's acquirers, processes each transaction and commission, reconciles those processed transactions against what was actually settled, and posts reconciled data into the ERP. Its purpose is to reduce the manual work between the acquirer and the ledger — importing settlement files, identifying missing fees, and matching payouts by hand at month-end. The Suite handles four stages: ingest settlements, process transactions and commissions, reconcile against what was settled, and post into the financial system. It works with payments captured through the Juno Hospitality Suite or through standalone terminals.

Related: Juno Hospitality Suite, Acquiring

How does Juno reconcile transactions against settlements?

Reconciliation compares the transactions Juno processed against the payments the acquirers settled, and flags mismatches, missing payouts and fee differences. There are two levels. Standard reconciliation is a two-way match — processed transactions against settlements — covering integrated and standalone terminals. Enterprise three-way reconciliation adds the property's bank and financial statements, so transactions, settlements and bank records are matched together — addressing the gap where money can appear settled by the acquirer but be delayed, short-paid or mis-posted before it reaches the bank. 934 offers three-way reconciliation for enterprise estates, where transaction volume and the number of acquirers make a bank-level match worthwhile. Because discrepancies are surfaced rather than discovered later, finance teams can resolve them before close.

Related: Reconciliation, Acquiring

Which ERP systems can Juno post to?

After reconciliation, the Financial Suite posts data into the property's ERP, reducing re-keying at month-end. Supported systems span SME accounting tools through to enterprise platforms: bexio, Xero, SAP Business ByDesign, SAP Business One, Microsoft Dynamics 365 Business Central and Oracle NetSuite, with a growing ecosystem of further connectors. The posted data is reconciled and enriched — transactions matched to settlements, with commissions and fees attributed — so the figures that reach the ledger are already aligned to what was settled.

Related: ERP integration, Juno Hospitality Suite

What reports does the Financial Suite produce?

The Financial Suite produces breakdowns aimed at hospitality finance teams. These include commissions by brand or property, commissions by transaction, DCC reports — covering Dynamic Currency Conversion (DCC) volume and the associated revenue share — and delayed-payout reports that flag settlements not received on time. Because the reporting is built on reconciled data, the figures reflect what was processed and settled. The reporting is aimed at finance controllers and group finance teams rather than operational staff. DCC itself is described under acquiring.

Related: Acquiring, Juno Hospitality Suite

Can the Financial Suite reconcile standalone terminals?

Yes. The Financial Suite reconciles transactions from both integrated systems and standalone terminals. Where a terminal is not connected to the PMS or to Juno's acceptance layer, its transactions can still be matched against the acquirer's settlements, so a property running a mix of integrated and standalone hardware can get a single reconciled view rather than reconciling each device separately. The same two-way or three-way matching applies, and discrepancies surface automatically.

Related: Payment integration, Acquiring