VENIKOM ERP — FEATURE BRIEF REF. E.01 APR 2026

eFactura · Electronic invoicing

The invoice is the source of truth — not a PDF in someone's inbox.

Electronic invoicing handled where it belongs: inside the ledger. Every invoice has a link to the document it came from, the approval chain it passed through, the posting it created, and the signature that closed the loop. No reconciliation marathon at month-end.

PAGE REF. E.01

FIG. E.00

§ 01 / 04 The pain we removed

REF. E.01

Invoices do not
belong in email.

Pre-Venikom, the typical month is an archaeology dig: PDFs in inboxes, scans in shared drives, notes in spreadsheets, and everyone retyping the same numbers into different systems until the accountant draws the short straw and reconciles it all under deadline pressure. Errors creep in. Audit becomes theatre.

FIG. E.01.a Before / after diagram

BEFORE

× PDFs scattered across inboxes
× Excel sheets as the master list
× Retyping into accounting at month-end
× Audit trail rebuilt from memory
× Exceptions discovered late

AFTER

✓ One inbox inside the ledger
✓ Invoice status is the master
✓ Posting at receipt, not at close
✓ Audit trail written on every action
✓ Exceptions surfaced in a dashboard

§ 02 / 04 Document lifecycle

REF. E.02

Five steps, every time.

STEP 01

Receive or issue

Supplier invoices arrive through the eFactura channel or via upload. Outbound invoices are issued directly from Venikom ERP — single source, consistent templates, right legal entity.

STEP 02

Match to the ledger

Each document is linked to the purchase order, contract, warehouse entry, or customer it belongs to. The match is explicit; nothing sits in limbo between inbox and posting.

STEP 03

Approve along rules

Approval flows enforce who sees what and in which order. No more informal chains; the trail is captured and searchable — audit-ready by default.

STEP 04

Post to accounting

Once approved, the document flows into financial accounting with its mapping. VAT, cost centres, and analytics are determined at post time — not retyped later.

STEP 05

Archive with the signature

The original document and its chain of approvals land in the archive module. Retention, search, and legal export all happen in the same place as everything else.

§ 03 / 04 What the operator sees

REF. E.03

FIG. E.03.a Inbox

Inbox

Every incoming invoice lands in a single queue — not an email folder. Filters by status, supplier, due date, and amount. The operator works the top of the stack; nothing hides in a sub-folder.

— Status: received · matched · approved · posted · archived
— Bulk actions that respect the approval policy
— Full-text and structured search

FIG. E.03.b Document view

Document view

Open a document and you see both the original and the parsed fields side by side. Hover a field to see its source on the page. Fix a mismatch in-place — the trail captures the change.

— Original + extracted fields, side by side
— Explicit provenance for every number
— Editable with audit, not a replacement

§ 04 / 04 Compliance posture

REF. E.04

Built against the
local rules
we actually live under.

We are not a generic European billing tool squeezed into a Macedonian context. The tax schemas, VAT posting, and archival expectations are shipped — and updated when the regulator publishes. The NBRM exchange rate feed, the UJP MPIN export, and the e-payment cycles live in the same system as this feature.

INTEGRATIONS IN SCOPE

NBRM: Daily exchange rates
UJP: MPIN export for payroll
Fiscal printers: Connect automatically — no setup
Web store: Products & orders
Email: Sent from your own domain
Document storage: Cloud or on your own servers

FIG. E.04 Not a full list — the important ones

See all integrations Pair with intelligence

§ CLOSING — Move the documents where they belong

Your invoices, in one ledger by the end of the quarter.

We'll scope the migration against your current flow, map the integrations, and give you a realistic timeline. The only slide deck you'll need is the one you already have.

Book a demo hello@venikom.com