Create a payable
Add a new payable by providing the amount, currency, vendor name, and other details. You can provide the base64_encoded contents of the original invoice file in the field base64_encoded_file.
You can use this endpoint to bypass the Monite OCR service and provide the data directly (for example, if you already have the data in place).
A newly created payable has the the draft status.
Request
- Base URL: https://api.sandbox.monite.com/v1
- URL: https://api.sandbox.monite.com/v1/payables
- Auth: HTTP bearer
Headers
The ID of the entity that owns the requested resource.
Request body
Base64-encoded contents of the original issued payable. The file is provided for reference purposes as the original source of the data.
Any file formats are allowed. The most common formats are PDF, PNG, JPEG, TIFF.
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.
The ID of counterpart VAT ID object stored in counterparts service
An arbitrary description of this payable.
The value of the additional discount that will be applied to the total amount. in minor units. For example, $12.50 is represented as 1250.
A unique invoice number assigned by the invoice issuer for payment tracking purposes.
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.
Id of an existing approval policy that should be enforced when submitting the payable for approval.If this field is set, no other policies will be evaluated via their triggers - the specified policy will always be applied instead.
The original file name.
The date when the payable was issued, in the YYYY-MM-DD format.
Metadata for partner needs
The ID of a project
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.
A list of IDs of user-defined tags (labels) assigned to this payable. Tags can be used to trigger a specific approval policy for this payable.
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.
Response
Successful Response
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.
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.
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.
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.
The value of the additional discount that will be applied to the total amount. in minor units. For example, $12.50 is represented as 1250.
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 URL to download the original e-invoice file.
Id of an existing approval policy that should be enforced when submitting the payable for approval.If this field is set, no other policies will be evaluated via their triggers - the specified policy will always be applied instead.
The ID of the entity to which the payable was issued.
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 date by which the payable was paid
Metadata for partner needs
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.
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.
The total price of the payable in minor units, excluding all issued credit notes.
Changes
No recorded changes to this operation across all 1 revision of this API.