Revelation Technologies Insights  /  Intercompany
Insights · Intercompany in A&D and GovCon

Intercompany

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

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.

Revelation TechnologiesNovember 2026
Commercial entity and government entity on either side of a legal entity boundary The government entity sends a purchase order across the boundary. The commercial entity sends parts in project stock and an invoice with the trading partner back. Commercial entity Builds the part Catalog or market pricing Commercial cost structure GAAP and company policy Project stock per order Seller Government entity Uses it on contract CAS-covered contracts FAR Part 31 allowability DCAA and DCMA oversight Cost traced to the unit Buyer Legal entity boundary Purchase order Parts + delivery Invoice + trading partner
The purchase order, the delivery and the invoice cross the legal entity boundary.
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.
The bifurcation

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.

In operations, a part that one plant used to hand to the next is now bought and sold between companies.

A parent group with a commercial entity, a government entity and a shared or offshore entity, trading parts and labor Parent group Consolidated books Commercial Products at market price Commercial cost structure Government CAS-covered contracts Disclosed practice, DCAA Shared or offshore Plant, labor, engineering Bills both sides Parts at cost or price Labor and engineering
A typical A&D group structure, with intercompany flows between the entities.
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.

The spectrum

Seamless or Arm's Length

We place intercompany flows on a spectrum.

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.

Seamless transfer

Same legal entity, different plant or segment

What moves
Stock and its cost, inside project stock
Price
Cost
Documents
Stock transfer
Margin
None

Intercompany at cost

Separate entities under common control

What moves
Parts plus actual cost with burden and G&A
Price
Cost incurred
Documents
Purchase order, sales order, invoice
Margin
None

Cost plus fee

Cost basis with a transfer pricing fee

What moves
Parts, cost and a fee line
Price
Cost plus percent or fixed fee
Documents
Purchase order, sales order and invoice, with a fee line
Margin
Own account, eliminated at consolidation, kept out of allowable cost

Arm's length

Commercial item sold between entities

What moves
Product and title
Price
Catalog or market price
Documents
Order-to-cash and procure-to-pay
Margin
Inside the price; allowable under the exception
The complexity

Where Intercompany Becomes Difficult

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

These issues come up on our engagements, grouped by the team closest to them.

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.
  • Once a sales order item is partly billed, its price is hard to change. Corrections become cancel and rebill.

Logistics

  • Project stock on both sides keeps a part pegged to the contract that paid for it.
  • Cross-company delivery, goods issue and goods receipt post in sequence across company codes.
  • 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.
  • The handoff between the authorizing and performing teams runs on email.
  • 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.
  • The audit trail runs from the government invoice back to the unit and the intercompany document.
The handoffs

Following a Part Between Entities

The steps below follow a part through a cost-based intercompany flow as we typically find it before automation, and what changes with IWA.

StepWhat happensTodayWith IWA
01Authorizing entity raises a purchase order to its sibling companyAuthorizing entityToday: ManualWith IWA: Unchanged
02Someone rekeys it as a sales order and picks the WBS and pricePerforming entityToday: RekeyedWith IWA: Automatic
03Build in project stock, deliver and post goods issuePerforming entityToday: StandardWith IWA: Unchanged
04Pull actual cost per unit, add burden and G&A in a spreadsheetPerforming entityToday: SpreadsheetWith IWA: Automatic
05Bill, with revenue split by category by handPerforming entityToday: ManualWith IWA: Automatic
06Update the purchase order price and post the goods receiptAuthorizing entityToday: ManualWith IWA: Automatic
07Key the supplier invoice and match it to the billing numberAuthorizing entityToday: RekeyedWith IWA: Automatic
08Reconcile both sides by category before consolidationBoth entitiesToday: Month endWith IWA: Monitor
From the field

Field Notes From Our Customers

Patterns from recent engagements.

Intercompany at costDefense primeProject stock

Work authorization between business units

An authorizing business unit buys builds from a performing business unit under the same parent. The performing side builds the units in project stock, pegged to the authorizing contract.

The invoice price comes from the cost on that unit: material, labor and overhead burden, with G&A on its own line. When a unit needed rework before delivery, the rework order was pegged to that unit, which raised its price and left the other units unchanged.

Our recommendationGive the unit its own cost object, or a pegged requirement on the posting, before pricing it.

Invoice price per delivered unit · lab illustration
Unit 1Delivered
Unit 2Reworked before delivery
Unit 3Delivered
Material, labor, burdenRework pegged to unit 2
Cost plus markupAerospace manufacturerCross-currency

Offshore manufacturing feeding US government contracts

A manufacturer builds parts at an offshore plant in a separate entity and currency, then ships them to a US entity that consumes them on government contracts. The transfer price includes a markup.

