5092 Add visual learning aids to documentation - Compliance

[shon-button]

Ticket: 5092

🚀 Impact

• Adds infographics to compliance docs

🔬 Local Testing:

Use Open Preview on files:

• docs/compliance/automated_process_compliance_handlers.md
• docs/compliance/penalties.md
• docs/compliance/supplementary_report_handlers.md
  Expected Results
• Infographic displays and correctly details the related documentation
• Infographic includes AI generation details

[fviduya]

This is amazing, @shon-button! A few things I noticed:

1. The scheduled compliance sync is scheduled at 2AM as denoted in tasks.py file instead of 4AM
2. To clarify, if user submits report after the compliance deadline:

• If non-supplementary > Automatic Overdue Penalty only regardless if paid before or after the invoice due date
• Else > GGEAPAR Interest calculated from compliance_deadline + 1 day until the obligation is paid. Automatic Overdue Penalty comes in if obligation is paid after the invoice_due_date.

3. Not covered in these (not sure if needed) is the back-dating logic for when user submits a supplementary report that decreases the outstanding balance > penalty calculation will use the adjusted amount from the start (fee_date) instead of the base amount being reduced on the day the supplementary report was submitted.

[shon-button]

This is amazing, @shon-button! A few things I noticed:

1. The scheduled compliance sync is scheduled at 2AM as denoted in tasks.py file instead of 4AM
2. To clarify, if user submits report after the compliance deadline:

• If non-supplementary > Automatic Overdue Penalty only regardless if paid before or after the invoice due date
• Else > GGEAPAR Interest calculated from compliance_deadline + 1 day until the obligation is paid. Automatic Overdue Penalty comes in if obligation is paid after the invoice_due_date.

3. Not covered in these (not sure if needed) is the back-dating logic for when user submits a supplementary report that decreases the outstanding balance > penalty calculation will use the adjusted amount from the start (fee_date) instead of the base amount being reduced on the day the supplementary report was submitted.

@fviduya

Thanks very much for reviewing the images, your knowledgeable insights are very appreciated!

I have updated images:

• docs/compliance/images/bciers-compliance-cycle.png
• docs/compliance/images/bciers-penalties-overview.png

[fviduya]

Thanks for the updates, @shon-button! Looks good! I couldn't see the other images you had earlier, there was one that illustrates the calculation of penalty when partial payments are made which I think would also be helpful. Not sure if that image also illustrated the part about how penalties were determined if it's not a special case (such as user submitted the report before the compliance deadline). Suggesting to still add those if possible, but overall it all looks clear on my end 🤩

[shon-button]

Thanks for the updates, @shon-button! Looks good! I couldn't see the other images you had earlier, there was one that illustrates the calculation of penalty when partial payments are made which I think would also be helpful. Not sure if that image also illustrated the part about how penalties were determined if it's not a special case (such as user submitted the report before the compliance deadline). Suggesting to still add those if possible, but overall it all looks clear on my end 🤩

Thank-you very, very much @fviduya

Reverted to initial penalty infographic including:

• standard case for reports submitted on or before the compliance deadline: Automatic Overdue begins the day after the compliance deadline if an outstanding balance remains.
• late-report scenarios, distinguishing non-supplementary from supplementary reports.
• partial payment example
• supplementary balance-decrease back-dating, showing that the adjusted amount applies from the fee_date.

[fviduya]

🥇