Create bill
Authentication
Path parameters
The paypoint’s entrypoint identifier. Learn more
Headers
Optional but recommended A unique ID that you can include to prevent duplicating objects or transactions in the case that a request is sent more than once. This key isn’t generated in Payabli, you must generate it yourself. This key persists for 2 minutes. After 2 minutes, you can reuse the key if needed.
Request
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 array 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.
When vendor enrichment is enabled and the first attachment is a PDF, the invoice is scanned and extracted vendor contact information and bill details (invoice number, amount due, due date) are merged into the request. Fields in the request body take precedence over extracted data. If the scan fails, bill creation proceeds with the original request data. See the vendor enrichment guide for details. Contact Payabli to enable this feature.
Date of bill. Accepted formats: YYYY-MM-DD, MM/DD/YYYY.
Array of LineItems contained in bill.
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.
The bill’s status. Values are:
-99: deleted or canceled1: Active2: Sent to approval5: Partially approved11: Rejected20: Approved50: Payment in transit100: Paid ”
Payment terms for invoice. If no terms are defined, then response data for this field defaults to NET30.
Available Values:
-
PIA: Payment in advance -
CIA: Cash in advance -
UR: Upon receipt -
NET10: 10 days after invoice date -
NET20: 20 days after invoice date -
NET30: 30 days after invoice date -
NET45: 45 days after invoice date -
NET60: 60 days after invoice date -
NET90: 90 days after invoice date -
EOM: Due end of this month -
MFI: 1st of the month following the invoice date -
5MFI: 5th of the month following the invoice date -
10MFI: 10th of the month following the invoice date -
15MFI: 15th of the month following the invoice date -
20MFI: 20th of the month following the invoice date -
2/10NET30: 2% discount if paid within 10 days, otherwise net 30 days -
UF: Until further notice -
10UF: 10 days until further notice -
20UF: 20 days until further notice -
25UF: 25 days until further notice -
50UF: 50 days until further notice
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
Response text for operation: ‘Success’ or ‘Declined’.
Code for the response. Learn more in API Response Codes.
Field not in use on this endpoint. It always returns 0.
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.