Help · Troubleshooting
HIBR ERP Troubleshooting
Why a VAT 201 return fails validation or refuses to file, what each of HIBR's WPS pre-check codes means, how POS invoices are counted into a return, and — just as important — what HIBR does not do on your behalf.
Updated August 2026
6 min read
For: Beta participants
Beta opens: October 2026
Pre-launch note: HIBR ERP is in development and not on sale. The private beta is planned for October 2026 and there are no subscribers yet. This page describes the beta build and nothing else. Where HIBR does not do something — filing with the FTA, transmitting e-invoices, submitting to your agent bank — this page says so plainly rather than describing a feature that is not there.
What HIBR never does for you. HIBR prepares filings; it does not submit them. There is no FTA connection, no agent-bank connection, and no e-invoicing network connection. Every submission is an export that a person uploads. Anything on this page that ends in "you upload it" ends that way because there is no automated path behind it.
VAT 201 and CT 201 returns
By design HIBR will not submit the return to the FTA
What happens: HIBR computes the return, validates it, and gives you the figures. It does not transmit anything to the FTA.
What you do:
- Compute and review the return in HIBR.
- Export the figures and enter the filing in EmaraTax yourself.
- Set the return's status to
Filed-Manually — that status records your filing, not a transmission by HIBR.
There is no FTA API integration in HIBR and no rejection notice comes back into the product, because nothing is ever sent from it. The
CT 201 corporate tax return works the same way. If the FTA rejects a filing, that happens inside EmaraTax and is handled there.
Blocks filing Validation failed — "output VAT does not reconcile"
Cause: Box 8 does not equal the output VAT actually recorded on the period's documents.
Why it blocks: A return that does not match the documents behind it understates tax, so HIBR marks it
Failed and refuses to submit rather than warning and letting it through.
Fix:
- Read the message — it states the documents' total, the Box 8 total, and the difference between them.
- Open the invoices in the period and check each one's VAT 201 Box Summary field. That field is what the return reads.
- A difference means some VAT landed on a treatment the return does not read into any box. Correct the treatment on the offending document, then re-run Compute.
Blocks filing Validation failed — "unreadable VAT summary on N document(s)"
Cause: One or more documents carry a VAT 201 Box Summary that HIBR cannot parse, so their VAT cannot be confirmed to be inside the return.
Fix: The message names the documents (first five). Open each one and re-save it so the summary is rebuilt, then re-run Compute.
A summary that cannot be read is deliberately not treated as a summary of zero — that is why this fails the return rather than quietly excluding the document.
Blocks filing A computed return went stale before you filed it
Cause: Submitted invoices entered the period after the return was last computed, so the figures on screen no longer describe the period.
Fix: HIBR lists the late documents and refuses to file. Re-run Compute and review the new figures before filing.
This is expected, not a fault: Article 67(1) allows 14 days to raise a tax invoice, so an invoice dated inside a period can legitimately be created after that period ends. Period membership follows Date of Supply (Art. 25) where it is set, and posting date otherwise.
Note: the count of late documents is always complete, but only the names of documents you have permission to read are shown to you.
Invoice VAT looks wrong
Check first An invoice's VAT is not what you expected
The UAE tax fields on the invoice decide the treatment — they are not just labels:
- Customer Emirate — drives the emirate split in Box 1 of the VAT 201.
- Is Export (Zero Rated) and Designated Zone Supply — either one removes standard-rate VAT from the supply.
- Simplified Tax Invoice — changes the content the invoice is required to carry.
- Date of Supply (Art. 25) — decides which return period the invoice falls into, independently of its posting date.
Where to look: the
VAT 201 Box Summary field on the invoice shows which VAT 201 boxes that document feeds and the VAT it contributes. It is the same field the return reads, so it is the right place to check whenever an invoice and a return disagree.
Credit notes: a credit note needs a
Credit Note Reason (Art. 61(1)). It nets into the same supply box as the original invoice, so a box legitimately going negative in a heavy-credit period is not an error.
Expected Till (POS) sales look duplicated or missing in the return
What happens: At shift close, ERPNext consolidates the day's POS Invoices into a single Sales Invoice and stamps each POS Invoice with the consolidated invoice it now belongs to.
How the return counts them: HIBR counts unconsolidated POS Invoices directly, and counts consolidated days once via the Sales Invoice that replaced them. Counting both would double every till sale — so a POS Invoice that shows a consolidated invoice is intentionally not counted a second time.
If a day looks wrong: check whether that day's shift was closed and consolidated. A day mid-shift sits on unconsolidated POS Invoices; the same day after close sits on one Sales Invoice.
Payroll — WPS SIF checks and bank rejections
HIBR checks the salary file before generating it, so most problems are caught before the bank ever sees the file. The codes below are HIBR's own check codes, not agent-bank rejection codes: each agent bank reports rejections in its own words and codes.
| Code | Meaning | Fix |
|---|
410 | Employer MOHRE ID missing, or not exactly 13 digits | Correct Employer MOHRE ID on the WPS SIF Batch record |
103 | Employee labour card ID is not 14 digits | Fix MOHRE Labor Card on the employee record |
304 | Employee IBAN is invalid | Re-validate the employee's IBAN |
207 | Deductions exceed 50% of the wage | Reduce the deduction — FDL 33/2021 Art. 25 caps total deductions at 50%; some deduction types have lower caps |
710 | Net salary is zero or negative | Review that employee's basic, allowances, and deductions |
601 | Days on payroll is zero with no unpaid-leave days recorded | Set days on payroll or days of unpaid leave |
502 | Batch total does not equal the sum of the employee rows | Regenerate the batch after correcting the rows |
Passing check 207 does not make the month WPS-compliant. Under MOHRE Ministerial Resolution 340/2026 a worker transferred less than 85% of the wage due counts as unpaid, so deductions above about 15% put the month at risk even though check 207 passes. HIBR does not check that 85% threshold; review it yourself before you upload the SIF.
HIBR has no agent-bank connection. The SIF is a file you download and upload to your agent bank's portal yourself. A batch's final status is Submitted-to-Bank-Manually, which records that a person did that upload. Fix the underlying record, regenerate the SIF, and upload it again.
E-invoicing
By design E-invoice status shows "Not Transmitted — no ASP contracted"
HIBR builds the PEPPOL PINT AE e-invoice document and stores it against the invoice, but sending it onto the network requires a contracted Accredited Service Provider, and HIBR has not contracted one. That is the only transmission status an E-Invoice Document can currently hold.
The XML is generated and available to you. Nothing is sent anywhere, and no acknowledgement will ever come back. PEPPOL Ready on an invoice means the document met the PINT AE rules — not that it was delivered.
Signing in
HIBR ERP runs on Frappe/ERPNext v15, and sign-in, password reset, and the role and permission system are the standard ones from that platform. If you are locked out of a beta site, or a role is not granting what you expect, email info@hibr.ai — during beta these are handled by hand rather than through a self-serve recovery flow.
When to contact us
Email info@hibr.ai when:
- A calculation looks wrong and the checks above do not explain it — VAT treatment, a return box, a gratuity or WPS figure.
- A return refuses to file and the validation message does not name the cause.
- You have hit an error that is not on this page.
- You have a security concern — suspicious sign-in, suspected account compromise, or possible data exposure. Say so in the subject line.
Include in your email: the record's identifier or URL, the exact error message, and roughly when it happened (UAE time). For a return, include the period and its validation status.
There is no support SLA during beta. HIBR ERP has no paying subscribers yet, so no response-time commitment is offered and none should be assumed.
Related help articles