## TL;DR

In OneWorld accounts, every bill line must belong to the header subsidiary; lines coded to another subsidiary fail validation. Determine the correct subsidiary from the ship-to location or cost center owner before import, and split cross-subsidiary invoices into separate bills per subsidiary with intercompany handling where needed.

## Error

```text
Subsidiary mismatch: line subsidiary 2 does not match header subsidiary 1
```

## Steps

1. Identify the owning subsidiary for each line from location or cost center.
   Expected: A subsidiary per line.
2. Group lines by subsidiary.
   Expected: Clean groups.
3. Create one bill per subsidiary.
   Expected: Valid bills.
4. Handle intercompany settlement per company policy.
   Expected: Correct accounting.
5. Add a pre-import subsidiary check.
   Expected: The error stops recurring.

## When to use

- OneWorld multi-subsidiary bills
- Cross-subsidiary cost allocations
- Shared-service invoices

## When not to use

- Single-subsidiary accounts
- Location or department errors
- Non-NetSuite ERPs

## Compatibility

NetSuite OneWorld.

## Variant phrasings

### subsidiary mismatch vendor bill

### line subsidiary header subsidiary

### OneWorld bill subsidiary error

## Root cause

Subsidiaries are separate accounting entities. A single vendor invoice spanning entities cannot post as one bill; the validation enforces entity boundaries.

## Edge cases

- Elimination subsidiaries need special handling; consult accounting
- Tax nexus follows the subsidiary; recheck tax on split bills
- Vendor records are per-subsidiary; the vendor must exist on each

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_DuFjkQUp3YqsJVKUqf6m5w