0

Best-practice tips for multi-project invoices

Grey

February 26, 2014 15:06

None

Follow

Hi all,

I'm new to Studiometry, so I'm still trying to wrap my brain around all the options and functions. My question, now, is how best to deal with multi-project invoices for my specific situation.

I'm a freelance translator and do a lot of shortish jobs for various clients to whom I typically send invoices at the end of each month. I see how to make multi-project invoices, but attaching an invoice to one of the projects in a given month essentially at random strikes me as a bit odd. Would it make sense to make a sort of generic "header" project each month and then add sub-projects to that header project as the month progresses? Then I'd just invoice that header project with all of the sub-projects for the month. Or is that making things more complicated than they need to be?

Cheers,

Grey

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Rob Sherrard - Imageer February 26, 2014 18:54

  Not knowing what a shortish translation job might contain in terms of quantity of itemizable work items, I'd be inclined to define the current month as a project for a client, and then make each shortish job a work item. I'm personally not a fan of multi-project invoices. I prefer to invoice each project separately and use the Statement feature to provide a total of what's currently outstanding for a client.

• 0
  
  Grey February 26, 2014 19:22

  Hi Rob, Most jobs I do have just one work item to bill (number of words times the rate per word). Some have multiple word counts for various rates (such as a combined translation/editing job), and so have more than one work item, but it's relatively rare. I don't think invoicing each individual job would go over very well here. A lot of jobs are only about €20, and I can have over 10 jobs a month for a given client. A bunch of small invoices each month just wouldn't fly with most clients here in Italy. Maybe I could go for a hybrid solution: one generic "project" for small jobs (as sub-projects), which I'd invoice once a month, and then separate projects for larger jobs that I'd invoice immediately once the job is done. Hmmm.... Cheers, Grey
• 0
  
  Henry Boyd April 02, 2014 20:36

  I'm in a similar sort of position.  I do consulting work for a number of large banks.  Typically I "work" for multiple people on multiple transactions during the course of a month (one person per transaction = project).  The multi project invoice works fine, except I need it to at the least separate line items on a per project basis.  I tried doing two invoices one with line items merged as a cover sheet and individual invoices per project.  The problem is that once invoiced lie items can't be re-accessed.  Failing all of the above a simple consultant's time sheet report would be great.  Any auggestions?

   

  Henry