Less re-entry for the accountant
A cloud interface keeps documents and context together, including for colleagues who create a document but are not accountants.
Accounting
Every posting knows which car it came from.
Double-entry accounting and tax records built into the dealership, so a document carries its vehicle and order, or sends that context to your own ledger, and month-end becomes a view rather than an investigation.
Accounting
Sample data
PostingSample data · entity CZ-01
Octavia 2.0 TDI · every posting
Purchase invoiceSourcing
476 900paid
Transport & VATCarvago BUY™
31 500paid
Preparationwork order 4471
4 000internal
Sales invoiceUsed Car Sales
589 000deposit 50 000
Insurance commissionpartner
1 420paid
Gross margin on this car78 020
Nobody typed these lines into accounting in the concept. Each retained the module that created it; automatic bank matching leaves one open item.
A code-native posting list for one sample Octavia: purchase, transport and VAT, preparation, sale and insurance commission, each retaining the source module or work order, followed by the concept gross margin. Sample data, not a live ledger or measured result.
- Best fit
- Accountant · Site manager · CFO or controller · External bookkeeper
- Operational job
- Keep every sales, workshop, stock, bank and commission posting tied to its source vehicle, branch and order so finance can match payments, close entities and answer vehicle-margin questions without reconstruction.
- What you get
- Postings and payment matches traceable to the vehicle, order and legal entity.
The problem
Accounting usually finds out last, and separately.
Documents arrive in a folder, get retyped into another program and lose the connection to the car and order that produced them. Whether you use Omnetic Accounting or keep your own ledger, the posting should carry that context from the start.
Or communicate with your ledger
A local statutory ledger can remain in place while receiving clean postings through the agreed market integration.
Accounted at the level you work
Branch, order or minor job remains on the record, so a figure can be opened to the business event inside it.
The workflow
Every document reaches a ledger you can trust
Five stages from a business event to a statutory filing and management view. Select one.
Invoices issued and read receipts
Issue invoices from the deal, send them from the system and see delivery or read status where the channel supports it.
Pricelist items drop onto the document without retyping, and the vehicle and order remain attached.
- In
- A signed sale of the Octavia
- Omnetic
- Issues the invoice from the deal, sends it and records the available delivery status
- Out
- A document attached to the car, not a PDF in an outbox
Double-entry accounting, or tax records
The source supports double-entry accounting and tax records, with costs and revenues followed online for a company or sole trader.
Cash flow is presented as a chart while the ledger retains the vehicle, branch and order dimensions.
- In
- Five documents from four different modules
- Omnetic
- Posts each to the configured account, branch and order while preserving the vehicle link
- Out
- Gross margin per car without reconstructing a spreadsheet
Bank movements matched, not eyeballed
Bank movements load automatically where supported or arrive through imported statements; documents are then paired to their payments.
Cash registers sit beside the bank, so a desk deposit and overnight transfer reach the same reconciliation view.
- In
- An overnight statement and a card deposit at the desk
- Omnetic
- Loads the movements, matches open documents and flags what remains unmatched
- Out
- One open item to examine instead of a full manual reconciliation
The declarations the year requires
The source names the balance sheet, profit and loss, cash ledger, VAT, inspection reports and Intrastat for cross-border trade.
Forms, filing support and certification are market-specific and confirmed during scoping.
- In
- A quarter of trading that includes imported cars
- Omnetic
- Builds the configured VAT, Intrastat and statutory statements
- Out
- Prepared filings · forms and rules per market
Reports in the format they are asked for
Accounting reports carry the branch, order and vehicle dimensions, so a group figure can open down to the document and deal that produced it.
That common lineage lets a site manager and controller discuss the same number even when their views differ.
- In
- A month across six branches and three entities
- Omnetic
- Builds statutory views per entity and management views per branch, drillable to a document
- Out
- A figure the site manager and CFO can both trace
Capabilities
Everything clear and in one place
The twelve accounting capabilities the source names, grouped by the job they do.
Accounting
Costs and revenues followed online.
Tax records
Income, expenditure, income tax and a cash-flow view.
Double-entry & tax records
Both models supported for the relevant legal form.
Branch, order or job level
Account at the dimension where the question is asked.
Invoicing
Issue, send and retain available read status.
Bank & cash register
Connected or imported movements and payment exports.
Payment pairing
Documents matched to payments with exceptions surfaced.
Pricelist
Items placed on documents without retyping.
Reports
Accounting outputs in the required configured format.
Statutory declarations
Balance sheet, P&L, cash ledger, VAT, inspection reports and Intrastat where supported.
External ledger link
Context-rich postings sent to a supported local program.
Cloud, anytime
Online access with vehicle and order context on documents.
By role
Who this changes the close for
Accountant
Receives documents already tied to a branch, order and vehicle, then matches payments instead of typing them.
Site manager
Can open a figure in the site's view and see the deals underneath it.
CFO or controller
Closes across configured entities and currencies without asking sites for separate reconciliations.
External bookkeeper
Receives clean postings in a supported program's agreed format instead of a folder of scans.
Platform & data connections
Where the postings come from
Used & New Car Sales
Purchase and sales invoices, deposits and stock movements.
Workshop & Warehouse
Labour, parts consumption and stock valuation, including corrections.
Time-keeping
Labour cost per job and the configured inputs payroll needs.
Open Platform
Bank connections and exports to a supported external ledger, configured per market.
System relationship
Accounting in the connected product system
Sales, service, time and external systems write events with their context intact; Accounting turns them into one ledger or forwards them to the configured statutory system.
Outcome & proof
What we can and cannot claim yet
Less re-entry
A document starts with its vehicle, branch and order, so finance does not have to reconstruct the same context.
Margin at vehicle level
Costs and revenue remain tied to one car and can be opened down to the source document.
Payment matching
Supported bank movements are paired with open documents while unresolved items stay visible.
Local rules stay explicit
Forms, certification and closed-period behaviour are confirmed per market and ledger.
Implementation & availability
Secondary product demonstration
Margin for one vehicle
One sample vehicle joins acquisition, preparation, sale and commission in one traceable accounting trail.
Review AccountingOctavia · accounting trailsample data
Purchase invoice
paidSourcing · 476,900
Transport & VAT
paidCarvago BUY · 31,500
Preparation
internalWork order 4471 · 4,000
Sales invoice
matchedUsed Car Sales · 589,000
Costs
512,400Gross margin
78,020Pick a car you sold last month
We will map every document and posting it generated, then show how the vehicle and order context changes the answer to what it earned.
See it in practiceThe vehicle
One completed purchase-to-sale record and its work orders.
The documents
The invoices, deposits, labour and parts postings it generated.
The ledger
The statutory program, banks and entities that need to remain in scope.