Insights · Intercompany

Intercompany

Intercompany and intracompany relationships, with design insights for organizations that run complex flows between commercial and government entities.

November 16, 20269 min readRevTech
Original Whitepaper
View the formatted version

Includes full visual design, diagrams, and callouts.

View formatted version

When a commercial entity builds for a government entity under the same parent, parts, hours and cost move across a legal entity boundary. The transfer price between them falls under FAR Part 31, and the books on both sides have to agree.

At a glance

  • Many A&D and GovCon groups place commercial and government work in separate legal entities. Supply between them becomes an intercompany transaction with compliance rules attached.
  • Intercompany flows sit on a spectrum, from seamless transfers at cost to arm's-length sales at a market price. Where a flow sits decides the documents, the margin and how the government treats the cost.
  • Our Intercompany Work Authorization (IWA) Accelerator creates the sales order, billing, goods receipt and supplier invoice from the authorizing purchase order, priced from actual unit cost in project stock.

Why A&D Separates Commercial and Government Work

Many of the A&D and GovCon groups we work with run more than one legal entity, and the line between them usually follows the customer.

A commercial business sells products at catalog or market prices. A government business holds CAS-covered contracts, forward pricing rates and a DCAA audit calendar. Often a third entity sits beside them: an offshore plant, a shared engineering center or a services company that bills labor to both.

Separate entities keep commercial cost structures out of government cost disclosure, ring-fence classified and export-controlled work, and let both sides run rates that fit their markets.

Rule Commercial side Government side
Price basis Catalog, market or negotiated price Cost incurred under FAR Part 31, plus fee where the contract allows
Cost accounting GAAP and company policy Cost Accounting Standards and a disclosed practice
Oversight External financial audit DCAA audits and DCMA business system reviews
Margin on internal transfers Normal course of business Allowable only under the price exception

The rule behind it: FAR 31.205-26(e). Transfers between divisions, subsidiaries or affiliates under common control are allowable at cost. Price, margin included, is allowable when the selling entity has an established practice of pricing those transfers at other than cost for commercial work, and the item qualifies for an exception from certified cost or pricing data under FAR 15.403-1(b).

Our view is that the transfer price between affiliates should be settled against this rule before the accounting design starts.

Seamless or Arm's Length

At the seamless end, stock moves at cost inside one program with no invoice. At the arm's-length end, the entities deal like independent companies, with a purchase order, a sales order, a price with margin, title transfer and an invoice. Our customers typically run several points on the spectrum at once, sometimes on the same program.

Flow Price Documents Margin
Seamless transfer Cost Stock transfer None
Intercompany at cost Cost incurred Purchase order, sales order, invoice None
Cost plus fee Cost plus percent or fixed fee Purchase order, sales order and invoice, with a fee line Own account, eliminated at consolidation, kept out of allowable cost
Arm's length Catalog or market price Order-to-cash and procure-to-pay Inside the price; allowable under the exception

Where Intercompany Becomes Difficult

The intercompany documents are standard. The design work is keeping both entities, their teams and the government audit trail aligned.

Accounting

  • The trading partner belongs on both sides of the posting so consolidation can eliminate it.
  • Revenue and cost are split by category (part, G&A, fee) onto matching accounts.
  • Cost lands at goods receipt and revenue at billing, so the two sides can close in different periods.

Logistics

  • Project stock on both sides keeps a part pegged to the contract that paid for it.
  • Units on one production order can cost different amounts, so pricing needs unit-level cost.
  • A plant copied from a template can keep the template's customer, which turns a cross-company flow back into an internal one with no error message.

Execution

  • A purchase order on one side has to become a sales order on the right WBS on the other.
  • Rework before delivery has to land on the unit it fixes.
  • Reconciliation waits for month end, when missing documents are traced by hand.

Compliance

  • Transfers are at cost unless the price exception applies, with evidence for the choice.
  • G&A sits on its own line so the receiving entity can treat it under its disclosed practice.
  • Fee is excluded from cost-to-cost revenue, resource-related billing and allowable cost reporting.

Field Notes From Our Customers

Work authorization between business units. An authorizing business unit buys builds from a performing business unit under the same parent. The invoice price comes from the cost on the unit: material, labor and overhead burden, with G&A on its own line. Our recommendation: give the unit its own cost object, or a pegged requirement on the posting, before pricing it.

Offshore manufacturing feeding US government contracts. An offshore plant in a separate entity and currency ships parts to a US entity that consumes them on government contracts, with a markup in the transfer price. We posted the markup on its own account on the receiving contract WBS, excluded from cost-to-cost and allowable reporting and eliminated at consolidation. Our recommendation: decide where the markup posts before parts ship.

