![]() A llocating a milestone (attached to an order) to an invoice is the first supported use case. Type of payable receiving the allocation. This is true for both the From and To payables. Only one of the three needs to be provided. an invoice-id), then source-transaction-reference (e.g. When figuring out which payable to attach the allocation to, we will first try to use payable-to-id, then source-transaction-from-id (e.g. Order number, invoice number, etcĬoupa ID of payable receiving the allocation. External identifier of document associated with the payable from. Source Transaction type of the sending payable Source transaction ID of the sending payable When figuring out which payable type we’re looking for, we accept the following values: invoice, milestone, expense, expense_preapproval, virtual_card_expense_preapproval, trip_booking, external_payable, supplier_payable, employee_payable.Īmount to allocate from Payable From document an invoice-id or order-id), then source-transaction-reference (e.g. order milestone and invoice) rather than needing to dig up the associated “payable” ids. We built in enough flexibility to allow integration to reference the source documents (e.g. The format is set up so that we can allocate from any type of payable document to any type of payable document. Our first use case is to allocate a prepayment (milestone) for an order to the associated invoice, so that it will not be overpaid. Allocations move the payment responsibility from one document to another.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |