When it refuses
Every error we hit, and what it actually means.
Search this page for the number in front of you.
Error -1021: Date is not valid for this transaction.
There is no date in your file. Date is required, despite
being marked optional everywhere MYOB documents it.
Add a Date column in your system's format —
29/09/2026 on an Australian machine.
Error -274: The combination of Quantity, Unit Cost and Amounts values is invalid.
Your Amount and Quantity disagree. MYOB divides one by the
other to get a unit cost, and it has to come out sensible. Amount
+24.38 against Quantity -1 implies
a cost of minus $24.38. Both must carry the same sign.
It can also mean a stale field mapping is feeding a Unit
Cost you never sent. If your file has no Unit Cost column and you still get this, go
back to Match Fields and Unmatch All.
Error -4253: Please select the {1} account.
There is no account in your file. Required, and marked
optional. The {1} is MYOB's — their message cannot
name the field it wants.
Add an Account column with an existing code, five digits
with a separator after the first: 6-4700.
Error -275: You may not transfer more items than you have on hand.
Genuinely this, if you are writing off more than MYOB thinks you hold.
But we also saw it with a stale field mapping, on a line
taking one unit off eighteen. If the quantity looks reasonable, suspect the mapping
before you suspect the stock.
Warning 835: Unit Cost is invalid or blank; recalculated.
Not an error. The line imported. You left Unit Cost out, so
MYOB divided Amount by Quantity and used the result. The stored figure is identical
either way.
Supply Unit Cost if you would rather not see "imported with
warnings" against a sixty-line file.