Handling missing or invalid amounts

Assume you have Empty value by default selected for an amount field, and an AP Essentials Office user clears the field because he cannot find it on the invoice. In this case, the user is warned that the value is empty, but he is allowed to override the warning, and the empty value is sent to the target system.

Assume you have Zero amount by default selected for an amount field, and an AP Essentials Office user clears the field because he cannot find it on the invoice. In this case, the empty value is not sent to the target system. Instead, the empty value is automatically changed to a zero amount (0.00) when the user moves to another field, and the zero amount is sent to the target system.

There are many validations for amount fields. In most cases, empty values are treated as zero, when it comes to calculating validations which involve amount fields. For example, assume you have the Total amount validation enabled and you have the tax field set to Empty value by default. If a user leaves the tax field empty, the field value remains empty and is sent to the target system empty. However, for the purpose of calculating the total amount validation, the tax value will be treated as zero.

Some integrations require amount fields in a specific format, while other integrations accept amounts in any format. If you accidentally choose a setting that conflicts with your integration, you can receive an error when documents are exported to the target system. This table shows some common fields for each integration and tells you whether the field must be a number. In other words, if the target system requires a numeric value for a specific field, avoid using the Empty value by default setting on that field.