The strictly essential fields for an acceptable invoice are:
1. Name of the company making the payment
The full name of the original payer.
It does not need to be an exact match, as long as we can be sure it's the same company as the payment. This accounts for typos, for example.
It's helpful to inform the address as well because then it's faster to certify who is the company.
2. Name of the beneficiary
When the payment is for a company, the invoice should have the name of the company. If it is for the individual, invoice with the individual name. It can not be a payment for an individual and the invoice have the company name or vice versa.
With companies is accepted either an exact match with their original name or their fantasy name.
With individuals does not need to be an exact match, as long as we can be sure it's the same individual as the payment. This accounts for typos, for example.
The following data helps us certify who is the individual or company: address, CPF or CNPJ.
3. The amount
It doesn't need to be an exact match, however, the payment amount must be lower or equal to the invoice amount.
It is not an issue if the payment and the invoice are in different currencies, as long as the payment amount persists to be lower or equal to the invoice amount.
We do have a tolerance though, to account for conversion rate fluctuations or banking fees prior to Husky receiving the payment. But if the payment amount is considered to be higher than the invoice amount, even if accounting for these differences, it will not be accepted.
4. The description of the payment
The reason why that payment is being made.
You can see an example invoice below. It's generated by Husky with fictional data, with the strictly essential fields highlighted by a red rounded square.
The highlights in blue are the helpful information that when analyzing an invoice may speed up the process.
The other information we have in this example is useful for either the payee or the payer, but they do not have compliance implications.