DeshLoopThakurgaonWhich financial year do these repeated account figures describe?
Three totals repeat under different year labels. Correct period attribution and a corrected/certified account are needed before financial reconciliation.
THE HELD EVIDENCE
Each statement is attached to its source and location. An official claim and a finding from review are shown separately.
The printed figures are income Tk 21,003,524; expenditure Tk 6,920,063; surplus Tk 14,083,461. These remain quarantined source assertions.
The printed figures are income Tk 21,003,524; expenditure Tk 6,920,063; surplus Tk 14,083,461. These remain quarantined source assertions.
FOLLOW THE REASONING
These checks apply to the stated evidence and scope. A flag identifies a question for further review; it does not by itself establish corruption.
Source conflict: all three totals match despite different fiscal-year labels. This does not establish a cash loss or explain why the figures repeat.
Compare income, expenditure and surplus in taka for the same account scope while preserving the two printed year labels.
Cannot determine until the statement period and certified account are confirmed.
An unresolved source-period conflict prevents current-year attribution. Arithmetic agreement alone does not resolve it.
These are possibilities, not established explanations or official replies.
A republication, copied template or incorrect year label could explain the repetition. No explanation is verified.
Issuer clarification, original signed statements and publication/correction history.
THE NEXT EVIDENCE
The status below describes this collection. A record not held here may still exist at the institution.
Obtain confirmation of which year each statement describes, any republication and the corrected version.
Establish the correct period before comparing opening/closing figures and receipt/payment registers.
No submission or response is recorded for this request. Downloading a draft does not send it. Confirm the recipient, add the applicant’s details and use the official submission process.
No official reply to this case is held in the reviewed collection. This does not establish that the institution has never responded elsewhere.
A public case was assembled from retained official records; unresolved questions and missing inputs remain explicit.
Reviewed the separate three-page implementation report. It does not settle the conflicting annual-account years; scheme unit qualifications remain separate.
Selected source passages reviewed; this is not a complete institutional record search.
Selected FormA revenue figures in documents labelled FY 2024–25 and FY 2020–21. No current-year spending attribution is admitted.
Reviewed pages: 1
Method: Visual PDF review and retained-hash checks.
Selected claims above; no executed settlement or independent inspection verified.
Retained source SHA-256
ef971b2f3888c50dcef6457133f8deb9a0e10984071b66013ed09ffe4af83828Capture timestamp:
A matching hash identifies retained bytes; it does not independently authenticate the issuer or establish completeness.
Selected FormA revenue figures in documents labelled FY 2024–25 and FY 2020–21. No current-year spending attribution is admitted.
Reviewed pages: 1
Method: Visual PDF review and retained-hash checks.
Selected claims above; no executed settlement or independent inspection verified.
Retained source SHA-256
913e091e5999a25412d89bd483ecdaacd6ab7a45e2ae0cc494e452d8900fe057Capture timestamp:
A matching hash identifies retained bytes; it does not independently authenticate the issuer or establish completeness.
Separate scheme implementation report. Its ADP/revenue scope is not a correction of either FormA statement.
Reviewed pages: 1, 2, 3
Method: All three pages visually reviewed, including monetary headers and selected rows.
The report mixes ADP and revenue schemes. Allocation-unit wording does not independently establish every scheme amount’s unit; no new BDT conversion or resolution of the FormA period conflict is admitted.
Retained source SHA-256
c25977d9525fbf9a4f17075b9d5b5613eb3fe84c6729253a129f77f3bee30ba5Capture timestamp:
A matching hash identifies retained bytes; it does not independently authenticate the issuer or establish completeness.