Shared workforce across company codes. An employee is paid by one company code and works on projects owned by another. The activity allocation between the home and sender cost centers crosses company codes and posts the intercompany entry. Our recommendation: settle which entity owns the employee and which owns the hours before time entry goes into production.

SAP Design Considerations

The decisions below are specific to SAP S/4HANA. Several are difficult to change after go-live, so we would settle them during design.

Design area What to decide Our recommendation
Organizational structure Company code per legal entity, the trading partner on the intercompany customer and supplier, and which plants sell to which company codes. Assign the trading partner in the business partner master for the intercompany customer and supplier, so it reaches the postings without manual entry.
Document flow A cross-company stock transport order, or a purchase order on the authorizing side and a sales order on the performing side. Use a purchase order and sales order linked to the unit WBS for contract-specific parts. A stock transport order fits replenishment that is not tied to a contract.
Project stock Valuated or non-valuated project stock, and whether the receiving purchase order is account assigned to project stock or to the WBS as cost. Valuated project stock where the part is pegged to a contract, so the inventory value is tracked against the WBS that owns it.
Pricing Standard intercompany pricing reads condition records (PI01 and PI02 in the standard procedure). Cost-based transfers need the actual cost of the unit, which sits on the WBS. Keep condition records for catalog transfers. For cost-based transfers, price from WBS actual cost, with G&A and fee on separate conditions.
Billing and supplier invoice Intercompany billing (billing type IV), and whether the supplier invoice is keyed, created through EDI output or created by automation. Create the supplier invoice from the intercompany billing document with the same reference, so both sides reconcile on one key.
Accounts and cost elements Revenue and cost accounts for part, G&A and fee, mapped to the receiving entity's disclosed practice. Post fee to its own account on the receiving side, so it can be excluded from cost-to-cost progress, results analysis and allowable cost reporting.
Group valuation Legal valuation only, or group and profit center valuation in the Material Ledger to remove intercompany margin from inventory. Decide during design. Parallel valuation is difficult to add after go-live, and without it the margin in inventory is removed by a manual consolidation entry.
Close and reconciliation How performing revenue is matched to authorizing cost, and how timing differences between goods receipt and billing are handled. Reconcile by purchase order and cost category before the consolidation run, using the intercompany matching and reconciliation apps in S/4HANA.
Clean core Custom code in the order, billing and invoice path, or extensions built on released APIs. Build automation on released APIs and standard documents, so upgrades and the audit trail follow the standard.

The Intercompany Work Authorization (IWA) Accelerator

An authorizing company code issues a purchase order, and a performing company code builds in project stock and bills back its actual cost. IWA creates the documents between them inside S/4HANA from that purchase order.

  1. Order. The authorizing purchase order creates the intercompany sales order on the performing side, on the unit WBS in project stock, with a provisional price.
  2. Price. After goods issue, IWA prices the delivered unit from the cost on its WBS and splits it into categories: part, G&A and fee.
  3. Bill. Billing posts revenue per category to its own G/L, tagged with the trading partner.
  4. Receive. The billing document updates the purchase order, posts the goods receipt and creates the supplier invoice with the billing number as reference.
  5. Reconcile. The IC Document Monitor matches performing revenue to the authorizing invoice, per purchase order and category.

IWA supports cost, firm fixed price and catalog arrangements; pricing from actual cost on the unit WBS, cost stamped to the pegged delivery, or standard condition records; and a transfer pricing fee as a percent, fixed per unit, fixed per bill, or percent with a cap, floor or range, posted to its own account for elimination at consolidation.

Questions to Answer Before You Automate

  • Which entities trade with one another, in which direction, and for what?
  • Is the flow at cost or at price? If at price, where is the evidence for the exception under FAR 31.205-26(e)?
  • Does the unit need its own cost, or does the contract?
  • Where does the transferred cost land on the receiving side? Map material, labor, burdens, G&A and any fee or markup to accounts and cost elements that fit the receiving entity's disclosed practice.
  • How will consolidation find and eliminate the margin?

See IWA run in S/4HANA. We walk a purchase order through the sales order, billing, goods receipt and supplier invoice in project stock, then review the monitor and the reconciliation with your team. Book a walkthrough.

This post reflects the perspective of Revelation Technologies as of November 2026. It is not legal, tax or accounting advice.

IntercompanyGovConSAP
Share on LinkedIn
Ready When You Are

Ready to transform your SAP landscape?

Let's discuss how RevTech can accelerate your mission, whether you're scoping a Greenfield S/4HANA build, modernizing a legacy estate, or planning your AI roadmap.