We e-mailed a 6-digit code to . It expires in 10 minutes.
Fees are priced per verified report by transaction volume, over whatever period you choose — not monthly. Set your brackets once; the calculation then uses each report's actual transaction count.
Bands are inclusive and may not overlap — 0–30 then 31–60, so a 40-transaction report bills at the 31–60 rate.
The transaction list as finally agreed — after the partner answered the findings and Orienthelfer approved it. The interim report is consolidated from this version, not from the one the verification produced, because corrections made during the resolution round are only in this one. Replace it whenever a later adjustment is agreed.
Several months of verified transactions, read as one report. Choose the period and it is consolidated on the spot — the pivot by budget line and month, planned against actual, and the exchanges behind the rate. Built from the verified reports, so nothing unverified can reach it.
Optional. Supply an interim report prepared outside this system and it is matched against the verified monthly lists, receipt by receipt and budget line by budget line. Differences are reported rather than reconciled away.
The date is recorded automatically — you do not need to enter it — and the assigned A.M.C. controller is notified at once.
Every recorded action: verifications run, reminders sent, rules approved, records changed, sign-ins and "view as" sessions. Manager-visible only, and never edited — entries are added, not amended.
Password — stored only as a one-way salted hash (PBKDF2-HMAC-SHA256, 240,000 rounds). It is never saved in a form anyone can read back, not even a manager or a database administrator.
Second factor — after your password, a 6-digit code is e-mailed to this address. It lasts 10 minutes, works once, and allows 5 attempts. A stolen password on its own opens nothing.
Manager access — the manager can issue you a temporary password or view the application as you, and every such action is recorded in the audit trail with a timestamp.
Raised when sign-ins keep failing. An account locks itself after 3 wrong passwords or 3 wrong codes and frees itself 15 minutes later — nobody is ever stranded waiting for you, and unlock below only saves them the wait.
Give them this password directly; they can change it from their own Account page.
A controller sees only the projects assigned to them, and one of Orienthelfer's people sees only the projects they are on — partners, reports, reminders, reviews and interim reports are all filtered to these. Orienthelfer's To and Cc addresses assign their people automatically; this is where that is adjusted.
Moved to its own tab, where it can be searched and exported — open it.
Every deadline in the verification cycle is counted in working days, so a holiday the calendar does not know about makes each downstream date wrong — and the reminders with them. Changes take effect immediately, on deadlines already running.
Dates marked estimated are not confirmed. The Islamic holidays follow the lunar calendar and their exact days in Lebanon are set by decree, sometimes only days beforehand; the two Easters move as well. Check them against the Banque du Liban banking-holidays calendar and correct them here — that is what this page is for.
Your suggestion goes to the manager for authorisation. It does not move any deadline until approved.
Loading…
Loading…
Closed by default — tap a month to see its reports and where each one stands.
Loading…
Tap a column heading to sort by it; tap again to reverse. Ending soon is any project finishing within six months. Tap a row to open that partner below.
No reports yet — start one from the Report tab.
Notes the AI reads before every verification of this project and updates afterwards. Everything here is editable — nothing is learned silently, and none of it trains a model.
Who works on this project — A.M.C.’s controller and Orienthelfer’s reviewers — is set under Admin › Account › Project assignments, where every project is visible at once.
Leave these empty to follow the standard rule. Anything filled in applies to this project only.
A project starting mid-period usually reports its first months together. Set the last month the first report covers — it runs from the project start date to the end of that month, and the months inside it never appear separately.
Archive a finished engagement — it leaves the active lists but keeps every report, finding and figure. Delete only something created by mistake: it destroys the reports and findings under it. The contract rate drives budget-vs-actual in EUR; the project period drives payment-date eligibility.
Leave these empty to follow the standard rule. Anything filled in applies to this project only.
A project starting mid-period usually reports its first months together. Set the last month the first report covers — it runs from the project start date to the end of that month, and the months inside it never appear separately.
Deadlines are normally worked out from the submission date in working days. Typing one keeps it — an agreed extension is not undone by the next save. Recalculate discards typed deadlines and derives them again. Clearing a field and saving removes that date.
These were paid this month and no contract or agreement on file answers to them. Link one and every later month finds it without being told again — nothing here is guessed, and nothing changes until you choose.
Reads handwritten, Arabic and Turkish scans — checks documentation completeness, re-adds timesheet hours, verifies amounts in words vs figures, and cites the exact rulebook section for every finding. Low-confidence reads are marked for you to confirm.
Waiting to start...
When the partner sends missing documents after the first verification, add them here. Only the rows those documents affect are re-checked — findings they clear are removed, anything new is added, and every other row is left untouched. The whole report is not verified again.
Losing the connection never loses the verification — it keeps running on the server. Collect fetches a finished run's files when they never appeared. Resume continues a run that stopped part-way (credit ran out, key lapsed) — fix the cause first.
Re-verify runs the documents again under the current rulebook and guidelines; rules added since the last run only take effect that way, and it costs API credit.
Upload your hand-verified transaction list for this report. It is compared with the agent's row by row, matched on receipt number, and the differences become draft notes you edit and approve into this project's knowledge base — so the next run starts from your corrections. Nothing is learned automatically.
One conversation per project and month, and both sides write in it. Separate from the formal review, which has an outcome and a date the resolution period runs from — this is the talking around it, kept with the month it is about instead of scrolling away in a chat window.
Orienthelfer's monthly sheet, filled from the verifications rather than by hand. A.M.C. owns the first seven columns; the last three are Orienthelfer's and are left empty. Counts come straight from the reports, so they cannot drift out of step with them.
| Projectnumber | IP | Month | AMC-Staff | OH-Staff | Reviewed | Flagged |
|---|
Click any underlined value to correct it, on the row it belongs to. IP and AMC-Staff are what Orienthelfer's own sheet calls the partner and the controller — their dropdown rejects anything else. OH-Staff is the team pairing on that project. Reviewed is the transaction count on that month's report. Flagged is counted from the findings and cannot be typed: it counts transactions carrying at least one A.M.C. comment, not the number of comments — one voucher with four problems is one flagged voucher.
Add financial guidelines, contract annexes, budgets or amendments anytime — for all partners or one IP, each with a version and effective date. Every active document is mounted into each matching verification run; changes apply from the very next run.
Annex 8: upload the signed budget here with Annex 8 in the name and the scope set to that one project. The interim report then fills its Budget sheet from it and compares actual against budget. The same for a project’s interim report workbook.
Your addition is sent to the manager for authorisation. It is not used in any verification until approved, and you can keep editing it while it waits.
Corrections found on one project and judged true of all of them. Every entry here is read on every verification, whichever partner it is for. A correction that is only true of one partner belongs in that partner's guideline document instead — or, if it is a one-off, unlearn it so it never becomes a rule.
This changes every project, so it goes to the manager for authorisation. It is not used in any verification until approved.
Every save keeps a backup. The rulebook keeps a timestamped copy of each previous version; library documents are stored as uploaded. Given the internal-only classification, documents are read in-context by the AI, not used to train models.
Pick the report below — the findings drafted by its verification run appear here for your review. You edit and send; nothing goes out automatically.
Open in Outlook opens a ready-to-send draft with the full text and
the verified workbook already attached. This works because the app is running on
this machine. Once it moves to the hosted server it will no longer be able to reach
your desktop, and this button will fall back to a plain mail window without the
attachment.
Save draft (.eml) always works: full text, workbook attached, saved
to Downloads — double-click it to open as a draft.
Nothing is recorded against the report and no email is sent. They return to the list tomorrow.
Shown only once. Copy it now.
This is the figure the report is billed on. Confirm it, or type the right number.