Multi-entity, multi-currency, multi-tax.
AU-HQ distributors almost always have a New Zealand subsidiary, sometimes a Singapore office, occasionally a Pacific Islands line. The billing stack you chose in 2019 probably wasn't built for that shape — and retrofitting multi-entity into it every year is getting expensive.
The questions that eat operator time.
Which entity billed which partner?
Your AU entity holds the Microsoft CSP. Your NZ entity holds the local Dropsuite contract. Partner sees both on one invoice? Two invoices? Consolidated statement? All three are valid — all three are supported.
AU GST or NZ GST?
Reverse-charge, vendor-of-record, zero-rated exports, inter-entity recharges. The platform applies the right tax treatment at the right layer with documentation for the auditor, on both sides of the Tasman.
Which currency at which FX rate?
Vendor bills USD. AU entity reports AUD. NZ entity reports NZD. Partner invoices AUD or NZD. Margin calculations need to be deterministic and reproducible, not "whatever the spot rate was when Jen ran the report".
Which region does the data live in?
AU partners ask; NZ partners ask; government-adjacent partners insist. The platform is AU-primary with scoped residency options for regional tenants.
Built-in, not bolted on.
Entity-scoped ledgers
Every reconciled line carries its entity tag. Close by entity, or close consolidated. Journals post to the right GL per entity automatically.
Cross-entity recharges
Service delivered from AU into NZ and recharged? First-class recharge lines with reverse-charge documentation.
Deterministic FX
FX rate locked at reconciliation time, per line, per entity. Margin reports reconcile to GL, always.
Stop paying consultants to patch multi-entity into a US product.
Show us your entity tree. We'll show you the reconciled close.