Currently the VAT Returns having 3 columns, where another column require to add any adjustments, this is can be seen below:
Kindly add 1 more column to accomodate this required as per the regulators, all standard software already included in their solutions…
Where do you expect the program to get the data? Or do with it if you put your own adjustments in? If you are making up these adjustments, you should do it in a spreadsheet of your own.
This is required by the law for VAT and expected to generate reporting from Manager…
Your law does not refer to Manager. As you should know well, tax accounting and financial accounting are two separate things. Manager does not perform tax accounting. It is a financial accounting package that can be used to support preparation of tax filings, but only to the extent that it contains transaction data necessary to do so. Nowhere in the program are adjustments used or recorded.
@Tut though your point is valid, however this was a matter related to localization, unfortunately not taken care as requested couple of years ago, anyway will inform customers not possible.
Localizations only present data already present within the system from entered transactions.
Generating a system report that exactly matches the tax return form isn’t a requirement by the law.
Also, the allocation/adjustment column is reserved for two scenarios:
This is a very complex and judgemental adjustment and if we want Manager to display the exact format automatically, it would require a lot more data to be captured in Manager which would make the processes long and convoluted.
The alternative is, of course, to use a spreadsheet to manually allocate things. Even a localization would give you blank cells to be filled manually.
Also, localizations are to be submitted by the community and they’re not part of the development of Manager; they’re community add-ins, if you like.
Generation of a localisation requires:
A detailed understanding of a particular countries accounting conventions and reporting requirements, not just for a single business but for all businesses Manager’s localisation is going to support (ie the general case).
Sufficient programming ability to code the accounting requirements into Mangers localisation interface. Again the requirement is for all data users may enter (ie the general case) not just the subset a particular business needs.
In additions Manager’s localisation interface must also have the breath of program functionality to allow implementation of particular countries reporting and data entry requirements.
The OP request is not currently possible due to limitations in item 3. Specifically
localisation need to allow a maximum of 4 columns not 3. I suspect this would not be a major change.
localisation need to support arithmetic on interim values. This is a more significant change and I suspect this feature is much less likely to be added.
There may also be problems achieving items 1 & 2 but that primarily depends an forum users motivation.
Actually it’s quite surprising how come other solutions available in market have done this…
@Ealfardan check this out الجهاز الوطني للإيرادات - إقرار القيمة المضافة as local regulations, sure you know about it!
@danowagroup you got me scratching my head for a while there. 
I’ve read the whole thing again and even followed the link to the guides there but it just confirmed what I had in mind: there’s no requirement for a system generated report to copy the exact same format of the tax return form.
As far as I know, the books must match the total obligation or credit filed for the period (i.e. a single Journal entry per filing is legally sufficient) and each return item must be supported somehow whether from within or outside your books of accounts (i.e. paper records and spreadsheet calculations are sufficient) so we are only discussing voluntarily enhancing documentation beyond what’s required by regulation.
I am curious what other systems did that. Could you please name them?
I would also be cautious of the reliability of information for adjustments and allocations because the nature of requested information requires a lot more data entry and review work and it appears that these systems have cut some corners here and there.
Anyway, I have made a localization using liquid transformations but unfortunately the whole liquid transformations were dropped before I had the chance to share it. Still, I intend on making a new one using the new transformations but I am certain it’s not going to be ready for this quarter but maybe before this year end, hopefully. 
Then we should have something to talk about.
There are various ERP having it already Tally ERP 9, Zohobooks, Bookkeeper etc. Here is the actual screenshot:
Where we can find community add-on?
Have you tested it?
What I mean is this:
Confirm it’s not just exceptions. QuickBooks also gives a three column format but it gives exceptions in the second column which are all the changes in previous period books. These figures should be ideally reported under item 15 “Corrections” if they were less than BD100000 in VAT base value (BD5000 VAT) otherwise an amendments to previously filed taxes “voluntary disclosure” should be submitted. Could you please confirm that that’s not the case?
Entering new exempt sale. How does that affect apportionment of standard rated inputs? What criteria does it use to determine whether an expense is related to a taxable sale or not? Also how does it separate overheads from direct costs?
Credit/Debit notes. How do they get reflected? What criteria takes them out from first column to second column? How does it distinguish between corrections and returns? Say you overinvoinced in Q3 and then issued a Credit Note in Q4: that should be a correction of error under item 15. On the other hand a return is an adjustment in the second column. How can Zoho tell this from that?
That’s why I said there’s a lot of judgement here. And it really should be sound judgement to avoid overpaying taxes on one hand or risking tax penalties on the other. There needs to be a balance and I am not sure if I can trust a rigid one-size-fits-all approach.
