Skip to main content

Dialogue booking - enter bookings and journalise them directly

Updated over 2 months ago

Overview

Use the dialogue posting function to enter postings and immediately journalise them in compliance with GOBD.

Enter and post booking

Navigation:

  1. Open Finance > Postings > Dialogue postings

  2. Fill in the mandatory fields, at least the posting date, external document date, the debit account, the credit account and the amount. Other fields in yellow are also mandatory.

  3. Complete other fields.

  4. Post the transaction using one of the following options:

    • Key combination CTRL+S

    • Click on the Post button

    • Click on the disc symbol

image-20251024-125413.png

Important: Saving and posting are identical for dialogue posting. The posting is immediately written to the journal.

Clearing function

If you are using a person account, the clearing area is displayed and you can

  • Assign the posting amount to open items.

  • Offset postings against each other.

Detailed information can be found in the article"Clearing".

Check postings

  • A link to the posting log appears in the notes area immediately after posting.

  • Below the entry screen you will find a journal extract as a table.
    This is sorted by creation date by default, with the most recent entry being the first in the overview.

Changing postings at a later date

  • Journalised postings can only be edited in a few fields (e.g. cost dimensions). Click on the booking number in the journal table.

  • If you would like to change other fields, the article Cancellation and correction describes the correct procedure.

Create posting templates

You can save frequently used postings as a template:

  1. Select a recorded posting in the journal table.

  2. Right-click to open the context menu and select Create template.

  3. The template is saved in your workplace menu.

  4. You can reuse the template for future postings.

image-20251024-131351.png

Tags:
#journal #mandatory field #booking #booking template #correct

Did this answer your question?