Edit a receivable

Note: Only works when all linked Loans are in CREATED state. proofIds is not accepted here, it is a creation-only field: once the object exists, evidence is added through POST /companies/{companyId}/proofs and linked through POST /companies/{companyId}/proofs/{proofId}/link. The deprecated attachments field is still accepted and still replaces the list, see the field description for how it maps onto proofs.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Defaults to me
string
required
Body Params
uuid

Unique ID assigned to a Debtor.

attachments
array of objects
deprecated

Deprecated, use proofIds on creation or the proof endpoints instead. Lists the non-archived proofs linked to this Receivable with source: COMPANY. On PATCH the list you send replaces the current one: a new file becomes a proof of type: UNKNOWN, a dropped one is archived. Omit the field and nothing changes. See the Proof guide.

attachments
number

Receivable Amount excluding tax.

number

Receivable Amount including tax.

string
enum
Allowed:
date-time

Date on which the service or good has been delivered, after which the receivable can be considered as UNBILLED

string
enum

Indicates the ultimate owner of the Receivable who is responsible for assigning the debt. The owner can either be your company or the beneficiary of the Loan. Please use this field only when you encounter different use cases.

Allowed:
debtorIdentifier
object

Identifier representing the debtor being invoiced

string

Unique reference of your choice that defines the Receivable.

date

The date on which you expect the invoice to be issued, as a calendar date in ISO 8601 format (YYYY-MM-DD).

number
≥ 0

Payment terms that will be indicated on the Invoice. You can find available durations with a GET /companies/{companyId} call. To be set if you have these information early on but did not create the Invoice yet.

string
enum
Allowed:
Headers
string

IP of the end-user doing the action resulting in the API call.

Responses

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json