Set up invoice automation

Learn how to set up invoice automation in Stripe Connector for NetSuite (SCN).

Before you begin

1. Install the SCN Stripe App and connect it to NetSuite.
2. Configure the general settings and workflows in the SCN Stripe App.
3. Learn how Invoice Automation works before configuring it.

Quickstart guide

Start here whether you use Stripe Billing, Invoicing, or both. Then review and complete any optional sections that apply to your use case. Use the default settings for testing where applicable.

Configure general settings that affect all record sync scenarios

1. Confirm that the General tab settings are configured for your use case. No changes are needed if you’re using the following default settings. If you require a more advanced configuration, follow the General tab setup guide before proceeding. General setting Default configuration Conditional alternatives NetSuite subsidiary ID Blank (single entity NetSuite account with no subsidiaries) You must set this Stripe account to pair with one specific subsidiary if you use a multi-subsidiary NetSuite account. Record sync timing controls Webhook events - Initiate sync at time of default triggers Denylist is the only other compatible option for this workflow and is required if you’re using SCN Payment Linker simultaneously—allowlist is incompatible. Customer sync controls: Stripe to NetSuite workflows SCN creates a new individual NetSuite customer for each Stripe customer. Customer matching settings prevent duplicates if NetSuite customers already exist for the customers handled by this workflow. Currency sync controls A single settlement currency in Stripe and NetSuite. This assumes that the NetSuite Multiple Currencies setting isn’t enabled. You must turn on the SCN Multiple currencies setting if the NetSuite Multiple Currencies setting is being used.
2. Go to the Account Mapping tab. Make sure the Required account mapping fields ( Payment processing fees, Undeposited funds, and Bank deposit accounts) are configured from your general setup. Invoice Automation requires one additional section. Subsection Configuration Invoices Income Required This account is required for this workflow, whether you link to existing NetSuite items or let SCN create its own. Configure the Tax liability and Discounts fields if you plan to charge sales tax or use Stripe coupons. Note While on the Account Mapping tab, you can configure any optional fields for other GL account scenarios that apply to your use case. This generally isn’t necessary for sandbox testing.
3. This workflow interacts with tax, revenue recognition, subsidiary, and other accounting settings on multiple NetSuite records that it creates automatically, including global items for specific scenarios. These automations begin as soon as you turn on the Connection > Stripe Connector for NetSuite setting. To prevent errors, add one of the following field mapping starter templates. Don’t delete any fields that seemingly don’t apply to your use case; SCN automations may require them. Go to the Field Mapping tab. Click on the Advanced subtab. In the Field defaults (Static Mappings) text box, paste one of the following starter templates, depending on your use case. Click Save when done editing. If you’re using a single-entity NetSuite account with no subsidiaries, paste the following template, which uses the standard NetSuite system defaults 2 and -7 for Non-Taxable in the United States. These default mappings prevent NetSuite Legacy Tax or SuiteTax from calculating tax twice on NetSuite invoices. The tax for this workflow is calculated on the Stripe invoice by either Stripe Tax or a third-party tax engine you’ve integrated directly with Stripe. Note If you’re using Avalara or another tax engine integrated directly with NetSuite to calculate tax on other NetSuite invoices outside of this workflow, modify the internal IDs to use the custom non-taxable tax schedules and tax codes provided by the Avalara integration. Use the Avalara in NetSuite instructions on this page to fully configure your workflow to support this scenario. single-entity.json { "service_sale_item": { "tax_schedule_id": 2 }, "non_inventory_sale_item": { "tax_schedule_id": 2 }, "discount_item": { "tax_schedule_id": 2, "non_posting": true
4. In preparation to run your first test, check whether your NetSuite account has any non-standard fields set as mandatory on the forms SCN uses to create new records. SCN already maps all standard mandatory fields by default, so this step only applies if your forms have been customized to set more fields as mandatory. Follow the mandatory fields process in the configuration guide, using the record types below for this workflow. Form type NetSuite record types Entry Customer Transaction Customer Payment, Credit Memo, Customer Refund, Invoice, Deposit Item Service for Sale Item, Non-Inventory Sale Item, Discount Item
5. Go to the App Settings > Connection tab. Turn on both Stripe Connector for NetSuite and Automatic record sync settings.
6. Run your first test to confirm nothing is blocking the primary records of the Invoice Automation workflow from being created in NetSuite. SCN uses all of the default settings on the Stripe Invoices tab, which you can change after the test.
7. Open Workbench to the Shell tab.
8. Paste one of the following triggers into the command line that says Enter a shell command... and press Enter .

• Simulate a customer paying an invoice. Stripe objects synced to NetSuite: customer , invoice with invoiceitem , charge . Command Line stripe trigger invoice.payment_succeeded
• Simulate a customer creating a subscription and paying the first invoice. Stripe objects synced to NetSuite: customer , price , invoice , charge . Command Line stripe trigger customer.subscription.created

3. Open the Dashboard to the Home page in a new browser tab. Click the SCN App logo to open the side drawer view of the App.
4. After a moment, cards populate at the top of the list representing each record SCN attempted to sync to NetSuite. Click each card.

• If the sync was successful, open the links to view the records in Stripe and NetSuite. In Stripe, observe the metadata SCN added to each object. In NetSuite, observe the values added to fields, GL impact changes, record statuses, and the relationships between the records.
• If the sync failed, you see an error log indicating which settings to alter before retrying the sync or triggering another test in Workbench.

When this test is successful, your environment is capable of handling the most basic scenarios supported by the default settings of the Invoice Automation workflow. The next section of this guide explains how to change the settings on the App Settings > Stripe Invoices tab to support more complex scenarios.

Optional Configure record sync controls

Optional Configure advanced field mapping

Optional Use Advanced Revenue Management

Optional Mark Stripe invoices as paid out of band

Optional Configure advanced settings

See also

• Stripe-initiated payments workflows
• NetSuite-initiated payments workflows