Credit Memo Invoicing

The Orderful for NetSuite connector supports generating outbound 810 EDI transactions from Credit Memo records in addition to standard Invoices. This allows you to send credit adjustments to your trading partners using the same EDI workflow you already use for invoices.

How It Works

When a Credit Memo is billed in NetSuite, the connector generates an 810 EDI transaction just like it does for a standard invoice. The key difference is the Purpose Code in the EDI output: Credit Memos produce an 810 with purpose code CR (Credit), while standard invoices use 00 (Original).

Your trading partner receives the same 810 document structure in both cases, with the purpose code indicating whether it represents a charge or a credit.

Setup

Credit Memo 810s are configured as a separate EDI Enabled Transaction Type entry on the customer entity, alongside your existing Invoice 810 configuration.

Step 1: Add a Credit Memo transaction type

1. Navigate to the customer's Entity record in NetSuite
2. Open the EDI Enabled Transaction Types subtab
3. Add a new entry with:
   • Document Type: 810 Invoice
   • Source Transaction Type: Credit Memo
4. Configure Auto Send and Consolidation Method as needed (these work the same as standard invoice 810s)
5. Save the entity record

The Source Transaction Type field is what distinguishes a Credit Memo 810 configuration from a standard Invoice 810 configuration. Both use the 810 document type, but the source transaction type controls which NetSuite record triggers the EDI generation.

Step 2: Generate Credit Memo EDI

Once configured, Credit Memos generate 810 EDI transactions the same way invoices do:

• Automatic: If Auto Send is enabled, the 810 is generated and posted to Orderful automatically when the Credit Memo is saved in NetSuite.
• Manual: If Auto Send is disabled, navigate to the Credit Memo record and use the Generate 810 button, then send from the Orderful Transaction record.

The Generate 810 button appears on Credit Memo records once the customer has a Credit Memo-sourced 810 enabled transaction type configured.

EDI Output Differences

The 810 generated from a Credit Memo is structurally identical to an invoice-sourced 810, with these differences:

All other mappings (addresses, references, terms, carrier details, line item structure) follow the same logic documented on the 810 Invoice mapping page.

Consolidation

Credit Memo 810s support the same consolidation methods as standard invoices:

• Parent 850: All Credit Memos linked to the same original EDI 850 are consolidated into a single 810.
• Ship To: Credit Memos shipping to the same destination from the same EDI 850 are consolidated.
• None: Each Credit Memo generates its own 810.

Resending

To regenerate a Credit Memo 810 after making changes:

1. Navigate to the Orderful Transaction record linked to the Credit Memo (found in the Created Orderful Transaction field or the Orderful EDI join table)
2. Click Generate and Send
3. The connector recreates the 810 JSON using the latest Credit Memo data and resubmits to Orderful