One movement, one record, one truth
Goods receipts, shipments, invoices and production confirmations write stock, accounting and cost at the same moment, in the same transaction. There are no transfer runs between modules.
Journal list: documents from goods receipts, shipments and production, with document type and source number
Separate modules, one record
Stock, accounting and cost in the same database, in the same transaction.
Journal document from a goods receipt: stock and goods-received/invoice-pending lines
In the same transaction
For goods receipts, goods issues, shipments, invoices and counts, if the accounting entry can’t be written the movement isn’t either; there are no half records with stock gone but no accounting.
No transfer runs
There is no scheduled data transfer between modules; accounting and cost update the moment something moves.
Balanced documents
Manual journal entries and bulk postings such as payroll, depreciation and stock transfers aren’t posted unless debits equal credits.
Documents with a known source
Goods documents, invoices, production orders and payroll runs are linked to their accounting document; the journal shows the source document number.
A database of your own
Each customer runs in a separate database; your records never sit in another customer’s tables.
Production order detail: actual cost broken down into material, activity and overhead
Real cost in production
A production confirmation writes component consumption, finished-goods receipt, accounting and cost together; the order’s actual cost exists at that moment.
The journey of a movement
At every step stock, accounting and cost are written at the same moment.
Goods receipt
A goods receipt against a purchase order writes stock and accounting together.
- Stock quantity and value go up
- Stock and goods-received/invoice-pending accounts at the same moment
- Invoice matching relies on this record
Goods receipt document: lines, quantity and amount
Issue to a cost centre
A goods issue to a cost centre writes accounting and cost together.
- Stock goes down, the expense account is debited
- The cost centre’s actuals go up at the same moment
- The budget report is current the next time it’s opened
Cost centre plan/actual report
Production confirmation
The confirmation writes consumption, finished-goods receipt and cost in one go.
- Components leave stock, the finished product enters
- Accounting and cost documents in the same transaction
- The order’s actual cost and variance show immediately
Journal document from a production confirmation
Shipment and invoice
The shipment writes stock and cost of goods sold; the invoice writes the receivable and profitability.
- Stock goes down at shipment and cost of goods sold is posted
- Customer receivable and revenue on the invoice
- The profitability line in the same transaction as the invoice
Sales invoice and its accounting document
Report
Trial balance, cost and stock reports read the same record.
- Right after the movement, no transfer wait
- Trial balance, cost centre and stock reports see the same movement
- No inter-module transfer step at closing
Trial balance
Which modules the single record connects
The same record in every module; no interim transfers.
- Procurement & InventoryGoods receipts and supplier invoices write stock and accounting together.
- Production PlanningA production confirmation writes consumption, finished goods and cost in one transaction.
- Sales & DistributionShipments and invoices write stock, receivables and profitability together.
- Finance & AccountingEvery movement lands in the journal at the same moment.
- Costing & ControllingCost centre and production order actuals exist the moment something moves.
- Warehouse ManagementCount differences are written to warehouse, stock and accounting together.
About the single-record architecture
The most common questions before going live.
A business event, such as a goods receipt, is recorded once; its stock, accounting and cost sides are written in the same transaction. There is no data transfer between separate programs and no month-end sync run.
For goods receipts, goods issues, shipments, invoices and counts the movement isn’t written either, and the user is told why, for example a closed period. There are no half records with stock gone but no accounting.
With no transfer runs, there is no “was it transferred” reconciliation. Closing tasks such as depreciation, cost allocation and period close still happen, but not to move data.
Yes. The journal document shows the source document number, and goods documents, invoices, production orders and payroll runs are linked to their accounting document.
No. Each customer runs in a separate database; connection details are stored encrypted and every request is routed only to that customer’s database.
No. Trial balance, cost and stock reports read the transactional database; a movement shows in the report the moment it’s written.
See Hadron with
your own data
In a 30-minute demo, we set up your processes on Hadron together.