Open-source manufacturing ERP, MES and QMS. Quoting, MRP, inventory, shop floor, quality and lot/serial traceability on one Postgres schema, with a REST API and MCP server. Self-host or use Carbon Cloud.
TypeScript ai-agentsbill-of-materialserpinventory-managementleanmanufacturingmanufacturing-execution-systemmcp-servermesmrpopen-source-erppostgresqlproduction-planningqmsquality-management-systemreact-routerself-hostedsupabasetraceabilitytypescript
// SPDX-License-Identifier: LicenseRef-Carbon-Commercial
// Carbon Enterprise file, licensed only under the Carbon Commercial License
// (packages/ee/LICENSE). Not AGPL. Running, modifying, or copying it beyond those terms requires a commercial license.
/**
* Which Carbon documents are eligible to push to a spend platform.
*
* These are statements about CARBON's lifecycle, not any platform's API — a
* released purchase order is a commitment worth mirroring, a Draft one is not;
* an employee-party invoice is a reimbursement that originated in the platform
* and must never be pushed back to it. A second provider changes none of it.
*/
import type { Database } from "@carbon/database";
type PurchaseOrderStatus = Database["public"]["Enums"]["purchaseOrderStatus"];
/** Released statuses that push. */
export const SPEND_PUSHED_PURCHASE_ORDER_STATUSES: PurchaseOrderStatus[] = [
"To Receive",
"To Receive and Invoice",
"To Invoice",
"Completed",
"Closed"
];
/**
* Settled statuses. The platform's counterpart is retired rather than updated —
* HOW it is retired (archive, close, delete, or not at all) is the provider's
* business; that it should no longer look open is Carbon's.
*
* `Completed` is deliberately NOT here, and the distinction is the whole point.
* A Completed order is fully received AND invoiced, so its bill is arriving at
* the platform at almost the same moment — and a bill can only be matched to an
* order that still exists. Retiring it on Completed destroyed the counterpart
* exactly when it was about to be used: the bill landed with no order to match,
* and the three-way match the order was pushed for could never happen.
* (Verified against Ramp 2026-09-27: an archived purchase order 404s and is
* absent from every list.)
*
* Note what is NOT claimed here. Ramp does NOT demonstrably match a bill to an
* order by itself: sandbox PO000101 (`archived_at: null`,
* `billing_status: OPEN`, `bill_ids: []`) and draft bill AP000009 carried the
* same vendor and the same total and were still unmatched. And Ramp DOES accept
* a purchase-order link on a draft — `purchase_order_ids` (an array of Ramp PO
* uuids) is documented and writable on both `POST /bills/drafts` and
* `PATCH /bills/drafts/{id}`, as are `line_items[].purchase_order_line_item_id`
* and `inventory_line_items[].purchase_order_line_item_id`. An earlier probe
* concluded otherwise and was wrong twice over: `purchase_order_id` SINGULAR is
* not a field on that endpoint at all (an unknown key, silently ignored), and
* `GET /developer/v1/bills/drafts/{id}` exposes no purchase-order key, so
* reading the draft back could never have detected storage either way — those
* fields are readable only on a SUBMITTED bill (`GET /bills/{id}`). So keeping
* the order is a PREREQUISITE for the match, and sending `purchase_order_ids` +
* the per-line ids is a follow-up Carbon has not wired up yet.
*
* `Closed` is short-closed or abandoned: no bill is coming, nothing will ever
* match it, and retiring it is the tidying it was always meant to be.
*/
export const SPEND_SETTLED_PURCHASE_ORDER_STATUSES: PurchaseOrderStatus[] = [
"Closed"
];
/**
* Payable statuses that hand off.
*
* Read from the `purchaseInvoices` VIEW, never the table — the view DERIVES
* status, so a fully settled invoice reads "Paid" there while the table still
* stores "Open", and "Partially Paid"/"Overdue" exist only in the view. Reading
* the table would hand the platform bills that are already paid.
*/
export const SPEND_PUSHED_INVOICE_STATUSES = [
"Open",
"Partially Paid",
"Overdue"
];
/** Reimbursement suppliers — their invoices are the platform's own. */
export const EMPLOYEE_SUPPLIER_TYPE = "Employee";
export function isPushablePurchaseOrderStatus(
status: PurchaseOrderStatus
): boolean {
return SPEND_PUSHED_PURCHASE_ORDER_STATUSES.includes(status);
}
export function isSettledPurchaseOrderStatus(
status: PurchaseOrderStatus
): boolean {
return SPEND_SETTLED_PURCHASE_ORDER_STATUSES.includes(status);
}
export function isPushableInvoiceStatus(status: string): boolean {
return SPEND_PUSHED_INVOICE_STATUSES.includes(status);
}