Skip to main content
IBC, RESTRUCTURING & DISPUTE RESOLUTION

Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow

A detailed, decision-useful guide with current 2026 framework, legal and financial mechanics, worked examples, documentation controls, risk analysis and primary-source references.

Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow visual

The resolution professional (RP) is a statutory process manager, not the commercial owner of the corporate debtor. Duties span preservation of value, custody/control, CoC administration, claims, information, avoidance-transaction work, compliance and reporting under the Code and current CIRP Regulations.

Finin2min takeaway

  • Classify before computing.
  • Use the law/regulation in force for the actual transaction or process date.
  • Separate legal, tax, accounting and cash-flow conclusions.
  • Reconcile every material conclusion to evidence and the filed output.
01jurisdiction and applicant
02debt/default evidence
03statutory gateway
04process rights and moratorium

1. Overview — what exactly are we analysing?

The resolution professional (RP) is a statutory process manager, not the commercial owner of the corporate debtor. Duties span preservation of value, custody/control, CoC administration, claims, information, avoidance-transaction work, compliance and reporting under the Code and current CIRP Regulations.

This version focuses on mechanics, computation, evidence and worked examples. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, the objective is not to produce a one-line rate or checklist answer. The objective is to make the position reproducible: another reviewer should be able to identify the legal event, apply the current rule, rebuild the calculation and trace the result into the relevant return, form, register, financial statement or board paper.

What makes this topic difficult?

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, the difficult part is linking jurisdiction and applicant to debt/default evidence and then proving the result through appointment order. A commercially similar transaction can produce a different outcome when the profile-specific facts change. The first failure mode to guard against is acting beyond authority, so this guide starts with classification and evidence rather than a headline percentage.

2. Current framework — 5 September 2026

Current-position note for Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow. The IBC process framework changed materially in 2026, including amendments to the Code and multiple IBBI process regulations and forms. Every admission, CIRP, liquidation or personal-guarantor workflow should therefore be checked against the regulation set and form in force for the relevant proceeding date, not an old procedural checklist.

The RP’s powers and duties should be read with the IBC and CIRP Regulations in force for the proceeding date. This point is the first technical checkpoint because a wrong classification at this stage contaminates every later calculation. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, that means the computation file should show the classification step separately from the amount calculation.

The RP must distinguish decisions within statutory/professional authority from matters requiring CoC approval under the Code. In practice, finance teams often discover this issue only during return preparation or diligence; the better control is to resolve it when the transaction is designed. If the fact changes, the team should rerun the conclusion rather than preserve the old answer for convenience.

Going-concern operations require cash, vendor, employee, insurance, licence and information controls. The supporting memo should state the factual assumption that makes the rule relevant and identify the document that proves that assumption. The practical consequence is that the same cash amount can produce a different tax, accounting or regulatory result when the legal fact pattern changes.

Claims and creditor records should be updated transparently and tied to the current process formats. A reviewer should be able to reproduce the conclusion from the source records without relying on a management explanation or a spreadsheet note. This is also where audit defence is won: consistent contracts, registers, bank evidence and filed forms are stronger than a later explanatory note.

Conflicts, related-party issues and professional appointments require documented independence and approval controls. Where the commercial contract uses a broad label, the legal/tax analysis should translate that label into the statutory concept before applying a rate, formula or form. The article therefore treats this as a decision rule, not as a generic caution.

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, where an older circular, precedent, section number or accounting policy is relevant to an earlier period, keep it in the chronology but label it as historical. The current-period analysis should not silently mix two regimes.

Decision flow for Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow
A controlled decision flow: classification → rule → computation → evidence → filing/review. Local SVG, responsive and kept in normal document flow.

3. Detailed mechanics

Computation and evidence focus

This version focuses on mechanics, computation, evidence and worked examples. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, start with the legal event and transaction date, then build a source-to-output bridge. The computation should show opening position, event-specific movement, tax/accounting/regulatory classification, amount recognised, closing position and the exact return/form/register where the outcome is reported.

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, a reviewer should be able to select any material number and trace it backwards to the governing rule and source document. Where the answer is conditional, show both the base case and the fact that would flip the result. This is more useful than a single “applicable/not applicable” conclusion because it tells the finance team what to monitor before filing.

