Loading article…
Loading article…
Last updated on Sep 19, 2026
Look up which Advanced Billing activity posts to Avalara and which Avalara field each piece of it lands in. Payments, prepaid charges, invoices, refunds, credit notes, and voids each behave differently, and the mapping depends on whether you use classic invoice billing or Relationship Invoicing. Nothing posts at all unless Post documents to Avalara is enabled.
Advanced Billing only attempts to void a document in Avalara if that document was already committed there. An uncommitted (Saved/draft) document is deliberately not voided, to avoid errors on documents Avalara hasn't finalized. If the void call itself fails, for example because Avalara has already filed the document, Advanced Billing doesn't automatically create an adjustment or negation transaction in its place.
On classic invoicing, a refund doesn't void or negate the original transaction at all; it creates a new, separate return-type transaction that references the original one.
These mappings apply only if you use classic invoice billing in Advanced Billing. If you use Relationship Invoicing instead, see the Relationship Invoicing mapping section below.
Payment field mappings for classic invoice billing
| From (Advanced Billing) | Prefix | To (Avalara) |
|---|---|---|
| Transaction ID | CHARGIFY-PAYMENT | DOCUMENT CODE |
| Statement ID | CHARGIFY-STATEMENT | REFERENCE CODE |
| Customer ID | N/A | CUSTOMER |
This occurs if automatic billing has been selected. If there is a current negative balance (credit) on the Subscription, this prepaid charge, covered by the existing credit, is applied to the full cost of all of that statement's charges. This is marked in Avalara as prepaid using Record External Payment or Adjust Balance options.
Charge (prepaid) sync happens during Subscription renewal (at the end of the period).
A charge for a zero (or fully discounted) amount is not synced, the same way a zero-amount invoice is not posted. For example, the recurring renewal charge on a free Subscription creates no document in Avalara.
| From (Advanced Billing) | Prefix | To (Avalara) |
|---|---|---|
| Transaction ID | CHARGIFY-PREPAID-CHARGE-{charge_id} | DOCUMENT CODE |
| Statement ID | CHARGIFY-STATEMENT | REFERENCE CODE |
| Customer ID | N/A | CUSTOMER |
Invoice field mappings for classic invoice billing
| From (Advanced Billing) | Prefix | To (Avalara) |
|---|---|---|
| Subscription ID and Invoice ID | CHARGIFY-SUB-{subscription_id}-INV-{invoice_id} | DOCUMENT CODE |
| Unpaid (Status) | Saved | |
| Paid (Status) | Committed | |
| Customer ID | CUSTOMER | |
| Reference Code | N/A | Not used |
Refund field mappings for classic invoice billing
| From (Advanced Billing) | Prefix | To (Avalara) | Notes |
|---|---|---|---|
| Refund ID | CHARGIFY-REFUND- | DOCUMENT CODE | |
| Payment ID | CHARGIFY-PAYMENT- | REFERENCE CODE | |
| Invoice ID | CHARGIFY-SUB-{subscription_id}-INV-{invoice_id} | REFERENCE CODE | Applicable if refunded payment is related to an invoice |
| Customer ID | CUSTOMER |
Line item field mappings for classic invoice billing
| From (Advanced Billing) | Prefix | To (Avalara) | Notes |
|---|---|---|---|
| Component ID | Component-{component_id} | ITEM | |
| Product ID | Product-{product_id} | ITEM | |
| Plan name | CHARGIFY-SUB-{subscription_id}-INV-{invoice_id} | ITEM DESCRIPTION | With Subscription date or to Product name field |
| Plan Tax Type | TAX CODE | ||
| Product Tax Type | TAX CODE | ||
| Tax Origin Address | ORIGIN ADDRESS | ||
| Billing Address or Shipping Address | DESTINATION ADDRESS |
These mappings apply only if you use Relationship Invoicing in Advanced Billing.
Invoice field mappings for Relationship Invoicing
| From (Advanced Billing) | Prefix | To (Avalara) | Notes |
|---|---|---|---|
| Subscription ID & Invoice ID | CHARGIFY-CENTRIC-SUB-{subscription_id}-INV-{invoice_id} | DOCUMENT CODE | |
| Unpaid (Status) | Saved | ||
| Paid (Status) | Committed | ||
| Voided (Status) | Canceled | ||
| REFERENCE CODE | SUBSCRIPTION-GROUP-ID-{subscription_group_uid}, PARENT-INV-NUM-{parent_invoice_number} | Applicable if invoice segment | |
| Customer ID | CUSTOMER |
Whether an open (Unpaid) invoice posts to Avalara as Saved or Committed depends on the Accounting Method you choose when you Set Up AvaTax in Maxio Invoicing Suite: Accrual Basis commits open invoices at issue; Cash Basis defers the commit call until the invoice is paid.
Credit notes sync when they are created, from prorated credits, refunds, manually applied service credits, and voiding partially paid invoices.
| From (Advanced Billing) | Prefix | To (Avalara) | Notes |
|---|---|---|---|
| Credit note ID & Subscription ID | CHARGIFY-CENTRIC-SUB-{subscription_id}-CN-{credit_note_id} | DOCUMENT CODE | |
| Status | Committed | Always | |
| Invoice IDs | CHARGIFY-CENTRIC-SUB-{subscription_id}-INV-{invoice_id} | REFERENCE CODE | Origin invoices that were credited or refunded |
| Customer ID | CUSTOMER |
Line items follow the same mapping patterns as classic Invoice Billing, above.
To understand what Maxio sends Avalara and when tax is calculated, see How AvaTax Calculates Tax in Maxio.
If a void, refund, or other activity doesn't appear in Avalara, see AvaTax Troubleshooting and FAQs.
To learn how Relationship Invoicing works more broadly, see Understand Accounting Invoices.
Still need help?
Reach out and our support team will take it from here.