Should Shipping and Invoicing Be Separate Processes?

A packing slip and an invoice serve different purposes, so manufacturers often treat shipping and billing as separate processes.

The packing slip records what leaves the building. The invoice tells the customer what they owe. In many companies, shipping prints the packing slip and sends a copy to accounting. Accounting then reviews the sales order and creates the invoice.

Separating these steps can be necessary. A manufacturer may combine several shipments on one invoice, bill by project milestone, add freight after shipment, or require an accounting review before sending the invoice.

For a standard shipment, the packing slip and invoice rely on much of the same information. The system already knows what shipped, which sales order it came from, who the customer is, and what should be billed.

Requiring accounting to recreate the transaction adds paperwork and delays the invoice. In many cases, completing the shipment should also create the invoice or make it ready to send.

The Shipping-to-Accounting Flow

A manufacturing ERP should connect the commercial process from shipment through accounting:

Shipment → Invoice creation → Accounts receivable → General ledger

Once shipping records the transaction, the system has the shipped parts and quantities. The sales order provides the customer, pricing, payment terms, and billing information.

That data can generate both documents. The packing slip accompanies the product, and the invoice goes to the customer’s billing contact.

This also supports partial shipments. If a customer orders ten units and six ship, the packing slip records six units and the invoice can bill six units. The remaining four stay open until they ship.

Accounting does not have to re-enter the quantities or wait for someone to deliver a copy of the packing slip.

Delayed Invoicing Delays Payment

Controllers care about timing. If a product ships Monday but the invoice is created Thursday, payment terms effectively start late. Over time, that creates avoidable AR delays. Any delay is a risk to cash flow.

Common problems include:

• Shipped orders that have not been invoiced
• Invoices created from memory or manual reports
• AR aging that does not reflect current shipments
• Accounting teams chasing shipping status
• Revenue and margin reports lagging behind production activity

For small and mid-sized manufacturers, this matters because cash is often tied up in material, labor, and overhead long before shipment.

What Automatic Invoice Creation Solves

A connected shipping-to-invoice process gives accounting a cleaner close process and fewer manual checks.

When the product ships, Cetec ERP can connect the shipment back to the customer order and accounting record. That means accounting is working from the same transaction history as shipping, production, and inventory.

This fits Cetec ERP’s full-suite approach: one system for manufacturing, inventory, shipping, accounting, and reporting, rather than separate tools passing updates back and forth. The brand guidance emphasizes direct, practical content grounded in actual system use and manufacturing processes.

When Shipping and Billing Should Remain Separate

Automatic invoice creation does not fit every order.

The manufacturer may need to hold or review an invoice when:

• Several shipments must appear on one invoice
• The customer is billed by milestone or percentage of completion
• Freight, tooling, or other charges are added later
• Customer acceptance is required before billing
• Taxes, deposits, or payment terms need review
• Supporting documents must be included with the invoice

The ERP should support these requirements while allowing standard shipments to move directly into invoicing.

The question is whether the separate billing step follows a customer or accounting requirement. If accounting reviews every shipment because a packing slip has always been handed from one department to another, the company may be maintaining a paper-based process inside its ERP.

What Controllers Should Look For

A manufacturing ERP should support:

1. Invoice creation from shipment activity: The invoice should use the parts and quantities recorded on the shipment. Employees should not have to enter the same information again.
2. Control over invoice timing: Standard shipments may create invoices immediately, while orders with special billing requirements remain available for review.
3. Connection to accounts receivable: Once the invoice is created, the customer balance and payment terms should move into accounts receivable without duplicate entry.
4. Posting to the general ledger: Invoice activity should flow into the company’s accounting records and financial reports.
5. Support for outside accounting systems: Some manufacturers use QuickBooks or another accounting package. The ERP should maintain the sales order, shipment, and invoice records before sending the accounting transaction to the outside system.

Conclusion

Cetec ERP connects sales orders, shipping, invoicing, accounts receivable, and the general ledger in one system.

When an order ships, Cetec ERP already has the customer, shipped quantities, pricing, and order history needed for billing. The shipment can support invoice creation without requiring accounting to rebuild the transaction from a packing slip.

The packing slip and invoice remain separate documents. Both come from the same order and shipment data.

Manufacturers can retain separate billing steps where the order requires them and remove the handoff where it does not. For many standard shipments, that means creating the invoice when the product leaves the building and sending it to the customer without another round of paperwork.