How the mechanics should be documented

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, create a transaction sheet with six columns: legal event, date, party/status, source document, rule relied on and amount/result. This prevents the common problem where the amount is correct but the legal reason is missing, or the legal memo is correct but the underlying amount is pulled from the wrong ledger. Add a seventh column for the person responsible for the next action.

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, create a reconciliation bridge that begins with the source system or legal register and ends with the statutory output. Differences should be explained, not manually forced to zero. In this article, the bridge may need to distinguish claim amount, admitted debt, ledger balance, liquidation value and resolution-plan distribution. The working should state the purpose, date and source of each value so a legitimate difference is not mistaken for an error — and an actual mismatch is not hidden as a “valuation difference”.

Practitioner deep dive — five topic-specific checkpoints

Technical checkpoint 1

The RP’s powers and duties should be read with the IBC and CIRP Regulations in force for the proceeding date. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, this checkpoint should be resolved before the team moves to "take formal handover". The working paper should identify the exact fact being tested, the date on which that fact is measured, and the source record used to support it. A useful evidence anchor here is appointment order. If that record points in a different direction from the spreadsheet or commercial summary, the legal classification should be reconsidered before any number is carried into a return, model or statutory form.

Computation consequence. The failure mode to test is acting beyond authority. Do not solve that risk by inserting a balancing figure. Instead, rebuild the bridge from source fact → applicable rule → amount/character → reporting destination. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, the calculation file should preserve both the original source amount and every adjustment, allocation, valuation or classification step applied to it. This lets a reviewer distinguish a genuine legal adjustment from an unexplained spreadsheet difference.

Technical checkpoint 2

The RP must distinguish decisions within statutory/professional authority from matters requiring CoC approval under the Code. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, this checkpoint should be resolved before the team moves to "secure records/assets/accounts". The working paper should identify the exact fact being tested, the date on which that fact is measured, and the source record used to support it. A useful evidence anchor here is handover inventory. If that record points in a different direction from the spreadsheet or commercial summary, the legal classification should be reconsidered before any number is carried into a return, model or statutory form.

Computation consequence. The failure mode to test is weak handover evidence. Do not solve that risk by inserting a balancing figure. Instead, rebuild the bridge from source fact → applicable rule → amount/character → reporting destination. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, the calculation file should preserve both the original source amount and every adjustment, allocation, valuation or classification step applied to it. This lets a reviewer distinguish a genuine legal adjustment from an unexplained spreadsheet difference.

Technical checkpoint 3

Going-concern operations require cash, vendor, employee, insurance, licence and information controls. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, this checkpoint should be resolved before the team moves to "constitute/administer CoC". The working paper should identify the exact fact being tested, the date on which that fact is measured, and the source record used to support it. A useful evidence anchor here is bank and asset-control records. If that record points in a different direction from the spreadsheet or commercial summary, the legal classification should be reconsidered before any number is carried into a return, model or statutory form.

Computation consequence. The failure mode to test is CoC approvals not documented. Do not solve that risk by inserting a balancing figure. Instead, rebuild the bridge from source fact → applicable rule → amount/character → reporting destination. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, the calculation file should preserve both the original source amount and every adjustment, allocation, valuation or classification step applied to it. This lets a reviewer distinguish a genuine legal adjustment from an unexplained spreadsheet difference.

Technical checkpoint 4

Claims and creditor records should be updated transparently and tied to the current process formats. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, this checkpoint should be resolved before the team moves to "manage claims and going concern". The working paper should identify the exact fact being tested, the date on which that fact is measured, and the source record used to support it. A useful evidence anchor here is CoC minutes. If that record points in a different direction from the spreadsheet or commercial summary, the legal classification should be reconsidered before any number is carried into a return, model or statutory form.

Computation consequence. The failure mode to test is claims register not updated. Do not solve that risk by inserting a balancing figure. Instead, rebuild the bridge from source fact → applicable rule → amount/character → reporting destination. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, the calculation file should preserve both the original source amount and every adjustment, allocation, valuation or classification step applied to it. This lets a reviewer distinguish a genuine legal adjustment from an unexplained spreadsheet difference.

Technical checkpoint 5

Conflicts, related-party issues and professional appointments require documented independence and approval controls. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, this checkpoint should be resolved before the team moves to "run resolution/valuation/information process". The working paper should identify the exact fact being tested, the date on which that fact is measured, and the source record used to support it. A useful evidence anchor here is claims register. If that record points in a different direction from the spreadsheet or commercial summary, the legal classification should be reconsidered before any number is carried into a return, model or statutory form.

