NEWKodevERP: one controlled line from purchase request to general ledger →
Home / KodevERP
New · KodevERP · Procurement, Payments, Fixed Assets and General Ledger

One controlled line from the purchase request to the general ledger.

Most organisations run purchasing, supplier payments and the fixed asset register in separate tools. KodevERP joins them, so finance sees one record from the first request to the last depreciation entry.

  • Budget checked before any order
  • Every asset traced to its purchase order
  • Every event posted to the ledger

Illustrative screen with demo data.

Why finance chooses it

Know what was bought, who approved it and where it sits in the books.

01

Budget control before commitment

An over-budget requisition cannot be approved until a budget extension is raised and approved by a second person within their authority limit.

02

Every asset traces to a purchase order

Assets are capitalised from received goods, with cost, vendor and category locked. An asset without a PO is a controlled exception with a reason.

03

Nothing waits unnoticed

Every open step names the people who can act on it and how long it has waited. One widget lists who has what pending across the organisation.

04

Journals your GL can rely on

Depreciation runs monthly and in sequence. Every journal balances, goes to your general ledger as a batch file and is reconciled before the period is closed.

05

IAS 16 and IAS 36 reporting built in

The IAS 16 roll-forward, revaluation surplus, impairment and disposal gain or loss come straight from the register, ready for the year-end notes.

06

Ready for audit on any day

Maker-checker on every financial event and access change, segregation-of-duties rules, and an audit trail that shows if a record was altered.

The flow

One flow, from request to register.

Ten steps in a fixed order. Each one is recorded, each approval needs a second person, and the tracker shows who holds the next action.

01 · REQUEST

Requisition

Raised by a site or department.

02 · SOURCING

Vendor and price

Vendor and price selected.

03 · BUDGET CHECK

Within budget

Extension needed if over budget.

04 · PURCHASE ORDER

Order issued

Issued after approval.

05 · RECEIVING

Goods received

A goods received note per delivery.

06 · INVOICES

Invoice recorded

Recorded against the order.

07 · PAYMENT

Payment approved

Approved by a second person.

08 · SETTLEMENT

Payment confirmed

Settlement confirmed and recorded.

09 · CAPITALISE

Units become assets

Received units are capitalised.

10 · ASSET REGISTER

On the register

Tagged, assigned and depreciated.

Then the asset lifecycle, with a balanced journal for every financial event

Monthly depreciationTransfer between sitesRevaluation and impairmentPhysical verificationDisposal
Procurement and payments

Approved before it is committed.

The budget is checked on the requisition, and no one can approve their own request or approve beyond their limit.

  • Budget first: the budget line, the amount available and the shortfall sit on the requisition
  • A second person approves each budget extension, which tops up the budget line
  • Reject, withdraw and cancel each need a reason that stays on the record
  • One inbox for pending tasks across purchasing, payments and assets
  • When Approve is not offered, the screen says why and who can act

Illustrative screen with demo data.

Fixed assets and the general ledger

Balanced journals, reconciled balances.

One register for premises, plant and machinery, IT hardware, vehicles, furniture and software licences, kept in step with your general ledger.

  • Depreciation runs month by month, straight-line or reducing balance, with residual values
  • The journal is shown before approval, and it has to balance
  • One person prepares the run and the GL controller approves it
  • Each journal is marked posted with the ledger’s batch reference
  • Once reconciled, the period is closed against further entries

Illustrative screen with demo data.

Eight standard reports, each exportable

Asset registerDepreciation scheduleIAS 16 roll-forwardDisposalsPhysical verificationCustodiansExpiry datesSite summary
For every role

Each person lands on the page for their job.

Nine role-based landing pages, each limited to the user’s rights and scope.

01

CFO

Net book value, open orders, pending approvals and a control watch.

02

Senior management

An executive overview of spend and assets.

03

Audit and control

Exceptions, segregation of duties and the audit log.

04

Payments

Invoices, payment approvals and settlements.

05

Procurement officer

Requisitions, sourcing and purchase orders.

06

Budget approver

Budget lines and extension requests.

07

Stores

Receiving, with a goods received note per delivery.

08

Asset management

Capitalisation, transfers, verification and disposal.

09

Requester

Raise a request and follow it on the process tracker.

Controls

Controls your auditors will recognise.

The security model follows the way well-governed organisations separate duties between business users, checkers, administrators and audit.

Maker-checker everywhereNo one approves their own request, whether a financial event or a change in access.
Segregation of dutiesConflicting roles, such as asset inputter and finance checker, cannot be held together.
Administrators see no moneyThe system administrator manages access only and cannot open asset screens or approve.
Data scope on every userSite, region or company-wide, applied to screens, reports, exports and approvals.
Tamper-evident audit trailEvery action is logged with user, time and old and new values, in a hash-chained log.
Sign-in policyPassword rules, lockout, idle timeout, single session and disabling of dormant users.
Available today

Working now, ready to demonstrate.

  • Request-to-payment tracker with budget control
  • Capitalisation from received purchase orders
  • Register, depreciation, transfers, revaluation, impairment and disposal
  • Balanced journals, batch GL file, reconciliation and period close
  • Physical verification by tag scanning
  • Role-based landing pages and executive overview
At implementation

Completed with your team.

  • Real-time GL posting through an adapter for your finance system
  • Active Directory or single sign-on
  • Payment file and withholding tax rates
  • Your approval matrix, GL mapping and master data
  • User acceptance and security testing with your teams
Works beside your finance system

Your ledger stays the book of record.

KodevERP is the sub-ledger and your existing general ledger remains the book of record. Users work in a browser, with nothing to install on their PCs.

Running a bank? KodevFAM is our fixed assets system built for banks, with a separate Ijarah book and journals to the core banking GL.

RoleSub-ledger for procurement, payments and fixed assets, with a built-in general ledger
GL outputBalanced batch file in CSV format, each journal with a unique reference, ready for the journal upload of your ERP or accounting system
ReconciliationSub-ledger against posted GL balances by account; the period locks once reconciled
Asset classesPremises, plant and machinery, IT hardware, vehicles, furniture and software licences
StandardsIAS 16 and IAS 36 reporting from the register
AccessBrowser-based; Active Directory or single sign-on completed at implementation

See it run on your own process.

Ask for a guided demonstration of KodevERP for your finance and technology teams.