Multi-entity and cross-border
Keep revenue accurate across every entity and country
Each entity bills in its own currency, under its own rules, on its own systems. xfactrs checks contracts, invoices and revenue data across all of them, so one number holds up under ASC 606 and IFRS 15.
This is for you if
- You bill customers from more than one legal entity or country
- You report under ASC 606 and IFRS 15, or will soon
- Local rules like e-invoicing are adding steps to how you bill
See where your entities disagree
Tell us how you're set up. We'll show you where contracts and invoices don't match across entities, with the dollar amount and root cause.
- Read-only access
- SOC 2 Type II
- No system changes
We have your message.
Thanks for reaching out. Someone from our team will get back to you shortly.
The problem
One customer. Several entities. Several versions of the truth.
A global deal is signed once, then split across entities, currencies and billing systems. Each piece looks right on its own. Together, they often don't add up to the contract.
Then reporting asks for the same revenue two ways, under ASC 606 and IFRS 15, and local rules add their own invoice requirements. Every handoff is a place for revenue to slip.
Each entity adds handoffs on top of that baseline. The risk grows with every country you add.
Where it breaks
Six places revenue goes missing between entities
None of these show up in one entity's books. All of them show up when you consolidate.
01
Contracts split the wrong way
A global deal billed twice by two entities, or by neither, because each assumed the other had it.
02
FX applied the wrong way
Spot rates where the contract fixed a rate, or rates that were never updated.
03
Terms that stay in one entity
Uplifts, credits and renewal changes applied in one entity and missed in another.
04
Intercompany charges that don't tie
What one entity charges another doesn't match what the customer actually paid.
05
Invoices held up by local rules
E-invoicing and local invoice requirements that delay or reject invoices, and the cash behind them.
06
Two standards, two answers
ASC 606 and IFRS 15 numbers built from data that doesn't agree to begin with.
How xfactrs works
One set of revenue checks across every entity
Connect every entity
One view across entities
We connect read-only to billing, CRM and ERP in each entity. Ray, our AI agent, lines up every global contract with each invoice issued under it, in every currency.
Every billing cycle
Check each piece
500+ control points check entity splits, FX, contract terms and intercompany charges. Every finding comes with a dollar value and a root cause.
Close and reporting
Report once, both ways
ASC 606 and IFRS 15 reporting start from the same checked data, with fewer manual adjustments at close.
xfactrs sits on top of your billing, CRM and ERP. It doesn't replace them. Each entity keeps its systems and local process. We add the check that they agree.
Proof
$20.4M
in revenue protected every year
That is what one xfactrs client protects each year with continuous checks across quote-to-cash. The same controls run across every entity and currency you bill from.
See client storiesWhat changes
What changes for your team
CFO
One revenue number, globally
Consolidated revenue that ties back to contracts in every entity.
Controller and CAO
A faster multi-entity close
Fewer intercompany and FX adjustments, with 70% faster reconciliation.
Internal Audit
Controls that cross borders
The same revenue checks in every entity, with an evidence trail behind every finding.
Tax and compliance
Cleaner inputs for local rules
Invoices that match the contract before they go into e-invoicing and local filings.
Questions
Before you start
Anything else? We're happy to walk through your entity setup.
Talk to the teamWhen should we start?
Before you add the next entity or country. If you're already multi-entity, start with the entities that bill the most cross-border contracts.
Does xfactrs work with both ASC 606 and IFRS 15?
xfactrs checks that contract, billing and revenue data agree, so both ASC 606 and IFRS 15 reporting start from the same checked data. Your revenue system still builds the schedules.
Do you need write access to our systems?
No. xfactrs is read-only. Nothing in your CRM, billing or ERP changes.
Does xfactrs submit e-invoices?
No. Your e-invoicing provider handles submission. xfactrs checks that what goes out matches the contract before it does.
Start with one finding.
The 15-Day Challenge connects to billing across your entities, read-only, and brings back one confirmed leak with the dollar amount and root cause.