Invoices - is a unique ref no essential?

[JBean]

Is it a legal requirement for a company to use sequential unique ref no on invoices? If so, why would a company not comply, what would they benefit? And if they don't comply, would HMRC even notice or do anything about it? Thanks for any guidance.

[northernladuk]

http://forums.contractoruk.com/showthread.php?t=80544

[Alias]

The ‘invoice number’ can be numerical, or it can be a combination of numbers and letters, as long as it forms part of a unique and sequential series.

A VAT invoice must show: An invoice number which is unique and follows on from the number of the previous invoice - if you spoil or cancel a serially numbered invoice, you must keep it to show to a VAT officer at your next VAT inspection

[Pondlife]

https://www.gov.uk/invoicing-and-tak...y-must-include

Having a sequential number makes it easier to see which have been paid and which are outstanding. Something that might prove useful if you wanted to demonstrate to HMRC that you're in control of Your Cos finances and that everything is above board.

[TheFaQQer]

https://www.gov.uk/invoicing-and-tak...y-must-include

Having a sequential number makes it easier to see which have been paid and which are outstanding. Something that might prove useful if you wanted to demonstrate to HMRC that you're in control of Your Cos finances and that everything is above board.

In some countries (Italy?) the sequence must be numerical and have no gaps in it at all. That way it makes it harder to "lose" an invoice and pocket the cash, and why you always get a receipt for everything.

[TheCyclingProgrammer]

AFAIK the unique sequential requirement only applies to valid VAT invoices although I don't think there's anything stopping you from having more than one sequence (e.g. CLIENTA-001, CLIENTA-002, CLIENTB-001 etc.).

[TheFaQQer]

AFAIK the unique sequential requirement only applies to valid VAT invoices although I don't think there's anything stopping you from having more than one sequence (e.g. CLIENTA-001, CLIENTA-002, CLIENTB-001 etc.).

That's how I've always done it. Sometimes I've included an agent code as well, eg AAA-CCC-NNN where AAA is the agency, CCC is the client and NNN is the sequential number. At the moment I just use CCCNNN since there's no agent in the mix.

[NotAllThere]

In some countries (Italy?) the sequence must be numerical and have no gaps in it at all. That way it makes it harder to "lose" an invoice and pocket the cash, and why you always get a receipt for everything.

And and a right pain it can be as well. I remember implementing SAP for an Italian company.

What's the procedure if you accidentally issue two invoices with the same number.

[ASB]

And and a right pain it can be as well. I remember implementing SAP for an Italian company.

What's the procedure if you accidentally issue two invoices with the same number.

Don't even get me me started on the fiscal rules for point of sale eastern europe.

[TheFaQQer]

And and a right pain it can be as well. I remember implementing SAP for an Italian company.

What's the procedure if you accidentally issue two invoices with the same number.

IIRC, Oracle has a default cache on the invoice number sequence (or it used to) which needs to be disabled when you are in environments like this. All fun and games