DGMOS's bank movement infrastructure. It collects every statement, from MT940 to Excel, parses it and turns it into one model without ever writing the same movement twice.
Read only. No payment orders, no transfers, no approval flows.
No guessing. If the account is not certain, the statement goes to quarantine and a person decides.
No rewriting. What the bank sent is what is stored; the raw file is kept too.
A file arrives. The service does the rest.
Channels
SFTP pullScheduled · pinned host key · no egress to internal networks
SFTP_PULL
SFTP drop boxThe bank drops files · write only · IP allow-list
SFTP_PUSH
Manual uploadThrough DGMOS · same pipeline
MANUAL_UPLOAD
The same content arriving twice is recognised by its SHA-256 digest and not processed again.
One line, split into its fields
:61:2511041104C15000,00NTRFREF001//BNK0001
Value date
2025-11-04
Direction
Credit
Amount
15,000.00 TRY
Transaction code
NTRF
Customer ref.
REF001
Bank ref.
BNK0001
Quarantine
ACCOUNT_UNRESOLVED
The account in the file did not match any known account with certainty. No movements were written.
Account in file
TR12 •••• 0042 · TRY
Movements
7
Assign to accountClose without import
A statement whose currency does not match is never written to the account, not even with a forced assignment.
Same day, same amount
Rent, November04.11 · BNK0003
−1,000.00
Rent, November04.11 · BNK0004 · flagged as similar
−1,000.00
Two real payments are not collapsed into one. Both are stored; the second is flagged with duplicate_candidate_of. A pending intraday movement is updated in place when the end-of-day statement books it.
