Ledger Type (JD Edwards)

In JD Edwards, a ledger type is a code that identifies which set of financial figures a transaction belongs to, such as actual amounts, budgets, or units, and using the right one is essential to accurate reporting.

What Is a Ledger Type in JD Edwards?

In JD Edwards, a ledger type is a code that identifies which set of financial figures a transaction belongs to. The same account can hold several different ledgers at once: the actual amounts posted, the budget, statistical units, and others, each distinguished by its ledger type. When you look at an account balance in JD Edwards, the ledger type tells you which version of the numbers you are looking at. Getting it right is fundamental to accurate reporting, because using the wrong ledger type produces numbers that look valid but answer the wrong question.

Ledger types are central to how JD Edwards handles finance. Rather than keeping budgets, actuals, and other figures in separate places, EnterpriseOne stores them against the same accounts, separated by ledger type. This is efficient and flexible within the system, but it means any reporting on JD Edwards data has to understand and filter by ledger type to return correct results.

Common JD Edwards Ledger Types

JD Edwards uses a set of standard ledger types, and organizations can define their own as well. Some of the most common include:

AA (Actual Amounts). The actual posted financial amounts, the figures most reporting is based on. This is the ledger type behind the standard financial statements.

BA (Budget Amounts). Budgeted financial amounts, used for budget-versus-actual analysis against the AA ledger.

AU (Actual Units). Actual quantities or statistical units rather than currency amounts, used for non-financial measures tracked in the ledger.

Other and custom types. Standard types also include CA (foreign currency amounts, which sit beside AA when you post in more than one currency) and BU (budget units). Ledger types are defined in user-defined code list 09/LT, and JD Edwards reserves codes such as U1 to U9 for your own ledgers, for alternate budgets, forecasts and similar needs.

Why Ledger Types Matter for Reporting

Ledger types are one of the details that make JD Edwards reporting tricky and one of the most common sources of error. A report that fails to filter by ledger type, or filters by the wrong one, can combine actuals with budgets, or report units as if they were currency, producing numbers that are simply wrong while appearing legitimate. Anyone building analytics on JD Edwards has to handle ledger type correctly, every time.

Used well, ledger types are powerful. Because actuals, budgets, and other figures live against the same accounts, distinguished only by ledger type, budget-versus-actual reporting and similar comparisons become straightforward once the semantic model understands the ledger types. The structure that makes reporting error-prone if mishandled is the same structure that makes rich financial comparison possible when handled correctly.

Ledger Types in JD Edwards Analytics

In the JD Edwards account ledger (F0911) and account balances (F0902) tables, ledger type is one of the key fields that determines what a row represents. Modeling JD Edwards data for analytics means treating ledger type as a deliberate part of the design: separating actuals from budgets, presenting each measure against the correct ledger type, and making it easy for reports to compare them where appropriate.

This is exactly the kind of system-specific knowledge that makes JD Edwards analytics specialized, alongside Julian dates, user-defined codes, and the Address Book. Handling ledger types correctly is part of what a pre-built JD Edwards semantic model provides, so reporting starts from clean data where actuals, budgets, and units are already correctly separated.

Common Challenges and Best Practices

  • Always filter by ledger type. Never report on JD Edwards financial data without accounting for ledger type. Unfiltered or wrongly filtered reports produce convincing but incorrect numbers.
  • Know which type each measure uses. Actuals come from AA, budgets from BA, units from AU, and foreign currency amounts from CA, which must never be added to AA. Map each reporting measure to its correct ledger type deliberately.
  • Model for comparison. Because actuals and budgets share accounts, design the semantic model so budget-versus-actual reporting is easy and correct.
  • Account for custom ledger types. Organizations often define their own ledger types. Identify and handle these, not just the standard set.
  • Use a pre-built semantic model. Correct ledger type handling is part of what a JD Edwards semantic model provides, removing a common source of reporting error.

Frequently Asked Questions

What is the AA ledger type in JD Edwards?

AA stands for Actual Amounts. It is the ledger type holding the actual posted financial figures in JD Edwards, and it is the basis for standard financial statements. Most financial reporting is built on the AA ledger.

What is the CA ledger type in JD Edwards?

CA holds foreign currency amounts. When a transaction is entered in a currency other than the company’s, JD Edwards posts the domestic amount to AA and the original foreign amount to CA against the same account. Reports that add the two together overstate the balance, so CA belongs in its own measure.

Can you compare budget and actuals using ledger types?

Yes. Because actual amounts (AA) and budget amounts (BA) live against the same accounts, distinguished by ledger type, comparing them for budget-versus-actual analysis is straightforward once the semantic model correctly separates and presents each ledger type.

Ledger Types and QuickLaunch's Approach

QuickLaunch Analytics builds ledger types into the JD Edwards Application Pack’s semantic model, so each measure reads the ledger it belongs to and report authors don’t have to remember the filter. The general ledger perspective, income statement and balance sheet hierarchies, and fiscal calendars sit on the same governed foundation, so your reports and your AI tools work from the same definitions of actual and budget.

About the Author

Avatar photo

Louie Benitez

Louie learned the product the practical way, by deploying it. After years on the implementation team getting customers live, he moved into sales engineering, where he now demos and scopes the solution for prospects. He writes from the delivery seat about what a real rollout looks like and where ERP data tends to break.

Related QuickLaunch Solutions and Products

Foundation Pack

Accelerate time to insight while lowering total cost of ownership by creating a unified and centralized business foundation with your CRM, ERP, and other data sources.

Key Features

  • Automated Data Pipelines
  • Governed Data Lakehouse
  • Enterprise Semantic Layer
  • Kept current through upgrades
Learn More About the Foundation Pack

JDE Pack

Finance, supply chain, manufacturing, job cost and payroll analytics for JD Edwards EnterpriseOne, with the business logic built and validated.

Key Features

  • 35 perspectives
  • 3,900+ measures
  • Income statement and balance sheet hierarchies
  • Automatic Julian date conversion
  • User-defined code translation 
Learn More About JD Edwards Analytics

Get Your Custom Analytics Blueprint

See the ideas working in a live demo. We'll show the semantic model, the governed lakehouse and AI answers for JD Edwards, Vista, NetSuite, OneStream, Salesforce or Spectrum.

Get Custom Demo