Understand How Maxio Billing Activity Syncs to AvaTax
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.
How voids and refunds sync
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.
Invoice billing mappings between Advanced Billing and Avalara
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.
Payments mapping
A Payment posts to Avalara as its own document, referencing the statement it settled:
| From (Advanced Billing) | Prefix | To (Avalara) |
|---|---|---|
| Transaction ID | CHARGIFY-PAYMENT | DOCUMENT CODE |
| Statement ID | CHARGIFY-STATEMENT | REFERENCE CODE |
| Customer ID | N/A | CUSTOMER |
Charge (prepaid) mapping
Prepaid charges sync during Subscription renewal, at the end of the period, 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.
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 |
Invoices mapping for classic invoice billing
An Invoice posts under a document code built from its Subscription and Invoice IDs, and its Avalara status follows whether the Invoice is paid:
| 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 |
Refunds mapping
A refund posts as its own document with a single reference back to what was refunded. That reference is the Invoice when the refunded Payment is tied to one, and the Payment itself otherwise:
| From (Advanced Billing) | Prefix | To (Avalara) | Notes |
|---|---|---|---|
| Refund ID | CHARGIFY-REFUND- | DOCUMENT CODE | |
| Payment ID | CHARGIFY-PAYMENT- | REFERENCE CODE | Applicable if the refunded Payment is not related to an Invoice |
| Invoice ID | CHARGIFY-SUB-{subscription_id}-INV-{invoice_id} | REFERENCE CODE | Applicable if the refunded Payment is related to an Invoice |
| Customer ID | CUSTOMER |
Line item mapping for classic invoice billing
Each line on the document carries the Component or Product it came from, the tax code that classifies it, and the addresses used to source the tax:
| 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 |
Relationship Invoicing mapping between Advanced Billing and Avalara
These mappings apply only if you use Relationship Invoicing in Advanced Billing.
Invoices mapping for Relationship Invoicing
Relationship Invoicing uses its own document-code prefix, and adds a Voided status that classic invoice billing has no equivalent for:
| From (Advanced Billing) | Prefix | To (Avalara) | Notes |
|---|---|---|---|
| Subscription ID and Invoice ID | CHARGIFY-CENTRIC-SUB-{subscription_id}-INV-{invoice_id} | DOCUMENT CODE | |
| Unpaid (Status) | Saved | ||
| Paid (Status) | Committed | ||
| Voided (Status) | Canceled | ||
| Subscription group ID and parent Invoice number | SUBSCRIPTION-GROUP-ID-{subscription_group_uid}, PARENT-INV-NUM-{parent_invoice_number} | REFERENCE CODE | Applicable if the Invoice is a segment of a consolidated Invoice |
| 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 mapping
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 and 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 item mapping for Relationship Invoicing
Line items follow the same mapping patterns as classic invoice billing, above.
Related information
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.