We posted the markup on its own account on the receiving contract WBS. The markup follows the part, is excluded from cost-to-cost and allowable reporting, and is eliminated at consolidation, with no separate offset WBS to reconcile.

Our recommendationDecide where the markup posts before parts ship. A separate account on the contract is simpler to trace and audit than a holding WBS.

Where the transfer price lands
Offshore entityBuilds the part, local currency
US entityContract WBS, USD
Part cost to the material cost account, allowable
Markup to its own account on the same WBS, excluded and eliminated
Seamless laborDefense electronicsTimesheets

Shared workforce across company codes

An employee is paid by one company code and works on projects owned by another. Hours are recorded against the performing entity's projects, and the activity allocation between the home cost center and the sender cost center crosses company codes and posts the intercompany entry.

Our recommendationTreat shared labor as an intercompany flow, and settle which entity owns the employee and which owns the hours before time entry goes into production.

Cross-company labor
Home company codePays the employee
Performing company codeOwns the project
Hours recorded on the performing project
Activity allocation credits the home cost center across company codes
In SAP S/4HANA

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
Hard to change after go-live
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
Hard to change after go-live
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
Hard to change after go-live
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.
RevTech Intercompany Work Authorization (IWA) Accelerator

The Purchase Order Starts the Process

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.

IWA intercompany flow across the authorizing and performing entities The purchase order creates the intercompany sales order on the unit WBS. The performing entity builds and delivers, IWA prices from unit cost and bills per category. Billing updates the purchase order, posts the goods receipt and creates the supplier invoice. Reconciliation runs per purchase order and category. Authorizing entity · buyer Performing entity · seller Shaded boxes are created or updated by IWA Trading partner boundary Purchase order to the IC supplier PO updated price + G&A line Goods receipt cost by category Supplier invoice ref = billing no. IC sales order unit WBS, project stock Build + ship goods issue Price per unit actual cost split Billing revenue per category Order Price Bill Receive Reconcile performing revenue vs authorizing invoice, per purchase order and cost category OK Difference Open

Swipe the diagram sideways to follow the flow.

01Order

The authorizing purchase order creates the intercompany sales order on the performing side, on the unit WBS in project stock, with a provisional price.

02Price

After goods issue, IWA prices the delivered unit from the cost on its WBS and splits it into categories: part, G&A and fee.

03Bill

Billing posts revenue per category to its own G/L, tagged with the trading partner.

04Receive

The billing document updates the purchase order, posts the goods receipt and creates the supplier invoice with the billing number as reference.

05Reconcile

The IC Document Monitor matches performing revenue to the authorizing invoice, per purchase order and category.

Configured per Company Code Relationship

IC customer, IC supplier and the account determination between them, maintained in a Fiori configuration app with a built-in check.

Pricing strategies

Actual cost on the unit WBS, cost stamped to the pegged delivery, or standard condition records.

Cost, fixed price or catalog

Choose the arrangement per company code relationship, from at-cost work authorization to firm fixed price and catalog transfers.

Transfer pricing fee

Percent, fixed per unit, fixed per bill, or percent with a cap, floor or range. It posts to its own account for elimination at consolidation.

Readable top-level item

Journal entry and project line item reports show the pegged requirement as a readable delivery or sales order item with its text.

Monitor and control

Process Now and Retry from the monitor, a rerun-safe background job, and admin, processor and display roles.

How one unit price is built · illustrative mix

Unit price split by cost category

Category
Performing side
Authorizing side
Part
Part revenue G/L
Part cost on the PO line
G&A
G&A revenue G/L
Own PO line and cost G/L
Fee
Fee revenue account
Fee cost account
Fee stays on its own accounts on both sides, so consolidation eliminates it and allowable cost reporting excludes it.
A document flow from our S/4HANA lab

Reconciled per cost category

Purchase orderEntered by buyerauthorizing
Sales orderCreated by IWAperforming
BillingPart and G&A linesperforming
Goods receiptPosted by IWAauthorizing
Supplier inv.Created by IWAauthorizing
PartRevenue matches invoiceOK G&ARevenue matches invoiceOK

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.

Before you automate

Questions to Answer Before You Automate

We work through these questions with customers before configuring the company code relationships.

Which entities trade with one another, in which direction, and for what?

Parts, labor and services usually follow different flows.

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?

Unit pricing needs a unit cost object or a pegged requirement on the posting.

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?

Trading partner on both sides and the fee on its own account let consolidation eliminate it with a query.

Revelation Technologies

Talk to Us About Your Intercompany Flows

We build intercompany, project stock and GovCon cost flows for A&D companies. Start with a walkthrough of IWA, or a working session on your own entity map.