Bank Integrations Bank Feeds That Post Themselves
Money moves. The record writes itself.
Connect your bank once. Movements arrive on their own, each is posted where it belongs with its voucher, and the balance matches the bank to the kuruş.
Month end. The statement arrives.
Hundreds of lines, several banks, several passwords. It is nearly midnight and you are still at the desk.
- Line by line, by hand. You sign in to each bank with its own password, download the statement and read it line by line.
- Who sent this? A customer, a salary, a fee? You guess the account from the description and enter each voucher by hand.
- The balance is off. One line slips through; the bank and the books disagree, and the search begins.
- Who paid, who didn’t? You chase a customer who has already paid, and miss the one who hasn’t.
Put the statement down. EFG Assist talks to your bank directly.
From Ziraat to Garanti, from Akbank to VakıfBank: connect your bank once. Every movement arrives on its own, including the last year’s.
Connect once. The rest arrives on its own.
Connect each bank once with the sign-in details it gives you; all your banks and accounts sit on one screen. The last year of movements arrives first, then new ones at the interval the bank allows, without you lifting a finger.
- First connection
- The last 12 months of movements
- Then
- At the bank’s allowed interval; every 15 minutes at QNB
- Any time
- Sync now
- Older than a year
- One opening-balance voucher
Every movement finds its place.
A customer’s transfer goes to their account, a salary to the employee, a bank fee to expenses, interest to income, a transfer between your own accounts to an internal transfer. The vouchers write themselves.
- From a customer
- To the customer: by tax no., IBAN or name
- Salary and advances
- To the employee: by IBAN or ID no.
- Fees, commission, tax
- To expenses
- Interest and yield
- To income
- Between your own accounts
- To an internal transfer
Show it once. It won’t ask again.
If the counterparty matches no account, the movement waits under “Awaiting account”. Pick the account once: the movement is posted, the IBAN is learned, and later movements from that counterparty match on their own. If the bank brings a transfer you already entered by hand, no second voucher is written, and re-entering it warns you.
- Unmatched
- Awaiting account → Pick → Post
- Entered by hand
- Matched to the voucher: same amount, ±2 days
- Wrong account
- Change account: the voucher is cancelled and rewritten
The bank’s balance, right beside yours.
The balance the bank reports sits right beside the app’s in the bank accounts list, on the dashboard and in the account movements, with any difference spelled out. Movements older than a year are gathered into one opening-balance voucher, so the balance starts level with the bank on day one.
Who paid is clear. For who didn’t, the phone rings.
When a movement posts to a customer, their balance changes, and your Smart Tables read that live balance. The payer’s row turns Done and their rep gets a WhatsApp; a voice call reminds your collector of a missed promise. You set the rules: if an account balance drops below a limit, your finance manager gets a call.
The whole story in ninety seconds.
From the midnight desk to the record that writes itself.
Connected in three steps.
Your bank asks for the agreement; EFG Assist prepares the form.
- 01
Create the form.
Open Integration Form from the account’s menu in Bank Accounts: the bank’s Web Integration Agreement downloads as a Word file filled with your company and IBAN details.
- 02
Hand it to your bank.
Sign it and give it to your branch. The bank sends you your web service sign-in details.
- 03
Connect.
In Bank Integrations, Set up connection: enter the details, pick the accounts, Connect. The last year of movements starts arriving.
Your password stays between you and your bank.
We connect on the bank’s own terms and show what your permissions allow.
-
Stored encrypted
Sign-in details are encrypted with AES-256, and the password is never shown back on any screen.
-
Only from our servers
The bank only answers queries from EFG Assist’s allow-listed servers, over HTTPS and only to the bank’s own address.
-
Your bank user won’t lock
If the bank refuses the sign-in, syncing stops and asks you for new details instead of retrying.
-
Seen by those allowed
Setting up connections and seeing movements are separate permissions, and everyone sees only the accounts they’re allowed.
-
The bank’s line stays as is
Corrections happen on the voucher: change the account and the voucher is cancelled and rewritten, while the bank’s line stays untouched.
-
Removed means deleted
Remove a connection and its sign-in details are deleted; the movements already pulled stay in the inbox.
One company. One record.
Every movement from the bank is written to the same books as if you had entered it: a transfer to the bank account and the customer’s account, a salary to the employee, a fee to its expense type, interest to its income type, an internal transfer to both your accounts. The vouchers are the Banking app’s own, and Accounting Reports and Smart Tables read them from the same record.
- Bank Integrations
- Banking
- Customer Accounts
- Employees
- Smart Tables
- Accounting Reports
Every feature.
Connection
- Banks: Akbank, Denizbank, Fibabanka, Garanti BBVA, Halkbank, ING, Kuveyt Türk, QNB, VakıfBank and Ziraat Bankası
- Direct to the bank’s web service, with the sign-in details the bank gives you
- One connection per bank, several accounts each
- Bank-specific sign-in fields: customer no., username, password, service address
- Test, edit, pause / resume and remove a connection
- Web Integration Agreement: the bank’s template filled with your company and IBAN details
Sync
- The last 12 months of movements on the first connection
- Then at the bank’s allowed interval; every 15 minutes at QNB
- Sync now, whenever you like
- Resumes where it stopped; no movement arrives twice
- If the bank’s daily query limit runs out, carries on by itself the next day
- Movements older than a year in one opening-balance voucher
Automatic posting
- Incoming and outgoing transfers to customer accounts
- Salary and advance payments to employees
- Bank fees, commission and taxes to expenses
- Interest and yield to income
- Transfers between your own accounts as internal transfers
- Matches vouchers entered by hand: same amount, ±2 days
- Auto-posting: every movement, history included, becomes a voucher
Matching
- Customers are found by tax number first, then IBAN, then name
- Suffixes like A.Ş., LTD., ŞTİ. and Turkish letters don’t break a match
- Every match teaches it the counterparty’s IBAN
- Unmatched movements wait under “Awaiting account”: pick a customer or employee
- Suggested account
- Optionally open a new account for an unmatched counterparty
Incoming movements
- Search by description, IBAN or tax number
- Filter by account, direction (in / out) and status
- Statuses: Queued, Posted, Matched to voucher, Awaiting account, Not posted, Tracked by hand, Ignored
- Each line links to its voucher, customer and employee
- Change account: the voucher is cancelled and rewritten correctly
- Unlink the voucher, ignore / restore
Balance and security
- The bank’s balance, the app’s balance and the difference side by side
- The bank-reported balance in the bank accounts list and on the dashboard
- A warning when you enter a transfer the bank feed has already posted
- Sign-in details encrypted with AES-256; the password is never shown back
- Only EFG Assist servers connect to the bank
- Per-account permissions: no access, no movements
Specs
- Banks
- Akbank, Denizbank, Fibabanka, Garanti BBVA, Halkbank, ING, Kuveyt Türk, QNB, VakıfBank and Ziraat Bankası
- Connection
- Direct to the bank’s web service, with the sign-in details the bank gives you
- History
- The last 12 months on connection; anything older in an opening-balance voucher
- Sync
- At the bank’s allowed interval (QNB 15 minutes, VakıfBank 2 hours); sync now on demand
- Automatic vouchers
- Incoming/outgoing transfer, internal transfer, salary, advance, expense payment, income receipt, opening balance
- Not posted automatically
- POS, cheques, cards and cross-currency transfers (conversion): left as “Not posted”
- Branches and currency
- Each branch has its own connection; movements post in the account’s currency
- Security
- AES-256 encrypted sign-in details, allow-listed server addresses, HTTPS only, to the bank’s own address
- Permissions
- Managing connections and seeing movements are separate permissions; access per account
- Package
- Separate add-on; runs on top of the Banking app
Start with the Starter package.
During the campaign, open your account with the Starter package.
Starter package
₺249₺99Campaign
per month · VAT included
What every business needs: customers, cash, banks, stock, purchasing, sales, reports, documents, calendar, reminders, approvals and settings. No user classes: the general manager and the warehouse clerk start in the same place.
Start with the campaign- Sign-in details arrive by email after payment
- 10 GB storage included
Questions, answered.
Which banks does it work with?
Akbank, Denizbank, Fibabanka, Garanti BBVA, Halkbank, ING, Kuveyt Türk, QNB, VakıfBank and Ziraat Bankası. To connect you sign a web integration agreement with your bank; EFG Assist prepares the form, filled with your company and IBAN details.
How often do movements arrive?
As often as the bank allows: every 15 minutes at QNB, every 2 hours at VakıfBank, which limits daily queries. You can refresh any time with Sync now.
Does history come in too?
Yes. The first connection brings the accounts’ last 12 months, all posted as vouchers. Anything older is gathered into one opening-balance voucher, so the app’s balance starts level with the bank’s.
How are movements posted?
On their own. Customer transfers in and out go to the customer’s account (found by tax number, IBAN or name), salaries and advances to employees, bank fees and taxes to expenses, interest to income, and transfers between your accounts to internal transfers. If you already entered the voucher by hand, no new one is written; the movement is matched to it.
What if no account matches?
The movement waits under “Awaiting account”. Once you save the account it posts itself on the next sync, or you pick the account on the line and post it right away. The IBAN is learned, so later movements from that counterparty match on their own.
What isn’t posted automatically?
POS collections, cheques, card payments and cross-currency transfers between your own accounts. These lines stay in the inbox as “Not posted” with the reason, and you record them in the Banking app as usual.
Are my sign-in details safe?
Sign-in details are encrypted with AES-256 and never shown back on any screen. The bank only answers queries from EFG Assist’s allow-listed servers. If the bank refuses the sign-in, syncing stops so your user isn’t locked, and removing the connection deletes the details.