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 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.
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.
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.
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.
Same legal entity, different plant or segment
Separate entities under common control
Cost basis with a transfer pricing fee
Commercial item sold between entities
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.
The steps below follow a part through a cost-based intercompany flow as we typically find it before automation, and what changes with IWA.
Patterns from recent engagements.
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.
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.
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.
The decisions below are specific to SAP S/4HANA. Several are difficult to change after go-live, so we would settle them during design.
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.
Swipe the diagram sideways to follow the flow.
The authorizing purchase order creates the intercompany sales order on the performing side, on the unit WBS in project stock, with a provisional 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.
Billing posts revenue per category to its own G/L, tagged with the trading partner.
The billing document updates the purchase order, posts the goods receipt and creates the supplier invoice with the billing number as reference.
The IC Document Monitor matches performing revenue to the authorizing invoice, per purchase order and category.
IC customer, IC supplier and the account determination between them, maintained in a Fiori configuration app with a built-in check.
Actual cost on the unit WBS, cost stamped to the pegged delivery, or standard condition records.
Choose the arrangement per company code relationship, from at-cost work authorization to firm fixed price and catalog transfers.
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.
Journal entry and project line item reports show the pegged requirement as a readable delivery or sales order item with its text.
Process Now and Retry from the monitor, a rerun-safe background job, and admin, processor and display roles.
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.
We work through these questions with customers before configuring the company code relationships.
Parts, labor and services usually follow different flows.
If at price, where is the evidence for the exception under FAR 31.205-26(e)?
Unit pricing needs a unit cost object or a pegged requirement on the posting.
Map material, labor, burdens, G&A and any fee or markup to accounts and cost elements that fit the receiving entity's disclosed practice.
Trading partner on both sides and the fee on its own account let consolidation eliminate it with a query.
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.