 These line items, which are the income statement side, are assigned to the customers. That's why it breaks out the income statement properly, I believe, and not the checking account. Save it and close it, and then run it to the right, running. And so you can see here, it didn't break out the cash account like it has been breaking out nicely the AR accounts. So if I go to the tab to the right, run it, then now we've got our another sub account here on 512. So it can get kind of an extensive sheet here, but you can see it works, it does its thing quite nicely in a job kind of system so I can break out my income statement by customer, although it gets a little bit tedious, so a little bit redundant because you have this concept of the customer and then the sub customers and then the total. So, I mean, you have basically two extra columns here. I mean, sometimes it'd be kind of nice to just run the report by just the jobs, to see the open jobs and not having these two redundant columns, which can make your report really long. If you were using class tracking, then you can do it that way, right? You could sort it by job and it's a little bit shorter of a report. Then you got customer two, which has the sub customer, sub customer, and the total for customer number two, and then the total income statement. So one of the primary things that is nice here is that you can run this report that has all of the customers in it and it's got the total so that you can tie everything out to your actual financial statements, as opposed to like tags or sometimes when you go into the project reports, just the individual reports, they just give you the income statement activity, by that particular project or job. Great, that's great to zoom in sometimes like that, but it's nice to be able to see the whole, everything tied out so you can tie it out to your financials. Then you can filter this kind of report by going to the customize up top and you can use your filtering options. And if you were using other kinds of things as well like classes and location tracking, then you can filter, you can run the report by customer and filter by location and class tracking, right? That's one way that you can do it. If you don't have location and class tracking, then you would most likely filter by customer. So if I wanna focus in on one customer or one job, I can say let's just take a look at that, let's take a look at that 415 customer only and run it and I didn't do anything for 415 apparently. Let's run it again, wrong pick, don't pick that one. Let's do it for 410, 410, run it and so there we have it. Now again, it's a little bit tedious even when you do this because the subcustomer is tied to the job so you're gonna have the customer and then the subcustomer, the subcustomer is tied to the customer I mean. So you got the customer, the subcustomer and then the total and then the total over here but that's not too bad to deal with, right? So now you can zoom in to each individual job by filtering to each of those individual jobs. So it's a workable kind of system. Now note that the primary thing that happened after subcustomers were in play is the projects. So if you go over to the projects, then like if you were using subcustomers before in another accounting system or jobs before in QuickBooks desktop or subcustomers in QuickBooks online and then they added the jobs, then the question is, well, do you wanna convert everything over to, I'm sorry, then they added the projects. The question is, do you wanna convert everything over to projects? And I mean, if you have a system that's working maybe it's not worth it but they have some conversion concepts that you can look at to try to convert everything to projects but it's still kind of a scary task to do. But the projects are different. They work in a similar fashion. So we'll talk more about projects later but you'll see that basically you have your own kind of area that's separate from the customer area that sorts the projects and you've got a little bit more of the sorting tools down here for the projects as opposed to the jobs and then you could run the reports by project. So do the projects then make the jobs or subcustomers obsolete? Not necessarily, because again, you could imagine that you're using subcustomers quite well and thank you very much. I'm going forward quite well with them. You might keep going with that. The projects also add some features like sometimes when you're trying to integrate payroll and stuff into the projects but you might still use the jobs or you could say, hey look, I would like to have a use the projects but let's say I wanna tie them to a job. So now you can say I'm gonna make a project that ties to a customer. The projects ties to the customer in a similar way as the subcustomers or jobs tie to customers even though it's not in the same window but you might say, hey look, I've got a customer and then I've got the subcustomer which has a different billing address to the other customer. So I would like to say yes, it's tied to customer number one but I wanna make the project tied to the subcustomer. So you can see the tiering action you might have customer number one, then the subcustomer and then you might tie your project for some reasons to the subcustomer. So if I make a project for example, I have to tie it to a customer instead of actually customer number one, I could tie it to a subcustomer which might be useful for like billing type of purposes. So obviously the subcustomers haven't gone away. They haven't removed the subcustomers. They are there in a system where you might need them if you don't have access to the projects possibly even if you have access to the projects if you're using the subcustomers and you're content with the subcustomers because that's what you've been using. Then the question is, do you wanna try to convert all the subcustomers to projects or are you good going forward with the subcustomers? And then of course you could still use the subcustomers in conjunction in some cases with the projects even if the projects are kind of taking over some of the functionality that the subcustomers would have done in the past. So we'll get into projects more in future presentations.