Computation consequence. The failure mode to test is professional conflicts not checked. Do not solve that risk by inserting a balancing figure. Instead, rebuild the bridge from source fact → applicable rule → amount/character → reporting destination. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, the calculation file should preserve both the original source amount and every adjustment, allocation, valuation or classification step applied to it. This lets a reviewer distinguish a genuine legal adjustment from an unexplained spreadsheet difference.

4. Decision workflow

1Take Formal HandoverBuild the file so this step is evidenced before the next one is computed or filed.
2Secure Records/Assets/AccountsBuild the file so this step is evidenced before the next one is computed or filed.
3Constitute/Administer CocBuild the file so this step is evidenced before the next one is computed or filed.
4Manage Claims And Going ConcernBuild the file so this step is evidenced before the next one is computed or filed.
5Run Resolution/Valuation/Information ProcessBuild the file so this step is evidenced before the next one is computed or filed.
6File Reports And Preserve Audit TrailBuild the file so this step is evidenced before the next one is computed or filed.

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, each workflow step should have a named evidence owner. Finance may own the ledger, legal may own contract/approval status, tax may own classification/return treatment and secretarial/compliance teams may own statutory registers and filings. The hand-off points should be recorded because an ownerless spreadsheet is not a control.

5. Worked example

Illustrative worked example

Facts. After appointment, an RP discovers unreconciled bank accounts, missing inventory records and a major vendor threatening disconnection.

Analysis. The first priority is not drafting a resolution plan; it is stabilising records, control, cash and critical operations while documenting issues for the CoC.

Finin2min control. This Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow example is deliberately simplified. In a live transaction, add dates, counterparties, statutory status, taxes already withheld/paid, accounting entries and form/return references before treating the illustration as a filing position.

The Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow worked example should be accompanied by a sensitivity note. Identify the profile-specific assumption most likely to change the result and show how the conclusion changes if it moves. The sensitivity should use the actual driver in this article — not a generic market variable — so management can monitor the fact that truly changes the legal, tax or model outcome.

6. Scenario analysis

ScenarioWhat changesReviewer action
Base caseCore facts align with the intended legal routeCompute and report using the primary rule, with a clear source bridge.
Classification changesOne decisive fact changes — instrument, party, project use, resident status or process stageRe-run the rule before changing only the numeric output.
Timing changesAll facts are same but transaction/allotment/default/completion date changesRe-test the applicable law, rate, deadline and limitation/holding-period consequences.
Data mismatchCommercial report differs from statutory register/return/bank recordPause filing and reconcile the underlying records first.

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, scenario analysis is a control for conditional law and model sensitivity rather than forecasting theatre. The scenario table should identify the fact that must be watched, the evidence that proves a change, and the action that follows when the fact crosses from the base case into an exception.

7. Documentation and audit trail

Core evidence file

  • appointment order
  • handover inventory
  • bank and asset-control records
  • CoC minutes
  • claims register
  • compliance calendar
  • IBBI forms/reports

Evidence standards

  • Use final signed/executed documents, not only drafts.
  • Preserve the version of valuations and models actually approved.
  • Keep bank/portal acknowledgements and not just screenshots.
  • Reconcile dates across agreement, ledger, register and filing.
  • Record reviewer name/date and unresolved assumptions.
  • Archive the current primary-source rule relied on.

For high-value or litigated Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow matters, add a chronology and an issues index. The chronology should be factual and date-based; the issues index should state the rule, management position, contrary evidence and remediation owner. This makes future assessment, diligence or dispute work materially faster.

Evidence-to-conclusion matrix for Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow

Use this Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow matrix as a file-index template. It links each source record to a process step and a known failure mode, so evidence is collected for a reason rather than archived as an undifferentiated document dump.

EvidenceDecision stepReviewer testRed flag
appointment ordertake formal handoverReconcile appointment order to the working used for take formal handover; investigate dates, quantities, values and legal status before sign-off.acting beyond authority
handover inventorysecure records/assets/accountsReconcile handover inventory to the working used for secure records/assets/accounts; investigate dates, quantities, values and legal status before sign-off.weak handover evidence
bank and asset-control recordsconstitute/administer CoCReconcile bank and asset-control records to the working used for constitute/administer CoC; investigate dates, quantities, values and legal status before sign-off.CoC approvals not documented
CoC minutesmanage claims and going concernReconcile CoC minutes to the working used for manage claims and going concern; investigate dates, quantities, values and legal status before sign-off.claims register not updated
claims registerrun resolution/valuation/information processReconcile claims register to the working used for run resolution/valuation/information process; investigate dates, quantities, values and legal status before sign-off.professional conflicts not checked
compliance calendarfile reports and preserve audit trailReconcile compliance calendar to the working used for file reports and preserve audit trail; investigate dates, quantities, values and legal status before sign-off.acting beyond authority
IBBI forms/reportstake formal handoverReconcile IBBI forms/reports to the working used for take formal handover; investigate dates, quantities, values and legal status before sign-off.weak handover evidence

