Daily Time Sheet 2.Xls: Fill & Download for Free

Every Balance Sheet account should be reconciled on a daily, weekly, or monthly basis (depending on how big/complex your ops are). Let’s break it down…ASSETSBank Accounts: self explanatory.Accounts Receivable: check your AR Aging. Do you have any severely past due accounts that should be written off? Do you negative line items that indicate that you may have over/under recorded a transaction? Do your records match your clients records?Current Assets: if you have prepaid expenses, now is the time to reconcile them against external xls workpapers.Fixed Assets (And Depreciation): do your records match what you actually have on hand? Were their spoilages, theft, damages, or changes in fair market value?Inventory: do your records match what you actually have on hand? Were their spoilages, theft, damages, or changes in fair market value?LIABILITIESAccounts Payable: check your AP Aging. Do you have any severely past due accounts that should be written off? Do you negative line items that indicate that you may have over/under recorded a transaction? Do your records match your vendors records?Credit Cards: self explanatory.Current Liabilities: if you have accrued expenses, now is the time to reconcile them against external xls workpapers.Payroll Liabilities: ***I cannot stress this enough*** if you have any sort of balance in this account you need to be reconciling on a regular basis. These payments to tax agencies (IRS, FTB, etc) are real, and they want their money on time. Knowing exactly how much you owe every month is critical. I’ve had clients come to us without ever reconciling their Payroll Liabilities and untangling the mess cost thousands and thousands of dollars to unwind. This is a key pitfall feature of Intuit Online Payroll. These sorts of messy reconciliations don’t happen when you’re on Gusto.Notes Payable: record and reconcile interest paymentsEquity: match it and reconcile it to the cap table.Bottom line, the three other accounts (besides bank and CCs) that you should have your eye on when it comes to reconciliations are 1) Payroll Liabilities 2) Accrued Expenses and 3) Prepaid Expenses. The reason why you want to reconcile these accounts is because the Balance Sheet can be a vehicle to create and hide phantom revenues and expenses. Don’t get caught by surprise; reconcile and verify each account.

I have a lot of experience with this particular question as I’ve written a ton of tools for a few companies years ago.First of all, don’t leak the code to an external web app without the consent of your boss. Even though your tool doesn’t contain any business sensitive data itself, it will expose at least some sort of information about your workflow. I agree that you might think that what the tool exposes is basically meaningless, but I’m not sure if the action itself is legal if you don’t have permission from an internal authority.It is easy to technically hide VBA tools from your boss. VBA requires a host application to function (presumably a MS Office application), and the code that you write is merely a part of the file that you store on your hard drive. You don’t even need to expose the file extension on your hard drive, you can access your tool from USB if you want to, and run the application independently from the external resources on which you’re operating.In reality, depending on your particular situation it may be very hard to hide the fact that you are using tools. Sooner or later they will notice that something is off; as routine becomes part of daily life, they will notice that at times you don’t seem to be doing much while the work gets done. This can only mean that you’re dealing with some sort of automation. If you have colleagues, they will notice that you’re clicking buttons sooner or later and they will try to figure out what you’re doing.Now your boss most likely won’t mind and may even be surprised by the unexpected power of VBA. He’ll see the error margin drop, and work getting done faster. He may congratulate you for your good work, perhaps ask you to create a few more tools, and you may even get a raise and more authority. This isn’t very unlikely and it happened to me at my first serious job: as you learn to develop the tools, you become very familiar with the business flows (more than usually required). You’ll get the opportunity to teach others, and your manager sees you as some sort of technical wizard since nobody has possibly done what you did before. In order to create the tools, you obviously have to understand the business first. Profoundly. Business people usually like to see fast results and VBA makes it very easy to deliver. So everybody is happy. Or not?Some caution is required. (Note that what I tell you next is not an answer to your question, just some thoughts that I want to share).VBA is a very controversial solution to business automation and not without reason. I have written a ton of Excel and Access tools with VBA in the past and I have been a first class witness of its possible consequences. Be aware that for business people other than yourself, VBA tools are basically a magical black box and potentially result in disastrous consequences for stability of business continuity.As you automate your work, the newly delivered speed / quality quickly becomes the standard, and it’s only a matter of time when shit hits the fan. When you’re not available and someone else takes over your work, bang, a bug appears. Everyone looks at you as being the evil guy who created the black box and left everyone else helpless. Some day, another guy who knows some VBA supports the tool and adds some code “on top of” (literally) what you’ve written, without actually understanding how you constructed the tool (if there is any structure in it - at all). It becomes a literal mess. I’ve analysed a VBA tool which had existed for 10+ years, and it took data from a ton of Excel sheets, for which most administrators didn’t understand what the data represented anymore. Ridiculous business flows occurred (in one of the largest existing energy companies of which I’m not going to mention the name) like communicating data between departments through Excel attachments in automated Outlook emails. One department sent the xls, the other department retrieved it from the mail, based on the subject title and/or attachment filename of the email. This data contained exchange and auction information, and was sensitive. It was total madness, looking backward. Some day some auditors come along and want to see the data but guess what…. the name of the xls files changed, the template structures were changed over time, the subject of the emails changed, etc.If you happen to work for a large corporation, don’t count on any help from the IT department and there are in my opinion three main reasons for it.The first reason being that the largest benefit of VBA is also it most dangerous feature: the fact that you don’t have to be a programmer to write usable code. Most tools I’ve witnessed (including the tools that I have developed myself during the first years) are all written in procedural fashion. Opposite to common belief, VBA is a language that offers object oriented features, and one should understand and use them! Most development I’ve seen from business people happens in random VBA modules without giving any consideration to basic principles like encapsulation. Most business people writing VBA assume that a module is “the place where you write code”, but this isn’t how it is supposed to work. So what you’ll often see is one large module with all the business knowledge written in one giant “blob” with a ton of code duplication and worse, code that is even plain redundant but happens to be past leftovers. If you throw a lot of nested loops with “offset” into the mix, you’re in for a world of trouble. Not using basic good practices like parameter sheets and named ranges to make code more dynamic turns it into an absolute abomination. Maintaining the code becomes worse than hell and if you’re the guy who happens to know VBA, be sure that over time they’ll be at your desk daily to solve annoying bugs (for tools written by yourself, but also - and probably worse for you - others).The second reason being that writing a VBA tool usually doesn’t precede the required system analysis to build solid software. Without going into detail on the topic, it is usually clear that VBA tools are written “on the fly” and miss solid ground. This means that they are quickly modified over time, another reason why these tools have the tendency to quickly turn into an unmaintainable mess.The third reason is that VBA is a dying language although Microsoft can’t seem to get rid of it, even though they have tried it in the past. My guess is that too many businesses still depend on it for business continuity. The reasons why it matters is because I don’t have the impression that there is a good community who is willing to bring some unity for stable VBA app design. I’ve read a few books on VBA in the past, and they don’t explain what really matters for a business; which is how to write stable VBA tools in a way that prevents (or at least reduces) the previously mentioned problems from happening. Writing standard frameworks / modules could help; they possibly exist, but I haven’t seen any dominant player during my VBA years.I could probably give a ton more thoughts on the subject, but I’ll leave it at that. Anyway, good luck. Just be warned not to write tools that grow out of proportion. :-)

Hi there, I'm finding an app which I can enter data and export it to *.csv, *.xls and etc. I want something like a mini spread sheet to store data.For example I want to take note how much time takes to arrive home daily and after 2 months I export it to excel.Please tell me if you know something.