Update bill
Updates a bill by ID.
Path parameters
Payabli ID for the bill. Get this ID by querying /api/Query/bills/
for the entrypoint or the organization.
Headers
Request
Optional custom field.
Optional custom field.
Custom dictionary of key:value pairs. You can use this field to store any data related to the object or for your system. Example usage:
An arry of bill images. Attachments aren’t required, but we strongly recommend including them. Including a bill image can make payouts smoother and prevent delays. You can include either the Base64-encoded file content, or you can include an fURL to a public file. The maximum file size for image uploads is 30 MB.
Date of bill. Accepted formats: YYYY-MM-DD, MM/DD/YYYY.
Array of LineItems
contained in bill.
Unique identifier for the bill. Required when adding a bill.
Any comment or description.
Due date of bill. Accepted formats: YYYY-MM-DD, MM/DD/YYYY.
End Date for scheduled bills. Applied only in Mode
= 1. Accepted formats: YYYY-MM-DD, MM/DD/YYYY
Frequency for scheduled bills. Applied only in Mode
= 1.
Bill mode: value 0
for one-time bills, 1
for scheduled bills.
Net Amount owed in bill. Required when adding a bill.
The bill’s status. Values are:
-99
: deleted or canceled1
: Active2
: Sent to approval5
: Partially approved11
: Rejected20
: Approved50
: Payment in transit100
: Paid ”
Description of payment terms.
The vendor associated with the bill. Although you can create a vendor in a create bill request, Payabli recommends creating a vendor separately and passing a valid vendorNumber
here. At minimum, the vendorNumber
is required.
Response
Success
Boolean indicating whether the operation was successful. A true
value indicates success. A false
value indicates failure.
If isSuccess
= true, this contains the bill identifier. If isSuccess
= false, this contains the reason for the error.
Response text for operation: ‘Success’ or ‘Declined’.