8. Risk controls and common mistakes

  • acting beyond authority
  • weak handover evidence
  • CoC approvals not documented
  • claims register not updated
  • professional conflicts not checked

Most Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow errors are not simple arithmetic errors. They arise when the right arithmetic is applied to the wrong legal bucket, a stale rule is used, a decisive date is missed, or commercial-system data is allowed to overwrite the statutory evidence trail. Controls should therefore target the specific risks listed above rather than merely recalculate the final total.

9. Professional review checklist

  • Has jurisdiction and applicant been resolved using the current framework for the actual transaction/process date?
  • Can the conclusion be traced to appointment order and handover inventory?
  • Has the team separately documented debt/default evidence and statutory gateway rather than assuming one answers the other?
  • Are the dates needed for take formal handover and secure records/assets/accounts supported by source records?
  • Has the specific red flag “acting beyond authority” been tested and closed?
  • Do the working papers explain any difference among claim amount, admitted debt, ledger balance, liquidation value and resolution-plan distribution?
  • Are the worked-example assumptions clearly separated from the actual Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow fact pattern?
  • Has a second reviewer checked the technical conclusion, arithmetic and evidence trail for Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow?

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, a finance expert should review the economics and reconciliation; a tax/legal/secretarial professional should review the governing framework and filing; and the transaction owner should confirm that the factual assumptions used in the memo are actually true. The review is complete only when these perspectives agree on the same dated fact set and unresolved exceptions are explicitly assigned.

10. Frequently asked questions

What is the first question to ask?

Start with jurisdiction and applicant for Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow. A commercial label is not enough; identify the parties, the profile-specific legal/economic event, the decisive date and the governing regime before calculating or filing anything.

Which law should be cited for a 2026 transaction?

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, The IBC process framework changed materially in 2026, including amendments to the Code and multiple IBBI process regulations and forms. Every admission, CIRP, liquidation or personal-guarantor workflow should therefore be checked against the regulation set and form in force for the relevant proceeding date, not an old procedural checklist.

Can I rely only on a broker, ERP, portal or consultant report?

No. For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, secondary reports are useful working evidence, but the final position should reconcile to the profile-specific source file — including appointment order, handover inventory — and to the current primary-source rule.

What if two values are different?

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, do not force them to match. First identify whether they answer different questions. In this pillar, the relevant bridge may involve claim amount, admitted debt, ledger balance, liquidation value and resolution-plan distribution. Label each value by purpose, valuation date and source, then document why the difference is legitimate or what correction is required.

What is the biggest practical error?

acting beyond authority. The remedy is to resolve the classification and evidence before filing or closing.

How should I prepare for scrutiny or diligence?

For Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow, maintain a dated technical memo and a file index that includes appointment order, handover inventory, bank and asset-control records. Preserve the calculation version, reviewer sign-off and the reconciliation from those source records to the statutory filing, model, board paper or financial statement that uses the conclusion.

Should the example be copied into my return or model?

No. The Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow example demonstrates mechanics only. Replace each assumption with the actual dates, status, amounts and documents in your case, and re-check the current rule before using the result in a return, model, filing or decision memo.

When should the analysis be refreshed?

Refresh the Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow analysis whenever a fact affecting jurisdiction and applicant, debt/default evidence or statutory gateway changes, or when the applicable law/regulation, approval status, transaction date or source evidence is updated.

11. Primary sources and validation basis

This article is anchored to primary/regulator material. Always check later amendments, notifications, circulars and transaction-specific facts before acting.

Disclaimer: This Resolution Professional Duties: Law, Timelines, Rights and Practical Workflow guide is for general educational information and does not constitute legal, tax, accounting, investment or financial advice. Transaction-specific positions may differ based on facts, dates, jurisdiction, documentation and later amendments. Obtain professional advice before acting.