US and EU Entities.
One Billing Workflow.
LedgerUp routes each contract to the right legal entity, bills with the right currency, tax treatment, and template, and keeps every entity’s ledger clean — without an ERP rollout.
Entity sprawl vs entity-aware billing
The second legal entity doubles your billing surface area. The third usually breaks the spreadsheet.
Without automation
- Someone decides per-invoice which entity bills — inconsistently
- EU customers invoiced from the US entity with the wrong tax treatment
- Each entity’s books maintained separately, consolidated painfully
- Collections run per-entity, so customers get chased twice — or never
- A full ERP rollout quoted as the only fix
With LedgerUp
- Entity routing rules applied automatically from contract and customer data
- Each entity bills in its currency, with its tax treatment and template
- Invoices post to the right entity’s books — QuickBooks per entity or NetSuite subsidiaries
- Collections coordinated across entities, one customer conversation
- Consolidated AR and aging across all entities, with per-entity drill-down
How multi-entity billing works
From signed contract to the correct entity’s ledger.
Entity determined at contract intake
When Ari reads a signed contract, it applies your routing rules — contracting party named in the agreement, customer region, product line — to assign the billing entity. Ambiguous cases flag for a one-click human decision.
Entity-specific billing applied
The invoice carries the entity’s legal name, address, registration numbers, bank details, currency, and tax treatment. Your EU entity invoices look like EU invoices because they are.
Posted to the right books
Each invoice posts to its entity’s ledger — separate QuickBooks files, NetSuite subsidiaries, or Sage Intacct entities — so per-entity books stay audit-clean without manual re-keying.
Collections and reporting roll up
Reminders and collections run with entity-correct details on every touch, while your team sees one consolidated AR picture: total exposure per customer across entities, aging rolled up and drillable.
Works with your existing stack
LedgerUp connects to the tools you already use — no migration required.
Multi-entity use cases
How multi-entity companies bill with LedgerUp.
US SaaS Adds a European Subsidiary
The classic trigger: EU customers need EU invoices — EUR pricing, VAT handling, local bank details. Ari routes EU contracts to the new entity from day one without disturbing US billing.
A German customer’s contract routes to the Dutch B.V., bills in EUR with reverse-charge VAT notation, and posts to the EU QuickBooks file.
Acquisition Integration
An acquired company’s customers keep their existing billing entity and terms while finance gets one consolidated view — buying time for (or avoiding) a full systems migration.
Acquired customers keep invoices from the acquired entity’s ledger; the consolidated aging report shows both entities the day the deal closes.
One Customer, Multiple Entities
A global customer buying from both your US and EU entities gets coordinated treatment: separate correct invoices, one coherent collections relationship, one view of total exposure.
A customer with $60K open across two entities gets one escalation conversation referencing both — not two parallel dunning tracks.
Multi-entity touches every workflow
Entity-awareness runs through invoicing, collections, and reporting.
Multi-currency billing
The currency half of the multi-entity problem — pricing, invoicing, and reconciling across currencies.
See multi-currency billingAging & ARR reporting
Consolidated AR visibility across entities with per-entity drill-down.
See AR reportingInvoicing
The contract-to-invoice engine that entity routing plugs into.
See invoice automationMulti-entity billing FAQ
Common questions about automating multi-entity billing with LedgerUp.
Do we need a multi-entity ERP like NetSuite for this?
No — that’s the point. LedgerUp handles entity routing and entity-specific billing on top of whatever you run: separate QuickBooks files per entity, NetSuite subsidiaries, or Sage Intacct entities. Teams often adopt this precisely to defer an ERP migration.
How does Ari decide which entity bills a contract?
Routing rules you define, applied to contract and customer data: the contracting party named in the agreement takes precedence, with region, product line, or CRM fields as fallbacks. Contracts that match no rule flag for a human decision, which becomes a new rule if you want it to.
How is tax handled across entities?
Each entity carries its own tax configuration — US sales tax treatment on the US entity, VAT treatment including reverse-charge notation on the EU entity. Ari applies the entity’s configuration per invoice; your tax advisors define the treatment, LedgerUp executes it consistently. See the sales tax automation page for details.
Can customers span entities?
Yes. A customer buying from multiple entities gets correct separate invoices per entity, while collections and exposure reporting treat them as one relationship — so you never run parallel uncoordinated dunning tracks against the same company.
What does consolidated reporting look like?
Total AR, aging, and DSO across all entities in one view, drillable to any single entity for local close and audit. Each entity’s ledger remains independently clean — consolidation happens at the reporting layer, not by mixing books.
How long does multi-entity setup take?
Roughly a week per entity connection, mostly configuration: entity details, ledger connection, routing rules, and templates. Adding a third entity to a working two-entity setup is typically days.