Starts the approval process once the uploaded payable is validated.
The ID of the entity that owns the requested resource.
A unique ID assigned to this payable.
UTC date and time when this payable was created. Timestamps follow the ISO 8601 format.
UTC date and time when this payable was last updated. Timestamps follow the ISO 8601 format.
The ID of the entity to which the payable was issued.
Specifies how this payable was created in Monite: upload - created via an API call, email - sent via email to the entity’s mailbox.
Specifies how the property values of this payable were provided: ocr - Monite OCR service extracted the values from the provided PDF or image file, user_specified - values were added or updated via an API call.
How much is left to be paid on the invoice (in minor units).
How much was paid on the invoice (in minor units).
How much is left to be paid on the invoice (in minor units) with discounts from payment terms.
Id of existing approval policy that applies to this payable, if any. A policy is applied if the payable matches the policy trigger conditions.
Object representing de-normalized counterpart data. Filled at the moment of invoice submitting for approval or payment.
The ID of counterpart address object stored in counterparts service
The ID of counterpart bank account object stored in counterparts service
The ID of the counterpart object that represents the vendor or supplier.
Object representing counterpart data which was extracted by OCR. Used for informational purposes.
The ID of counterpart VAT ID object stored in counterparts service
The ID of the role that the entity user who created this payable had at that time. If the payable was created using a partner access token, the value is null.
An arbitrary description of this payable.
A unique invoice number assigned by the invoice issuer for payment tracking purposes. This is different from id which is an internal ID created automatically by Monite.
The date by which the payable must be paid, in the YYYY-MM-DD format. If the payable specifies payment terms with early payment discounts, this is the final payment date.
The original file from which this payable was created.
File id to retrieve file info from file saver.
The date when the payable was issued, in the YYYY-MM-DD format.
The ID of the entity user who marked this document as paid.
An arbitrary comment that describes how and when this payable was paid.
Id of OCR request to match asynchronous result of processing payable.
The status of the data recognition process using OCR. The ‘processing’ status means that the data recognition is in progress and the user needs to wait for the data enrichment. The ‘error’ status indicates that some error occurred on the OCR side and the user can fill in the data manually. The ‘success’ status means the data recognition has been successfully completed, after which the user can check the data if desired and enrich or correct it.
Data extracted from the uploaded payable by OCR.
The date by which the payable was paid
Metadata for partner needs
The number of days to pay with potential discount for options shorter than due_date
Project ID of a payable.
The identifier of the purchase order to which this payable belongs.
The email address from which the invoice was sent to the entity.
The subtotal amount to be paid, in minor units. For example, $12.50 is represented as 1250.
The suggested date and corresponding discount in which payable could be paid. The date is in the YYYY-MM-DD format. The discount is calculated as X * (10^-4) - for example, 100 is 1%, 25 is 0,25%, 10000 is 100 %. Date varies depending on the payment terms and may even be equal to the due date with discount 0.
Registered tax percentage applied for a service price in minor units, e.g. 200 means 2%, 1050 means 10.5%.
Tax amount in minor units. For example, $12.50 is represented as 1250.
The total amount to be paid, in minor units. For example, $12.50 is represented as 1250.