Concepts¶
This section explains the domain knowledge that helps you use SWEN effectively. You do not need to be an accountant but understanding a few core ideas will make the UI and data flows more natural.
-
Why SWEN uses double-entry, what debits and credits mean, and how a bank import turns into journal entries.
-
What this protocol is, what bureaucracy is involved, and what is necessary to enable it for your bank.
-
The precise vocabulary used throughout SWEN: what a
Transactionis, how it differs from aBankTransaction, and why there is both anAccountand aBankAccount. -
Why bank APIs return the same transaction multiple times, and how SWEN's hash + sequence approach handles it correctly.