Fix NetSuite Journal Showing "Split" in GL

If you're an accountant new to NetSuite, seeing "-split-" next to your journal lines in the General Ledger report is confusing. You expected each credit card transaction to appear as its own line. Instead, NetSuite grouped them by account and labeled the result "split."

Here's what's happening and how to get the line-level detail you need.

Why NetSuite Shows "Split" Instead of Individual Lines

NetSuite's General Ledger report summarizes journal lines by account. When multiple lines in one journal entry hit the same account, the report combines them into a single row and marks it with "-split-."

For example, your monthly credit card journal might have five travel charges and three meal charges. The GL report shows one line for Travel & Entertainment and one for Meals, not eight separate transactions.

This isn't a setting you've missed. It's how the standard GL report works. The detail exists in the transaction itself, but you need to customize the report or use a different tool to see it. As covered in the Revenue and Expense Recognition Guide, NetSuite can post recognition journals in either detailed or summarized form. The summarization attributes include posting period, subsidiary, account, class, department, and location. When lines share those attributes, they collapse into one row.

The Real Problem: You're Using the Wrong Transaction Type

Before we fix the report, let's address the bigger issue. You mentioned importing credit card statements as journal entries. That's technically possible, but it's not how NetSuite is designed to handle credit card activity.

NetSuite has a dedicated Credit Card Charge transaction type. It lives under Transactions > Bank > Make Credit Card Charges. Using this transaction type instead of a journal entry gives you:

• Per-transaction tracking in the GL
• Line-level memos that carry through to reports
• Proper reconciliation against your credit card statement
• Support for dimensions like department or class on each line
• Better audit trails for your external auditors

The journal entry approach works for debits and credits, but it loses transaction-level detail. Your auditors will thank you for using the correct transaction type.

How to Display Each Journal Line in the GL Report

If you need to keep using journal entries for now, you can customize the GL report to show line-level detail. The key is adding the line memo field to your report.

By default, the GL report shows the header memo (Memo Main) but not the memo on each individual line. Here's how to fix that:

1. Open the General Ledger report: Reports > Financial > General Ledger
2. Click Customize at the top of the report
3. In the customization screen, go to the Columns subtab
4. Find Memo in the available fields list and add it to the report
5. Also add Line Memo if you want the per-line description
6. Click Save and name the customized report something like "GL Detail with Line Memo"

This splits the report by transaction line. Each journal line now appears as its own row, showing its individual memo and amount.

Using Saved Searches for Better GL Detail

For more control, create a saved search instead of relying on the GL report. Saved searches give you the exact fields you need without report customization limits.

Here's a saved search that shows every journal line individually:

1. Navigate to Reports > Saved Searches > All Saved Searches
2. Click New and select Transaction
3. Set the criteria:

• Type: Journal
• Date: within the current period
• Account: is not empty

4. Add these result columns:

• Date (field ID: trandate)
• Document Number (field ID: trandocnum)
• Account (field ID: account)
• Debit Amount (field ID: debitamount)
• Credit Amount (field ID: creditamount)
• Line Memo (field ID: memo)
• Name (field ID: entity, for vendor or customer)

Set the results to show All lines, not just the summary. This gives you every line from every journal entry in the period.

The Correct Way to Import Credit Card Statements

If you're importing monthly statements, use the Credit Card Charge import instead of a journal entry import. The CSV import documentation confirms you need a credit card account set up first. Here's the setup:

1. Go to Transactions > Bank > Make Credit Card Charges
2. Click Import at the top
3. Select your CSV file with columns for:

• Date (trandate)
• Account (the expense account)
• Amount (the charge amount)
• Memo (the vendor or description)
• Credit Card Account (the liability account)

4. Map the CSV columns to the NetSuite fields
5. Run the import

NetSuite creates one Credit Card Charge per row in your CSV. Each charge posts to the GL as its own transaction line. No more "-split-" labels.

What About Project or Task-Level Tracking?

One limitation of journal entries: they don't support tracking to the task level on a project plan. A journal entry can tag to the project as a whole, but not to individual tasks within that project.

Credit Card Charges and Vendor Bills support task-level tracking. If your team needs this granularity for project accounting, the correct transaction type matters even more.

Your Month-End Close Will Thank You

The "-split-" label isn't an error. It's NetSuite telling you the detail is summarized. The fix is either customizing your GL report to include line memos or switching to the proper transaction type for credit card activity.

For accountants coming from other systems, this is one of the biggest NetSuite adjustments. The platform handles transactions differently than traditional accounting software. Once you understand that each transaction type has a purpose, the GL starts to make sense.