Back Office Executive Interview Questions and Answers: 60 Questions from Easy to Hard
This guide is for freshers and working professionals in India applying for back office executive and operations roles at banks, NBFCs, insurers, BPOs, e-commerce companies and trading firms. It has 60 interview questions with sample answers in three levels: the basics freshers are asked (the role, documents, Excel and email), the real problems of the first one to three years (KYC and invoice processing, TAT, errors, audits and escalations), and the judgement questions for experienced executives and team leads (SLA design, compliance findings, staffing, quality plans and automation). Answers use Indian rules and rupee examples, and every Excel formula has been tested. If you are applying for a typing-heavy data entry job, see our Data Entry Operator guide too. Read each answer, then practise it aloud with your own numbers.
- 60 questions, 3 levels
- Updated
- CoreHRx Jobs
- 20 open Back Office jobs
What back office interviews cover
- The role itself: how back office work supports the front office in banks, NBFCs, insurers, BPOs, e-commerce and trading firms, and what a normal day of checking, entering and tracking looks like.
- Documents and checks: KYC documents and the RBI's rules on them, GST invoice fields, purchase orders and goods receipts, order and refund records, and how you spot errors or tampering.
- Tools: Excel trackers with COUNTIFS, NETWORKDAYS and XLOOKUP, an ERP, CRM or loan system, and email written for a shared mailbox.
- Numbers: TAT and SLA, accuracy and error rates, backlog and capacity, often asked as quick calculations during the interview.
- For senior roles: quality check design, audit findings, team productivity, SOPs, automation and pressure from sales or branches to skip a check.
How freshers should prepare
- Read the job description and list the documents and systems it names, such as KYC, invoices, loan files or returns, then prepare one line on what you would check in each.
- Practise Excel on a small tracker you build yourself: COUNTIF and COUNTIFS for status counts, NETWORKDAYS for pending days, and a lookup that matches two lists.
- Learn the basic vocabulary: TAT, SLA, maker-checker, OVD, CKYC, PO, GRN, IRN, RTO and NDR. Freshers are often asked to explain two or three of them.
- Prepare one real example of careful work with numbers, such as reconciling college fee receipts or checking stock in a family shop.
- Write a short practice email asking for a missing document, since an email-writing task is common in operations hiring.
How experienced candidates should prepare
- Know your numbers: daily volume, TAT achieved against the SLA, accuracy or error rate, backlog and team size. Vague figures raise doubts.
- Prepare STAR stories for an error you caught, an error you made and fixed, a TAT or accuracy improvement, and a time you refused a shortcut.
- Revise the rules behind your process, such as the RBI's KYC Directions for a bank or NBFC, or Rules 46 and 48 of the CGST Rules for invoice work, and check the latest version before the interview.
- For team lead roles, be ready to plan staffing from volume and handling time, design a quality sample and explain how you closed an audit finding.
Tests, shifts and targets
- Interview reports from BPO and banking operations roles often mention a typing test, an aptitude or Excel test and an email-writing task, so ask the recruiter which ones apply.
- Ask how targets are set: cases per day, the accuracy floor and TAT, and whether incentives depend on quality as well as volume.
- Ask about shift timings, month-end or quarter-end peaks and Saturday working, which vary a lot between banks, insurers, BPOs and e-commerce firms.
- Check whether the job is on the company's own payroll or through a staffing agency, since this affects benefits and growth.
Common mistakes to avoid
- Describing KYC as collecting an Aadhaar copy. Interviewers want to hear that KYC is verification against reliable documents, with rules on what is accepted.
- Saying you never make mistakes. A strong answer explains how you check your work and what you do when an error is found.
- Answering TAT and backlog questions without numbers. Work out the pace, backlog or staffing aloud, even roughly.
- Offering to bend a rule to please sales or a big client. The back office exists to apply the checks, and interviewers test whether you will.
- Blaming previous teams or branches. Describe the problem, the data and what you did to fix it together.
Back Office interview questions: Easy questions (freshers)
20 questions1. What does a back office executive do, and how is the role different from the front office?
The front office meets customers: branch staff, sales executives and call centre agents who take applications and answer queries. The back office makes those requests actually happen, usually without meeting the customer: checking documents, verifying KYC, entering data in the core system or ERP, matching invoices to orders, processing refunds and preparing daily reports. For example, a sales officer collects a personal loan application in Pune, and the back office in Mumbai checks the file, raises a query for missing papers and releases it for disbursement within the agreed TAT. Interviewers want to hear that accuracy and turnaround matter more in this job than selling or talking skills.
2. Why do you want a back office job rather than a customer-facing role?
Give a reason linked to the work, not a dislike of people. For example: 'I enjoy work where I check details carefully and finish a clear task. In my final year I helped the college office reconcile 300 fee receipts with the bank statement and found four mismatches, and I liked that work. Back office jobs reward accuracy, discipline and process knowledge, and I want to build a career in banking operations.' Add that you are comfortable with daily targets and repetitive work. Avoid saying that you do not like talking to customers, because back office staff still deal with branches, vendors and other teams every day.
3. How does back office work differ in a bank, an insurer and an e-commerce company?
The core skills are the same, checking, entering and tracking, but the documents and rules differ. In a bank or NBFC you check account opening and loan files, KYC documents and disbursement details, and follow the RBI's KYC Directions. In an insurer you scrutinise proposal forms, issue policies, process endorsements such as a change of address or nominee, and check claim papers. In an e-commerce company you handle order exceptions, returns, refunds, seller payments and courier reconciliations. A trading firm adds purchase orders, goods receipts, invoices and stock entries. Name the sector you are applying to and two or three tasks you expect, which shows you have read the job description.
4. What is KYC, and why do banks and NBFCs insist on it?
KYC, or Know Your Customer, means identifying a customer and verifying that identity and address from reliable, independent documents or sources before opening an account or giving a loan. Banks and NBFCs follow it under the Prevention of Money-laundering Act and the RBI's KYC Directions; since 28 November 2025 there is a separate set for each type of regulated entity, such as commercial banks or NBFCs, in place of the 2016 Master Direction. The aim is to stop accounts in fictitious or benami names, money laundering and fraud. KYC also covers the customer's risk category and keeping details updated. Do not describe KYC as collecting an Aadhaar copy; it is verification.
5. Which documents are accepted as Officially Valid Documents for KYC in a bank?
Under the RBI's KYC Directions for commercial banks, the Officially Valid Documents are the passport, driving licence, proof of possession of Aadhaar number, Voter ID card, NREGA job card signed by a State Government officer, and the National Population Register letter showing name and address. If the document lacks the current address, a deemed document such as a utility bill not more than two months old can be used for address, and an OVD with the current address must follow within three months. A PAN card is not on this list: PAN, or the no-PAN declaration (Form 60 in the RBI text, or the form that replaced it under the Income-tax Rules, 2026), is collected separately.
6. What is the difference between a self-attested copy and a certified copy of a document?
A self-attested copy is a photocopy the customer signs to declare that it is a true copy of his own document. A certified copy is one where an authorised officer of the bank or company compares the copy with the original and records that on the copy, often with a stamp such as original seen and verified, plus the date, name, employee code and signature. The RBI's KYC Directions define a certified copy in this way. The difference matters because the officer, not the customer, confirms that the original was really seen. In the back office, a missing or incomplete verification stamp is a common reason to return a file to the branch.
7. How do you check a scanned document before you accept it into the system?
I check five things in order. First, readability: the full page is visible, not cut at the edges, with no blur or glare on the number, name or photo. Second, completeness: every page is there, both sides of an ID card, all pages of a bank statement. Third, match: name, date of birth and address agree with the application form and the other documents. Fourth, validity: the document has not expired, and dates fall in the required range, such as a utility bill not more than two months old. Fifth, signatures and verification stamps are present. If any check fails, the query names the exact problem rather than saying documents incomplete.
8. How would you name and store scanned documents so that anyone can find them later?
Use one naming rule for the whole team, built from the case reference, the document type and a date, for example LN204587_PAN_20261112.pdf or SUP118_INV4471_20261105.pdf. Names like scan001 or final_new_2 mean nothing a month later. Save files in the document management system or the agreed shared folder against the right case, never on the desktop or a personal drive, and merge a multi-page document into one PDF in the correct page order. Follow retention rules too: the RBI's KYC Directions require banks to keep identification records for at least five years after the relationship ends, so deleting files carelessly is also an error.
9. What details do you check on a GST tax invoice before you enter it?
Rule 46 of the CGST Rules lists what a tax invoice must contain, and the back office checks the key fields: supplier name, address and GSTIN; a serial number of up to 16 characters, unique for the financial year; the invoice date; our company name, address and GSTIN; HSN or SAC code and description; quantity and unit; taxable value after any discount; the rate and amount of CGST and SGST, or IGST; place of supply for inter-state supplies; whether reverse charge applies; and a signature, unless it is an electronic invoice. Then check the arithmetic and the purchase order. A wrong buyer GSTIN is a common error that can hold up input tax credit.
10. What stages does an online order pass through in an e-commerce back office?
A typical flow is: order placed, payment confirmed or cash on delivery accepted, order confirmed against stock, picked and packed, invoice and shipping label generated, handed to the courier, in transit, and delivered. The back office watches the exceptions: orders not picked up, NDR cases where delivery failed and the customer must be contacted, RTO shipments returning to the warehouse, cancellations, returns and refunds. For example, if a Jaipur order shows delivered but the customer says it never arrived, you check the courier's proof of delivery before approving a refund. Interviewers check whether you know that every status change must agree with the system record and the courier record.
11. How would you count open and closed cases in an Excel tracker?
Use COUNTIF for one condition and COUNTIFS for more than one. In the example, COUNTIF on the status column returns 4 open and 3 closed cases, and COUNTIFS counts 3 cases that are both KYC and open. The remaining case, marked Pending docs, can be found by subtracting both counts from COUNTA, which counts non-blank cells. This only works if everyone types the same status words: COUNTIF ignores capital letters, but it treats Opened, or Open with a trailing space, as a different value. So give the status column a drop-down list instead of free text. A pivot table then gives the count for every status and case type at once.
A B C
1 Case Type Status
2 C101 KYC Open
3 C102 Invoice Closed
4 C103 KYC Closed
5 C104 KYC Open
6 C105 Invoice Open
7 C106 KYC Pending docs
8 C107 Invoice Closed
9 C108 KYC Open
=COUNTIF(C2:C9, "Open") -> 4
=COUNTIF(C2:C9, "Closed") -> 3
=COUNTIFS(B2:B9, "KYC", C2:C9, "Open") -> 312. How do you work out how many working days a case has been pending?
Subtracting dates counts weekends, so use NETWORKDAYS, which counts Monday to Friday and skips any holidays you list. A case received on Monday 2 November 2026 and still open on Thursday 12 November is 10 calendar days old, but NETWORKDAYS gives 9 working days, and 8 if 10 November is listed as a holiday (assumed here). NETWORKDAYS counts both the start and end dates, so subtract 1 if your TAT clock starts on the next working day. If your office works on some Saturdays, use NETWORKDAYS.INTL with Sunday as the only weekend day and list the Saturdays off as holidays. Keep the holiday list in one range that every formula uses.
A B C
1 Received Today Holiday
2 02-11-2026 12-11-2026 10-11-2026
=B2-A2 -> 10
=NETWORKDAYS(A2, B2) -> 9
=NETWORKDAYS(A2, B2, C2) -> 8
=NETWORKDAYS(A2, B2, C2)-1 -> 713. A branch sent a home loan file without the borrower's latest salary slips. What should your email asking for them contain?
Make the email easy to act on and easy to find later. The subject carries the reference and the action, for example: LN204587: 2 documents pending, needed by 14 Nov. Use the file number rather than the customer's name or PAN, because subject lines get forwarded widely. In the body, list exactly what is missing: salary slips for September and October 2026, and the signature on page 3 of the application form. Say what happens next: the file stays on hold until the documents arrive. Keep it to a few lines, address the person responsible, and copy the team mailbox so others can see the thread. Close with your name and extension.
14. What is an ERP system, and what entries would a back office executive make in one?
An ERP, such as SAP, Oracle or Microsoft Dynamics, or TallyPrime in smaller firms, connects purchasing, stores, sales, finance and often HR, so that one entry flows to every department. A back office executive typically creates or updates vendor and customer master records, raises purchase orders, records goods receipts, enters supplier invoices against the PO, books sales orders and updates dispatch status. A CRM, such as Salesforce or Zoho CRM, holds customer and lead records instead, and lenders use a loan management system. The interviewer wants to know you understand that one wrong entry, say a wrong rate on a PO, travels into stock, payments and reports, so you check before you save.
15. What is maker-checker, and why do back offices use it?
Maker-checker means one person enters or prepares a transaction (the maker) and a different person verifies and approves it (the checker) before it takes effect. For example, a maker enters a new vendor's bank account from the cancelled cheque, and a checker compares the entry with the document before any payment can go to that account. It catches typing errors, stops one person from pushing through a wrong or fraudulent entry alone, and leaves an audit trail of who did what. The checker must look at the source document, not just glance at the maker's screen; approving without checking defeats the control and is treated as a serious lapse.
16. How do you check your own work before you submit a batch?
I check in three passes. First, a count check: if 85 forms came in, 85 records were created, with no gaps or extras. Second, a field check of the critical fields against the source, such as account number, amount, date, name and PAN, reading the document and the screen digit by digit rather than from memory. Third, a total check: the sum of amounts in my entries equals the total on the batch sheet, for example Rs 12,45,600. Then I note anything I could not complete, with the reason. Interviewers like candidates who check critical fields first, because a wrong amount costs far more than a typing slip in a remarks field.
17. What do TAT and SLA mean in back office work? Give an example.
TAT, turnaround time, is how long a task takes from the moment it is received with everything needed until it is completed. An SLA, a service level agreement, is the agreed promise and the rules for measuring it, for example: 95% of account opening files processed within one working day of receipt. If a complete file reaches you at 11 am on Monday and you finish it at 3 pm on Tuesday, the TAT is more than one working day, so that file breaches a one-day SLA. Know what starts and stops the clock in your process, and that a file waiting for the customer's documents is usually tracked separately.
18. You must finish 120 cases by 5 pm, starting at 9:30 am with a 45-minute break. How do you plan the day?
Work out the pace first. From 9:30 to 5:00 is 7 hours 30 minutes; minus the break, that leaves 6 hours 45 minutes, or 405 minutes, so 120 cases need about 18 an hour. I would keep the last 30 minutes for checking and pending queries, which leaves 375 minutes, a little over 3 minutes a case, or about 19 to 20 cases an hour. I would start with the cases closest to their cut-off, check my count every hour, and tell my team leader by midday if I am falling behind, not at 4:45. Interviewers check whether you plan with numbers and raise a risk early.
19. What does confidentiality mean in back office work, and what must you never do?
Back office staff see PAN and Aadhaar details, bank statements, salaries, policy details and vendor bank accounts, so confidentiality means using that data only for the task in hand. Never photograph screens or files, forward customer data to personal email or WhatsApp, discuss a customer's details outside the team, leave printouts on the desk or the printer, or share your login. The RBI's KYC Directions tell banks to keep customer information confidential and not to use it for cross-selling without the customer's permission, and most employers ask staff to sign a confidentiality agreement. Interviewers want a concrete list of habits, not just a promise to keep data safe.
20. When should you escalate an issue instead of trying to solve it yourself?
Escalate when the decision is outside your authority, when the SOP does not cover the case, when a TAT or cut-off will be missed, when money or customer data is at risk, or when you suspect fraud. For example, a refund above your approval limit, or a cheque signature that does not match the specimen, is not yours to decide alone. Escalate early, to the person named in your escalation matrix, with the facts: case number, what you found, what you have already done and what you need. Do not escalate everything either; routine queries that the SOP answers should be solved by you, or your manager becomes the bottleneck.
Back Office interview questions: Medium questions (1-3 years)
20 questions21. A customer's Aadhaar shows her old address in Nagpur, but she now lives in Pune. How do you handle her address proof?
It depends on how her KYC is done. If the bank authenticates her Aadhaar number through UIDAI e-KYC and her current address differs from the address in the Aadhaar records, the RBI's KYC Directions let her give a self-declaration of the Pune address. If she instead submits a physical OVD showing the Nagpur address, she can give a deemed OVD for the current address, such as a utility bill for the Pune flat not more than two months old or a property tax receipt, and must then submit an OVD with the current address within three months. I would record that due date in the tracker and follow it up, and apply my bank's policy where it is stricter.
22. A customer opening a savings account has no PAN. Can the account still be opened, and what do you check?
Yes. Under the RBI's KYC Directions an individual gives PAN, its equivalent e-document, or the no-PAN declaration: Form 60 in the RBI text, or the form that replaced it under the Income-tax Rules, 2026. I check that the declaration is complete, signed and consistent with the OVD and, since it is only a declaration, that expected income and deposits fit the customer's profile. When a PAN is given, I verify it through the bank's PAN check rather than trusting the card: the name must match the form, and the fourth character shows the holder type, P for an individual, so a C or an F means a company or firm PAN was entered by mistake.
23. A low-risk customer's KYC is due for periodic updation and nothing has changed. What does the bank need from her?
Under the RBI's KYC Directions, periodic updation is due once in two years for high-risk, eight years for medium-risk and ten years for low-risk customers, counted from account opening or the last update. If nothing in her KYC has changed, a self-declaration is enough, given through her registered email or mobile number, an ATM, internet or mobile banking, or a letter. If only her address has changed, she can declare the new address through the same channels, and the bank must verify it by positive confirmation, such as an address verification letter or contact point verification, within two months. The back office tracks due dates so that reminders go out before KYC falls overdue.
24. What is CKYCR, and what does the back office do with a customer's KYC Identifier?
CKYCR is the Central KYC Records Registry, which stores customers' KYC records digitally so regulated entities can reuse them. Under the RBI's KYC Directions, a bank uploads the KYC record to CKYCR within 10 days of starting an account-based relationship, makes sure the KYC Identifier generated by the registry is communicated to the customer, and sends updated details within seven days of an update. With the customer's explicit consent, a bank can download a record using the KYC Identifier instead of collecting the documents again. Under an amendment of 29 December 2025, the entity that last uploaded the record answers for its identity and address verification, but the downloading bank still owns every other due diligence step.
25. A loan file reaches you with one page of the bank statement missing and an unsigned declaration. How do you handle it without wasting TAT?
Check the whole file first and list every deficiency in one go, so the branch gets one complete query instead of three emails over two days. Here: page 4 of the June bank statement is missing, and the declaration on page 6 is unsigned. Mark the file as pending documents in the tracker with the date and time, which in most processes stops your TAT clock, and send the query to the file's branch or sales owner. Continue the steps that do not depend on these documents, such as the credit bureau check, if the process allows it. Follow up before the end of the day, and close the query in the tracker once the documents arrive.
26. What signs suggest that a document may have been tampered with, and what do you do when you see them?
Watch for fonts that change within a line, figures that look pasted or misaligned, statement balances that do not add up, salary credits that differ from the salary slip, a photo that looks stuck on, and the same document turning up in another customer's file. Do not accuse the customer or discuss it casually with the branch. Record what you found, keep the file on hold and escalate to the credit, risk or fraud control team as your process says. If money laundering is suspected, the RBI's KYC Directions say a bank should not pursue due diligence that would tip off the customer, and should file a suspicious transaction report instead.
27. A PO for 40 office chairs at Rs 3,200 each says the price includes delivery. Stores accepted 38 and rejected 2 as damaged, and the invoice bills 40 chairs plus Rs 2,500 freight. Assuming GST at 18% on the whole invoice, what do you approve?
Approve what the PO allows and stores accepted: 38 chairs at Rs 3,200 is Rs 1,21,600, plus GST of Rs 21,888, so Rs 1,43,488. The invoice asks for Rs 1,28,000 for 40 chairs plus Rs 2,500 freight, Rs 1,30,500 before tax and Rs 1,53,990 with GST, which is Rs 10,502 more. The gap is the 2 rejected chairs, worth Rs 6,400, and the freight of Rs 2,500, which the delivered price already covers, plus GST on the Rs 8,900. Hold the invoice, send the supplier the rejection note from stores, and ask for a credit note or a revised invoice. Freight can be paid only if purchase first approves a PO amendment.
28. A supplier's invoice shows your company's GSTIN with one wrong character. What do you do?
Do not correct it by hand, or enter it in the ERP as if nothing were wrong. The supplier reports the invoice in its GST return against the GSTIN printed on it, so the tax credit will land under another GSTIN, or be rejected, and will not reach your company's GSTR-2B. Put the invoice on hold, tell the supplier in writing which character is wrong, and ask for a corrected invoice or for the details to be amended in its return, as your tax team advises. Inform accounts payable so the payment waits too. Also check whether the wrong GSTIN came from your own PO or billing address, because then it will repeat.
29. The courier's cash on delivery remittance for last week is Rs 3,000 less than your system shows for delivered COD orders. How do you find the gap?
Reconcile order by order, not on totals. Download the delivered COD orders from your system and the courier's remittance file with order numbers and amounts, and match them on the order or AWB number. The gap usually comes from a few causes: orders marked delivered in your system but actually RTO with the courier, orders remitted in the next cycle, partial deliveries, courier charges netted off the remittance, or cash collected but not remitted. For example, two orders of Rs 1,200 and Rs 1,800 missing from the file explain exactly Rs 3,000. Raise the unexplained orders with the courier with the proof of delivery, and carry the open items forward until they are settled.
30. How would you add a column to a KYC tracker that shows when each customer's periodic updation falls due, and flag the overdue ones?
Use EDATE, which adds whole months to a date, with the interval set by the risk category: under the RBI's KYC Directions, every 2 years for high-risk, 8 years for medium-risk and 10 years for low-risk customers, so 24, 96 or 120 months from the last KYC date. Keep the report date in one cell, here G1, so the status does not change every time the file is opened. In the example, C301 fell due on 10 Oct 2026 and C303 on 1 Jun 2026, so both are overdue; C304 falls due on 20 Dec 2026, within 60 days, and C302 not until March 2027. Sort by due date and send reminders well before it.
A B C
1 Cust Risk Last KYC
2 C301 High 10-10-2024
3 C302 Medium 15-03-2019
4 C303 Low 01-06-2016
5 C304 High 20-12-2024
G1 = 19-11-2026 (report date)
D2: =EDATE(C2, IF(B2="High", 24, IF(B2="Medium", 96, 120)))
E2: =IF(D2<$G$1, "Overdue", IF(D2<=$G$1+60, "Due soon", "Later"))
D2:D5 -> 10-10-2026, 15-03-2027, 01-06-2026, 20-12-2026
E2:E5 -> Overdue, Later, Overdue, Due soon31. How would you build an ageing summary of pending cases for your daily report?
Add a column with the working days each case has been pending, using NETWORKDAYS from the received date to a report date kept in one cell, minus 1, because NETWORKDAYS counts both ends and a case received today would otherwise show 1. Then count the cases in bands with COUNTIFS. In the example, 3 of the 8 cases are 0 to 2 days old, 3 are 3 to 5 days and 2 are over 5 days. The bands must not overlap or leave gaps: <=2, then >=3 with <=5, then >5, and the counts must add up to the total. Below the summary, list the cases over 5 days with their reasons, such as pending customer documents.
A B C
1 Case Received Days pending
2 L201 18-11-2026 1
3 L202 13-11-2026 4
4 L203 19-11-2026 0
5 L204 10-11-2026 7
6 L205 17-11-2026 2
7 L206 12-11-2026 5
8 L207 06-11-2026 9
9 L208 16-11-2026 3
C2: =NETWORKDAYS(B2, $F$1)-1, with F1 = 19-11-2026
=COUNTIFS(C2:C9, "<=2") -> 3
=COUNTIFS(C2:C9, ">=3", C2:C9, "<=5") -> 3
=COUNTIFS(C2:C9, ">5") -> 232. How do you manage a shared team mailbox so that no request is missed or answered twice?
Agree a few rules and follow them every time. Each new mail is picked by one person, who marks it, for example with a category or flag carrying their initials, or moves it to their folder, so others can see it is taken. Every request is logged in the tracker with the time received, because the mailbox alone does not show TAT. Replies go from the shared mailbox, keeping the original subject and reference number, so the history stays in one thread. At fixed times, say 11 am and 4 pm, one person checks for unclaimed mails older than two hours. At shift end, nothing stays unread or unassigned without a note for the next shift.
33. A branch manager emails your team and his regional head, blaming you for a delayed disbursement that was held for his missing documents. How do you reply?
Reply with facts, not emotion, and only after checking the record. Keep the same recipients so the record is corrected where the blame was made, but write calmly, for example: File LN204587 was received at 11:40 on 10 Nov. Our query for the signed loan agreement went at 12:15 on 10 Nov and again on 11 Nov. The document arrived at 16:05 today, and the file will be disbursed by 11 am tomorrow. Quote or attach the earlier query. Add no comments about his team. Then call him, because a conversation repairs the relationship better than a long thread. Interviewers check that you defend your team with evidence and stay professional.
34. You posted an entry with the wrong amount in the ERP, and it has already been approved. What do you do?
Report it at once to the checker and your team leader; do not try to fix it quietly. In an ERP, an approved document is usually not edited or deleted: it is reversed or cancelled through the proper transaction, such as a reversal entry or a credit memo, and then posted again correctly, so the audit trail shows both. Check what the error has already touched, such as a payment run, a stock value or a report sent to the client, and stop or correct those too. For example, if Rs 1,45,000 was posted as Rs 14,500 on a supplier invoice, the payment proposal must be corrected before the run. Then note the cause and how you will prevent it.
35. What do you check before creating a new vendor in the ERP?
First search the master by PAN, GSTIN and name, so you do not create a duplicate vendor, which is a common cause of double payments. Then check the documents: PAN, GST registration certificate, a cancelled cheque or bank letter, and the address. Verify the GSTIN on the GST portal and check that the legal name there matches the PAN and the bank account name; a GSTIN contains the holder's PAN, so the two must agree. Confirm the bank account through the company's validation process, such as a penny-drop check. Fill in payment terms, MSME status if declared and the tax codes, and send the record to a checker before any PO is raised.
36. QA checked 50 of your 600 cases this month and found errors in 2, one of them fatal. What is your accuracy, and what happens next?
Case accuracy is 48 out of 50, or 96%. Many processes also report fatal accuracy separately: one fatal error in 50 cases gives 98%, and a fatal error, such as a wrong account number, a wrong amount or a KYC document not checked, is often treated as a serious breach whatever the overall score. Next, I would go through both errors with QA, find out why each happened, and correct them in the live records if the cases are still open. If the fatal error came from a habit, such as skipping a field check under time pressure, I change the habit and ask for a closer check of my next batch rather than arguing about the score.
37. Three urgent requests reach you at 4 pm, and the cut-off for all of them is 5 pm. How do you prioritise?
First, estimate the time each needs and what happens if it misses the cut-off. Say a disbursement takes about 20 minutes and delays the customer's money by a day if missed, a customer refund takes 10 minutes, and an internal report takes 40 minutes. That is 70 minutes of work in 60. I would do the disbursement first because its impact is the hardest, then the refund because it is quick, and at 4:05 tell my team leader that the report needs another person or a new deadline. Telling her at 4:55 leaves no options. Interviewers look for priority based on impact and time, and for early communication.
38. You join a team with 300 pending cases. About 150 arrive every day and the team clears 180 a day. How long will the backlog take to clear, and what would you do?
The backlog falls by only 180 minus 150, or 30 cases a day, so 300 cases take about 10 working days, if nothing else changes. That is too slow if those cases are already breaching TAT. Options: add capacity, for example overtime for part of the team or borrowing trained staff, so that clearing rises to about 210 a day and the backlog clears in 5 working days; process the oldest cases first so TAT breaches stop growing; and look at why cases stay pending, such as incomplete files that could be returned faster. I would track the backlog daily on a simple chart so everyone sees it come down.
39. The sales team keeps sending incomplete loan files, and your TAT suffers. How do you fix this with them?
Use data, not complaints. For two weeks, track which documents are missing and from whom: for example, 38 of 120 files incomplete, most missing the latest bank statement or a co-applicant's signature. Share this with the sales manager along with a one-page checklist for each product, and agree that a file is logged as received only when it is complete. Offer a short session for new sales staff, and give quick feedback on the day a file is returned. When incomplete files fall, say so; recognition helps the relationship. Interviewers want to see that you fix the cause together with the other team instead of only escalating against them.
40. A customer gives a photocopy of her Aadhaar card with the full 12-digit number visible, as address proof only. What should you do?
Under the RBI's KYC Directions, when a customer submits proof of possession of Aadhaar and Aadhaar authentication is not being carried out, the bank must make sure the customer redacts or blacks out the Aadhaar number. So this copy should not go into the file as it is. Ask her to black out the number on the copy, or to give a properly redacted copy, before it is scanned and stored. The Directions also say the Aadhaar number is not mandatory for KYC, so she may give another OVD, such as a passport or voter ID, instead. Never type the full number into system notes, trackers or emails.
Back Office interview questions: Hard questions (experienced)
20 questions41. A private limited company opens a current account. Ravi holds 42%, Meena 9%, a holding company 30% and 40 small shareholders the rest, and Imran owns 60% of the holding company. Who are the beneficial owners?
Under the RBI's KYC Directions, a company's beneficial owner is any natural person who, alone, together or through other legal entities, owns or is entitled to more than 10% of the shares, capital or profits, or controls the company by other means. Ravi at 42% qualifies. Meena at 9% does not on shareholding, unless she controls it otherwise, for example through a shareholders' agreement letting her appoint most directors. The holding company is not a natural person, so look through it: Imran owns 60% of a 30% holder, an interest of 18%, and controls that holder, so he qualifies. If nobody qualified, the senior managing official would be recorded.
42. You lead a video KYC team. Which checks must every V-CIP call pass before the account goes live?
Under the RBI's KYC Directions, V-CIP is a live, consent-based audio-visual interaction run only by specially trained bank officials, with connections from IP addresses outside India or spoofed ones blocked, and live GPS coordinates with a date and time stamp captured. On each call I check liveness and spoof detection; that the face matches the photos on the Aadhaar or OVD and on the PAN; that an offline Aadhaar XML or Secure QR is not older than three working days; that PAN details are verified from the issuing authority's database, for example through DigiLocker, since a printed e-PAN is not valid; and that questions are varied. Any prompting means rejection, and accounts go live only after a concurrent audit.
43. An internal audit sampled 200 KYC files: 12 had no certification by the officer and 3 had expired documents. How do you respond as team lead?
Treat it as a process failure, not 15 bad files. That is 7.5% of the sample; if it was random and the team handled 4,000 such files, about 300 could have similar gaps, so review the whole population or a larger risk-based sample. Fix the 15 properly: certification means an officer compared the copy with the original, so re-verify those customers against their originals or through e-KYC, and collect valid OVDs for the expired ones. Never stamp a copy now as if the original had been seen. Then find the root cause, add controls such as a mandatory certification field and an expiry block in the tracker, and give audit a dated action plan with owners.
44. While processing, you notice a customer's account receives many cash deposits just below a reporting threshold, each moved out the same day. What do you do?
This looks like structuring: splitting cash to stay below a reporting or identification limit, then moving it out at once, a classic money-laundering red flag. The RBI's KYC Directions name the same pattern for any customer, account holder or walk-in, who splits a transaction to stay below Rs 50,000. Do not question the customer, mention it casually to the branch or block the account on your own. Record the facts and report them through the channel your AML policy names, usually the compliance team supporting the Principal Officer, who furnishes reports to FIU-IND. The fact that a suspicious transaction report is made must stay confidential, and operations cannot be restricted only because one was filed.
45. As a team lead, you find that an executive emailed a file with 800 customers' PAN and mobile numbers to his personal Gmail to finish work at home. What do you do?
Act first, then investigate. Report it at once to information security and your manager under the incident process, since it is a data breach whatever the intention. With IT present, ask the executive to confirm where the file went and to delete it from the mailbox, its trash and any device, and get that in writing. Preserve the evidence, such as the sent mail log. The security and legal teams decide who must be told; CERT-In's 2022 directions require many cyber incidents, including data leaks, to be reported within six hours of noticing them. Then fix the cause: give secure remote access for work that runs late, and block external forwarding.
46. A supplier's email asks you to pay this month's Rs 8.5 lakh invoice into a new bank account. What do you do?
Treat it as possible fraud until it is proved genuine, because a change of bank details by email is a common payment scam, and the supplier's mailbox may be hacked or the address spoofed. Do not verify by replying to that email. Call the supplier on the number already in the vendor master, not the one in the email, and speak to a known contact. Ask for a signed request on letterhead with a cancelled cheque or bank letter for the new account, check that the account holder name matches the vendor, and run the company's account validation, such as a penny-drop check. The change then goes through maker-checker. Until then, the payment waits.
47. A supplier that is required to issue e-invoices sends you a tax invoice with no IRN or QR code. Why does it matter, and what do you do?
Under Rule 48 of the CGST Rules, a supplier notified for e-invoicing must upload each invoice to the notified portal and obtain an Invoice Reference Number, and Rule 46 requires the invoice to carry a QR code with the IRN embedded. Rule 48(5) says an invoice such a supplier issues in any other way is not treated as an invoice at all, so your company's input tax credit is at risk. Hold the invoice and the payment, ask the supplier for the e-invoice with IRN and QR code, and scan the QR code to check that its details match the invoice. If the supplier says it is exempt from e-invoicing, Rule 46 requires a declaration saying so on the invoice.
48. How would you set up a check that holds an invoice line when its rate is more than 2% away from the PO rate, or the rupee difference is large?
Look up the PO rate instead of typing it, and test two limits kept in their own cells: a 2% rate tolerance in G1 and a Rs 5,000 line limit in G2. XLOOKUP returns No PO when an item has no order, and ISTEXT stops that text from reaching the arithmetic. ABS catches both directions, since a lower rate can mean a wrong item. Here the cartons are 2.2% over and held; the laptop is only 1.7% over, but Rs 1,000 on 20 units is Rs 20,000, so it is held too; the printer and toner pass; the stapler has no PO and goes back to purchase. Agree both limits in writing with finance.
A B C H I
1 Item Qty Inv rate PO item PO rate
2 Cartons 100 460 Cartons 450
3 Printer 2 1210 Printer 1200
4 Laptop 20 61000 Laptop 60000
5 Toner 10 1015 Toner 999
6 Stapler 50 95
G1 = 2% (rate tolerance), G2 = 5000 (rupee limit per line)
D2: =XLOOKUP(A2, $H$2:$H$5, $I$2:$I$5, "No PO")
E2: =IF(ISTEXT(D2), "No PO", IF(OR(ABS(C2-D2)/D2>$G$1, ABS(C2-D2)*B2>$G$2), "Hold", "OK"))
E2:E6 -> Hold, OK, Hold, OK, No PO49. Your weekly ERP report shows 1,180 pending invoices, but your team's tracker shows 1,240. How do you reconcile the two before the review?
Do not pick the number you prefer; explain the 60-invoice difference item by item. Export both lists with a common key, such as vendor code plus invoice number, and match them both ways with XLOOKUP or COUNTIFS. The usual causes are timing (the ERP extract was taken at 9 am and the tracker updated at 6 pm), definitions (the tracker counts invoices on hold as pending while the ERP shows them as parked), duplicate rows in the tracker, invoices posted in the ERP but not closed in the tracker, and entries made only in one place. Present a bridge from 1,180 to 1,240 by cause, then fix the process gap behind the largest piece.
50. About 900 cases arrive daily, each takes 6 minutes on average, and a person has 6.5 productive hours a day. With 10% leave and absence, how many people do you need?
Workload is 900 times 6 minutes, or 5,400 minutes, which is 90 hours a day. At 6.5 productive hours each, you need 90 divided by 6.5, about 13.8, so 14 people actually working. With 10% of the roster away on an average day, divide by 0.9: 14 divided by 0.9 is about 15.6, so plan a roster of 16. Then test the plan against peaks: if Monday or month-end inflow is, say, 30% higher, check those days rather than only the average, and plan overtime or cross-trained staff. Recheck the 6-minute average every quarter, because new checks or a new system change it, and a wrong handling time breaks the whole plan.
51. Sales and operations keep arguing about TAT. How would you define an internal SLA that both sides accept?
Write down the rules that cause the arguments. Clock start: when a complete file is logged in the system, not when a courier bundle arrives; incomplete files are logged and returned. Clock stop: when the case is completed, or sent back with a query; time spent waiting for the customer or branch is excluded and reported separately. Working hours and cut-offs: files logged after 4 pm count from the next working day. Targets by case type, for example 95% of salaried loan files within one working day and self-employed files within two. Then agree on one source of data, report weekly to both heads, and review targets every quarter.
52. Your team breached TAT on 180 cases last month: 90 waited for branch documents, 45 sat in the checker queue, 27 were hit by system downtime and 18 had other reasons. What would you do?
Start with the biggest causes. Branch documents and the checker queue together explain 135 of the 180 breaches, or 75%, so fixing those two matters more than everything else. For branch documents, find which branches and documents recur, share a checklist with them, and check that genuinely incomplete files stop the TAT clock as the SLA says, since some of these may be measurement errors rather than real delays. For the checker queue, check whether checkers are short at peak hours, and add a second checker or a mid-day priority run. Log downtime with the IT ticket number for the vendor review and the SLA report. Then track the same breakdown monthly.
53. How would you design a quality check plan for a back office team of 12?
Base it on risk, not one fixed sample. New joiners get 100% checking for their first few weeks, and move to sampling once their accuracy stays above the target. Experienced staff get a random sample, say 5 to 10% of cases, with heavier sampling for high-value or high-risk work such as large payments, vendor bank changes and KYC for high-risk customers. Define errors in writing: fatal ones, like a wrong amount or account number, and non-fatal ones, like a wrong remark. Share scores weekly by person and by error type, coach on the top error types, and calibrate with QA so that two checkers score the same case the same way.
54. One executive in your team does 160 cases a day with a 3% error rate, and another does 110 with a 0.5% error rate. How do you manage both?
Look at the cost of errors, not only the volume. The first makes about 4.8 errors a day on average and the second about 0.6, so the faster executive creates rework for others and risk for customers; if his errors are fatal ones, his speed is a problem, not a strength. Coach him on his specific error types and set a target that combines productivity with an accuracy floor, such as 98.5%. For the slower executive, study her method; she may be rechecking every field when only the critical fields need a second look. Pair them for a week. A scorecard that rewards only volume would push the whole team towards the first pattern.
55. Your team spends about 3 hours a day matching the bank's disbursement file with the loan system by hand. How would you make the case to automate it, and what would you check after go-live?
Build the case on numbers. Three hours a day over 22 working days is 66 hours a month, plus the errors audit finds and the TAT lost when the match finishes late; set that against the build and licence cost IT quotes for Power Query, a macro or an RPA tool. Show that the task suits automation: the same file layout every day and clear matching rules on UTR and amount. After go-live, run the automated and the manual match side by side for two weeks and compare them line by line. Then watch the exception queue: if 15% of rows still fail, find out why. Name an owner, and plan for a change in the bank's file layout.
56. You must write the SOP for a new refund processing desk. What goes into it?
An SOP should let a trained new joiner do the work correctly without asking anyone. It covers the purpose and scope, meaning which refunds it applies to; the inputs and where they come from; the steps in the order they are done, with screen names and fields; the check at each step, such as matching the refund amount to the original payment; approval limits, for example refunds above Rs 25,000 need a team leader's approval; TAT and cut-offs; how to handle exceptions and whom to escalate to; and the records to keep. Test it by giving it to someone new and watching where they get stuck, then fix those steps. Add a version number and review date.
57. The sales head asks you to open an account for a large corporate client today and collect the authorised signatory's KYC documents next week. What do you do?
Refuse the shortcut politely and offer the fastest legitimate path. The RBI's KYC Directions say a bank must not open an account or start a relationship without following the customer due diligence procedure, and should not open an account where it cannot apply appropriate due diligence. I would explain that clearly, then help: list exactly what is missing, process the rest of the file now so the account can open within hours of the documents arriving, and arrange a branch visit or video KYC for the signatory if the process allows. If he still pushes, escalate to my manager and compliance in writing. Giving in once makes every big client an exception.
58. The core system has been down since 11 am, it is now 3 pm, and 250 cases are waiting with a 6 pm cut-off. How do you escalate?
Escalate with numbers, not just a note that the system is down. Send one clear message to my manager, the IT incident owner and the affected business teams: the ticket number, down since 11 am, 250 cases waiting, of which 60 are disbursements due today, and the impact if the system is not back by 4:30 pm. Ask for specific decisions: priority for the 60 disbursements once it returns, approval for the fallback process if the SOP has one, and extended hours for the team. Meanwhile, prepare the cases offline so they can be entered fast. Send short updates every hour, and record the impact for the SLA report and the incident review.
59. Your company is moving loan processing from Excel trackers to a new loan management system. What would you test before going live?
Test the system against real work, not only the vendor's demo. In user acceptance testing I would run end-to-end cases of every type, including the awkward ones: a file returned twice, a co-applicant, a partial disbursement and a cancelled case. Check the rules: mandatory fields, maker-checker approval, user roles so that a maker cannot approve his own entry, and the TAT calculation against the SLA rules. Check the data migration by matching record counts and amount totals between the old tracker and the new system, plus a sample of individual records. Check that reports match the old numbers. Plan training, a parallel run of a week or two, and a rollback plan.
60. Tell me about a time you caught an error that had already passed the checker.
Use the STAR method with your own facts; here is the shape. Situation: at an NBFC, during my end-of-day check of disbursement requests against sanction letters, I found a loan sanctioned at Rs 4,50,000 queued for release at Rs 5,40,000; the maker had swapped two digits and the checker had approved it. Task: stop that payment without delaying the other 60 cases in the batch. Action: I pulled the case from the batch, showed my team leader and the checker the sanction letter, and had the entry corrected through the proper reversal. Result: the batch went on time, and the error never reached the customer. End with what changed, such as a system check of disbursal amount against sanction.
Ready to apply?
There are 20 open jobs asking for Back Office on CoreHRx right now. Create a free profile once and apply with it.