Action Workflow

📘

Integrating through Apex AscendOS?

The product guidance on this page applies to you. The endpoints, fields and statuses are Monark's; use the AscendOS equivalents listed in Building on Apex AscendOS.

Registered fund transactions carry the same transaction actions as private company subscriptions, and are completed the same way. Read Transaction Actions first — this page covers only the differences.

The same in both

• GET /primary/v2/transaction-action/transaction/{transactionId} returns a bare array, not a paged envelope.
• The five types are DocumentSign, DocumentAcknowledge, TextAcknowledge, Questionnaire and ViewDisclosure.
• responsibleParty filtering: Investor and Partner are yours; Monark, Advisor and CoOwner are not.
• PUT /primary/v2/transaction-action/{id}/complete completes an action and returns 204.
• Questionnaire answers must be submitted before the questionnaire action can be completed.

Important: The document signing order applies here too, and it is the thing most likely to strand an order. POST /primary/v2/document/{id}/sign records the signature but does not promote the transaction; PUT /primary/v2/transaction-action/{id}/complete promotes but records no signature; and complete-all returns success without promoting when nothing is pending. Sign the documents, then complete a non-signature action last. See Transaction Actions for the full explanation.

What differs

Promotion is per responsible party, then whole-transaction. Completing an action checks whether any action remains pending for the same responsible party. For a registered fund, the completion handler for that party then runs — which is not identical to the SPV path, where signing additionally requires that no action of any party is still pending.

Questionnaire overlays. For a registered fund, completing a Questionnaire action populates the answers onto the subscription document itself. That does not happen for an SPV. An investor who completes a questionnaire and then re-opens the document should see it reflected.

Advisor actions are more common. Registered fund distribution is frequently advisor-led, so a transaction carrying a financialAdvisorId will often include Advisor actions. Those are not yours to complete — surface their state so the investor understands what is outstanding and who it is waiting on.

Status range. A registered fund transaction can sit in Initiated before actions open, and can pass through PendingCancellation on the way to Canceled. Neither happens for an SPV, so handling written only against the SPV path will meet unexpected states here.

Next steps

• The full action workflow: Transaction Actions
• The statuses this drives: Transactions