---
id: object/table/750
type: object
title: Table 750 "Standard General Journal"
summary: Table 750 "Standard General Journal" in Base Application (Microsoft.Finance.GeneralLedger.Journal). 3 fields, 4 public procedures, 5 events. Present since at least BC23, still in BC30, changed in BC24, BC29.
tier: official
language: en
tags:
  - table
  - base application
versions:
  introduced: null
  last_changed: "29"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 49eab8f930847134dd642497a50f42bd6cf2210016ee250eba675e821941d97e
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Finance/GeneralLedger/Journal/StandardGeneralJournal.Table.al
    title: src/Layers/W1/BaseApp/Finance/GeneralLedger/Journal/StandardGeneralJournal.Table.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/ui-work-general-journals
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/finance/manage-payables/make-payments
    - topic/business-central/business-functionality/general-business-functionality
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: table
object_id: 750
name: Standard General Journal
namespace: Microsoft.Finance.GeneralLedger.Journal
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "24"
  - "29"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 3
  procedures: 14
  events: 5
  subscribers: 0
relations:
  out: 2
  referenced_by: 1
  pages: 2
  extended_by: 0
  event_subscribers: 0
  calls: 2
  called_by: 0
  implements: 0
---

# Table 750 "Standard General Journal"

> Table 750 "Standard General Journal" in Base Application (Microsoft.Finance.GeneralLedger.Journal). 3 fields, 4 public procedures, 5 events. Present since at least BC23, still in BC30, changed in BC24, BC29.

Base Application · Microsoft.Finance.GeneralLedger.Journal · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Finance/GeneralLedger/Journal/StandardGeneralJournal.Table.al) · facts from BC29

Learn documents this table through its pages: [Page 750 "Standard General Journals"](../page/750.md) (1 Learn page), [Page 751 "Standard General Journal"](../page/751.md) (1).

## Properties

| Property | Value |
|---|---|
| Caption | Standard General Journal |
| DataClassification | CustomerContent |

## Fields

Explanation: the field's ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Journal Template Name | Code[10] | — | TableRelation [Table 80 "Gen. Journal Template"](../table/80.md) (Gen. Journal Template); NotBlank |
| 2 | Code | Code[10] | Specifies a code to identify the standard general journal that you are about to save. | NotBlank |
| 3 | Description | Text[100] | Specifies a text that indicates the purpose of the standard general journal. |  |

## Keys

- Key1: Journal Template Name, Code (clustered)

## Events published

- `OnAfterCopyGenJnlFromStdJnl(var GenJournalLine: Record "Gen. Journal Line"; StdGenJournalLine: Record "Standard General Journal Line")` (integration): Integration event raised after copying standard journal line data to general journal line. Enables custom field mapping and additional data processing during journal creation.
- `OnCopyGenJnlFromStdJnlOnBeforeGenJnlLineTransferFields(var GenJournalLine: Record "Gen. Journal Line"; var StdGenJournalLine: Record "Standard General Journal Line")` (integration): Integration event raised before transferring fields from standard journal line to general journal line. Enables custom field preparation and validation before standard field transfer.
- `OnCopyGenJnlFromStdJnlOnAfterInsertGenJnlLineFrmStandard(var GenJournalLine: Record "Gen. Journal Line"; StdGenJournalLine: Record "Standard General Journal Line")` (integration): Integration event raised after inserting general journal line created from standard journal template. Enables custom post-insertion processing and validation of generated journal entries.
- `OnCreateGenJnlOnBeforeCopyGenJnlFromStdJnl(var StandardGeneralJournal: Record "Standard General Journal"; var StandardGeneralJournalLine: Record "Standard General Journal Line")` (integration): Integration event raised before copying standard journal lines during journal creation process. Enables custom filtering and preparation of standard journal templates.
- `OnBeforeCreateGenJnl(var StandardGeneralJournal: Record "Standard General Journal"; var JnlBatchName: Code[10]; var DocumentNo: Code[20]; var PostingDate: Date; var IsHandled: Boolean)` (integration): Integration event raised before starting general journal creation from standard journal template. Enables custom validation and preparation logic before journal generation begins.

## Procedures

- `CreateGenJnlFromStdJnl(StdGenJnl: Record "Standard General Journal"; JnlBatchName: Code[10])`: Creates general journal lines from a standard general journal template. Copies all lines from the standard journal template to the specified journal batch with automatic document numbering.
- `CreateGenJnlFromStdJnlWithDocNo(StdGenJnl: Record "Standard General Journal"; JnlBatchName: Code[10]; DocumentNo: Code[20]; PostingDate: Date)`: Creates general journal lines from a standard journal template with specific document number and posting date. Copies all lines from the standard journal with the specified document details instead of automatic numbering.
- `Initialize(var StdGenJnl: Record "Standard General Journal"; JnlBatchName: Code[10])`: Initializes general journal line context and batch information for standard journal creation. Sets up journal template name, batch name, and locates the last journal line for proper sequencing.
- `IsZeroAmountJournal(): Boolean`: Determines if this standard journal contains only zero-amount lines. Used to determine if document numbering should be applied when creating journal lines.

Plus 5 local procedures.

## Triggers

OnDelete

## Relations

- lookup page [Page 750 "Standard General Journals"](../page/750.md)
- Journal Template Name: TableRelation [Table 80 "Gen. Journal Template"](../table/80.md)

## Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

- [Table 751 "Standard General Journal Line"](../table/751.md): Standard Journal Code

## Pages and codeunits on this table

- [Page 750 "Standard General Journals"](../page/750.md) (source table)
- [Page 751 "Standard General Journal"](../page/751.md) (source table)

## Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an `Object::"Name"` argument. Interface dispatch and calls through events are not counted, so the list is not complete.

- [Codeunit 230 "GenJnlManagement"](../codeunit/230.md) (1 call: `CopyGenJnlFromStdJnl → CalcBalance`)
- [Page 456 "No. Series"](../page/456.md) (1 call: `TryGetNextDocumentNo → (object)`)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC24, BC29

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

## Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: `bcatlas_resolve_node(object_type: "table", object_name: "Standard General Journal")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.
