---
title: "Revenue reconciliation in Topkey"
description: "Connect reservation, payout, and bank data, review exceptions, and close each month from one reconciliation workspace."
canonical: "https://topkey.io/academy/revenue-reconciliation"
language: "en"
---

# Revenue reconciliation in Topkey

Connect reservation, payout, and bank data, review exceptions, and close each month from one reconciliation workspace.

Product area

Revenue Reconciliation

Length

27 minutes

Presented by

Jason Mraz

Topkey revenue reconciliation brings reservation, payout, and bank activity into one workspace. This lesson follows Jason Mraz’s training from data-source setup through monthly exception review.

## Connect the three sides of reconciliation

The workflow needs reservation data from the property-management system, payout data from the booking channel or payment processor, and deposit activity from the bank. Topkey automatically syncs reservation data from the connected PMS and bank activity from a connected external or Topkey account.

Data-source settings connect supported payout providers. The training demonstrates direct connections for Airbnb and other processors, plus a report-upload path for Booking.com. Multiple accounts can be connected when the operation receives payouts through more than one account.

The sync log records each refresh and lets the user pull historical data when an earlier period needs to be included.

## Set the account rules

Choose which bank accounts should be monitored for payout activity. Auto-dismiss rules can set aside bank activity that is unrelated to reservations, such as interest, without deleting it. Dismissed activity can be restored later.

Optional manual-payment controls allow a user to record an off-platform payment against a reservation when the account’s process requires it.

## Review reservations and their payouts

The reservation view compares expected reservation revenue with payout and bank activity. It shows the property, owner, guest, source, PMS reference, payout details, bank account, and match status for the selected period.

When metadata connects the reservation, payout, and deposit, Topkey shows the matched lines together. Filters narrow the list to the records that need attention.

If an amount is missing from the PMS, add an invoice item and optionally send it back to the connected system. The total updates immediately, which makes an underpayment or overpayment visible. A manual payment can be recorded when money moved outside the normal payout feed.

Airbnb resolution adjustments arrive as their own lines, including increases or reductions to the payout.

## Work the monthly exception queue

The monthly reconciliation view separates payouts into matched, partially matched, pending, and dismissed groups. Summary tiles show how many payouts are fully matched and where an exception still needs work.

A partially matched payout is missing one part of the reservation, payout, and bank relationship. Enter a PMS confirmation code to connect a known reservation manually. When reservations are present but the payout metadata does not line up, select the correct reservation from the manual-match flow.

Manual matches can be undone. Non-payout bank activity can be dismissed and later restored, so the queue stays focused without losing the underlying record.

## Finish the handoff

Once the exceptions are resolved, the reconciled information is ready for the connected accounting system or property-management system. The same source records remain attached for review before that final sync.

## Keep learning

