Greys are caused by out-of-sequence submissions. They are solvable by submitting the missing invoices (which may not be possible if one of the invoices in sequence is no longer valid e.g. if deleted). This necessitates keeping a sequential record of submissions which does not necessarily correspond to the invoice sequence within Manager. This is important because users submit “at will” via the relay.
Reds are harder, because it can be one of many things that breaks the rules. The standard way is to validate and reject anything that won’t go through, so the user has the chance to correct it and re-submit.
If the source is open, I am willing to look around and give quick pointers. I can’t commit to working on it though.
Edit: Also, do not resubmit failed invoices. Reading closer, it looks like a specific invoice is the issue. Can you inbox me the submitted invoice data and the link in the output QR code
As promised, here is a quick update to advise that we have been successfully fiscalising through Fiscal Harmony and their Manager integration for a week now. We have had a few small teething issues, but they have been quick to help us resolve them.
@Mabaega I am trying to test the simulation integration as getting that error. How do I resolve and what could be the cause and have you ever encountered it?
I have not been able to confirm the cause.
Maybe Zimra closed or changed something on their api service,
I can’t access their web api from my computer.
My Manager.io Integration with zimra works fine. I am now dealing with the addition of HS codes. Axis sent me this list of requirements, most of which are new. Note the labels they say they want
Good day
Kindly make the following changes:
Add labels on your customer details as shown below and fill in
Add an HS code column and the codes should be 8 digits in length. These codes are available on their Zimra website so you put the code of the products that you sell. Be guided by the attached document.
Put Reason on your credit notes i.e Reason: Refund
