Frequently asked questions

In Hadron that difference never appears. When goods are received, production is confirmed or a shipment is posted, inventory, the general ledger and cost records are written in the same transaction, at the same moment. There are no overnight interfaces or staging tables between modules. If any part of the transaction fails, none of it is written, so you never end up with a half-posted document. Month-end becomes a close, not a reconciliation.

No second record is created. The same invoice number from the same supplier cannot be entered again unless the first one is cancelled. Invoice posting recognises repeated requests, so a dropped connection that retries or a double click never writes the invoice twice. The same protection applies to bulk CSV imports: re-uploading a file that stopped halfway does not duplicate the lines already written.

Neither. An incoming invoice cannot be blocked; the service was received and the debt exists. Instead of stopping it, Hadron escalates it: when budget usage crosses the threshold you set, approval goes to a senior manager or the CFO, and the approver must write a justification. Usage also counts invoices that are awaiting approval but not yet posted, so a budget that looks empty on paper shows as it really is. If the budget is later increased, that revision is logged with its reason, so the overrun never disappears.

Postings into a closed period are rejected. A posted document is never deleted; it is corrected with a reversal. Both the original entry and its correction stay in the ledger, along with who did what and when. The history of every figure you show your auditor stays traceable.

Minutes. For batch-managed materials, every shipment records which batch it came from, so the chain runs unbroken from batch to shipment line, to sales order, to customer. It also works backwards: you see which production order made the batch and which raw material batches went into it. An expired or blocked batch cannot be picked for shipment at all; the system prevents it up front.

No. If the connection is not set up or the integrator does not respond, the invoice is not considered sent and this is shown clearly; the system never records a fake success. Documents are generated in GİB’s UBL-TR format, and the recipient’s tax or ID number is validated before sending. You don’t need to change your integrator; during setup Hadron is configured to connect to the one you already use.

No rate is hard-coded in the payroll calculation. Social security floors and ceilings, income tax brackets, the minimum wage exemption and the severance ceiling are stored as parameters with effective dates; a new year is added as a new row, and past periods keep calculating with their old values. Every parameter stays marked “unverified” until your own accountant approves it, and every payslip calculated with those values carries a visible warning. Payroll never runs silently on an unverified rate.

Each company’s data lives in its own separate database; it never shares tables with other customers and can be handed over to you in full whenever needed. Hadron runs on the infrastructure you prefer, such as AWS, Azure, Google Cloud, Oracle or your own Kubernetes environment. In high-volume installations, analytical reports read from a separate data warehouse, so day-to-day operations are not affected by reporting and reports stay fast even across millions of rows.

A posted document is never deleted; it is corrected with a reversal. Both the original entry and its correction stay in the ledger, with who did what and when. Nothing can post into a closed period.

MT940 or CAMT.053 statements are imported. Lines whose amount matches exactly one open item are cleared automatically; lines that match several items or none are set aside for manual matching.

Yes. E-invoices, e-archive invoices and e-waybills are generated in UBL-TR format; the buyer’s tax or ID number is validated before a document number is used. Sending goes through the private integrator you already use; you don’t have to switch.

Yes. An intercompany posting is written to both companies’ books in one transaction. Consolidated trial balance, balance sheet and income statement eliminate intercompany postings, and the elimination amount is shown on each line.

Straight-line or declining-balance by asset class, run per period. The same period can’t run twice and a run can be reversed. On sale or retirement, the gain or loss is posted to the defined accounts.

Not when an approval flow is defined. The invoice goes to the person responsible for the supplier, is coded to a budget line and sent for approval; the accounting entry is created after approval. A budget overrun doesn’t block the invoice; it escalates to a higher approver and requires a justification.

No. An incoming invoice is a liability that already exists; blocking it doesn’t make it go away. On an overrun the invoice escalates to a higher approver who must give a justification, so the overrun is visible and owned.

Invoices that are coded, awaiting approval or approved but not yet posted are commitments. They sit in their own column in the plan/actual report, so you see how much of the budget is really spent before the invoice reaches accounting.

