Close the Gap Between Xero, Ezidebit, and Your Operations

When an accounting event happens in Xero, your operations system knows about it only if someone manually tells it. When a payment event happens in Ezidebit - a successful collection, a failed debit, a skipped cycle - the team managing the operational side finds out through manual reconciliation, if they find out at all. And when a subscription contract changes in your operational system, neither Xero nor Ezidebit updates automatically.

These disconnects are structural. They're not the result of poor processes or careless staff - they're what happens when three systems that each manage a critical piece of the business have no awareness of each other. The result is revenue that leaks silently: invoices that aren't generated when they should be, collection schedules that don't reflect current contract terms, failed payments that sit unresolved because nobody was notified in time.

Petriko closes this gap by making the operational domain the authoritative source that drives both Xero and Ezidebit - not just alongside them.

Xero Integration - Events Become Invoices

Every subscription lifecycle event in Petriko has a corresponding financial consequence. Activation generates an invoice. Renewal generates an invoice. A change in subscription terms triggers the appropriate financial adjustment. These aren't manual steps - they're automatic, triggered by operational events in the system.

The integration handles multi-organisation complexity from the start. Two separate Xero organisations, each mapped to its own franchise entity. When a subscription event occurs, Petriko routes the resulting invoice to the correct Xero organisation based on which entity the subscription belongs to. Invoices are attributed correctly at the point of generation - not corrected after the fact at month-end reconciliation.

For businesses with complex entity structures, this is significant. The accounting in Xero is accurate not because someone cross-checked it against the operational system, but because the two systems are wired together at the event level.

The integration status is visible in the admin panel - connection health for each Xero organisation is surfaced in real time, not discovered when an invoice fails to generate.

Ezidebit Integration - Contracts Become Collections

Every subscription in Petriko maps to an Ezidebit direct debit agreement. The collection schedule reflects the subscription terms: weekly, fortnightly, or monthly - whatever the contract specifies. When subscription terms change, the Ezidebit schedule updates.

Two Ezidebit accounts - one per franchise entity - with collections attributed to the correct account based on entity. This is not a filter or a label applied after the fact. It's architectural: Petriko routes collection events to the correct Ezidebit account at the point of scheduling.

When a payment fails, the failure state is immediately visible in the operational view. The arrears screen shows which subscriptions have outstanding collections, what the failure reason was, and how long the balance has been outstanding. The information flows to the people who can act on it - without requiring manual reconciliation or a separate Ezidebit login.

A Unified Payment View

Every collection event from Ezidebit surfaces in the payment records view, linked to the subscription and customer it belongs to. This is not a data export or a periodic sync - it's a continuous, operational view of payment state.

The payment history for any customer is available directly from their profile. The collection history for any subscription is available from the subscription detail. Financial state and operational state are in sync because they share the same underlying event stream, not because someone exported and imported data between systems.

The Goal Is Not Replacement

Xero is the right tool for accounting. Ezidebit is the right tool for direct debit. The goal of the Petriko integration layer is not to replace either - it's to make each system aware of the operational domain, so that when something changes in the business, the financial and payment systems reflect it automatically.

When a new subscription activates, Xero knows. When a contract is renewed, Ezidebit's schedule updates. When a payment fails, the operations team knows immediately. The gap between systems closes - and with it, the silent revenue leakage that fills that gap.