At what point does Sage not recognise the invoice?
When entering it? I have a VAT only invoice I have to enter once a year for one client I don't have any bother entering it.
Is the problem when it comes to the VAT Return? Is it caught up in one of Sage's error checks? (The one client I have this for is still on Sage 50 2012 which doesn't have this error checking thing).
__________________
Never buy black socks from a normal shop. They shaft you every time.
As Peasie said - I also sometimes enter 'VAT only' invoices.
In my case, if I receive a supplier invoice that includes a VAT element but which lacks a VAT registration number, I put the VAT element on hold and contact the supplier to let them know/get a valid invoice with number.
I do this by posting the invoice on two lines - the first line shows the net amount, with a T1 tax code and zero VAT. The second line is the 'VAT only' invoice - it is a zero net amount, T1 tax code and the VAT amount.
Sage has no problem with this for me, but I'm on Sage 50 Accounts 2013 - also before the newer versions with error checking.
If the problem is down to the error checking, then the error checking needs to be checked by Sage for errors - because VAT only invoices are perfectly valid. (For example, consider a windscreen replacement - the companies that handle this will usually bill the insurance company, but if the customer is VAT registered, the VAT element is billed to the customer: A VAT only invoice.)
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
Just to clarify, in case Peasie and I have misunderstood...
You have input an invoice on the supplier ledger, which has 0.00 in the net column, T1 in the tax code column, and an amount (say 40.00 for the sake of argument) in the VAT column.
Is that correct?
Can you also clarify which version of Sage this is, and the exact wording of the error message?
I suspect this will be something that needs to be referred back to Sage under your Sagecover contract (if you have one) - but it's worth clarifying the above, just in case.
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
Okay. I'd guess it's the VAT element of an insurance claim relating to a damaged or lost shipment.
(Although the actual reason for it doesn't matter, that means - if I'm right - that it's along the same lines as the windscreen replacement example I gave above: the VAT element of an insurance claim.)
The important point, though, is that it is an invoice with 0.00 for the net, and a non-zero amount for the VAT.
Judging from your first comment, you have already input this invoice, and this is the error checking that Sage now performs before processing the VAT return.
What is the nature of the message? In your first post, you said "Sage doesn't recognise this VAT amount" - but in your later one, you said you "have a warning message" about it.
In Sage terms, a "warning" is usually a non-severe error, something that brings an important point to your attention, but can be ignored - so, since some of us are working with an older version of Sage that doesn't have the new "hells and missiles" it'll help us to help you if you are precise. Can you quote word for word what the warning says, as follows:
* If it comes up in its own little window, the exact 'title' of the window (if there is one),
* the exact wording of the warning message,
* and the wording in any buttons in the window (if there are any).
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
I know when I do a VAT return I panic when it throws up 30 errors/warnings - and when you look at the warning it is because the VAT on an invoice is 1p different from what Sage expects. The ones I have overwritten to be the same as on the invoice. I keep on intending to see if I can alter the margin of error.
__________________
Never buy black socks from a normal shop. They shaft you every time.
FFS, are newer versions of Sage really that pernickety? That's ridiculous.
If I have an invoice with (say) two items, one with VAT and one not, and both will end up in the same nominal code, I don't enter it on two lines, I enter it on one line and put the correct amount of VAT in. I'd probably make Sage's error checking explode, doing things like that.
Can it perhaps be switched off or bypassed?
(The latter of which, incidentally, is the point of my last question to the OP; I'm trying to establish if it's just a 'warning' that can be skipped past.)
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
Yes, it is correct what you said....Zero net, T1 and a VAT amount.
The waring message said "1 transaction with unexpected VAT value"
This issue appear on Verification Results Summary, there is a column "other potential issues", there is a warning message with a "view" button, I can click on it and I can see the invoice and also there are two buttons to print and to convert in Excel. That's it, nothing else
-- Edited by Boris on Wednesday 29th of April 2015 10:39:33 AM
That's the same message I get when I'm 1p out on an invoice between what Sage calculates and what the invoice actually states. I ignore it as I am using the correct figures.
__________________
Never buy black socks from a normal shop. They shaft you every time.
It is flagging it as a potential issue. This means you need to check and verify it. If you are happy with it, which I believe you are you can still go ahead and submit the return.
It is Sage's way of trying to be helpful. This is generally good (and it is not often I compliment Sage!)
__________________
Phil Hendy, The Accountancy Mentor
Are you thinking of setting up your own practice or have you set up and need some help?
If so a mentor may be the way forward - feel free to get in touch and see how I can assist you.
I haven't found Sage to be too pernickety and am on 2015 version. It's just checking that VAT values are within a tolerance that it expects to see (not sure if I've ever changed the tolerance - can't remember!). This is a red flag that there might be a problem but is not an error as such, just a validation tool. If you're happy that your transaction is correct then feel free to ignore the check.