e-Solutions
e-Ledger
The period ledger produced from your accounting entries, taken through approval and left unchanged once the period closes, so ledger work stops being a separate exercise disconnected from your ERP records.
How a period runs
From entry to closed period.
A ledger is the orderly form of what the period has already gathered.
Entries accumulate
Through the period, accounting entries are created as part of daily work.
The period ledger is formed
The ledger and its summary record are prepared and taken through approval.
The period closes
Once submitted, the period is closed and its entries no longer change.
Starting point
Ledger work does not begin when the period ends.
In most organisations the ledger only comes into view once the period has closed: entries are gathered, missing fields are chased and corrections are made after the fact. Yet everything the ledger holds was created during the period itself.
A missing field or an entry that does not tally is expensive to fix once it surfaces at closing; the work moves back and forth between finance and operations, and the closing days stretch.
So we start from where the entry is created rather than from the ledger output: which transaction produces which entry, and which fields does the period require?
Common situations
- Missing fields chased in bulk at the end of the period
- Closing days spent on retrospective corrections
- Ledger preparation that depends on one person
- No clear place where the approved record sits
- A change made in a closed period going unnoticed
Workstreams
The ledger handled at the source of the entry.
Scope is set together based on your current accounting flow and systems; regulatory detail is confirmed with the relevant specialists.
Preparing the period records
The ledger and the summary record that accompanies it, the berat, are produced from the accounting entries of the period, in the structure the period requires.
Field checks on the ERP side
Checks are set up on the ERP side so the fields a period requires are complete and consistent at the moment the entry is made.
Approval and period close
The berat goes through the approval step, the approved record is taken back into the system and can be viewed, and the submitted period is closed to further change.
Delivery approach
We run one full period together.
Ledger work follows the calendar, so the transition is planned around the rhythm of a period.
Reviewing the current flow
We map where entries are created, which fields are completed by hand and what gets repeated at closing.
Adapting the ERP side
The fields and checks a period requires move to the point of entry, so correction work happens during the period rather than at the end of it.
Running one period end to end
The process is run with real entries across a single period and reviewed together.
Monitoring and a closing routine
Closed periods are monitored, the steps that do not work are addressed, and the routine becomes repeatable for the periods that follow.
Scope note
Connections and regulatory detail are agreed at the start of the project
The ledger process does not stand on its own: the entry is created in the ERP, the approval step is completed elsewhere, and the result becomes visible in the system again. Those connections can be built over services; which system takes part at which step depends on your current environment.
Ledger detail follows regulation and can change over time. That is why this page carries no scope or compliance claims; the scope that applies to your organisation is confirmed with the relevant specialists.
Let's talk about your ledger process before the period starts.
Let's review your current closing flow and systems together, and agree the scope and the sequence.