Every answer and its explanation appears here once you have finished the path. Each one then links to the matching glossary entry, where the concept is set out in full with its worked example.
1. On an international sale, which limitation periods run in parallel?
That of the receivable against the debtor, that of the insured's action against its insurer, and that of the insurer's subrogated action which inherits the first: not the same duration, not the same starting point, not the same interrupting events
A file is lost on the one nobody watches, which is why counting them is the first step. The answer merging them is the commonest and costliest: an exporter can hold a perfectly valid receivable against its debtor and have lost its recourse against its insurer, or the reverse, because the second is fixed by the insurance contract and often runs from a different event, frequently for a shorter time. The answer making all of them depend on the law of the contract anticipates the next question and gets it wrong.
Glossary entry →2. Worked case: contract governed by French law, jurisdiction given to the courts of the buyer's country, which applies a three-year period and treats limitation as procedural. Receivable due January 12, 2023. Absent any interrupting act recognized by that court, where does it stand?
The forum treats limitation as procedural and applies its own three-year period: the receivable lapsed on January 12, 2026
The French law answer is not absurd, and that is what makes the point hard: some systems do attach limitation to substance, hence to the law of the contract, and reasoning that way is correct elsewhere. That is precisely why the module says to settle the question once per country rather than file by file. The answer running the period from the formal demand confuses the starting point with an interrupting event which, in many systems, is not one. The one seeing an interruption in the indemnity misreads subrogation: the insurer receives the right as it stands, with the time already run, it does not renew it. The October 2024 email, taken up in the next question, is precisely the act that can change this result.
Glossary entry →3. In October 2024 the buyer wrote that it acknowledged the amount and was looking for currency. What is that email worth?
It is the key document: a written acknowledgment of debt interrupts almost everywhere, would start a fresh period, and it is easily obtained from a debtor in difficulty while the relationship has not cooled
The exporter has held the document that saves its file for eighteen months and has not produced it, which is the commonest scenario: an acknowledgment of debt does not look like a legal act when it arrives by email. The answer seeing novation borrows a correct consequence from a different act, the rescheduling agreement, which remakes the debt and can destroy subrogation; acknowledging what is owed remakes nothing. Formal demands do not interrupt in every system and that one must be checked, which makes them less certain, not worthless. The practical step is upstream: obtain that writing at the first serious default, because it can no longer be obtained afterward.
Glossary entry →4. Why does a policy sanction an insured that lets a receivable lapse, even though that receivable was indisputable?
Because the subrogated insurer receives only the right as it stands, and a lapsed receivable leaves it without recourse after paying: the reduction is then argued on that harm and not on a principle
Limitation is not sanctioned as a moral fault but because it destroys the only value left to the insurer after settlement, and that changes the whole discussion: it is argued on harm, which is why the outcome of the worked case depends entirely on whether the email interrupts. If it does, there is no harm and no reduction. The answer collapsing the two periods together is the one the previous question already set aside, and it returns naturally because it is simpler. The one invoking prior recovery borrows a real mechanism from another module of this certification.
Glossary entry →5. What discipline does the module prescribe, and why is an invoice schedule not enough for it?
Keeping a limitation schedule alongside the invoice schedule, with the period and its starting point established once per country, because an overdue invoice announces itself while a receivable dies one morning with nothing to announce it
The two schedules do not carry the same dates and one is not derived from the other: the starting point varies as much as the duration, at the due date, at delivery, at knowledge of the default, and on installment payments whether the period runs per installment or from the last one changes everything. The answer relying on invoice due dates is the most natural because those are the dates already at hand, and it is precisely the reasoning that lets a receivable die inside an accounting system that flags only what it was taught to flag. Systematic protective action is expensive and backfires, since an action brought before a court without jurisdiction does not always interrupt and turns two years of proceedings into two years of loss.
Glossary entry →