Getting started

Teller not working: filling the gap when a bank feed stops

Teller not working or a bank feed stopped? How to measure the gap, fill it from statements, reconcile the balance and avoid double entries.

Editorial illustration for Teller not working: filling the gap when a bank feed stops

When Teller, or any service that pulls bank transactions into another tool, stops working, the practical problem is a gap: days with no transactions in your records. First measure the gap, then fill it from official statements, then reconcile the balance. Teller is a developer-facing service and we cannot describe its dashboards, limits or policies, so for fixes on the service itself use the provider's own documentation or support.

How big is the gap?

Find the date of the last transaction that arrived and compare it with today. In a sheet with dates in column A, =MAX($A$2:$A$1000) returns the latest date, and =TODAY()-MAX($A$2:$A$1000) gives the number of days since the last row. If the result is 9, you are missing about nine days of activity, and anything after that date in your records cannot be trusted.

Why do feeds usually stop?

  • The connection to the bank expired or needs to be authorised again.
  • The bank changed something on its side.
  • A credential changed and the stored one no longer works.
  • The service itself has an incident or a limit has been reached.
  • Your own application stopped refreshing.

Which of these applies is a question for the service's logs and support. Do not enter a banking login anywhere unless it is the provider's own, documented flow.

Worked example: fill and reconcile

Say your last good row is dated the 3rd with a balance of ₹52,400, and today is the 12th. Download the bank's statement for the 4th to the 12th from your own net-banking. It shows five debits of ₹1,200, ₹560, ₹3,400, ₹780 and ₹2,150 (total ₹8,090) and one credit of ₹15,000. Expected balance: 52,400 - 8,090 + 15,000 = ₹59,310. If the statement's closing balance is ₹59,310, the gap is fully filled. If it is different, one row is missing or misread, and you find it before it spreads.

StepWhat to doCheck
1Measure the gapLast date versus today
2Download the statement for the gapOpening balance equals your last good balance
3Add the missing rowsRow count matches the statement
4ReconcileClosing balance equals the statement

How do you avoid double entries when the feed returns?

When the connection works again, it may resend rows you already filled by hand. Before switching it back on, note the date range you entered manually and, afterwards, search for pairs with the same date, amount and description. A formula such as =COUNTIFS($A$2:$A$1000, A2, $C$2:$C$1000, C2) greater than 1 flags candidates for review.

Is there a way to work without a live feed at all?

Yes. SpendixAI does not connect to banks and never asks for net-banking logins. You pick the account, upload the statement as PDF, CSV or Excel, review the rows and save. Possible duplicate imports are flagged, and a Possible duplicate charges report lists the same amount to the same merchant within two days, which helps if two uploads overlap. The trade-off is that you do the upload yourself, say monthly, instead of having rows arrive on their own.

What should you check about the transactions themselves?

Once the gap is filled, scan the rows for oddities that often come with feed problems: the same description twice with the same amount on the same day, a missing sign on a debit, or a date that sits outside the range you downloaded. Sort by amount and walk down the list. This takes five minutes and catches most of the errors that would otherwise surface in a report months later.

Before you contact the provider

  1. Write the last good date and the first missing date.
  2. Copy the exact error or status message.
  3. Say what changed recently on your side.
  4. Ask whether re-authorisation is needed and how to do it safely.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports