New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingCPQPaymentsRevRecGrowthReveal
Support

Product Updates

  • Release Notes

Getting Started

  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Developer Resources
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee

  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

Agentic AI

  • Chargebee Copilot
  • Catalog Setup Assistant
  • MCP Servers

Product Catalog

  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions

  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers

  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Invoices and Credit Notes

  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes

  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities

  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Mobile SDKs and Wrappers
  • Articles and FAQ

Site Configuration

  • Add Users & Assign Roles
  • Chargebee Notifications
  • Custom Fields & Metadata
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Reports and Analytics

  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations

  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Order Management
  • Mobile Subscriptions (Legacy)
  • Other Integrations
  • Articles and FAQ

Data Privacy & Security

  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations

  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  3. Integrations
  4. Freshworks Releases Links
  1. Billing
  3. Integrations
  4. Freshworks Releases Links

Freshworks Release Notes links

Void Older dated invoices

If the user voids the older dated invoice before the sync start date, and a mapping exists in the third-party mapping table. Then a credit memo is created, and invoice status is updated as part of the NetSuite connector.

To enable this feature, reach out to support. The following prerequisites should be met:

  • Add config with key enable_void_older_invoice_if_voided and set its value to true.
  • A mapping exists for the older invoice in the TPEM.

For example, if you create an invoice on June 09 and the sync start date is June 15. After enabling this configuration, the TPEM mapping for this record is voided and a credit memo is created.

  • Void the invoice in Chargebee and sync.
  • The NetSuite invoice status will be updated, and a credit memo will be created.

Void Unsynced invoices

If a customer creates the invoice and voids it before the sync happens, then an invoice and a credit memo are created in NetSuite (for void action), and the invoice status is updated.

  1. Create an Invoice in Chargebee and Void it before syncing to NetSuite.

    image

  2. An invoice will be created in NetSuite with a Closed state.

    image

  3. Void Credit Note is created to close the invoice.

    image

Note

The invoice is created in an open state first and then immediately voided and a credit memo will be created and applied to the invoice as a post-operation. Both operations would occur in a single sync request.

image

Voided credit note, is deleted in NetSuite.

Ignore Invoice updates

The Ignore invoice update feature is enabled in Netsuite. If the user now voids an older dated invoice before the sync start date and a mapping exists in the third-party entity mapping table (TPEM). Then a credit memo is created, and the invoice status is updated as part of the NetSuite connector. At times, the merchants make an update to an invoice or credit note once it is created in NetSuite.

Possible reasons for the update are:

  • The accounting period is closed
  • Some business wants invoice to immutable
  • Migrated or imported invoices could result in invoice failures at certain configurations.
  • Tax-related issues in, suite tax enabled accounts.

Reach out to support to enable this feature. Once the feature is enabled then the following actions will be synced.

  • Applying to a payment - It is achieved by updating the payment record.
  • Applying to a credit note - It is accomplished by updating the credit note record.
  • Voiding an invoice - It is done by creating a new credit memo record. -Write off an invoice - It is done by creating the write-off credit note record.

Note

  • To force an invoice update, invoice status is set to update_failed in the TPEM.
  • An invoice would be skipped if the ignore_invoice_update is set to true and invoice status is neither new nor update_failed.
  • If ignore_invoice_update is enabled, the delete action will not be synced to NetSuite.

Sync payment/credit notes to older invoices with TPEM

Earlier updates for the older dated invoices, such as the payment and credit notes were not synced. Now if the mapping is established, we will sync the updates made to the invoice.

Applying older credit notes/payments to new invoices

You can now sync older credit notes and payments to new invoices.

  • An older payment (payment dated six months earlier) is created/imported into NetSuite.
  • Mapping is established between Chargebee to NetSuite payment while setting up the integration.

Note

Earlier, older payments were ignored, and no updates were made to the invoice.

A new feature is introduced to enable syncing the older payment if any newer allocations are made.

Feature - Prop - enable_older_resource_new_allocations

  • The integration is set up with a recent sync start date.
  • A new invoice is created for the older payment. The price from the older payment reflects in the created invoice.

Was this article helpful?