ERP Sync

ERP Sync exports your revenue-recognition journal entries to your accounting system, so recognized revenue lands in your general ledger without manual re-keying. It is configured as part of Revenue Recognition (Pricing Studio → Revenue Recognition → ERP Sync).

ℹ

ERP Sync moves journal entries, not raw invoices. It's the bridge between Aforo's revenue-recognition schedules and your ledger's chart of accounts.

Supported connectors

ERP	Auth	Format
QuickBooks Online	OAuth 2.0	QBO journal entries
Xero	OAuth 2.0 + PKCE	Xero manual journals
NetSuite	Token-Based Auth (TBA)	NetSuite journal entries
Custom Webhook	HMAC-SHA256 signed	Your format

Connecting an ERP

Go to Pricing Studio → Revenue Recognition → ERP Sync.
Choose your provider and enter its connection config.
Run Test to verify the connection before enabling it.
Set the sync frequency and activate.

ℹ

One ERP configuration is allowed per billing entity — enforced at the database level. A workspace with several billing entities (e.g. a US entity and a UK entity) configures one ERP per entity; there is no separate "multi-ERP" toggle to enable.

Sync frequency

Mode	Behavior
`MANUAL`	Sync only when you trigger it
`DAILY`	Sync once a day on a schedule
`ON_CLOSE`	Sync when a revenue-recognition period is closed

Retry — a failed sync is retried 3 times with exponential backoff.
Manual sync — trigger an export on demand from the ERP Sync panel.

Custom webhook adapter

Send journal entries to any HTTP endpoint in your own format:

Endpoint URL — your receiving webhook URL.
Signing secret — Aforo signs the payload with HMAC-SHA256 so you can verify authenticity.
Connection config — the fields your endpoint needs (headers, mapping) as key/value pairs.

Your endpoint must return 2xx to mark the sync successful; any other response triggers a retry.

Deactivating

Deactivating stops future syncs immediately. Entries already exported remain in your ERP. Reconnect or switch providers at any time by updating the configuration for that billing entity.