TABLE OF CONTENTS
- Conditions
- What is the Instruction Period?
- Cases Waiting for Instruction
- Instruction logic
- Instructions: Step-by-step
- Grace period: how to instruct after the instruction deadline?
- How are future updates to the case transferred?
- Changing the Type of Order (Standing ↔ Single)
- Abandon a case
- Delete a Case
Conditions
In order to transfer instructions, make sure the following information are well populated on the cases:
- Type of Order = Single Order or Standing Order 
- Payment Management By = Pavis 
- Pavis Registration = True 

⚠️ Without this information, the instruction won't be sent to Pavis.What is the Instruction Period?
The Instruction Period is the time window during which you’re allowed to change the renewal Instruction (e.g., switch between Pay and Do not pay – Abandon) on a renewal in EC+. Outside this window, EC+ blocks the change because PAVIS can no longer accept it.
Instruction periods opening:
- Patent/Design: if renewal due date is in <180 days 
- Trademark: if renewal due date is in <365 days 
When you save a change to Instruction, EC+ checks two dates and allows the change only if today is before at least one of them:
- Order Until (from PAVIS, when available) 
- Instruction Deadline (a calculated safety date used when Order Until is blank) 
- If today > Order Until, EC+ then checks Instruction Deadline. 
- If both are passed, EC+ prevents the update and shows a blocking message (e.g., “it’s too late … due to a PAVIS dependency”). 
Where the dates come from:
- Order Until: provided by PAVIS. It is the primary cutoff.
- Instruction Deadline: define by the client as a preference. It needs to be set per case type in the Pavis Service Configuration (managed by your solution engineer) 
Cases Waiting for Instruction
Access the "Waiting for Instruction" list view (available for patent, design and trademark)

In this list, you will have access to all renewals waiting for your instruction where the renewal period is open.
Once you have selected one renewal, you will be able to edit the Instruction field, as follows:
Don't forget to click on save to store your instruction
Instruction logic
Renewal Status reflects last successful flow:
- Pay ⇒ Instruction Sent. 
- Do not pay ⇒ Won’t be Renewed. 
- Any error ⇒ Pavis Error (dedicated list views highlight these). 
By default, the instruction is set to "To be decided".
| User change on Instruction | EC+ pre-check | Renewal Status | 
|---|---|---|
| To be decided → Pay | Must be before Order Until or Instruction Deadline. | If successful, Instruction Sent. If error, Pavis Error. | 
| To be decided → Do not pay | Same deadline rule. | If successful, Won’t be Renewed If error, Pavis Error. | 
| Won’t be Renewed → Pay (user reconsiders) | Same deadline rule. | If successful, Instruction Sent. If error, Pavis Error. | 
| Instruction Sent → Do not pay | Same deadline rule. | If successful, Won’t be Renewed If payment already processed ⇒ no change + blocking message. | 
Instructions: Step-by-step
Send Pay
- Open Renewal (Type of Order = Single Order) with Renewal Status = Waiting for Instruction. 
- Set Instruction = Pay.
- Save (only if before Order Until or Instruction Deadline).
- EC+ calls Pavis, updates Renewal information, sets Instruction Sent
- A PAVIS Request record is created/archived with request/response payloads for audit.
Send Do not pay
- From Waiting for Instruction, set Instruction = Do not pay (before deadline). 
- EC+ calls Pavis and sets Won’t be Renewed for Single Orders;
- The parent case status is updated to Abandoned and Abandon Date = today
- A PAVIS Request record is created/archived with request/response payloads for audit.
Revert Won’t be Renewed → Pay
- Ensure still before deadline. 
- Set Instruction = Pay → EC+ calls Pavis then updates renewal information, status becomes Instruction Sent if OK.
- A PAVIS Request record is created/archived with request/response payloads for audit.
Stop an already sent instruction (Instruction Sent → Do not pay)
- Ensure still before deadline. 
- EC+ runs History. If payment_status in {01,02,03,04}, EC+ proceeds to Cancellation and sets Won’t be Renewed when Cancellation OK. If 05/06, EC+ blocks (payment already processed).
- A PAVIS Request record is created/archived with request/response payloads for audit.
Grace period: how to instruct after the instruction deadline?
Enable users to send or change renewal instructions after the due date for Single Orders—within the legally allowed grace period—while staying aligned with PAVIS cut-offs.
Scope & prerequisites
- Applies to: Patents & Designs managed by PAVIS, Type of Order = Single Order. Standing Orders are excluded (“would have already been paid”).
- Feature flag: Solution engineers must enable Use grace period in PAVIS Service Configuration. 

