SIWES Logbook for Banking and Finance: How to Fill It (With Examples)

Banking and Finance students train in banks, microfinance banks, insurance companies and finance departments. The work is sensitive, so many students write almost nothing, in case they reveal something they shouldn't.

The fix is simple: describe the process, not the private data. Follow your school's logbook format first. This post covers what to write inside the spaces your logbook gives you.

Golden rule: never write private information

Do not write customer names, account numbers, balances, loan amounts for named people, staff names (beyond your supervisor's role) or internal passwords. Describe the task and what you learned.

Wrong:

I opened an account for Mr Adewale with a deposit of ₦500,000.

Right:

I assisted a customer service officer in account opening. I checked the KYC documents against the form, entered the details in the system and helped the customer complete the account opening form. I learned the importance of customer identification.

What a good entry contains

Answer these questions each day:

1. Which unit or department? Customer service, operations, credit, treasury, etc.
2. What did I do? The task.
3. Which documents or systems were involved? Forms, ledgers, core banking application, spreadsheets.
4. What did I learn? One clear lesson.
5. Compliance or control point: KYC, reconciliation, authorisation, if relevant.

Three to six lines is enough.

Sample entries by unit (fictional, for style only)

Customer service

I assisted at the customer service desk by directing customers, helping them complete deposit and withdrawal slips and explaining the steps for card requests. I learned that clear communication reduces queues and errors.

Account opening and KYC

I helped a customer service officer in account opening. I checked identification documents against the form and made sure all required fields were completed. I learned why Know Your Customer (KYC) rules protect the bank and customers.

Cash and teller operations

I observed the teller process cash deposits and withdrawals. I saw how each transaction is posted, how the cash is counted twice and how the till is balanced at the end of the day. I learned the importance of accuracy and dual control in cash handling.

Operations and reconciliation

I helped the operations team reconcile the day's transactions. I matched the entries in the daily report against the supporting vouchers and listed items that did not match for review. I learned how reconciliation helps catch errors early.

Credit unit

I assisted the credit officer in filing loan applications and checking that the required documents were attached. I learned the stages of the loan process, from application to approval and disbursement.

Treasury and funds

I observed how the treasury unit monitors the bank's liquidity position. I learned the basic meaning of liquidity and why banks keep reserves.

Digital banking and cards

I helped to resolve simple customer complaints on card and mobile banking issues by following the procedure for logging and escalating complaints. I learned that every complaint should be recorded and tracked until it is closed.

Finance or accounts department

I helped to enter payment vouchers into the accounting system, filed supporting documents and prepared a summary in Excel. I learned how transactions flow from voucher to ledger.

Weekly summary sample

This week I worked in the operations unit. I learned how daily transactions are reconciled, how supporting documents are filed and how exceptions are escalated. I learned that accuracy and documentation are central to banking operations.

Tips specific to Banking and Finance

• Describe the process, not the person. Say "a customer" or "a loan file".
• Name the document or system type. "Deposit slip", "voucher" and "core banking system" are fine to mention.
• Show control awareness. KYC, authorisation and reconciliation show you understand how banks work.
• Link to your courses. Banking operations, financial accounting, credit management and money and capital markets give your entries depth.
• Use plain language. Short, clear sentences are enough.

If the week was slow

Describe what you observed, what you studied (such as the bank's products) and any small tasks you did. See what to write in the logbook when no work was done.

Getting signatures

Show your supervisor your entries weekly. See how to fill your SIWES logbook properly. If you are an Accounting student, see the Accounting and Finance logbook guide.

Drafting entries faster

Tell the MonoEd SIWES Logbook your course, company and tasks and it drafts weekly entries in the right style. You still copy them into your official logbook by hand and get your supervisor to sign.

At the end, the MonoEd SIWES Report Generator drafts your report from your notes. See the Accounting SIWES report guide for a related example. For banks and fintech firms to approach, see SIWES placement for Computer Science students in Lagos, and for the letter itself, how to write a placement request.

Frequently Asked Questions (FAQs)

How do I fill a Banking and Finance SIWES logbook?

Write one short entry a day naming the unit, the task, the documents or systems and what you learned. Keep customer and account details private. End each week with a summary and get it signed.

Can I write customer names or amounts?

No. Describe the process, not the private data.

What if I only did filing and photocopying?

Describe what the files were for, what you learned about how the unit works, and any small tasks you did. Be honest and specific.

What if I worked in a microfinance bank?

Use the same format. Describe loan processing, savings collection, record keeping and customer service.

What if I worked in an insurance company?

Describe policy documentation, claims support and customer service, and what you learned about risk and premiums.

Who signs it?

Your industry-based supervisor signs weekly, and your school supervisor signs when they visit.