Overview
NexLog OS Finance is the accounting layer of logistics operations. It brings together six capabilities: accruals (Accrual Engine), cost allocation (Cost Allocation), claims and chargebacks (Claims & Chargebacks), profitability by dimension (Profitability Lens), carrier settlement (Settlement) and customer billing (Billing Engine).
The freightInvoices, costAllocations, claims and billingEntries entities live in the same canonical model as WMS, TMS and OMS, and every step emits a canonical event to the ledger.
Core entities
Each entity has a display name and an English code name (the MongoDB collection), the same across the platform.
| Entity | Code | Description |
|---|---|---|
| Freight invoice | freightInvoices | The carrier's billing document. It is reconciled in freight audit, accrued and paid at settlement. |
| Cost allocation | costAllocations | Distribution of logistics costs by order, SKU, customer, channel, DC, route or project. |
| Claim | claims | Compensation for damage, loss or delay, with an impact on settlement and customer billing. |
| Billing entry | billingEntries | Issuance of customer invoices (B2B and marketplaces) with versioned rules per contract. |
Capabilities
Native financial control of operations, fed by the same events that move the warehouse, transportation and orders.
Accruals (Accrual Engine)
Daily accounting of expected and actual cost, feeding the close and the P&L in real time.
Cost allocation (Cost Allocation)
Deterministic, configurable allocation by order, SKU, customer, channel, DC, route and cost center.
Claims and chargebacks (Claims & Chargebacks)
Complete claim and chargeback cycle, integrated with transitIncidents, freightInvoices and billing.
Profitability (Profitability Lens)
Margin by any dimension (order, SKU, customer, channel, region), with drill-down.
Settlement (Settlement)
Automated settlement of carrier invoices, with adjustments and netting.
Billing (Billing Engine)
Issuance of billingEntries with contract rules, service levels, surcharges and discounts.
From audit to settlement
The freight audit engine checks each invoice against the contracted rate table, surcharges, actual dimensional weight and the routes actually traveled.
Discrepancies raise an exception in Control Tower, block payment at settlement and feed the carrier risk score, a continuous score per carrier that combines punctuality (OTD), damage, claims and document compliance. With no discrepancy, the invoice moves on to cost allocation, accrual and settlement.
REST endpoints
The financial entities are exposed through the TMS API, versioned under /api/v1/.
| Endpoint | Method | Entity |
|---|---|---|
/api/v1/freight-invoices | GET | freightInvoices |
/api/v1/freight-audit/run | POST | Freight audit |
/api/v1/cost-allocations | GET | costAllocations |
/api/v1/claims | POST | claims |
/api/v1/transit-incidents | GET | transitIncidents |
Convention: kebab-case endpoints, versioned under /api/v1/, and camelCase collections. All financial events can also be exported through webhooks.
KPIs Finance delivers
Cost to serve
Total freight cost per order, SKU, channel and customer, with audited allocation in costAllocations.
Freight audit accuracy
Percentage of invoices (freightInvoices) audited with no discrepancy.
Margin by dimension
Margin by customer, channel, SKU and region, calculated from the financial ledger.
ERP integration
NexLog OS Finance does not replace SAP, Oracle or Totvs: it complements them. Financial events can be exported through the REST API and webhooks, on the same MDM shared with WMS, TMS and OMS.
ERPs receive only consolidated facts (accruals, accounts payable and accounts receivable), while NexLog OS handles the operational detail. This separation of responsibilities makes it possible to modernize the supply chain without replacing the ERP.
Finance as the accounting layer of the supply chain OS
Why logistics costs don't match the financials
In traditional operations, the transportation team approves invoices (freightInvoices) in spreadsheets, finance pays carriers in batches and the accounting close finds discrepancies weeks later. Predictability and margin are lost in that gap.
In NexLog OS, every invoice goes through freight audit, becomes costAllocations spread across the relevant cost objects, is accrued daily and paid at settlement with netting and adjustments. Everything is auditable, with canonical events in the ledger.
Profitability and billing
Profitability Lens calculates margin by any dimension (customer, channel, SKU, region) in real time, because it reads the financial ledger directly. The Billing Engine issues invoices to B2B customers with versioned contract rules: surcharges, discounts, service levels and rebates.
Claims and chargebacks also live here, connected to TMS incidents and OMS returns. Finance stops being a reactive module and becomes a strategic layer.