Spending pace is year-to-date actuals plus commitments divided by the plan for the same periods; the annual plan is multiplied by that pace. Because pace is measured against the plan’s own distribution rather than the number of months, an annual cost paid in January doesn’t create a false overrun.

An allocation cycle distributes a sending cost centre’s cost to receivers with fixed weights. The cycle runs once per period, posts a real accounting document and can be reversed if needed.

Yes. An internal order is opened with a budget and released; costs are posted to it and settled to a cost centre or account at period end. The internal order summary report shows budget overruns.

Yes. Billing takes the profit centre from the material and plant record; the profit centre income statement shows revenue, expense and net result per centre with an account breakdown.

The invoice line is linked to the order line. If the total invoiced quantity exceeds what was received, or the unit price variance exceeds the tolerance defined for the company and material group, the invoice is blocked. A blocked invoice is released with a justification.

No. For orders under an approval policy, goods can’t be received until approval is complete. Policies are defined by amount and company code; the approver can be a role or the requester’s manager chain.

Yes. There are ready-made field packs for textiles, furniture, food and automotive; fields are asked by material group and can be extended without code. Variants such as size and colour are created in one step with a matrix.

Moving average or standard price is chosen per material and plant. Moving average is recalculated on every goods receipt. Every stock movement creates an accounting entry in the same transaction.

Transfers between storage locations take one step. Transfers between plants take two: goods leave the sending plant and show as in transit until received, without counting as sellable stock. Batch identity is kept and e-waybills are generated for shipments between your own sites.

A non-PO expense invoice goes to the person responsible for the supplier, is coded to a budget line and sent for approval; the accounting entry is created after approval. A budget overrun doesn’t block the invoice; it escalates.

Yes. The planning strategy is set per material and plant. For make-to-stock materials, demand is combined. For make-to-order materials, each planned order stays linked to its own sales order, and free stock in the warehouse is never counted towards another customer’s order.

The subcontracted step is defined in the routing. When the order is released, a purchase order for the subcontractor is opened automatically. Material is sent to the subcontractor, and when the product comes back the subcontracting cost is written to the production order. The scrap report shows sent and returned quantities for each subcontract order.

No. Material consumption, activity and subcontracting cost are written to the order instantly with confirmations and goods receipts. When the order closes, the variance against standard cost is calculated and posted to accounting in the same transaction.

Operators scan the production order barcode on an Android shop-floor terminal and enter the confirmation. Each confirmation is written to the same record as the office screens; no separate transfer is needed.

The batch with the nearest expiry date is consumed first (FEFO). Blocked or expired batches are never selected. Consumed batches are linked to the batch produced, so you can trace back from finished goods to raw material, and forward from raw material to the batches made from it and the customers who received them.

Yes. Process industries such as food and chemicals use process orders that work with recipes and phases; quality inspections can be attached to phases. Discrete and process manufacturing run side by side in the same system.

Yes. Prices are defined for a customer, a sales organisation or in general; the most specific applies. Quantity tiers and validity dates are supported, and the customer discount is added to the order automatically.

No. Shipping only picks batches that are unexpired, unblocked and of sellable quality; if one is chosen by hand, the system rejects it.

No. Documents are generated in Hadron as UBL-TR and sent through the private integrator you already use; the connection is set up during onboarding.

Yes. On the Hadron Partner portal your customers sign in without a password, with a code sent to their email, and see their orders, shipments and invoices. Sharing the open balance and production status is off by default.

Today stock is checked at goods issue; quantity that isn’t in the warehouse can’t be shipped. Showing available stock and a delivery date at order entry is not available yet; it is on our roadmap.

A return order is opened, the goods come back into stock with a return goods receipt, and a credit memo corrects the customer balance. All three are linked in one chain.

GS1-128, GTIN, SSCC and bin barcodes are resolved in one scan. There is a handheld flow in the web app and an Android shop-floor terminal (transfer order confirmation, scanning, shipping).

