Set up projects and effective rules
Maintain projects, periods, expense types, account mappings, allocation rules, and effective-dated policy configuration.
Ledger helps enterprises prepare project-declaration expense records. It connects source ledgers, time and labor costs, vouchers, purchasing, and assets. Every collection run retains its sources, effective rules, approvals, and audit findings before producing project ledgers and summaries.
Import ledgers and validate fields and references
Approve time before trial and formal collection
Issue ledgers and evidence packages after audit
Ledger links online entry and template import with approvals, allocation, version comparison, audit, and export for zero-integration starting points.
Maintain projects, periods, expense types, account mappings, allocation rules, and effective-dated policy configuration.
CSV/XLSX preflight checks columns, formats, and references; correction files help fix bad rows, and 14 domains retain online-ledger entry.
Validate employee, project membership, dates, and hour limits; retain approval, delegation, rejection, and attendance-difference history.
Combine labor, vouchers, purchases, outsourcing, depreciation, and amortization under effective rules with accounting and tax views.
Missing sources, reconciliation failures, and anomalies become tracked findings; blocking items prevent formal issue or period lock.
Generate project ledgers and summaries from formal versions; asynchronously package XLSX/ZIP with checksums, source versions, and access logs.
Server-side authorization and lifecycle checks govern every critical operation. Formal results, reports, and evidence retain versions and verifiable lineage.
Fourteen versioned templates cover people, projects, attendance, labor, vouchers, purchases, assets, outsourcing, and evidence, with preview, conflict handling, and correction files.
Direct, proportional, multi-stage, capped, and reversal handling share a batch; each line retains source IDs, inputs, and rule versions.
Project ledgers and multi-project summaries pass consistency checks before issue. Successful files stay in private checksum-verified archives.
Researchers, project managers, finance, and external auditors have different boundaries; auditors download only assigned, project-scoped, expiring packages.
Executable rules create blocking or advisory findings; trusted actors are recorded for changes, sensitive reads, and downloads, while evidence is verified before archive.
Container deployment, health checks, versioned gates, encrypted backup, and isolated restore drills accompany production/demo data separation.