Invoicing is one of those tasks every business has to perform, whether big or small. Whether you have one thousand employees or one employee. If you are a Limited Liability Company, (in the U.S., LLC) raising invoices is mandatory when doing business. They are used for record-keeping purposes, as well as being a handy way for you to keep track of what a client owes, and what has been paid. in this guide, I will show you how to prepare an invoice by hand, and then how to prepare and send invoices using WordPress. This last part will be useful especially if you use WordPress to conduct your business.

Preparing An Invoice

This guide walks you through preparing an invoice, but I’m assuming you have already discussed with your clients what the payment arrangements are, and that they are in writing so that both you and the client have a copy. Having a written copy of payment arrangements, (as well as documentation for other parts of the project, such as scope, deliverables, ETC.), means that everyone is on the same page and knows what to expect. The invoice is part of that process of communication. it details how much is owed, how much work has been completed, and how payment should be made.

What Should An Invoice Include?

The first thing your invoice should include is company or contractor details. These are:

  • Company or contractor’s name
  • Company or contractor’s address
  • Company or contractor’s telephone number
  • Company or contractor’s email address

Invoice Number

Each of the invoices you generate should have its own number. The numbering scheme you use is up to you, but the numbers should be in sequential order. This is so that you can keep track of outgoing and incoming invoices, and so that you have something to refer back to if questions arise.

Dates

Your invoice should include two dates:

  • The date the invoice was raised
  • The date the invoice is due

if no due date is specified on the invoice, then it is assumed to be thirty days after the invoice was generated and sent.

Client Details

Every invoice should include client details. The name should be included at a minimum, but other details such as an address or phone number can be included as well.

Fees

The fees section of your invoice should include the following:

  • A description of the services rendered
  • The gross amount due
  • The taxes due, if applicable
  • The total amount due

Terms of Payment

The terms of payment section should include how the invoice should be paid. How you accept payments is up to you. If you need the invoice paid via money transfer, that should be specified here along with your baking information:

  • Bank name
  • Account number
  • Routing number if you bank in the U.S.

Sending the Invoice

Once you have finished adding all the above details to your invoice, it’s time to send it. How you do that depends on the relationship you have with the client and what has been previously discussed concerning invoicing. Some clients want paper copies of invoices, while others will accept digital copies. If sending a digital copy, a good practice is to send the invoice as a PDF so that it cannot be altered. You can also send invoices via email or in some other attached format.

Invoicing With WordPress

As discussed above, you can generate your invoice manually. But if you’re working with WordPress, there are several plugins that will help with the invoicing process, allowing you to automate as much of it or as little of it as you like. Elegant Themes has an excellent roundup of invoicing plugins for WordPress, (both free and paid), as well as a few themes specifically created for invoicing. I personally use a plugin called WPInvoice, which leaves a lot to be desired as far as accessibility goes, but comes with a lot of features in the free version, including the ability to accept payments using Stripe, and integration with the WPCRM plugin so that I can keep track of clients and automatically select the client’s information when generating an invoice.

Summing Up

Invoicing is a necessary task. It helps ensure that you get paid. You can generate them manualy, but you can also streamline the process using WordPress, which will make invoicing much easier. There are also other non-WordPress solutions for generating invoices. If you have a favorite WordPress or non-WordPress one, share it in the comments below.

The providers of the Conductor plugin have compiled an extensive guide to developing with WordPress. There are links to free and paid tutorials, as well as podcasts and books, and they are accepting submissions to the guide through comments to the post. The guide highlights best practices and is pretty thorough so far. If you have development resources, free or paid, why not go over there and add them? I have not checked to make sure all of the listings are accessible, specifically the paid ones, and I do not think the books are available on Bookshare. Most of them are, however, available on Kindle, which you can use accessibly if you have an iPhone, iPad, or iPod current model. The guide is an excellent resource whether you’re just getting started with development or have any level of experience in that area. It’s definitely worth adding to your bookmarks/favorites if you’re interested in development for WordPress in any way, whether that be for themes, plugins, or core code.
CloudFlare a href=”http://blog.cloudflare.com/introducing-universal-ssl/”>announced on their blog today that they have started offering free SSL to all of their customers, both free and paid. There’s a lot of detail in that post, but the roll-out promises to be quick for everyone, within twenty-four hours. This is clourFlare’s contribution to a completely secure web. They’re hoping that their example will influence other providers to start offering SSL for free. We’ll see how this develops and what kind of influence CloudFlare has on the hosting/CDN industries. I’m completely in favor of a secure web and am glad that CloudFlare is making SSL accessible to a lot more people who might otherwise avoid it due to cost and/or difficulty in setting it up. This wouldn’t have happened if Google weren’t behind the SSL push. I can’t help but think of what could happen if Google got behind accessibility in a serious way like they are with SSL.
http://www.youtube.com/watch?v=XeP5Kl4GDgA
No one wakes up in the morning and says “You know what? I think it would be great if a very large subset of the web-using public couldn’t use my website”. Or web application. Pick your poison for the last word in that sentence. Nonetheless, accessibility often is last in line when it comes to project priorities. The Section 508 Refresh is right around the corner and with it, the expectation to make all government web properties compliant to WCAG 2.0 AA. For most organizations, this is nothing short of a nightmare. But does it really need to be? Accessibility requirements challenge development practices and jeopardize a project’s profitability. As accessibility affects every contributor, it is not advisable to base its liability on a single person’s shoulders. Sharing responsibilities between different specialists is the key to making accessibility happen. What if the only things an organization needed were a blueprint, a strategy and the right mindset? The slides below, delivered by Denis Boudreau at this year’s Accessibility Camp Terronto demonstrate the piitfalls of allowing accessibility to be the responsibility of one person, and also how to make the job of compliance easier for businesses.

Since I live in WordPress, I’ve heard about Easy Digital Downloads by Pippin Williamson a lot. He’s a prolific plugin author who contributes in a huge way to the WordPress community with both his plugins and the tutorials he writes, both for free and cost.

I’ve been pondering the idea of putting together some guides for WordPress that focus on performing tasks with accessibility in mind. I will still publish free tutorials on this site, but would also like to write more in-depth material.

So I took Easy Digital Downloads for a spin yesterday. I wrote a plugin that I thought would be useful and put up a post about it. As part of the work for that post, I tested Easy Digital Downloads.

The documentation promises that it’s easy. It is indeed that. But what pleasantly surprised me is that along with the ease comes accessibility. I was able to configure every option using a screen reader for the plugin, and I didn’t have to perform any crazy maneuvers to get it working. Given everything the plugin can do, I was a little worried that accessibility would have been compromised. I’m glad that I found that not to be the case.

If you’re a blind businessperson selling products that are digital, like music or ebooks, and you’re also running WordPress, give Easy Digital Downloads a spin.

Thanks Pippin. This is how you do accessible user experience. I’ll be buying extensions.

JavaScript: The Right Way is a guide intended to introduce new developers to JavaScript and help experienced developers learn more about its best practices. It is a project hosted on GitHub that gathers together tutorials, tips and tricks that show both beginners and seasoned developers the best way to write their code so they can get things done.

It can also be used as a free JavaScript course, because it starts at the beginning. It doesn’t cover everything yet, but because it’s hosted on GitHub, that means that multiple people can contribute. Content version control in action.

You can find the tutorial here, and of course add it to your bookmarks if you want to consume it.