Video summary

Hraðnámskeið - Innlestur bankahreyfinga í dagbók 10. september 2026

Main summary

Key takeaways

Finance

Finance-focused summary (bank transaction ingestion & reconciliation)

The video explains how to streamline bank account reconciliation and the posting of bank movements into financial statements using a DK system (referred to as DK / “DK Bank” and related modules). The goal is to reduce manual, line-by-line matching between bank statements and the general ledger / financial entries, lowering operational error risk and saving time.

Key finance/process concepts (what the system does)

  • Downloads bank transactions electronically into DK, either via a web service or by importing an XML/text file.
  • Uses posting definitions (rules) so standard or recurring bank messages are automatically mapped to the correct accounting outcome (e.g., creditor/debtor, ledger/accounts, and departments if available).
  • Generates a financial journal from the downloaded bank movements, then performs reconciliation between:
    • bank transactions (source from the bank) and
    • financial transactions (results in the ledger / financial statements).
  • Avoids duplicate postings by detecting “double entry / duplicate entry” scenarios.

Workflow (explicit step-by-step framework)

A) Electronic bank statement access prerequisites

  • The company must have the relevant syndicated web service enabled in its license.
  • The bank must be able to identify the company:
    • DK software definitions apply only to DK-affiliated companies.
    • Non-registered companies must use other electronic identification.
  • Users can store interbank access credentials:
    • Save username/password in settings to avoid re-entering them.

B) Setup: create and configure a bank account in DK

Navigate to:

  • Finance → Bank Transactions → Bank Accounts

Create a new bank account and ensure you enter:

  • Account number
  • Bank
  • Ledger
  • (Where applicable) social security number or similar identifiers
  • IBAN/SWIFT for foreign currency accounts

Enter initial reconciliation information for first-time use:

  • Opening date
  • Opening balance
  • Start date: when the company begins processing items in DK

The initial balance is recorded as the balance the day before starting statement ingestion.

Optional setting:

  • Enable “reconciling without bank transactions” for cases like certain bookkeeping corrections (e.g., loans), where transactions don’t need to be downloaded.

C) Setup: configure retrieval and posting behavior

Navigate to:

  • Finance → Bank Transactions → Setup → General settings

Set:

  • Voucher series
    • Recommended: starts with book number “B” for bank transactions and follows correct sequence
  • Whether document numbers auto-increment
  • Enable Use interbank web services if using direct electronic retrieval

Preferred retrieval method (course recommendation):

  • Retrieve via the journal:
    • Finance → Journal → (F5 menu) Download Bank Transactions → Create Journal

The course discourages the “older” alternative method to avoid mixed workflows.

D) Retrieval method rules (to prevent duplicates)

  • Choose one path and stick to it:
    • Do not mix old and new retrieval methods, or the same movements may be processed more than once.
  • Additional ordering rule (Denmark bank collection systems):
    • Retrieve deposits first, post them fully into financial statements, then retrieve bank transactions.
    • This reduces the risk of posting the same transaction twice.

E) Posting definitions (rules engine)

Posting definitions are used to match bank lines to ledger outcomes automatically.

Left side (trigger conditions)

Define what bank transaction characteristics trigger the rule, using fields such as:

  • Text key
  • Description text
  • Reference
  • Order / bank transfer number
    • Noted behavior: if a bank transfer number exists, the system won’t accept it unless it is manually entered
  • Amount sign (positive vs. negative)

Right side (posting outcome)

Define how matching transactions should be posted, including:

  • Transaction type (e.g., debtor/creditor/loan-related type)
  • Book link and/or ledger accounts
  • Credited vs. debited counterpart (creditor/debtor handling)
  • Optional department assignment (only if department capability is licensed)
  • Rule priority to resolve overlaps

Simplification technique

  • Use wildcards/asterisks to match partial strings in description/reference
    • Example: match a number like “5907” even when it appears anywhere in the description.

Key recommendation

  • Use one main condition per rule and keep rules simple.

F) Execute retrieval and reconciliation cycle

  1. Retrieve using Download bank transactions and create journal (via the journal method).
  2. The system indicates whether a movement was previously downloaded:
    • A red “double entry” indicator means it already exists in bank transactions.
    • The system can ignore already-reconciled lines when appropriate.
  3. Create/prepare the journal:
    • Journal is initially write-protected, but can be unlocked for corrections.
    • Entries can be split if needed (split amounts/lines).
  4. Review and finalize registration:
    • Review the registration; if correct, update registration.
  5. Perform bank reconciliation:
    • Go to Bank reconciliation transactions → select bank account → view movements.
    • Reconciliation matches appear as green in the demo.
  6. If needed, adjust matching (“alignment”) logic:
    • Pairing can use fields like date and amount.
    • Clean/refresh and re-download after changes.
  7. Recompute for other periods as needed.

Key cautions / timing guidance

  • Do not retrieve on weekends or immediately on Mondays.
    • Banks may change the posting date after weekend processing completes.
    • Monday invoice processing can cause the same entry to reappear with a different date.
  • Recommendation: wait until the transaction is fully booked by the bank before retrieving.

Disclosures / disclaimers

  • No explicit “not financial advice” disclaimer was included in the subtitles.

Instruments / tickers mentioned

  • No market tickers or instruments (e.g., ETFs, stocks, bonds, commodities, crypto) were mentioned.
  • The only “assets” discussed were bank accounts and system-specific ledger account references.

Key presenters / sources mentioned

  • No presenter names were clearly stated in the subtitles.
  • One attendee mentioned: Sigrún.
  • Follow-up instructions referenced: “Augusta” (from “Return to Augusta”)
    • Contact email domain mentioned: hjalvk.is
  • Another attendee: John (asked about a slide deck).

Original video