## TL;DR
When the ERP says unbalanced but shows no line detail, total the entry outside the ERP. Export the journal lines to a spreadsheet, sum debits and credits at full precision, and look for the usual three causes: a line rounded to zero, a foreign-currency line converted at entry level, or a duplicated header amount. Fix that line and resubmit; do not rebalance by editing the largest line.

```text
"unbalanced journal entry" rejected by the ERP with no line-level error detail
```

## Use this when
- Journal submission fails as unbalanced and the error dialog names no line.
- The entry was built by import, copy, or allocation rather than typed by hand.
- Displayed line totals look equal, so the imbalance is below display precision or in a hidden line.

## Not for this skill when
- The journal is blocked for a closed period, missing approval, or an invalid account. Those errors name their cause.
- A single hand-typed two-line entry is unbalanced. Just correct the typed amount.

## Steps
1. Export the journal lines with full decimal precision, including tax, currency, and system lines the entry screen hides. Verify: the export line count matches the import or source file count
2. Sum debits and credits in the spreadsheet at full precision and record the exact difference. Verify: you have a numeric difference, not just the ERP message
3. Scan for lines that round to 0.00, lines in a second currency, and lines with debit and credit both populated. Verify: each suspect line is listed with its amount
4. Correct only the offending line at its source, for example fixing the conversion or removing the zero line, then re-total. Verify: spreadsheet debits equal credits exactly
5. Resubmit the journal and confirm it posts, then view the posted entry to confirm no system plug line was added. Verify: posted totals match your corrected export

## Variant phrasings
### journal entry unbalanced but lines look equal
The hidden-precision phrasing.
### ERP rejects journal entry no error detail
When the message gives no line number.
### imported journal out of balance rounding line
For import-built entries specifically.

Compatibility: NetSuite, Oracle, SAP, and Dynamics journal entry with CSV export of entry lines.

## Why it happens
Entry screens round for display, posting engines do not. A journal can look balanced at two decimals while carrying a fraction-of-a-cent imbalance, a currency line converted twice, or an allocation line that displays as zero but posts a residual. ERPs that validate at header level report only the header result, which is why no line detail appears. Rebuilding the total outside the ERP exposes what the screen hides.

## Edge cases / pitfalls
- Allocation journals are the repeat offender: percentages that sum to 99.99 leave a residual line nobody entered. Add an explicit remainder line.
- If the export itself does not balance to the source file, the import mapping dropped a line. Fix the mapping, not the journal.
- Tax lines calculated per line versus per invoice can differ by cents. Pick one method and stay consistent for that tax code.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_eBtyABj7K-t2LcTSNv-W6Q