## TL;DR

SAP document splitting errors on vendor invoice posting mean the line items cannot be split into balanced documents by the splitting characteristics (profit center, segment): some line is missing a required split characteristic or carries an inconsistent one. Check each line for a complete, consistent profit center and segment assignment; the usual culprit is a tax or freight line without one. Fix the derivation rules or the line coding so every line carries valid splitting characteristics, then repost. Splitting is a zero-tolerance check: one bad line blocks the whole document.

## The query

```text
SAP document splitting errors when posting vendor invoices
```

## Use this when

- MIRO or FB60 failing with document splitting errors
- Vendor invoice lines missing profit center
- Splitting characteristics inconsistent on invoice lines

## Not for

- Price or quantity mismatches (tolerance errors, different fix)
- Tax code errors (separate validation)

## Steps

1. Read the full splitting error log to find the offending line and characteristic.
   Expected output: You know exactly which line and which field.
2. Check that line's profit center, segment, and other splitting characteristics.
   Expected output: The gap is visible: missing or inconsistent value.
3. Fix the line coding or the derivation rule that should have populated it.
   Expected output: Every line carries valid characteristics.
4. Pay special attention to tax, freight, and discount lines; they are the usual offenders.
   Expected output: The sneaky lines are covered.
5. Repost and confirm the document splits into balanced documents.
   Expected output: The invoice posts cleanly.

## Variant phrasings

### SAP document splitting error vendor invoice

### MIRO document splitting profit center missing

### FB60 splitting error fix

## Root cause

Document splitting enforces that every accounting document balances per characteristic (profit center, segment) for legal reporting; an unbalanced split would produce financial statements that do not foot. The hard block is intentional, which is why the fix is always in the line data, never in the posting program.

## Edge cases

- New GL splitting must be active and configured; check with your FI lead before changing rules
- Test derivation changes in the QA client; splitting rules are client-wide

## Provenance

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