Skip to content

New name, same team: SquareWorks Consulting is now Charted! Learn more

AP automation built for the complexities of manufacturing organizations

Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting
Industrial worker in a white hard hat and safety goggles using a tablet beside large industrial equipment in a factory setting

Transaction lifecycles are critical for manufacturing—here’s everything you need to know

Confused about what exactly is a NetSuite transaction?

In NetSuite, a transaction is any record that creates a financial or operational event: sales orders, purchase orders, work orders, item receipts, fulfillments, invoices, and assembly builds. Learn about key transaction types, manufacturing orders, assembly builds, how transaction types interconnect, and everything else you need to keep operations flowing.

Man in a blue shirt typing on a laptop at a desk in a modern office.

Frequently asked
questions

Charted Real-Time 3-Way Match supports vendor-specific threshold overrides on top of your global 0% default. Thresholds can be configured at the subsidiary, vendor, or item level, and set based on the line quantity, line rate, line amount, or total threshold for a given subsidiary or vendor.

The Charted dashboard shows whether a purchase order is associated with any of the invoices sitting in your inbox. From there, you can see the PO’s status and leave notes on the PO or invoice for other AP users to see. Once the receipt comes in and you’re ready for bill creation, our 3-Way Match functionality automatically takes over, matching the PO, receipt, and invoice in depth based on the thresholds your team has set.

Charted Invoice AI is built to extract line-level data from non-standard or inconsistent vendor invoice formats, without requiring manual templates per vendor. For manufacturers juggling dozens of suppliers with different billing formats (raw materials, equipment, logistics), this is usually the single biggest time recovery for AP teams. 

Yes, Charted Real-Time 3-Way Match ties invoices to POs and receipts directly in NetSuite, flagging discrepancies automatically rather than relying on manual cross-checking. This is especially valuable in manufacturing where blanket POs and partial shipments against a single order are common.

Charted Invoice AI has a Freight Capture setting that automatically identifies shipping charges on a scanned invoice and creates a separate line for them on the vendor bill.

You decide where that freight line goes:

  • Map it to a Default Shipping Item (an inventory item like “FedEx”) to increase inventory cost via NetSuite’s Landed Cost feature.
  • Map it to a Default Shipping Expense (an expense account) to treat it as a period cost.

    If both are configured, the item takes priority. The key point: Charted captures and separates the freight correctly either way. The decision of whether it hits landed cost or expense is a NetSuite configuration choice, not a Charted limitation.

Charted supports a Bill Before Receipt setting. When enabled, Invoice AI can process a vendor bill against a purchase order even if no item receipt exists yet in NetSuite.

Charted 3-way Match adjusts accordingly: when this setting is on, the billed amount is compared against the PO total rather than the received total, so the match still runs cleanly without a receipt to compare against. This is the right setup for environments where vendor invoices consistently arrive ahead of the warehouse logging physical delivery.

Yes. Charted 3-way Match logic was built specifically to handle multiple receipts and multiple bills against the same PO. The ordering logic works as follows:

When checking for variances on a saved bill, receipts and bills entered after the current one are excluded from the variance check, based on the order they were created in the system. This creates a first-in, first-billed-against processing sequence. Even if three receipts are logged simultaneously due to a backlog, the variance calculation processes them in sequence rather than treating them as a single batch.

If Bill Before Receipt is off: The system compares the billed quantity against the received quantity for that line. Since nothing has been received, Charted 3-way Match will flag a variance. The bill can still be saved using “Save With Variances,” and Charted can be configured to automatically place that bill on payment hold until the variance is resolved; payment won’t be released until the receipt is logged and the match clears.

If Bill Before Receipt is on: The bill processes against the PO total without requiring a receipt, so it goes through without a receipt-based variance.