Yes. Bin stock is kept per batch; picking takes the batch with the nearest expiry first.

Yes. SSCC numbers are generated from your GS1 settings. Templates are designed for material, batch, SSCC and bin labels; labels are produced as ZPL.

When a count is posted, the difference is written to bin stock, inventory and accounting in the same transaction; no separate adjustment entry is needed.

Yes. The planner plans the quantity, the floor loads units by barcode, and a specific unit can be pinned to the plan. The unit moves to the receiving plant with the same barcode and the e-waybill is generated with the packing list.

Yes. Every roll produced at confirmation is born with its own SSCC, width, weight and length; its passport shows which order and batch it came from. Cut pieces carry their source.

For materials under quality control, an inspection record opens automatically at goods receipt, at production order confirmation and when a process order completes. A record is also created on shipment; it opens after goods issue and is not a pre-shipment check.

Not for materials under quality control. The incoming quantity waits in quality stock and doesn’t show as available. A usage decision releases, blocks or scraps it.

The quantity scrapped in a usage decision leaves stock and its cost is posted to accounting in the same transaction. For inspections from production, scrap cost is added to the production order’s actual cost.

Monthly accept, reject and scrap rates per supplier and material are calculated from goods receipt inspection decisions. Delivery time and price are not part of this score.

The grade is kept on the unit or batch and every change is recorded with who, when and why. Goods of a non-sellable grade can’t be shipped; a stock transfer plan can require a specific grade.

Not yet. Today inspection works at quantity and decision level. Characteristic-level measurements, specification limits, statistical process control and certificates of analysis are on our roadmap.

Employee and employer social security, unemployment insurance, income tax on the cumulative base, stamp duty and the minimum wage exemption. Overtime, night and holiday hours from time tracking are linked to wage types automatically.

Parameters are kept with effective dates and confirmed with your accountant during onboarding. Every payslip calculated with an unverified parameter shows it as a warning.

The payroll run creates an accounting document in the same transaction through the defined account determination. If the run is reversed, the accounting document is reversed too.

Yes. With Hadron Me, employees request leave, see their balance, and request an employment letter or payroll document and download it as a PDF. Managers decide requests from their own approval inbox.

Yes. Time tracking warns when annual overtime or maximum daily working hours are exceeded; the record isn’t blocked and HR decides. Limits are set for your company.

Contractor workers are flagged separately on the employee record and linked to the contractor firm’s supplier record; they don’t enter payroll. Contractor workforce and a per-firm cost bridge are reported.

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.

No. Documents are generated in Hadron as UBL-TR and sent through the private integrator you use; the connection is set up for your integrator during onboarding.

Yes. The integrator connection is per company; because the tax obligation belongs to the tax number, each company works with its own contract and credentials. Number series are per company too.

No. The buyer’s tax or national ID number is checksum-validated before a document number is used; if invalid, no document is generated and no number is used up.

No. In test mode documents don’t reach the tax authority and a warning band is shown. If no integrator is configured, sending doesn’t fake success; it is rejected explicitly.

Yes. An inter-plant transfer generates an e-waybill in a separate series when the goods leave; sender and receiver share a tax number with different addresses. The packing list comes from the loaded units.

An incoming e-invoice can be parsed, matched to its supplier and linked to the supplier invoice approval flow. An inbox screen and automatic pulling from the integrator aren’t available yet; they are on our roadmap.

Purchase orders, sales orders, non-PO supplier invoices and leave requests. Policies are defined by document type, amount range and company and contain sequential steps.

At each step the approver can be a role or the requester’s manager and their manager. The manager chain is resolved from the employee record and fixed at request time; later org changes don’t move an open request.

No. The requester can’t decide their own document; this rule applies to every approval regardless of policy.

The invoice isn’t blocked; an incoming invoice is a liability that already exists. The overrunning request escalates to a higher approver who must give a reason. Budget usage % is fixed at request time, so the overrun record isn’t lost even if the budget is raised later.

