<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
Intercompany sale and purchase, auto-matched, auto-eliminated, audit-grade.
When entity A sells to entity B, the same transaction generates A's revenue, B's cost, the intercompany payable / receivable pair, the transfer-pricing record and the elimination instruction for consolidation — atomically, in one engine.
Matched documents
Intercompany sale and purchase generated from one transaction — not entered twice, not reconciled at month-end.
Automatic elimination
Elimination journals generated by configuration at the right consolidation level. The group P&L excludes the internal margin.
Transfer-pricing record
Method, comparable, justification — preserved with the transaction. The transfer-pricing audit becomes a query.
Real-time intercompany position
Every entity's intercompany payable and receivable visible in real time. Year-end reconciliation is a verification, not a reconstruction.
What the intercompany engine covers
Document matching
One operational transaction generates the seller's invoice and the buyer's invoice atomically. Pricing, currency, tax all reconciled at the moment of creation.
Elimination configuration
Per-account-pair elimination rules: revenue eliminates against cost, intercompany AR against intercompany AP, intercompany inventory profit deferred. Auditor-reviewable configuration.
Transfer pricing
Per-relationship transfer-pricing method (CUP, resale-minus, cost-plus, TNMM, profit-split) with documentation of comparables and justification.
Cross-currency
Intercompany flows in any currency pair. FX-related differences settled to a configured account; the audit trail preserves the original transaction currency.
Netting
Configurable intercompany netting cycles reduce the bank ticket while preserving every underlying transaction for audit.
Position monitoring
Real-time intercompany positions by entity-pair, by currency, by counterparty. Reconciliation breaks surface immediately, not at month-end.
Why "one transaction generates two views" matters
The classic intercompany failure mode is that entity A records the sale today, entity B records the purchase next week, the engine reconciles them in a month-end run, and the discrepancies become the controller's weekend.
Axional creates both views from one transaction at the moment of creation. The intercompany AR on A and the intercompany AP on B are the same number, in the same currency, posted in the same minute. Reconciliation is verification, not reconstruction.