This Canadian Credit Law guide develops the legal judgment used to grant credit, resolve disputes and recover accounts. Twenty original written exercises pair realistic files with model answers and assessable rubrics; sixty lessons explain contracts, business liability, security, litigation, estates, construction liens and insolvency. The scope follows the Credit Institute of Canada's Fall 2026 CL1 curriculum as of October 16, 2026. These exercises are a representative learning preview, not an official examination simulation: public material does not establish its item types or counts. Provincial rules and Quebec civil law are distinguished. Citation s1 establishes curriculum relevance, not independent verification of every technical proposition.
What this guide covers
Practise CCP Canadian Credit Law with 20 written exercises, model answers and 60 detailed concepts.
Canadian Credit Law
1. Governing law and Canadian bijuralism
Canadian private law is bijural: Quebec generally uses the Civil Code for private-law obligations, while other provinces generally use common law supplemented by legislation. Federal legislation can operate across both systems. Governing law asks which legal rules determine the obligation; jurisdiction asks which court may hear the dispute. These questions can produce different answers. A choice-of-law clause helps identify the intended law but remains subject to applicable conflict rules and mandatory legislation. Credit analysis should identify transaction connections before importing a familiar provincial rule.
Worked example: An Ontario seller delivers machinery to a Quebec buyer under a contract silent on governing law. The credit officer records negotiation, acceptance, delivery and payment locations before assessing the applicable law and the court connection.
Common mistake: Assuming the creditor's head-office province supplies both governing law and court jurisdiction ignores separate legal tests and mandatory rules.
Official syllabus reference: [1]
2. Court hierarchy and binding precedent
Court hierarchy determines which decisions bind other courts within the relevant legal system. A higher appellate decision can constrain a lower court, while a decision from another province may be persuasive rather than binding. Provincial statutes and procedural rules also differ, so a similar result elsewhere may rest on different legislation. Subject-matter and monetary jurisdiction determine where a claim can begin; appellate hierarchy answers a different question. When evaluating a legal proposition, identify the deciding court, jurisdiction, statutory version and whether later authority has changed its effect.
Worked example: A collector finds a useful Alberta judgment about enforcement. Before applying it to an Ontario file, the reviewer compares the statutes, checks the decision's court level and looks for controlling Ontario appellate authority.
Common mistake: Treating every Canadian judgment as equally binding overlooks court hierarchy, provincial legislation and later decisions affecting the proposition.
Official syllabus reference: [1]
3. Mediation versus arbitration
Mediation uses a neutral facilitator to help parties negotiate; the mediator ordinarily does not impose a decision. Arbitration gives an adjudicator authority, derived from an agreement and applicable legislation, to decide the dispute. A mediated settlement becomes enforceable through its resulting agreement or procedural implementation, whereas an arbitral award follows a distinct recognition and enforcement framework. Clauses should be checked for scope, prerequisites, seat and appointment procedure. Neither starting discussions nor attending mediation automatically suspends a limitation period, so deadline control remains a separate task.
Worked example: A supply agreement requires mediation before arbitration. When payment fails, the creditor invokes mediation, preserves its documents and separately addresses the limitation deadline rather than assuming the scheduled meeting extends time to begin proceedings.
Common mistake: Assuming a mediator can award payment confuses consensual settlement with adjudication and can leave the creditor without an enforceable outcome.
Official syllabus reference: [1]
4. Negligent misrepresentation in credit references
A careless credit reference can support negligent misrepresentation where a legally recognized duty exists, the statement is inaccurate, reasonable care was absent, the recipient reasonably relied on it and loss resulted. A specific statement prepared for a known lending decision differs from casual commentary to an unknown audience. Truth, scope, qualifications and the recipient's actual decision process matter. Liability does not follow merely because the borrower later defaults. Credit references should distinguish verified payment history from opinion and identify the period and information actually reviewed.
Worked example: A supplier reports that a customer paid every invoice within terms, although its ledger shows repeated extensions. The recipient must still show reasonable reliance and resulting loss; the inaccurate reference alone does not prove the entire claim.
Common mistake: Believing an honestly intended reference cannot create liability overlooks negligent preparation and the foreseeable use of specific factual statements.
Official syllabus reference: [1]
5. Vicarious liability for collection conduct
Vicarious liability can make an employer responsible for an employee's tort committed in the course of employment, even without personal authorization of the wrongful act. The connection between assigned work and misconduct matters; an entirely personal venture raises different issues. An independent-contractor label does not resolve the actual relationship or eliminate possible direct negligence claims. For credit operations, collection scripts, escalation authority and staff incentives can reveal how the work created or increased the risk. Organizational liability and the individual collector's own liability are distinct possibilities.
Worked example: A collector makes a defamatory statement while contacting a customer's trade reference as part of assigned recovery work. The employer cannot resolve potential liability merely by showing that its handbook prohibited defamatory language during calls.
Common mistake: Assuming a written prohibition automatically shields the employer ignores the connection between the employee's assigned work and the wrongful conduct.
Official syllabus reference: [1]
6. Defamation and qualified privilege
Defamation concerns reputation-harming statements communicated to someone other than the person or organization identified. In common-law provinces, truth and qualified privilege can be important defences, but their requirements differ. Qualified privilege may protect an appropriate communication between parties with corresponding duties or interests; it is not permission for excessive publication or malicious statements. A credit report should separate supported facts from accusations and reach only an appropriate audience. Quebec analyzes reputational harm through its civil-law framework, so common-law defence labels should not be transferred mechanically.
Worked example: An analyst sends a verified late-payment history to an authorized lender requesting a reference. Copying an unrelated customer list and adding an unsupported accusation of theft changes both the publication scope and the potential legal exposure.
Common mistake: Calling a message confidential does not establish qualified privilege or protect an unsupported accusation circulated beyond an appropriate audience.
Official syllabus reference: [1]
7. Offer, acceptance and objective agreement
Contract formation generally examines whether the parties objectively reached agreement on sufficiently certain terms. An offer invites acceptance; a response changing a material term may instead be a counteroffer. Acceptance can sometimes arise through conduct, such as shipping requested goods, depending on the communications and applicable law. Internal intention alone does not determine the outcome. Electronic exchanges require attention to attribution, timing and agreed methods. A credit file should preserve the quotation, purchase order, acknowledgment and performance evidence to establish both agreement and the terms actually accepted.
Worked example: A buyer requests thirty pumps at a quoted price but adds a different delivery date. The seller's later acknowledgment and shipment must be examined to decide whether it accepted the revised arrangement or maintained another proposal.
Common mistake: Treating every quotation as a binding contract skips whether an offer existed, whether it was accepted and which terms were agreed.
Official syllabus reference: [1]
8. Incorporating standard terms
Standard credit terms become contractual through effective incorporation, not simply because a business prints them somewhere. Timing, notice, signature, prior dealings and the exchange of inconsistent forms affect the analysis. An invoice sent after formation may document a price without adding a new guarantee, interest clause or liability exclusion. Particularly burdensome provisions can require closer attention to notice and enforceability. When purchase orders and acknowledgments conflict, reconstruct the formation sequence rather than assuming the last document always governs. Retain the version of the terms actually presented.
Worked example: A seller first mentions a monthly interest charge on an invoice issued after delivery. The analyst checks the accepted application and earlier communications before treating that charge as part of the original agreement or adding it to arrears.
Common mistake: Assuming repeated invoice printing automatically incorporates every term ignores formation timing, notice and the parties' actual course of dealing.
Official syllabus reference: [1]
9. Consideration and contract variation
Consideration is a common-law requirement involving an exchange supporting a promise; Quebec contractual analysis does not use consideration in the same way. Past performance alone ordinarily does not supply fresh consideration for a later promise. Variations require jurisdiction-specific analysis because Canadian common-law approaches are not perfectly uniform, and duress or other defects may invalidate a change. A documented new advance, binding forbearance or another fresh commitment can materially change the analysis. Credit amendments should specify the exchange rather than relying on an unexplained signature beside revised terms.
Worked example: After a debt arises, a supplier requests a guarantee and promises a documented additional credit facility in exchange. The new facility may support the bargain, unlike a guarantee justified only by goods supplied months earlier.
Common mistake: Applying a single consideration rule throughout Canada overlooks Quebec civil law and differences in common-law treatment of contractual variations.
Official syllabus reference: [1]
10. Assignment of receivables and debtor defences
An assignment transfers a creditor's right to payment, subject to the governing law, the agreement and relevant formalities. It does not automatically transfer every contractual obligation or improve the underlying claim. Notice helps the debtor identify whom to pay, but priority, set-off and discharge questions require separate analysis. Existing defences may remain available against an assignee. Receivables financing can also engage personal-property security law. Before redirecting payment, verify the assignment's authenticity, scope, effective notice and treatment of credits rather than treating a new payment instruction as conclusive.
Worked example: A factor demands payment of an assigned invoice. The buyer produces an earlier valid credit note for returned goods. The factor's ownership of the receivable does not by itself erase the buyer's underlying reduction of the amount owed.
Common mistake: Assuming assignment converts a disputed invoice into an unconditional debt confuses transfer of the claim with improvement of its merits.
Official syllabus reference: [1]
11. Misrepresentation and rescission
A false statement inducing agreement can raise misrepresentation issues, with consequences depending on its nature, applicable law and available remedies. Distinguish a pre-contract representation from a contractual promise, although one statement can have both significance and contractual effect. Rescission seeks to unwind the transaction, while damages compensate a recognized loss under an applicable cause of action. Delay, affirmation, restoration difficulties and third-party rights can affect rescission. Credit analysis should identify the exact statement, its falsity, who made it, the reliance and the remedy sought rather than equating every broken promise with fraud.
Worked example: A borrower supplies altered financial statements to obtain a facility. The lender preserves the originals and approval record to show what was represented and relied upon, then separately evaluates rescission, contractual recovery and any damages claim.
Common mistake: Calling every unfulfilled forecast fraudulent ignores the difference between an actionable false representation and a prediction honestly made on available information.
Official syllabus reference: [1]
12. Expectation damages and mitigation
Contract damages generally seek the financial position performance would have produced, subject to causation, remoteness, proof and applicable legal limits. The claimant must take reasonable steps to avoid preventable loss; mitigation does not demand unreasonable risk or perfection. Costs saved because performance stopped must be considered. A liquidated amount, consequential loss and a refund can overlap, so avoid double recovery. Credit professionals should distinguish the account balance from additional damages requiring evidence. Interest and enforcement costs also need their own contractual, statutory or procedural basis.
Worked example: A buyer reasonably replaces undelivered components for $700 more than the contract price. It documents the alternative purchase and deducts a delivery charge it no longer incurred, rather than claiming gross additional costs without accounting for savings.
Common mistake: Assuming all business disruption is recoverable ignores remoteness, causal proof, reasonable mitigation and costs the claimant avoided because of breach.
Official syllabus reference: [1]
13. Guarantee versus indemnity
A guarantee ordinarily supports another person's obligation, creating secondary liability according to its terms. An indemnity can create a primary promise to compensate for specified loss. The document's legal effect depends on its substance, not its heading, and combined instruments may contain both obligations. Scope, maximum amount, covered transactions, demand requirements and execution must be checked. Applicable provincial writing and other formalities matter. A credit officer should identify what event triggers liability and whether the underlying debt's invalidity or modification affects the particular promise before treating the instrument as equivalent to cash.
Worked example: A director signs a document headed 'Guarantee and Indemnity.' The reviewer separately analyzes the payment guarantee and the promise to cover specified loss, including their limits and triggers, rather than assuming the title establishes identical obligations.
Common mistake: Treating a guarantee and indemnity as interchangeable overlooks their different liability structures and the importance of the actual contractual wording.
Official syllabus reference: [1]
14. Surety discharge after material changes
Changes to the principal credit arrangement can affect a guarantor's liability. In common-law suretyship, an unauthorized material variation may discharge the guarantor, subject to the instrument, consent and applicable rules. Extensions, new facilities, releases of security and settlements require careful review; not every adjustment has the same effect. Continuing-guarantee wording may authorize some changes but should not be assumed unlimited. Before restructuring a debt, compare the original guaranteed bargain with the proposal and obtain any legally effective consent or replacement security needed to maintain the intended protection.
Worked example: A supplier converts short-term trade invoices into a substantially different revolving facility. Before relying on an old guarantee, the credit team checks its variation language and seeks the guarantor's documented consent to the proposed arrangement.
Common mistake: Assuming the phrase continuing guarantee covers every future restructuring ignores contractual limits and the legal consequences of unauthorized material changes.
Official syllabus reference: [1]
15. Sale-of-goods quality and description
Provincial sale-of-goods legislation can imply obligations concerning description, quality, fitness and title, with details and terminology varying by jurisdiction. Fitness analysis can depend on the buyer communicating a purpose and relying on the seller's skill or judgment. A defect allegation therefore requires the specification, intended use, representations and inspection evidence. Commercial exclusions require incorporation and enforceability analysis, while consumer transactions may attract additional mandatory protection. Quebec sale obligations arise through its Civil Code framework. An unpaid invoice must be assessed alongside any substantiated nonconformity defence or counterclaim.
Worked example: A buyer specifies that seals must tolerate a particular chemical, and the seller recommends a model. When that model fails the stated use, the reviewer examines the communicated purpose and reliance rather than dismissing the issue as ordinary buyer selection.
Common mistake: Assuming a signed delivery receipt proves goods met every contractual and statutory quality obligation confuses receipt with substantive conformity.
Official syllabus reference: [1]
16. Passing of title and allocation of risk
Ownership and risk of accidental loss are related but distinct legal questions. The contract may allocate them differently, and statutory default rules fill gaps where applicable. Identification of specific goods, delivery terms and the parties' intention can affect the result. Insurance coverage creates another question and does not itself settle title. Credit professionals should determine who bore the relevant risk when damage occurred before deciding whether the price remains payable. A retention-of-title clause may also function as security and require analysis under the applicable registration regime.
Worked example: A contract states that transit risk passes on carrier collection while title remains with the seller until payment. If the shipment is damaged in transit, the reviewer analyzes both clauses and insurance instead of assuming retained title settles payment responsibility.
Common mistake: Equating ownership, physical possession and risk of loss overlooks contractual allocations that can separate all three in one transaction.
Official syllabus reference: [1]
17. Nemo dat and competing ownership claims
The nemo dat principle generally means a seller cannot transfer better title than it possesses. Statutory and other recognized exceptions can protect particular purchasers, so the principle is a starting point rather than a complete answer. Possession, invoices and payment do not necessarily establish good title. Sale by an authorized agent, estoppel and rules governing certain commercial dispositions may alter the result. When goods are offered as collateral or recovered for resale, investigate acquisition documents and competing ownership claims before relying solely on the debtor's assertion that the goods are its own.
Worked example: A borrower offers a testing machine as collateral but holds it under another supplier's loan agreement. The lender obtains the underlying agreement and serial-number evidence because the borrower's possession and asset list do not establish ownership.
Common mistake: Assuming a purchaser always obtains good title by paying market value ignores ownership defects and the specific requirements of any exception.
Official syllabus reference: [1]
18. Acceptance, rejection and latent defects
Receipt, inspection and legal acceptance of goods are not necessarily simultaneous. Under the applicable sale law and contract, rejection can depend on the breach, notice, timing and whether acceptance has occurred. Using goods or keeping them without objection can affect available remedies, but latent defects may support claims discovered later. Acceptance does not automatically erase every damages remedy. A credit file should record delivery, inspection opportunities, complaints, use and attempted cure. These facts help distinguish a valid rejection from a buyer who must pursue damages while remaining liable for the price.
Worked example: A buyer immediately quarantines incorrectly sized valves and gives a documented rejection notice. Another buyer installs the same shipment and complains later. Their available remedies may differ even though both can prove the original dimensional defect.
Common mistake: Assuming acceptance means all defect claims disappear overlooks the distinction between losing a rejection remedy and retaining a damages claim.
Official syllabus reference: [1]
19. Sole proprietors and separate corporations
A sole proprietorship is generally the individual carrying on business under a personal or trade name, whereas a corporation has a separate legal identity. The distinction determines the contracting debtor, searches and potential recovery assets. A corporate shareholder does not become personally liable merely by owning or managing the business. Guarantees, independent wrongdoing and specific statutory liabilities require separate analysis. Credit applications should record the exact legal name and business form. A familiar storefront name may identify neither the correct individual proprietor nor the corporation that actually purchased the goods.
Worked example: Two customers trade as Summit Supply. One is an individual registered under that trade name; the other is Summit Supply Inc. The supplier verifies identities before opening accounts so its contracts and eventual claims identify the actual debtors.
Common mistake: Treating a trade name as proof of incorporation can produce a claim against the wrong party and an unenforceable credit assumption.
Official syllabus reference: [1]
20. Partnership agency and liability
In a general partnership, a partner can have authority to bind the firm in transactions carried on in the usual course of its business, subject to the governing statute and relevant knowledge of restrictions. Liability consequences differ from those of a corporation and from limited-partnership or limited-liability-partnership structures. An internal restriction may not protect the firm against an outsider who lacks notice where the law otherwise recognizes authority. Credit review should establish the partnership form, partners, transaction purpose and signing authority instead of applying corporate assumptions to every multi-owner business.
Worked example: A partner orders ordinary stock for the firm's retail business despite an internal purchasing cap. The supplier's knowledge of that restriction and the governing partnership rules matter when assessing whether the order binds the firm.
Common mistake: Assuming every partnership provides corporate-style limited liability ignores the legal form and the authority through which partners bind the business.
Official syllabus reference: [1]
21. Actual and apparent corporate authority
Actual authority arises from authority granted to an agent, expressly or by implication. Apparent authority concerns representations attributable to the principal that reasonably support a third party's belief in the agent's authority. An employee cannot ordinarily create apparent authority solely by asserting it. Position, prior authorized transactions and the principal's conduct can matter, as can warning signs or known restrictions. For unusual borrowing, guarantees or security grants, obtain appropriate authority evidence. The question is whether the corporation is bound, which remains distinct from whether the signing employee personally promised payment.
Worked example: A branch manager routinely places stock orders accepted and paid by the corporation. A new request for the corporation to guarantee an unrelated company's debt requires fresh authority analysis rather than automatic reliance on the manager's purchasing history.
Common mistake: Treating a business title as unlimited authority overlooks the transaction's nature, the principal's representations and restrictions actually known to the creditor.
Official syllabus reference: [1]
22. Employee and contractor classification
Worker status depends on the relationship's substance rather than the label selected in an agreement. Relevant factors can include control, tools, integration, financial risk and opportunity for profit, with the applicable test depending on the legal issue. Economic dependence can raise additional common-law questions even where a person is not an employee. Classification affects employment standards, tax and other obligations, but those regimes need not use identical analyses. Credit departments using external collectors should examine how the work actually operates before assuming a services invoice removes employment responsibilities.
Worked example: A collector works exclusively on company systems at fixed hours and cannot subcontract or profit through business decisions. Calling the collector a consultant does not resolve employment status when the practical arrangement resembles controlled personal service.
Common mistake: Assuming a worker's agreement to contractor status settles every legal classification ignores mandatory legislation and the actual working relationship.
Official syllabus reference: [1]
23. Termination entitlements and contractual limits
Termination analysis begins with the applicable provincial or federal employment regime and the employee's circumstances. Statutory minimum entitlements and potential contractual or common-law rights are separate layers. A termination clause may limit additional rights only if legally effective under the governing law. Service, compensation structure, benefits and the reason for termination can matter; a fixed weeks-per-year formula is not a universal common-law rule. Before recording the final employment liability, distinguish wages already earned, minimum termination obligations, any additional entitlement and enforceable release arrangements.
Worked example: A credit manager's agreement mentions a short notice payment. Payroll checks the complete clause, governing legislation, service and benefits before assuming that amount resolves all termination obligations or requesting a release in exchange for an existing entitlement.
Common mistake: Using one universal notice formula ignores statutory differences, contractual enforceability and the individualized assessment of potential additional termination rights.
Official syllabus reference: [1]
24. Accommodation and bona fide requirements
Human-rights law can require accommodation where a workplace rule adversely affects a protected characteristic, up to the applicable undue-hardship boundary. The analysis examines the rule's legitimate purpose and whether the person can perform essential requirements with accommodation. General preference, customer discomfort or unsupported assumptions do not establish undue hardship. Relevant factors and statutory wording differ by jurisdiction. Credit departments should distinguish essential collection duties from one preferred way of performing them and handle medical or other sensitive information proportionately. Accommodation is individualized rather than an automatic exemption from all performance requirements.
Worked example: A collector requests a schedule adjustment connected to a disability. Management identifies required customer coverage, explores workable scheduling alternatives and obtains necessary functional information instead of treating an unchanged shift pattern as inherently essential to the job.
Common mistake: Equating accommodation with removal of every job requirement overlooks essential duties and the individualized examination of workable alternatives.
Official syllabus reference: [1]
25. Fixtures and competing property regimes
An item attached to land may become a fixture rather than remain ordinary movable property. Common-law analysis considers the degree and purpose of attachment, while applicable statutes can alter priority and enforcement consequences. Labels in a loan agreement do not necessarily bind landowners, mortgagees or other third parties. Quebec uses its own classification and property rules. Before valuing installed machinery as recoverable collateral, investigate ownership of the land, installation, removal damage and competing registrations. Fixture status can change both the relevant priority analysis and the practical cost of realizing the asset.
Worked example: A lender finances a production unit bolted into a factory and connected to permanent services. Before assuming ordinary equipment enforcement, it reviews installation purpose, land interests, statutory fixture provisions and the expense of lawful removal.
Common mistake: Assuming anything removable remains personal property ignores why and how it was attached and the rights of land-interest holders.
Official syllabus reference: [1]
26. PPSA attachment and perfection
In a PPSA jurisdiction such as Ontario, attachment concerns when a security interest becomes enforceable against the debtor, generally involving value, debtor rights in collateral and the required security agreement or other recognized basis. Perfection adds the legally required step, commonly registration or qualifying possession, once attachment exists. Registration alone does not create the entire security bargain. These stages affect enforceability and competition with third parties in different ways. Review the agreement, collateral description, debtor identity and perfection method separately, and apply the relevant provincial statute and conflict rules.
Worked example: A lender registers before advancing funds but never obtains the required security agreement for the intended equipment. The registration record does not by itself establish an attached security interest, so the credit file remains substantively incomplete.
Common mistake: Treating a successful registry filing as proof of valid security ignores attachment, collateral coverage and the debtor's rights in the property.
Official syllabus reference: [1]
27. Ordinary priority and purchase-money exceptions
PPSA priority often begins with an ordinary first-to-register-or-perfect comparison, subject to continuity and the statute's detailed rules. A purchase-money security interest can receive special priority when its substantive and procedural conditions are satisfied. Inventory and equipment can have different requirements, including timing and notice issues, so financing a purchase does not automatically create superpriority. Identify the collateral class, purchase-money connection, attachment, registration, required notices and competing claims. Build a chronology before ranking creditors; the date money was advanced is not necessarily the decisive ordinary priority date.
Worked example: An equipment seller finances a new machine despite an existing blanket registration. The reviewer checks whether purchase-money status exists and whether all provincial requirements were satisfied before concluding that the seller outranks the earlier blanket lender.
Common mistake: Assuming every financed purchase defeats an earlier registration overlooks the conditions for purchase-money priority and differences among collateral classes.
Official syllabus reference: [1]
28. Quebec hypothecs and publication
A Quebec hypothec is a real right securing performance of an obligation and can affect movable or immovable property under the Civil Code. Constitution, permitted property, required form and publication must be analyzed separately. Movable rights commonly involve the RDPRM, while immovable rights involve the land-registration system. Publication helps determine effectiveness and ranking against third parties but cannot cure every defect in the underlying act. Credit documentation should use the applicable Quebec structure rather than replacing terminology in a PPSA template and assuming the legal requirements remain identical.
Worked example: A Quebec borrower grants security over business equipment. The lender reviews the hypothec's constituting document and RDPRM publication separately, checking debtor identification and property scope before assigning a recovery value to the collateral.
Common mistake: Assuming an Ontario financing statement is a Quebec hypothec overlooks the distinct constituting rules, publication system and civil-law framework.
Official syllabus reference: [1]
29. Retention of title and lease characterization
Keeping contractual title until payment does not necessarily avoid personal-property security legislation. In PPSA provinces, a transaction's substance and specified statutory inclusions can bring retention-of-title sales and certain leases into the registration and priority framework. A lessor's ownership label therefore may not protect against all competing claimants. Determine the transaction type, applicable provincial definition, term, collateral and required perfection steps. Quebec has distinct rules for reservations of ownership and leasing-related publication. Credit approval should evaluate third-party effectiveness rather than relying solely on who is called the owner.
Worked example: A seller retains title to delivered machinery until the final instalment. When the buyer becomes insolvent, the seller's priority analysis includes the applicable security statute and registration history rather than resting entirely on the invoice's ownership sentence.
Common mistake: Believing ownership language always defeats a debtor's secured lender ignores statutory treatment of retention-of-title transactions and some lease arrangements.
Official syllabus reference: [1]
30. Collection communications and regulated conduct
Collection conduct is regulated through a combination of provincial legislation, licensing rules where applicable, privacy law and general legal duties. Rules can differ between third-party agencies and original creditors, so one national contact schedule should not be assumed. Accurate identification, lawful audience, truthful statements and appropriate dispute handling remain central controls. Threatening an unavailable remedy or implying that ordinary civil debt automatically produces criminal consequences can create serious problems. Classify the collector's role and province, then design communications around the actual permitted process and the evidence supporting the debt.
Worked example: An agency collecting an Ontario account uses a national call script. Its compliance review checks the provincial rules and agency role before approving contact practices, and removes a statement implying that a disputed invoice automatically leads to criminal charges.
Common mistake: Assuming a script approved in one province satisfies every Canadian collection regime ignores differences in legislation and the collector's regulated role.
Official syllabus reference: [1]
31. Privacy purpose and proportionate disclosure
Credit operations handle personal information that can engage federal or provincial privacy legislation depending on the organization, activity and location. Collection, use and disclosure need an applicable legal basis, identified purpose and proportionate scope. Consent rules and statutory exceptions require actual analysis; an unpaid debt does not authorize disclosure to anyone who may influence payment. Accuracy, safeguards, access controls and retention also matter. Distinguish corporate account information from information identifying individuals, and examine any cross-border processing or external agency access before sharing an entire file.
Worked example: A collector wants to send a debtor's complete application to a relative who offered to relay a message. The privacy review separates a limited contact request from disclosure of financial details and checks the lawful basis for each proposed disclosure.
Common mistake: Assuming collection purpose permits unlimited disclosure overlooks necessity, applicable legal authority and the privacy interests of identifiable individuals.
Official syllabus reference: [1]
32. Interest entitlement and rate presentation
An interest calculation requires a legal entitlement before arithmetic begins. Check incorporation of the interest term, its wording, any applicable statutory requirements and the transaction's regulatory context. A rate stated for a period shorter than a year can engage federal Interest Act presentation rules, while criminal-interest and other restrictions require separate current analysis and may have exceptions. Do not infer a lawful charge from software capability. Distinguish contractual arrears interest from prejudgment and postjudgment interest, and avoid silently compounding where the governing term or law does not authorize it.
Worked example: A ledger automatically adds a monthly charge, but the signed agreement contains no interest term. The analyst removes the assumption from the demand and separately investigates any statutory interest entitlement instead of annualizing the software rate and treating it as agreed.
Common mistake: Assuming a mathematically correct interest calculation proves legal recoverability ignores incorporation, statutory requirements and the distinction between simple and compound interest.
Official syllabus reference: [1]
33. Discoverability and limitation periods
A limitation analysis identifies the applicable jurisdiction, claim type, triggering rule and relevant knowledge, rather than merely counting from the latest collection note. Discoverability can affect when a basic period begins, while ultimate periods, special statutes and contractual issues may require separate treatment. An invoice date, due date and discovery date need not be interchangeable. Starting the legally required proceeding in time is also distinct from sending a demand. Build an evidence-backed chronology and maintain the earliest defensible deadline until a legally supported analysis establishes another date.
Worked example: An account contains several deliveries, disputed due dates and a later reconciliation. The reviewer identifies the accrual and discovery issues for the actual claims instead of using the reconciliation date as an automatic fresh starting point.
Common mistake: Assuming the last collection activity restarts the limitation period confuses internal file management with a legally recognized event affecting time.
Official syllabus reference: [1]
34. Acknowledgment and part-payment effects
An acknowledgment or part payment can affect limitation timing under applicable provincial legislation, but the conditions are specific. Substance, signature, recipient, timing and the type of obligation may matter. A request for documents, settlement discussion or denial accompanied by negotiation should not automatically be treated as acknowledgment. A payment also requires analysis of allocation and whether it legally affects the relevant claim or obligor. Preserve the original communication and payment evidence. Until qualification is established, keep the existing limitation deadline rather than extending it through a collection-system assumption.
Worked example: A debtor emails that it needs invoice copies to determine whether any amount is owed. The collector preserves the message but keeps the current litigation deadline because the email does not clearly admit the account balance.
Common mistake: Treating every reply or small payment as a universal restart ignores statutory conditions and the particular debt or party affected.
Official syllabus reference: [1]
35. Proving an account before litigation
A persuasive account claim connects the legal debtor, agreed terms, performance, price, adjustments and unpaid balance through admissible evidence. An invoice is one document in that chain, not automatic proof of every element. Reconcile payments, returns and credits, and investigate specific disputes before pleading the amount. Identify witnesses with relevant knowledge and preserve source records, including electronic order and delivery data. Business-record evidence rules may assist but do not excuse unexplained inconsistencies. A pre-action review should expose gaps early enough to obtain evidence rather than merely assemble a large document bundle.
Worked example: A supplier has invoices but no signed delivery receipts. It retrieves carrier scans, warehouse dispatch records and the buyer's receipt emails, then reconciles a return credit so the eventual claim explains both performance and the net balance.
Common mistake: Assuming the accounting ledger proves the whole cause of action overlooks contractual identity, performance evidence and substantiated credits or defences.
Official syllabus reference: [1]
36. Demand, acceleration and waiver
A demand can request overdue payment, satisfy a contractual prerequisite or trigger an obligation, depending on the agreement and law. Acceleration makes future instalments immediately payable only where an effective right and required process support it. Prior acceptance of late payments may raise waiver or related issues that require careful analysis before strict enforcement resumes. Check notice language, cure opportunities and the amount actually due. A demand should distinguish matured debt from accelerated amounts and avoid asserting remedies that have not become available under the specific bargain.
Worked example: A lender has accepted several late instalments without objection. Before demanding the entire remaining balance, it reviews the acceleration clause, any notice requirements and the effect of its prior conduct, rather than treating one new late payment as self-executing acceleration.
Common mistake: Assuming a demand letter automatically makes every future payment due overlooks acceleration rights, required notices and the parties' prior conduct.
Official syllabus reference: [1]
37. Pleading material facts and proper parties
A pleading should identify the parties, material facts supporting the legal claim and relief sought under the relevant court's rules. Material facts establish the cause of action; evidence proves those facts later. Exact legal names, contractual capacity and representative roles matter, especially where trade names, affiliates or guarantors appear. Adding every associated person without a legal basis can increase cost and procedural risk. Separate the purchaser's obligation from guarantees, independent torts and statutory claims. The pleaded amount should reconcile with the account and distinguish principal, interest and requested costs.
Worked example: A buyer operates through two similarly named affiliates, while its president signed a separate guarantee. The claim identifies the purchasing corporation and pleads the guarantee against the president on its own terms instead of alleging that all related parties bought the goods.
Common mistake: Using a brand name and attaching invoices without material allegations can leave both the debtor's identity and the claim's legal basis unclear.
Official syllabus reference: [1]
38. Service and proof of procedural notice
Service formally provides documents through a method authorized by the applicable court rules or order. Rules vary by document, recipient, location and proceeding, and ordinary business delivery is not necessarily valid service. Proof commonly requires an affidavit or another prescribed record showing who received what, when and how. Response periods must be calculated from the legally relevant service event and applicable counting rules. Where a method fails, an alternative or validating order may be needed. Strong merits do not cure a service defect or justify assuming a default deadline has expired.
Worked example: A claim is left at a corporation's warehouse with an unidentified worker. The creditor investigates the recipient's role and applicable service rule before relying on that date to request default judgment or calculate the response deadline.
Common mistake: Equating proof that someone received an email with valid court service ignores authorized methods, required recipients and the particular document's rules.
Official syllabus reference: [1]
39. Defence, counterclaim and set-off
A defence contests entitlement to the relief claimed; a counterclaim seeks affirmative relief against the claimant. Set-off can reduce the net amount recoverable where the governing legal requirements are met, but not every unrelated complaint qualifies. These positions may coexist and can have different pleading and evidentiary requirements. When a customer alleges defective goods, identify whether it denies any price obligation, claims damages exceeding the invoice or seeks only a reduction. Reconcile the accounting dispute separately from deciding whether the alleged legal defence or cross-claim is sustainable.
Worked example: A buyer admits receiving $20,000 of goods but alleges $4,000 in provable repair losses. The reviewer distinguishes the admitted purchase, the proposed set-off and any counterclaim instead of treating the account as either wholly undisputed or entirely nonexistent.
Common mistake: Assuming any customer complaint cancels the invoice overlooks the legal basis, amount and procedural treatment of the proposed defence or set-off.
Official syllabus reference: [1]
40. Default judgment is procedural relief
Default judgment becomes relevant when a defendant fails to take a required procedural step, such as defending within the applicable time after valid service. The claimant must still meet the court's requirements for entitlement, proof and the relief sought. A liquidated debt can follow a different assessment route from unquantified damages. Default does not guarantee collection, and a judgment may face a setting-aside application under applicable rules. Before requesting it, verify service, deadline calculation, court status, any relevant communications and the supported balance rather than relying on age of arrears alone.
Worked example: A defendant has not filed a defence, but the service affidavit identifies no authorized recipient. The creditor resolves service proof before seeking default because a strong ledger does not establish that the defendant's response period legally expired.
Common mistake: Treating nonpayment as procedural default confuses an alleged breach of contract with failure to respond properly to a court proceeding.
Official syllabus reference: [1]
41. Summary judgment and genuine trial issues
Summary judgment seeks resolution without a full trial where the applicable court rules permit it and the evidentiary record supports the required determination. The precise test and judicial powers vary by jurisdiction. A defended action is not automatically suitable because the creditor has invoices or regards the defence as weak. Conflicting evidence, credibility and the ability to resolve the dispute fairly on the record must be assessed. Build focused admissible evidence addressing the actual contested elements, and compare the motion's cost and likely benefit with settlement or trial preparation.
Worked example: A buyer alleges nondelivery and supplies contemporaneous warehouse emails. The seller obtains carrier and receiving evidence before assessing summary judgment, recognizing that invoice production alone may not permit fair resolution of the delivery dispute.
Common mistake: Assuming summary judgment is default judgment for a weak defence overlooks the different procedural basis and the need for an adequate evidentiary record.
Official syllabus reference: [1]
42. Disclosure, privilege and record preservation
Civil proceedings can require disclosure of relevant records, including unfavorable ones, subject to applicable rules and valid privileges. Solicitor-client privilege protects qualifying confidential legal communications; copying a lawyer onto an ordinary business email does not automatically create it. Litigation privilege has a distinct basis involving preparation for litigation. Preserve relevant emails, messages, recordings and system data when litigation is reasonably anticipated, and suspend conflicting routine deletion where necessary. Separate existing business records from legal advice so the file can be reviewed accurately without assuming every collection document is privileged.
Worked example: After receiving a defended claim, a supplier preserves delivery scans and internal messages discussing an error. It does not delete the unfavorable messages or label them privileged merely because counsel later reviews the collection file.
Common mistake: Believing a privilege label prevents disclosure overlooks the communication's actual purpose and the legal requirements of the privilege asserted.
Official syllabus reference: [1]
43. Settlement privilege and formal offers
Settlement privilege can protect qualifying communications made to resolve a dispute, supporting candid negotiation. The substance and circumstances matter more than a without-prejudice label alone, and recognized exceptions can apply. Formal offers under court rules are a separate mechanism that may affect costs when their prescribed conditions are met. A commercial compromise should therefore distinguish confidential negotiation, a binding agreement and a rules-based offer. Keep limitation and procedural deadlines active during discussions, and record acceptance requirements so an exploratory conversation is not mistaken for a completed settlement.
Worked example: A creditor sends a compromise proposal while preparing its claim. It separately checks whether a formal offer could have costs consequences and keeps the commencement deadline active, because negotiation confidentiality does not itself stop procedural time.
Common mistake: Assuming without prejudice automatically creates privilege, prevents contract formation and pauses litigation combines three legally distinct questions into one label.
Official syllabus reference: [1]
44. Conditional releases and instalment settlements
A settlement should specify whether the original claim is discharged immediately or only after agreed performance. An unconditional release signed before instalments clear can remove remedies the creditor expected to retain. Define covered parties, payment dates, interest, default consequences, credits and treatment of proceedings. Broad language can affect guarantors and other claims, while a reservation of rights must be legally effective rather than merely emphatic. A consent judgment or stay may assist in some cases, but its availability and implementation depend on the court process and the agreement.
Worked example: A creditor accepts reduced payment over three months. The agreement makes the defined release effective after cleared final payment and explains default consequences, avoiding an immediate broad discharge that would leave only the new instalment promise.
Common mistake: Assuming a signed settlement preserves the original debt until payment ignores whether its release or substitution language already changed the creditor's rights.
Official syllabus reference: [1]
45. Execution against assets and exemptions
A judgment establishes an enforceable obligation but does not itself identify collectible assets or guarantee recovery. Execution requires an authorized process against property legally available to satisfy the judgment. Ownership, exemptions, prior security, sale costs and statutory priorities affect net value. Provincial rules determine the available tools and protections, so no universal Canadian exempt amount should be assumed. Asset investigation should distinguish gross market value from realizable equity. Record enforcement expenses and credits carefully because pursuing an encumbered asset can cost more than the unsecured recovery it produces.
Worked example: A debtor owns a vehicle worth $18,000, but a prior secured balance and realization expenses may absorb most proceeds. The creditor investigates legal exemptions and net equity before paying to pursue an apparently valuable asset.
Common mistake: Treating the debtor's gross asset list as available judgment recovery ignores ownership, exemptions, prior claims and the cost of lawful realization.
Official syllabus reference: [1]
46. Garnishment of debts owed to the debtor
Garnishment reaches a qualifying debt owed by a third party to the judgment debtor through the applicable enforcement process. Bank funds and employment income can raise different timing, ownership and exemption issues. The garnishee's obligation, service and response must satisfy the governing rules; a known account number alone is insufficient. Joint interests and protected amounts need separate examination. Competing creditors may affect distribution. Calculate expected recovery only after identifying the legally eligible fund and applicable priorities, and reconcile actual remittances rather than crediting the entire reported holding immediately.
Worked example: A bank reports a debtor's account balance, but part of the fund is subject to a court-confirmed exclusion. The creditor calculates recovery from the eligible remainder and checks competing claims instead of treating the reported balance as its payment.
Common mistake: Assuming garnishment transfers everything a third party holds ignores the debt relationship, exemptions, competing rights and the required enforcement procedure.
Official syllabus reference: [1]
47. Realization waterfalls and net recoveries
A realization waterfall allocates proceeds among costs and claims according to the applicable legal priorities. It is not simply an oldest-invoice list. Security interests, statutory claims, enforcement expenses and the specific insolvency or execution regime can alter ranking. Establish each claim's validity, collateral coverage and balance before applying the order. Avoid using a single blanket priority chart across all asset types and proceedings. For credit decisions, estimate net proceeds after realistic realization costs and senior claims, then distinguish any unsecured deficiency from the secured recovery.
Worked example: A machine sells for $50,000. Before allocating proceeds, the reviewer verifies sale expenses, the senior secured balance and whether any applicable claim outranks it; only the remaining amount can support a junior creditor's recovery estimate.
Common mistake: Assuming the first creditor to demand payment receives sale proceeds first overlooks the legally established order and asset-specific priority rules.
Official syllabus reference: [1]
48. Small-claims jurisdiction and claim splitting
Small-claims pathways differ by province in monetary jurisdiction, subject matter, procedure, representation and enforcement. Some disputes belong in a tribunal rather than the court a creditor expects. A claimant considering reducing a claim to fit a forum must understand whether abandoning the excess prevents later recovery of it. Splitting one cause of action into multiple proceedings can create procedural and finality problems. Confirm current rules and available relief before selecting the forum, and compare total recovery prospects rather than choosing solely because a form appears simpler.
Worked example: A supplier's account exceeds a forum's confirmed monetary jurisdiction. Before reducing the claim, it evaluates whether the excess would be permanently abandoned and compares that result with pursuing the full claim through the appropriate alternative court.
Common mistake: Assuming a creditor can divide one debt into repeated small claims ignores claim-splitting restrictions and the consequences of abandoning an excess.
Official syllabus reference: [1]
49. Estate claims and representative capacity
A deceased person's unpaid obligation may be recoverable through the estate, subject to valid defences, applicable deadlines and administration rules. Identify the authorized representative and the correct capacity for notices or proceedings. Relatives do not ordinarily become personally liable merely through kinship, and involvement in funeral arrangements does not establish authority over estate assets. Preserve the contractual evidence and investigate solvency before estimating recovery. Provincial estate procedure and any insolvency process matter. Personal liability of a representative, if alleged, requires its own legal and factual basis rather than assumption.
Worked example: A debtor's son answers a collection call but has no appointment as estate representative. The creditor identifies the proper administrator and submits supported account evidence instead of demanding that the son pay from his own bank account.
Common mistake: Assuming the nearest relative inherits the debt confuses estate administration with personal liability and can misdirect both communications and proceedings.
Official syllabus reference: [1]
50. Death, co-obligors and continuing guarantees
A debtor's death does not answer whether another borrower or guarantor remains liable. Analyze the particular promise, whether obligations are joint or several, the governing law and any release or variation. A guarantor's death can raise different questions for existing liabilities and future advances under a continuing guarantee. Notice, termination wording and estate law may affect the result. Separate each obligor's account and security position, then credit recoveries without double collection. Family status alone supplies no substitute for an actual co-borrowing agreement or guarantee.
Worked example: Two individuals signed as co-borrowers, and one dies. The lender reviews the surviving borrower's promise and the estate claim separately, ensuring that any estate payment reduces the common debt rather than generating duplicate recovery.
Common mistake: Assuming death either cancels every related obligation or transfers it to family overlooks the distinct promises of co-borrowers and guarantors.
Official syllabus reference: [1]
51. Construction lien entitlement and improvement
Construction lien rights arise under provincial legislation and depend on qualifying supply, the claimant's role, the improvement and required procedural steps. An unpaid invoice does not by itself prove lien entitlement. Identify the project, land or other legally relevant property, contractual chain, work or materials and unpaid amount. Distinguish an improvement-related supply from unrelated maintenance or inventory using the applicable statute's definitions. Provincial exclusions and special projects can matter. The lien supplements a contractual claim but does not guarantee sufficient property value or priority to produce full payment.
Worked example: A supplier sells materials for several jobs under one account. Before asserting a lien, it allocates deliveries to the identified improvement and checks which supplies qualify, rather than treating the entire customer balance as a lien against one property.
Common mistake: Assuming every construction customer's unpaid invoice creates a lien ignores qualifying supply, project identification, statutory exclusions and the required procedural steps.
Official syllabus reference: [1]
52. Statutory holdback and payment exposure
A construction holdback is an amount retained under the applicable provincial statutory framework to protect interests associated with project payment. The required amount, release conditions and consequences depend on the jurisdiction and project facts. Holdback is distinct from an ordinary disputed-invoice deduction and from a trust obligation. Paying a contractor in full does not necessarily eliminate an owner's statutory exposure if required retention or release rules were not followed. Credit analysis should identify the payment chain and applicable holdback mechanism without importing a percentage or release date from another province.
Worked example: An owner proposes releasing retained project funds after receiving a contractor's final invoice. The reviewer checks the applicable holdback and lien conditions first because a final invoice alone does not establish that statutory release requirements are satisfied.
Common mistake: Treating holdback as a discretionary customer discount ignores its statutory purpose and the conditions governing retention, release and potential payment exposure.
Official syllabus reference: [1]
53. Lien preservation versus perfection
Preservation and perfection are separate construction-lien stages under applicable provincial legislation. Preservation protects the lien through the required initial step; perfection requires further action to maintain and advance it. The triggering events, methods and deadlines vary, and contractual payment negotiations ordinarily do not substitute for compliance. Identify the actual statutory event rather than using the invoice date by habit. Maintain both dates and the evidence supporting them. Missing lien protection may leave a contractual debt claim alive, but the creditor can lose the additional property-based remedy.
Worked example: Counsel confirms separate preservation and perfection dates for an Ontario project. A contractor's promised payment falls between them, so the supplier keeps both steps diarized and does not treat the first filing as completion of the lien process.
Common mistake: Assuming preservation permanently secures the lien overlooks the separate perfection requirements and the possibility of losing the remedy through later inaction.
Official syllabus reference: [1]
54. Construction trust funds and tracing
Some provincial construction statutes impose trust obligations on defined project funds for specified beneficiaries. A trust claim differs from a lien against an improvement and from an ordinary unsecured contract claim. The applicable statute determines who holds funds, what funds qualify and when duties arise. Records showing receipts, project allocation and disbursements can be central. Personal exposure for those controlling a corporate trustee requires its own statutory and factual analysis. Do not assume every construction payment is freely available for unrelated debts or that every unpaid supplier automatically proves a trust breach.
Worked example: A contractor receives payment for Project Cedar and uses the money for an unrelated business purchase while project suppliers remain unpaid. The reviewer traces receipts and disbursements under the applicable trust provisions rather than relying only on invoice aging.
Common mistake: Assuming a lien filing proves a trust breach confuses two remedies with different property, evidence, defendants and statutory requirements.
Official syllabus reference: [1]
55. Insolvency stays and proceeding identification
An insolvency stay can restrict collection, litigation and enforcement, but its operation depends on the proceeding, statute, order and creditor position. Bankruptcy, a notice of intention to propose, a proposal and CCAA proceedings are not interchangeable. Identify the commencement event, debtor covered, order terms and any applicable exceptions before acting. The stay also differs from final discharge: it controls current remedies rather than necessarily extinguishing the debt. Suspend unsupported collection steps, preserve evidence and evaluate proof-of-claim or court processes while separately examining secured and ownership rights.
Worked example: A customer announces restructuring, but the notice does not identify the process. The credit team obtains the actual filing or order before deciding whether to continue litigation, file a claim or seek permission for a particular enforcement step.
Common mistake: Assuming every insolvency announcement creates the same stay ignores the proceeding, order, affected debtor and creditor-specific statutory position.
Official syllabus reference: [1]
56. Secured enforcement during insolvency
A secured creditor's position in insolvency depends on valid security, perfection, priority, collateral value and the governing proceeding. Registration is not a universal exemption from stays, notice requirements or court supervision. Federal insolvency rules can interact with provincial property and enforcement law, and receivership may introduce another process. Review the security agreement, searches, balances, default and applicable notices before taking possession or appointing a receiver. Compare lawful realization costs and senior claims with expected proceeds, and identify any deficiency separately from the secured portion of the claim.
Worked example: A lender holds registered equipment security when the borrower enters a proposal process. It verifies the stay and enforcement rules before arranging removal, while checking whether the machine's net value actually covers the secured balance and expected realization expenses.
Common mistake: Assuming registration authorizes immediate seizure in every insolvency ignores applicable stays, notices, court orders and defects in the underlying security.
Official syllabus reference: [1]
57. Proofs of claim and proportional dividends
A proof of claim documents the creditor's asserted entitlement in the insolvency process, including the amount, basis and relevant status. Reconcile payments, credits, security and any set-off before submission. Admission permits participation according to the applicable ranking; it does not promise payment in full. For equal-ranking claims sharing a fixed fund, divide the fund by total admitted claims to obtain the dividend rate, then multiply by the creditor's admitted amount. Use the actual distribution class and trustee information rather than mixing secured realizations with the general unsecured pool.
Worked example: A $40,000 fund is available for $200,000 of admitted equal-ranking claims. A creditor with an admitted $15,000 claim expects $3,000 in that distribution, while keeping any later dividend and accounting adjustment as separate matters.
Common mistake: Treating an admitted proof as a payment guarantee ignores estate resources, statutory ranking and the proportional sharing of an insufficient fund.
Official syllabus reference: [1]
58. Preferences and transfers at undervalue
Insolvency law can permit challenges to certain pre-insolvency transactions, including preferences and transfers at undervalue. A preference concerns favored treatment of a creditor under the statutory conditions; a transfer at undervalue concerns inadequate consideration and other required factors. Timing, solvency, relationship between parties and the applicable test matter, with different rules for different categories. Not every payment shortly before bankruptcy is automatically recoverable. Preserve payment history, negotiations and value evidence when a trustee questions a transaction, and assess the actual provision rather than relying on a single generic look-back period.
Worked example: Before bankruptcy, a debtor pays one related creditor in full and transfers equipment to another affiliate for a nominal price. The reviewer analyzes the payment and sale separately because the potential preference and undervalue claims require different facts.
Common mistake: Assuming every recent payment is automatically void ignores statutory elements, relationship distinctions, timing requirements and the particular remedy being asserted.
Official syllabus reference: [1]
59. Proposal compromise versus bankruptcy liquidation
A proposal seeks a legally binding compromise through the applicable insolvency process, while bankruptcy generally involves administration and realization of estate property under the statutory framework. Proposal terms, voting, approval and creditor classes determine the proposed bargain; an informal payment plan does not have the same legal effect. Assess expected net returns, timing, security and consequences of failure rather than comparing headline percentages alone. Consumer and commercial proposal pathways differ. Creditors should identify which claims are affected and distinguish support for a proposal from abandoning objections to an incorrectly stated claim.
Worked example: A commercial proposal offers a higher nominal dividend than the estimated bankruptcy return but pays over several years. The creditor compares timing, execution risk and class treatment before voting, rather than treating the larger stated percentage as conclusive.
Common mistake: Equating an informal instalment arrangement with a statutory proposal overlooks voting, approval, binding effect and the applicable insolvency protections.
Official syllabus reference: [1]
60. Discharge, exceptions and surviving security
An individual's bankruptcy discharge generally releases personal liability for provable claims, subject to statutory exceptions and the discharge order. It is distinct from an accounting write-off and from the treatment of valid security against collateral. An allegation of fraud does not itself establish a surviving debt; the facts must meet the applicable exception and procedural requirements. Corporate insolvency and dissolution require separate analysis rather than copying individual-discharge rules. Record the legal status of each obligation, any enforceable security and unresolved exception issues before deciding whether further collection is permitted.
Worked example: A supplier receives notice of an individual's discharge. It closes ordinary unsecured collection activity while separately reviewing a documented potential exception, recognizing that an internal fraud flag alone neither proves survival nor authorizes renewed demands.
Common mistake: Assuming discharge either erases every possible right or preserves every disputed debt overlooks statutory exceptions, order terms and the separate position of valid security.
Official syllabus reference: [1]