[Read the detailed revenue reconciliation workflow](https://topkey.io/blog/how-vacation-rental-property-managers-match-payouts-instantly-with-topkey-revenue-reconciliation).

## Put it into practice

See how this workflow fits your portfolio with a Topkey specialist.

[Book a demo](https://topkey.io/demo)

Video transcript

\[0:00\] What you're going to learn today is specifically going to be around the new revenue reconciliation tool, but there's going to be more facets to Topkey that are going to be improved and things we can spend some time on in the future. So, definitely let us know what you might be interested in. So, let's go through what a little bit about. First off, myself, my name is Jason Morazz. I'm a senior manager of financial technology consulting here at Topkey. I lead a lot of our customer success practice. O helps us stay in touch with you know all of our customers. you know personally responsible for onboarding clients and keeping those relationships as we \[0:33\] keeping those relationships as we roll out new platforms and new tools. but get the pleasure to work with each and every one of you in the trenches every day and understand some of the pains that you go through. so definitely near and dear to me you know what we'll be talking through today. just as I know it's going to be directly impacting anyone who's in the PM business. So very excited there. again, just to go through a little bit of the agenda here. So, I know some of y'all may already be Topkey customers. Some of you may be interested in Topkey. We always take an opportunity to just talk a little bit at Top Keyy's story. You know, why we exist and who we serve. \[1:06\] You know, why we exist and who we serve. but then we'll jump into what today's skill training is going to be specifically about as far as, you know, how we fit into the picture. What does this actually mean? to recognize revenue here, and then have an opportunity to jump into just some demo of the the walkthrough itself. So, I'll show you how it looks in practice with some actual data and see how that may look like if you were to move forward. Now, finally, we always open it up for some Q&A. So, we're set aside for an hour today, but if we don't use the full hour, we'll definitely have some time to address any of your questions or get you to the right \[1:39\] questions or get you to the right person. Yeah. Just talk a little bit about the short-term industry as we all know that we're in here, right? Finances are complex. It's doubly complex or maybe even triple complex for us because every owner that we're managing their property for is basically a miniature business within the business. So you got a business to run but then you got to make sure that all these individual P&Ls line up specifically for every single owner and everything culminates in these statements that you're putting together for them because if they're going to be working with you directly, right, they want to make sure they're making money and making a good margin. So, some of \[2:13\] and making a good margin. So, some of the errors downstream from that that we're no stranger to are things like cash leakage, messy financials, right? There's some areas that we want to focus on and that's where stopkey sits in. Now, we all know this. There are fragmented systems out there. They're very powerful tools, but they struggle to talk to each other. So, it makes a lot of your back office work really challenging. And specifically in the function of revenue reconciliation is how do we get all that information laid out? Where does where are the payments going? How do we know which reservations \[2:46\] going? How do we know which reservations need to be touched? We we'll go into that here momentarily. But just as a whole, you know, we know that all of these systems don't really talk well to each other. So that's kind of where Top each other. So that's kind of where Topkey sits in the middle. We have Key sits in the middle. We have specifically created a way to integrate into all of those systems to bring it into one dashboard, right? And there is a cost to this. So you can see some statistics here on the screen around \[3:10\] statistics here on the screen around financial friction potential profit loss due to cash leakage or just you know things you're not fully aware of. Visibility challenges make it difficult to know what the true numbers are. So just thinking about this you know how long it may take you to close the month is very painful but also there is a dollar component to that. So something to to keep in mind there as well. Okay. so here's Topkey right we sit in the middle as an AI powered financial operating system. So on the left side there you see all the different platform offerings. Again we've done some previous trainings on things like our expense management and \[3:45\] things like our expense management and bill pay and inventory but today we'll be talking about revenue reconciliation that we're rolling out features contained within those you'll see on the right hand side. But the idea is to synthesize everything into a place where we can, you know, of course have visibility and give you back time to put the the money you save back into growing the business, right? How can you actually go work with more owners? So, talk a little bit about that. don't take my word for it. We do have a little bit of pride here in our customer satisfaction and retention rate, working \[4:16\] satisfaction and retention rate, working with over 300 managers today. and across that portfolio is tens of thousands of properties under management. we have several over here on the right hand side they have u positive things to say about us so definitely I'm sure they'd be willing to chat with you maybe this is one of you sitting in the audience so very excited and thankful to be working with each of you individually and to be of service okay so the fun part revenue reconciliation so we just talked about a little bit what it's going to look like to come onto why we exist but I do want to jump into just a demo \[4:52\] want to jump into just a demo environment have an opportunity to show you the revenue reconciliation view, why it's built, and how it works in practice. Right, we'll schedule some time here at the end just to walk through a quick Q&A. So, while I do that, shift over here into just a demo environment. environment. All right, All right, so if you're a customer, you're used to seeing a similar dashboard. What we're going to point our attention to is this Revub section over here on the left hand side. So, what I'd like to \[5:23\] the left hand side. So, what I'd like to first do is talk a little bit about the setup and then we'll show it in action. As with everything else in Topkey, it always has to do with the integrations. Where can we get the data from? In order for revenue reconciliation to work well, we have three major things that we need to have plugged into Topkey, which if you're already on Topkey, you have two of those three. The first thing being your PMS. That's where all the \[5:47\] your PMS. That's where all the reservations take place. So by nature of being plugged into the PMS in this case, we do integrate with all major PMS systems. So don't let this particular demo think that it's just for guest. We plug into all major PMS systems. Just for today, we're going to be referencing guest. guest. That integration is going to give us access to reservations. You can actually see that here synced automatically. And part of setting you up, something that I would do with you or whoever your account manager might be, we'll go through and understand what information we need to pull from the PMS. Part of that is the reservation and we'll put \[6:22\] that is the reservation and we'll put that at an automatic sync for you. The second component that I mentioned is the bank. So through your initial setup, you're also going to either connect to an existing bank or will utilize Top Keys banking solutions. Either way, all of that activity does need to be referenced in some way. Okay, I'll show you how simple it is to set that up. And the third thing being the OTAA, the payment processor, or wherever the payment's originating from. And that's mostly here on this data sources page. So once you have those three, this enables us to take a look at all of the \[6:56\] enables us to take a look at all of the information that's in flux across those, pull together the like information, and automatically recognize and and reconcile the revenue against all those different lines. So that said, let's take a quick tour through the data sources as a function of the setup. We try to make it super easy for you. This page is mostly an overview page. So in practice, you wouldn't really be doing work on this section. You're just going to be connecting to all of the information that we're going to want to grab access to. So part of that is of course PMS, but Airbnb as well. So we \[7:33\] course PMS, but Airbnb as well. So we uniquely have a direct API to Airbnb which gives us direct access to the payout information as well as resolutions. So this is unique to us and allows us to have a more secure integration and give us more accurate data. Stripe as well. So, if you're utilizing Stripe for any sort of payment processing through direct booking engines, maybe VBO or other tools, we've built an application that allows us to get access into that. So, we'll just sign into that. And you may also \[8:06\] just sign into that. And you may also see that it does say connect another. This is also applicable to Airbnb. So, if for whatever reason you're managing multiple accounts on each of those, we can gain access to each of those and allows us to see all that activity. Okay. Okay. One thing we can also do is change the import date. So, as a function of setup, we may stick this into the past or maybe, you know, year to date, right? If we're getting started today, we're halfway through the year already, but maybe we want to look, you know, see how well we're doing already yearto date, we can go back into the past and pull that \[8:39\] can go back into the past and pull that information. information. Everything will be captured here in the view sync log. So, you can see all the activity, right? And we again let you know up here, hey, by the way, this is purelyformational. slot where you'll be working, but it is helpful to have in the event that you need to troubleshoot something or just see some more details. Right? So, all that would be outlined for you here. So, back it up screen. Similarly, you'd see that on Stripe. Now, when I scroll the page, you're going to find all of the other integrations that we integrate with as well. all major \[9:11\] integrate with as well. all major payment processors we would integrate with. We want to make sure that we have access to some of these as well. you know things like Brain Tree we actually do integrate with. I got to update this account here but just let us know if there's any unique ones you may be using and we'll be sure to latch on to those. want to call out booking and Marriott as well uniquely to this as a function of our process to reconcile some of this revenue. We do have to upload a CSV. so what we'll do is just click into this and we'll just give you a quick template over here on what that should look like. \[9:45\] on what that should look like. It's actually the same exact format you'll get from booking.com. So if you run your payout report, you just have to plug it in here and we're automatically going to start reading that and making those associations. those associations. Additionally, you have a quick hyperlink here to the integrations page directly from the data sources which jumps into your settings which if you're on top your settings which if you're on Topkey, you know, you're used to seeing key, you know, you're used to seeing that sort of thing and going there \[10:08\] that sort of thing and going there outside of this page, but it's just a hyperlink to get you there fast. All right, before we move on, I do want to actually hop back into settings and talk about one other setup step that we'll need to consider before we talk about actually reconciling the revenue. So, we'll have a separate Revub section here. And I mentioned that one of those other components was plugging into the bank account. So, in my account here, I have one Topkey bank account. If you have external accounts, all we really \[10:39\] have external accounts, all we really need is access to the debit credit activities. So, if you're receiving your OTAA payouts into one or multiple accounts that might be external to Top accounts that might be external to Topkey, maybe you've not transitioned to Key, maybe you've not transitioned to our trust accounting just yet, we can actually opt into those, provided they're connected. It's as simple as this toggle right here. Clicking the toggle just narrows our focus to look just at that bank feed. So, we're not actually getting confused by looking through multiple different accounts. You're just telling us where to point our eyes and and what to look at as far as the mapping goes. \[11:13\] auto dismissal. You'll understand this in a sec when we take a look at reconciliation, but we have a rules engine that allows us to look at the bank activity and basically say these are some areas you don't want to point your attention to because it doesn't have anything to do with recognizing my income. So, we can actually put a pattern to look into as far as the bank feed text, right? It is case sensitive or case insensitives rather. So the punctuation doesn't quite matter so much as what the text is that you've written out. So in my case, I've just created a rule here for the word interest because \[11:47\] rule here for the word interest because I know that I'm using a Topkey account. I'm earning a higher interest on that account, which is helpful for me, but also doesn't really have anything to do with a reservation, right? That's separate to that. So what I've said here is I just want to ignore any of those lines that come through. So it's not telling me I have something that's not matched. matched. We can create any number of those. By the way, you can enable or disable them at your leisure. And anything that is automatically dismissed, we'll be able to go back in and actually pull back if there's any sort of issue or anything. Nothing's ever permanently \[12:20\] anything. Nothing's ever permanently removed. removed. Manual payments as well. So, we have the ability here to mark payouts as manually paid. there is a bit of a risk here. so, that's why we give you a toggle. And the reason being is, you know, there may be payments that are coming through that are recorded mistakenly or maybe the payment just has yet to occur and then in the future we may get a payout and it it may look like you have a duplicate, right? So, we're trying to remove any sort of manual intervention. \[12:51\] remove any sort of manual intervention. but depending on how fast you're moving, right? Or maybe you you have different payout cycles. We want to give you the flexibility to say hey this is paid on this time from this bank and so on. so we do give you the flexibility to enable that. Everything we're going to go through today is also going to be permissions driven. So we are still very security focused based off user roles and permissions. We'll be able to adjust hey who has access to you know perform any of the functions we're taking a look at. Okay right so let's just jump into what the day-to-day would look like. So, we'll go \[13:26\] day-to-day would look like. So, we'll go into the reservation section here inside of Revub as well. And at a glance, we're just going to give you a quick overview. Up top, there's a couple tiles here. And right now, we're setting it by the check-in date over the last 30 days. We've made this highly customizable. So, when we go through the setup flow for you, we want to look at when you want to recognize this revenue. So, in my case, I've set it by check-in date. Maybe some of you are thinking about booking date or checkout date. There's different methodologies. That's a function of our setup. We talk through with you when we go through to enable it for your account \[13:59\] go through to enable it for your account and we'll make sure that that's set up for you as we go. Up top, we're going to see over that time frame, the last 30 days in my case by checkin, what is the expected reservation revenue, right? So, there's a number of reservations that have come through Guesty and I'm expecting this $30,000. $30,000. In that time frame, I've received around 26,000. So, that's about 84%. in terms of payout. And what this 84% represents is we've actually already taken those and associated that through those three items, the reservation, the \[14:35\] those three items, the reservation, the OTAA, and the bank fee. And you can see that displayed here. So, we give you information that's helpful to locate these, right? You'll see reservation information with a source through the property, and there's the owner, guest info, check-in dates, what you've expected, and what you've received. So very quickly you can see hey what's actually paid and the importance here is we want to fixate on that 16% those exceptions. So historically you're probably very used to looking at a payout as it comes into the bank feed from Airbnb. Maybe it's fairly modest. \[15:09\] from Airbnb. Maybe it's fairly modest. It could be a large amount and it's kind of your responsibility to go figure out how that is is broken down. For our purposes, due to our direct integration to Airbnb, we get all of that metadata. So, we could take at that lumpsum payout and we could automatically apply it across all the different reservations. So, for example, if we look at this paid one for 1,200, we'll go ahead and pull it up here. And this is the reservation payout screen. So, again, the information that you can \[15:41\] So, again, the information that you can filter by in that feed is going to be shown up top, which is a quick reference. So this is the reservation reference ID from the PMS. This would look different depending on your PMS there, but it's going to be in the same place. On the left hand side, these are all of the invoice items that come directly from that reservation. So what's expected, right? And that's already broken down for you. You should already expect to see that. What's going to be your income as far as rental revenues, your nightly rates, discounts, cleaning fees, and so on. It's going to be netted out for you in terms of what we're looking for. \[16:14\] looking for. And then on the right you'll see the actual payout activity. So we've noted here that there's an Airbnb payout to this bank account 7109 for 1230 exact match because in the in the metadata we found the same reservation reference. So we'll give you kind of a breakdown of how we identified that just so you can validate it and already do this match for you. So this is fully balanced, right? This allows us to downstream ultimately go ahead and take that log those post those as needed. \[16:48\] those post those as needed. In the event of needing to make adjustments manually, that's where this add button comes into play. We could click add here, choose a category, right? This is originating from the PMS. So, let's just say that we had a late checkout fee that needs to get added to this that was not captured. We can go ahead and add these here. We're going to be stingy and charge them $250, but you can go ahead and add that there. Any notes that are internal here are optional to you, right? We could \[17:21\] are optional to you, right? We could go ahead and add those here. But by the function of adding the invoice item, basically we're creating an additional line here. We're going to have the option to push this back say to Guesty. So there's kind of a birectional sync there to keep par between the systems. So you can kind of trust either one as you know kind of your source of truth there. So we add this invoice item, right? And what happens by this is we've adjusted this. So I'm expecting somewhere that there's a late checkout fee of this additional $250. now it shows as underpaid. So it's \[17:54\] now it shows as underpaid. So it's dynamically updating because we're expecting information that's going to come through later. In the case of Airbnb, if a resolution adjustment was updated, we may get this on a successive sync as it comes through from Airbnb. Those do take place nightly. Not sure if I mentioned that. So, the automation for these are they're being synced every day as in the newest round of payouts. Okay. And what'll happen is that'll get cataloged here and it'll bring it up bring it up to being fully balanced. We can also utilize the manual mark as paid like we enabled there in your settings just to say that we received this \[18:32\] today's date. Record the payment and now it's back to being balanced. Again, that would not be a common case, but it may be the case in which you have a record of this and need to make sure it's balanced in a pinch. but we would expect that this would update retroactive. Similarly, we'll be able to find things that are over underpaid. We have a direct filter for this here in payment status to help you highlight those exceptions. exceptions. I'm actually going to shift this back a little bit just so we have some more examples. Here's an example of an \[19:07\] examples. Here's an example of an overpayment. If I pull this up here, you're going to see that the PET fee was not logged into the PMS, which is a great opportunity for us to add that manually here just to say there was a $150 that didn't get logged. We can put it on there to make sure it's balanced. Let's do that real quick. And there we are. That would be the case if we got more money than we expected. But if we were underpaid, we might be waiting for a future payment to come through. So \[19:44\] future payment to come through. So similarly, we don't always have to add these here as there may be a time where that comes out u through a successive payout. We do want to monitor these actively of course just so we know where all the activity is going. All righty, let's go ahead and reset this back to where we were. You also find a column here for the resolution center. So, I'm going to set this back and we'll be able to very easily see that resolution payouts are going to be captured here as well. So, as those \[20:16\] captured here as well. So, as those adjustments are made, whether the dollar amounts going up or down, we're pulling that through directly from Airbnb. It's capturing things like damage reimbursements, and it's getting its own line. So you can also see that the payout even though it occurred on a future date, original payout here took place on the 25th. We got this one on the ETH. We were still able to go back and retroactively and retroactively balance this one. Again, all these were hands off. You saw where we were just making those slight adjustments, but we're trying to highlight that 10 to 20% of exceptions. \[20:48\] highlight that 10 to 20% of exceptions. Of course, close that gap as much as possible. possible. So, what can we start to do after we manage all of that? Well, we do have to reconcile the month. So, we do have these broken down by monthly periods, and we can move through these by, you know, closing them out as you go through each month. each month. We'll go ahead and click into one of these examples. Let's just hop into June here, just to reconcile. So, we have that pulled up. Just like the data sources section and the reservations section, we're going to \[21:22\] the reservations section, we're going to give you some tiles right up top with the information you need to know. On the left, we're looking at payouts. So, at a glance, you could see in the month of June. So far, we've received 42 payouts and 34 of those are fully matched. Right? I didn't touch any of those. We took care of all of that. But there's a slight exception, right? We have three that might be partial, some that are unmatched. They're in some varying state of balance, but we want to make sure we we get that right and we take a look at those. So, that's highlighting just what you do need to focus on. And then we're \[21:53\] you do need to focus on. And then we're also going to have a section to the right that is triaging some of these ones that we're a little confused about, right? It's there's really no information telling us about if it originated from an OTAA somewhere or really what we need to do with that. So, we want to highlight and say, "Hey, there's also some money in here. you need to tell us what to do with that. Okay, Okay, these are also broken down by columns. So, we're looking at mass here. Here's \[22:16\] So, we're looking at mass here. Here's those 34. those 34. And what's great about this is we'll be able to come through here just like before, see all the different reservation information, things like owners, right? I can click onto these and it's going to very similarly pull up the payout information that we were just looking at. So, you can access this from a couple different places, but this is just giving you insight as to what's fully balanced here. You can get to this as well by clicking into just this eye icon over here, right? You'll get a little bit more information broken down because the bank transaction is going to be shown. So in \[22:49\] transaction is going to be shown. So in this case, this was paid out from Stripe. Stripe. On the right hand side, it's going to give you information about the reconciliation. So we could take a look at things like our matched items and it's going to update for us and it's going to give you the reservation breakdown. So, in the event of this thousand, if this covered multiple payouts, we'll be able to see that. Sure, we could find a quick example in here. here. Two items found. So, this is a great example. Let's take a look. And there's each of the lines. \[23:22\] So, that's all and good. I could quickly scroll through here and see everything that's paid out, even these higher volume ones. This $2,000 one, right? This might just be a larger reservation, but in the event there being multiple items, we'd be able to show that. Now, moving towards the right, we can look at some of these that are not fully completed. These partial matches are not fully reconciled. So, we do need to make sure we do something with that. So, if I want to look at this second one here, I'll pull it up and it's going to say, hey, what's the status of this? Well, this is partially credited because \[23:53\] Well, this is partially credited because we are missing reservation data. So, usually this is a function of there being one of those three items. I keep returning back to just not being fully aligned. Again, the OTAA, the bank activity, and the reservation. You can see over here that we give you a breakdown like we looked at on the fully reconciled one, but letting us know there's something going on with this $760, $760, right? We want to make sure that we can take care of that. We built in the manual match for you because we want to be able to make sure that it's fully confirmed. So if we have that confirmation code from the PMS, you can \[24:27\] confirmation code from the PMS, you can just enter that identification code here and just go ahead and match it manually. That's how you do that by hand. Inside of pending, there's even less data. So we want to make sure that you know you're we're getting all the information in the right place, but it's not necessarily a bad thing. Could be a timing issue, right? In this case, we couldn't find the payout. So we have the reservation information but maybe the payout hasn't occurred. There might be a discrepancy with the ID. This is helpful \[25:00\] discrepancy with the ID. This is helpful to know because you know there may be some sort of discrepancy. So what we can do here also is click on the manual match and it's a separate manual matching here because we have the reservations but maybe because of something with the ID you'd want to go in and associate those separately. So, in my case, you can filter these out. I know that this one's Airbnb. I'm just for the sake of example here going to grab a couple quick examples here till it adds up. And you can see that it's adding those on there. So, once you match, it's going \[25:33\] on there. So, once you match, it's going to pull those together. It'll balance it and they'll all then be referenced. I did allude to earlier that we can always undo. So you do have this unmatch option. Go ahead and click on that. It's going to revert back for us. That'll go back to the pool. Finally, we do have this mississm here. So we do have insight into that, right? What are we going to do with these that are not really relevant to that? Oh, it looks like there was some money movement \[26:07\] looks like there was some money movement between accounts. So we dismiss that. We don't we're not looking for a payout here to match that 2500, right? Let's say for example it was you could restore it if you need to. We also give you a quick toggle up here in the top right if you want to jump between periods or we can just jump back to that primary reconciliation page. As these are fully balanced, they start to close out each month. So you can move forward and make sure you have full balance and visibility there. downstream from that you'll eventually be able to take that information and of \[26:45\] be able to take that information and of course push it externally just like we're used to doing with all other functions inside a Topkey. So if you need to get data into the accounting system we'll allow you to sync it. If you need to push things back to the PMS that's there as well.

## Disclosures

\*Topkey is a financial technology company and is not an FDIC-insured bank. Banking services provided by Thread Bank, Member FDIC. FDIC Insurance available for funds on deposit through Thread Bank, Member FDIC. FDIC deposit insurance covers the failure of an insured bank. Certain conditions must be satisfied for pass-through deposit insurance coverage to apply. The Topkey Visa debit card is issued by Thread Bank, Member FDIC, pursuant to a license from Visa U.S.A. Inc. and may be used anywhere Visa cards are accepted. The Topkey Visa charge card is issued by Thread Bank, Member FDIC, pursuant to a license from Visa U.S.A. Inc. and may be used anywhere Visa cards are accepted.

Accounts are eligible for pass-through deposit insurance only to the extent pass-through insurance is permitted by the rules and regulations of the FDIC, and if the requirements for pass-through insurance are satisfied. There may be a risk that pass-through deposit insurance is not available because conditions have not been satisfied. In such cases, funds may not be fully insured in the event the insured depository institution where the funds have been deposited were to fail.

\*\*Your deposits qualify for up to $3,000,000 in FDIC insurance coverage when Thread Bank places them at program banks in its deposit sweep program. Your deposits at each program bank become eligible for FDIC insurance up to $250,000, inclusive of any other deposits you may already hold at the bank in the same ownership capacity. You can access the terms and conditions of the sweep program at https://thread.bank/sweep-disclosure/ and a list of program banks at https://thread.bank/program-banks/. Please contact customerservice@thread.bank with questions on the sweep program. Pass-through insurance coverage is subject to conditions.

1 | The interest rate on the High Yield Deposit Account will be 2.93% with an Annual Percentage Yield (APY) of 2.97%. The interest rate on the Regular Deposit Account will be 1.52% with an Annual Percentage Yield (APY) of 1.53%. These rates are effective as of 9/17/26. These are variable rates and are subject to change after the accounts are opened based on the Federal Funds Rate. Minimum opening deposit and average balance requirements may apply. Fees could affect earnings on the account.

Topkey does not provide tax, legal, or accounting services. All information on this site is for educational purposes only.