Transforming industries with intelligent next-gen solutions

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.