What is a Fulfillment?

A fulfillment is the step that turns obligations into actual payouts. When you decide it’s time to pay your collaborators, you create a fulfillment, Siren gathers up the obligations you want to settle, and the result is a set of payout records ready to be processed.

How a fulfillment is built

Processing the payouts

Once payout records exist, you decide how to move the money. The most common approach is to export the payout list to CSV, run that file through your payment platform of choice, and then mark the payouts as paid in bulk. For smaller programs, or for handling one-off exceptions, you can also mark individual payout records as paid manually as each transfer goes out.

Either way, the payout record is the thing you update when the money lands. Siren doesn’t push money on your behalf. It gives you the totals, tracks which payouts have been settled, and leaves the actual disbursement to whatever tool you already use.

Reviewing historical fulfillments

Every fulfillment becomes a permanent ledger entry. You can open an old fulfillment and see exactly which obligations were included, which collaborators got paid, how much each one received, and when. This is what you reach for during audits, dispute resolution, or when a collaborator asks why last month’s payout looked the way it did. The fulfillment’s activity feed shows each payout that was cut, each obligation that was rolled into it, and any status changes along the way, so the full story is on one screen instead of spread across several. It’s also what protects you if a refund comes in after a payout has been sent, since the completed obligations on a historical fulfillment are deliberately left untouched by the refund pipeline.

For developers: This concept maps to the FulfillmentCreated event. See the events reference for the full pipeline.