Seven stages, one chain of controlled transactions.

Stage 01

Receiving

Goods arrive and become trustworthy stock

A receipt is booked against its purchase order, so what you own is what somebody actually checked in. The unit cost travels with the goods from this moment on. It is captured here, not estimated later at month end.

• Receive against the purchase order, line by line
• Landed cost captured on the receipt itself
• Put-away to a location, recorded as a movement
• Every receipt is a named transaction. There is no “edit the quantity” path

Stage 02

Inventory

Quantities backed by a ledger, not an editable field

Every number you can see is derived from the movements behind it. Nothing sets a quantity directly: stock changes because a receipt, a reservation, a pick, a shipment or an explicit, authorized adjustment happened, and each of those leaves its own row.

• On-hand, reserved and available derived from movements
• Location-level detail with a full movement history
• Adjustments are named transactions requiring authority
• FIFO or weighted-average costing carried on the ledger

Stage 03

Fulfillment

Allocation that cannot promise the same case twice

Reservation happens inside the transaction that claims the stock, and the database serializes competing claims. Two pickers racing for the last case do not both win it: one gets it, the other is told immediately, before a customer is promised anything.

• Allocate and reserve against real, available stock
• Concurrent claims serialized, with no oversell under load
• Picking recorded per line, per location
• Short-pick and release are recorded outcomes, not silent edits

Stage 04

Packing

A shipment that says exactly what left the building

Cartons and their contents are recorded as they are packed, so the shipment document is a statement of fact rather than a copy of the order. When a customer asks what was in the box, the answer comes from the pack record, not from memory.

• Cartons built from picked lines, contents recorded
• Packed units stay linked to their own unit history
• Repack and unpack are recorded transactions
• The pack record is what shipping and billing read from

Stage 05

Shipping

Goods out, cost and revenue recognized in the same breath

Shipping is the moment operations and accounting have to agree, so Corva makes them agree by construction: the same transaction that moves the goods out records the cost of those goods and recognizes the sale.

• Ship from the pack record, so what left is what is billed
• Cost of goods sold recorded from the actual cost layers
• Revenue recognized under ASC 606 on transfer of control
• Carrier and tracking detail kept with the shipment

Stage 06

Billing

Invoices built from what shipped, not what was hoped

An invoice is produced from the shipment record, which means the document you send and the goods that left are the same event seen twice. Corrections are issued as recorded credit documents. An invoice is never quietly rewritten.

• Invoice from the shipment, line by line
• Receivable raised as the invoice is issued
• Gapless document numbering, even under load
• Credits and adjustments are their own recorded documents

Stage 07

Receivables

Payments that settle against real open balances

A payment is applied to the invoices it actually settles, so the open balance is always explainable line by line. The subledger and the general ledger are two views of the same postings rather than two systems to reconcile by hand.

• Apply payments to specific invoices and lines
• Open balances and aging derived from the ledger
• Write-offs and adjustments require authority and leave a record
• Subledger totals reconcile to the general ledger by construction