Larnaca Marine Charter Ltd
Monthly bookkeeping close (DEMO — not a statutory obligation)
Preview or open work planPeriod 2028-03 · 1 Mar 2028 to 31 Mar 2028
Recorded filing
No filing timestamp is recorded. This is not evidence of a completed filing.
Record a filing already made
This does not submit to an authority or post to ERPNext. Only record a filing after checking what was actually submitted.
Dates and extensions
Statutory date
14 Apr 2028
What the rule said. Never overwritten by anything below.
Due date
19 Apr 2028
5 days later than the statutory date — the walk moves forward onto a working day, never back.
Extension
No extension
Nothing has been granted on this deadline.
Chased against
19 Apr 2028
The due date — this is the date the reminder ladder and the late flag both read.
Record granted extension
Record an extension that has already been granted, with its supporting document. The new date must be later than 2028-04-19. The original statutory and due dates remain in the record.
Future reminder calculations use the extended date. Earlier reminder history and any escalation are retained. Work dates are not moved automatically: review the linked work plan.
Upload the supporting approval first, then return here to record the extension.
Company documents / upload evidenceWhy this deadline exists
Rule · recurring definition
The reusable definition: when a deadline repeats, how its date is calculated and which document categories it requires. Changes belong in the rule catalogue, not in this occurrence.
- Label
- Monthly bookkeeping close (DEMO — not a statutory obligation)
- Key
- CEDAR_DEMO_MONTHLY_BOOKKEEPING v1
- Origin
- firm — the practice imposed it on itself
- Jurisdiction
- XX
- Authority
- —
- Status
- validator signed
- Signed
- 11 Sept 2026, 09:52 by demo|cedar-owner
- Due convention
- kind days_after_period_end · days 14
Company applicability · why this rule applies
The company-specific decision to apply this recurring rule, including approval and active dates. This is the subscription that generates occurrences; it is not another task to complete.
- Reference
- obl_96f555d04d194235
- Status
- active
- Because
- stated_by employee
- Approved
- 11 Sept 2026, 09:52 by demo|cedar-owner
- Active from
- 1 Jun 2026
- Active to
- still active
- Engagement
- eng_782326c003dc4b29
Responsibility and reminder policy
The person accountable for this deadline and whether it is actively managed or calendar-only. Work assignees remain on the linked Epic, Tasks and Subtasks.
- Owner
- Sofia Demetriou
- State
- pending
- Reminder policy
- Active with reminders
- Engagement
- eng_782326c003dc4b29
- Source key
- dl:CEDAR_DEMO_MONTHLY_BOOKKEEPING:2028-03
Work linked to this deadline
Add or remove linked work
Choose an existing item from this company. Removing a link keeps the work, hours, history and document requirements. This changes only the selected item; its children and working dates stay as planned.
| Task | Assignee | State | Due | Estimate |
|---|---|---|---|---|
| T94 Monthly bookkeeping close (DEMO — not a statutory obligation) — 2028-03Deadline work | Sofia Demetriou | open | — | — |
Required documents and evidence coverage
The obligation rule’s required documents become company-specific requirements for this deadline’s period. A work template can bind them to an evidence-collection subtask; staff can add further requirements from the work item.
How evidence is checked
Matching uses the company, document category, account/subject and recorded coverage dates. Existing documents can cover all or part of the requested period; only uncovered gaps are requested. Files marked for replacement do not count. OCR can help populate document information, but an extracted value or a matched file is not approval: covered evidence still needs staff acceptance.
The Epic’s outcome and acceptance checklist describe success. These document requirements provide the evidence for that checklist and can block completion of linked collection work. Completing work does not record an authority filing; use the filing record above.
One statement can cover more than one period. Coverage identifies missing intervals; staff acceptance confirms the evidence is suitable. Neither a matched file nor coverage alone records a completed filing.
| Category | Period covered | Mandatory | State | Still uncovered |
|---|---|---|---|---|
| Bank statementreq_d759906bbc1f4706 | 1 Mar 2028 to 31 Mar 2028 | yes | Outstanding | 1 Mar 2028 – 31 Mar 2028 |
Reminder schedule and escalation
The reminder ladder is a sequence of follow-ups: 14 days before, 3 days before, on the effective due date, and 3 days after; at 10 days overdue it hands responsibility to the firm. It applies only to active obligations with reminders enabled and published document requirements still missing.
Calendar-only, filed/waived, fully covered or already escalated deadlines are not chased. Each stage is recorded once. After an extension, future dates are recalculated; past reminders are not resent.
- Rung now due
- nothing is due to be sent yet
- Next rung
- 14 days before due — 5 Apr 2028
- Reminders sent
- 0
- Last sent
- this client has not been chased about it
- Escalated
- no — nobody has been handed this
The rung is derived from the date on every pass, never counted up per run — a service that was down for a week sends the one reminder now due, not the several it missed. Escalation is a handover, not an extra reminder.
This deadline ladder records communications and reminder history. That record is not confirmation that an email was delivered.