A post-due-date window during which EC+ allows you to send or change instructions (Pay / Do not pay / To be decided), guarded by PAVIS’ Order Until (Grace Period) field. If today is after the guard, the change is blocked.
The guard EC+ uses
- When Use grace period is enabled → EC+ checks Order Until (Grace Period)
- When Use grace period is disabled → EC+ checks Instruction Deadline 
What you’re allowed to do during the grace period
| From → To (Instruction) | Allowed during grace? | What EC+ does | Typical outcome | 
|---|---|---|---|
| Do not pay / To be decided → Pay | Yes, no explicit EC+ date limit; PAVIS’ Order Until (Grace Period) guards acceptance | Sends Z (Single payment order) (+ current spec budget/preview sequence) | Renewal Status = Instruction Sent, price updated; else error if PAVIS rejects (too late) | 
| Pay → Do not pay / To be decided | Yes, guarded by PAVIS | Runs History then Cancellation (if payment not yet processed) | blocked if payment already progressed past allowed status | 
| Abandoned → Pending (asset previously abandoned) | Yes, when grace is active and still before Order Until (Grace Period) | Keep the old renewal (don’t delete), set PAVIS Registration = false, and create a new renewal via P + N + Budget + Preview | New renewal becomes live; old one remains as historical (Abandoned) | 
What happens when it’s too late
- If PAVIS indicates payment cannot be accepted (guard passed), EC+ blocks the save and shows: 
 “It’s too late, your instruction can’t be accepted by Pavis. Please contact Pavis directly.” The record stays unchanged.
- For Pay → Do not pay/To be decided, the History check controls whether Cancellation is still possible. If payment status says it’s already processed, EC+ blocks the change. 
How are future updates to the case transferred?
EC+ starts the Biblio Change process as soon as you modify any “key field” on a Case that’s registered with PAVIS
EC+ only triggers this process for cases registered in PAVIS (Payment Managed By = PAVIS).| Case Type | Fields | 
| Patent (Case status must be Granted or Pending) | 
 | 
| Trademark (Case status must be Registered or Pending) | 
 | 
| Design (Case status must be Granted or Pending) | 
 | 
When you change important Case info (number, status, dates, name, billing…) on a Case managed by PAVIS, EC+ makes sure PAVIS stays in sync.
EC+ looks at any existing renewal/order and then decides whether to:
- just amend details at PAVIS, or 
- cancel an in-flight order first, then amend. 
You don’t choose the flow—EC+ does it for you. You just save your changes.
Changing the Type of Order (Standing ↔ Single)
Keep EC+ and PAVIS aligned when you decide to stop automatic renewals (Standing → Single) or to start automatic renewals (Single → Standing). The system sends the right update to Pavis, when needed, Cancellation, and updates the linked Renewal.
A) Standing → Single (stop automatic renewals)
- Open the Case (Patent/Design) with Type of Order = Standing Order and Provider = PAVIS. 
- Change Type of Order to Single Order and Save. 
- What EC+ does: - Sends the update to PAVIS. 
- If renewal had Instruction = PAY, sets Instruction = To be decided (when within the instruction period). 
- If PAVIS shows the renewal already started, EC+ cancels the order (History→Cancellation) before applying the change. 
 
- Result: - If Order Until / Instruction Deadline is in the future → Type of Order updated and Instruction set to To be decided (status unaffected). 
- If in the past → only Type of Order is updated (no Instruction/Status change). 
- On success: “Your case has been updated.” 
- On failure: “Your case cannot be updated because of a Pavis dependency…” 
 
B) Single → Standing (start automatic renewals)
- Open the Case (Patent/Design) with Type of Order = Single Order and Provider = PAVIS. 
- Change Type of Order to Standing Order and Save. 
- What EC+ does: - Sends the update to PAVIS. 
- Sets Instruction = PAY on the active renewal. 
- When still within the instruction period, EC+ also sets Renewal Status = Instruction Sent. 
 
- Result: - If Order Until / Instruction Deadline is in the future → Type of Order updated and Instruction = PAY (status may move to Instruction Sent). 
- If in the past → only Type of Order is updated (no Instruction/Status change). 
- Success and error messages behave as above. 
 
Abandon a case
What abandoning means
- You keep the record (for audit/history) but change its Status to an abandoned value (e.g., Abandoned/Withdrawn per your org’s picklist). 
- Equinox notifies PAVIS and logs the API call + response in the PAVIS Request object automatically. 
Steps
- Open the case (Patent/Trademark/Design).
- Click Edit and set Status to the correct Abandoned value; Save. 
- The system checks if the case is in PAVIS and then sends the cancellation request based on Payment Status. A history line and the API request details are saved. 
What you’ll see / what happens
- No manual PAVIS action is needed; the automation runs on save. 
- PAVIS request + outcome are stored for audit. 
Delete a Case
What deletion means
- The record is removed from EC+. 
- Before deletion completes, Equinox notifies PAVIS to delete/cancel any open order and logs the request in the PAVIS Request object. 
Steps (End User)
- Open the case record page (not from a list view).
- In the Actions menu, click Delete → confirm in the pop-up. 
- The system: - Verifies PAVIS registration. 
- Chooses the correct API path depending on Payment Status (01/03/05/06 vs 02/04/none). 
- Sends the cancellation request and saves the history + request payload/response. 
- Deletes the EC+ record. 
 
Note: Deletion from a list view is blocked by design so the API step can’t be skipped. Always delete from the record page.
 
                 