Skip to content
934 logo
An accounting team posting financial entries in a hotel back office.
ERP Integration

Turn payments into accounting.

ERP integration turns reconciled payment activity into correct entries in your system of financial record. Operations data — a room sold, a card charged, a fee deducted — becomes accounting data: debits and credits against the right accounts, in the right entity, with the right tax treatment. It is what closes the financial loop.

See it in the product
Operations become accounting

The translation from what happened to how it is booked.

A payment is an operational event. The ledger needs it as a balanced accounting entry — revenue here, fees there, tax separated, money-in-transit held until it funds. ERP integration depends on reconciliation having already matched transactions across the acquirer, the PMS or POS and the ERP itself, so what posts is a reconciled figure rather than a raw feed — the mapping that makes the translation correct, repeatable and auditable across every property.

How it flows

The elements involved.

RECONCILEDACCOUNT MAPPINGJOURNAL ENTRIESGENERAL LEDGERTransactionsmatched · explainedMapping rulesby type · methodRevenuePayment feesTax / VATClearingGL — Entity AGL — Entity BGL — Entity CReal-time or batched · API · OData · SOAP · file-based
01
General ledger and chart of accounts
The structure every figure must map into.
02
Journal entries
Debits and credits for revenue, payment fees, settlement, FX and tax.
03
Account mapping
Rules translating each transaction type and payment method into the correct ledger accounts.
04
Revenue recognition
When and how revenue is booked, which may differ from when payment is taken (deposits, advance bookings, deferred revenue).
05
Tax / VAT handling
Correct jurisdiction, rate and split, so tax is booked separately from net revenue.
06
Clearing / suspense accounts
A holding account that records money in transit and nets to zero once funds arrive — the accounting mirror of the settlement gap.
07
Multi-entity / multi-property
Separate books per legal entity or property, posted from one shared flow.
08
Posting mechanics
How entries reach the ERP (API, OData, SOAP, file-based) and whether posting is real-time or batched.
09
Period close and audit
Each period complete, balanced and traceable to source transactions.
Why it matters

By hand, this stage is slow, error-prone and impossible to scale across a portfolio. Automated and correctly mapped, every accepted payment flows through to an accurate, auditable ledger entry without re-keying — and the same logic holds whether a group runs five properties or five hundred.

Glossary

Key terms.

General ledger (GL)
the core accounting record.
Chart of accounts
the account structure.
Journal entry
a balanced set of debits and credits.
Clearing account
a transit account that nets to zero on funding.
Revenue recognition
the rules for when revenue is booked.
Posting
writing entries into the ERP.

Close the financial loop.

ERP integration is the last link — reconciled activity, posted as correct, auditable entries. Talk to our team about your accounting stack, or see how mapping and posting work inside the platform.

Juno Financial Suite

In summary

ERP Integration — the essentials

Quick facts

Supported ERPs
bexio, Xero, SAP Business ByDesign, SAP Business One, Microsoft Dynamics 365 Business Central and Oracle NetSuite, with further connectors on the roadmap.
What's posted
Reconciled transactions and settlements, with commissions and fees attributed.
Delivery
Delivered by the Juno Financial Suite, downstream of reconciliation.

Related on 934

Continue exploring

Product

Adjacent solutions

Operating guidance

See it live

Systems it works with

  • Integrations

    The source systems the posted financial record is built from.

Knowledge

ERP Integration — questions answered

Which ERPs does Juno post to?

The Juno Financial Suite posts into a set of ERPs that spans SME accounting through to enterprise finance platforms: bexio, Xero, SAP Business ByDesign, SAP Business One, Microsoft Dynamics 365 Business Central and Oracle NetSuite. The connector list is added to over time as customer demand and operational fit warrant it — the platform is not fixed to a single ERP family.

Related: Juno Financial Suite

What is posted — transactions or settlements?

Both, depending on how the property runs its ledger. Some finance teams prefer transaction-level detail landing in the ERP; others prefer settlement-level posting with transaction detail available in the Financial Suite for drill-down. Juno supports either — and can support both simultaneously where the estate needs it. Because posting happens downstream of reconciliation, whichever level is posted is already matched against what was settled.

How is the GL mapping configured?

The mapping between Juno's reconciliation output and the property's chart of accounts is configured during onboarding, per entity in the estate. Fees, commissions and DCC revenue lines are mapped to the accounts finance expects to see them in, so the ledger entries produced by Juno match the accounting policy already in place at the property.

How often does Juno post?

Posting cadence is configured per estate. Most customers post daily so the ledger stays in step with settlement activity, but weekly and month-end postings are also supported where that matches the finance team's close cycle. The cadence is not fixed by the ERP — it is set to the operating rhythm the customer wants.

What happens when a posting fails?

Failed postings — for example an ERP outage, a GL account that has been renamed on the customer side, or a validation error from the ERP — are flagged and retried automatically on a defined schedule. Where a posting cannot be retried without human input, the exception is raised so the customer's finance team, or the 934 team on a Services subscription, can resolve it before month-end close.

Related: 934 Services