The approver returns the invoice to coding with a reason; the chain resets and the corrected invoice goes for approval again. The return history is never deleted.

Yes. From the Hadron Me approval inbox they see requests, review history and reasons, and decide.

More than 50, for finance, controlling, purchasing, production, sales, warehouse and HR. They all use the same screen: date presets, company filter, previous-period comparison, totals row and export.

Yes. Reports read the transactional database; a movement shows in the report the moment it’s written. Cockpit figures are also calculated on the server from the current record.

No. Report access is per module; a user authorised for specific companies only sees data from those companies.

Yes. To Excel, CSV or PDF; the PDF carries the company and date range, and the totals row matches the screen.

No. With no data a card shows zero; gaps aren’t filled with sample figures.

Yes. The consolidated trial balance, balance sheet and income statement are produced with intercompany postings eliminated; the elimination shows separately on each line.

Yes. Each company has its own company code, fiscal years and periods, document number ranges and tax number. E-document numbering and the integrator are per company too.

Yes. Roles are assigned per company; the same person can approve in one company and only read in another. In accounting, purchasing and reports, records of an unauthorised company are rejected by the server.

A single transaction writes to both companies’ books. Clearing accounts are defined once for each pair of companies; the posting appears in both at the same moment or not at all.

You select the companies and the period; the consolidated trial balance, balance sheet and income statement are produced instantly. Intercompany postings are eliminated, and the elimination amount is shown on each line.

No. The business partner record is shared across the group. Each company adds it as its own customer or supplier; payment terms, reconciliation account and balance are kept per company.

Yes. Companies can use the same chart of accounts, which makes account-level consolidation direct. Material master data is shared across the group too.

Each customer runs in a separate PostgreSQL database and every request is routed only to that customer’s database. Database passwords are stored encrypted with AES-256-GCM.

A role defines which actions it may take on each authorisation object, and checks run on the server on every request. Roles can be limited per company; managing roles needs its own permission, so nobody can grant themselves rights.

Session tokens are kept only in httpOnly cookies that page JavaScript can’t reach. Access tokens last 15 minutes and refresh tokens are single-use; changing a password ends all sessions, and a deactivated user can’t refresh.

Yes. The audit trail records user, module, action, record and time; reading it needs its own permission. Salary amounts are deliberately kept out of the audit log.

The test role is read-only, with no access to HR, role management, the audit trail or free-form queries. A test user can’t reach any data before accepting the confidentiality and data-protection texts.

The integrator password and API key are encrypted with AES-256-GCM and never returned in any response. If the encryption key isn’t configured, the save is rejected; nothing is written in plain text.

Every employee whose employee record is linked to a system user. Someone working for several companies picks their company and switches without signing out.

No. Sign-in uses a one-time 6-digit code sent to the email address.

Yes. The approval inbox shows pending and decided requests; decisions come with a reason and the request’s approval history is visible. Leave, purchase order and supplier invoice approvals share the same inbox.

Employment certificates and salary certificates. The request goes to HR; once the document is ready it downloads as a PDF.

Turkish and English; the preference is changed in the profile. Light and dark themes are available too.

Hadron Me runs in the browser and adapts to the phone screen; the same account also works from a computer.

Your customers: the contacts on their business partner record. Access is granted per contact and is off by default. A supplier view isn’t available yet; it’s on our roadmap.

No. Every query is filtered to the customer’s own account; this rule is enforced on the server, not on the screen.

You do. Orders, shipments and invoices are on by default; balance and production status are off by default. A closed section isn’t just hidden on screen; the server doesn’t return that data.

No. A 6-digit code is sent to their email address; it’s valid for 10 minutes and becomes invalid after 5 wrong attempts. Sessions last 8 hours.

How much of the order is produced, in production and planned, and the estimated finish date. Internal order numbers, cost, work centre and scrap aren’t shown.

Yes. Invoices download as e-invoice PDF and XML, shipments as e-waybill PDF and XML when one exists, and lists export as CSV.