Supported General Ledgers for Advanced Revenue Summary GL Sync

Advanced Revenue Summary GL Sync supports five general ledgers, each with its own account-mapping field, dimension support, and (since it varies by platform) workpaper-attachment support.

Feature support matrix

Account-mapping field, dimension support, and workpaper attachment support by general ledger

A journal entry still syncs successfully on a destination that doesn't support attachments. Only the attachment step is skipped, and it's recorded as skipped in the sync history rather than as a failure.

Workpaper format

Configuring workpaper attachments lets you choose CSV or PDF as the format. Today, the attached file is always generated as CSV regardless of that selection; PDF generation isn't available yet. This applies only to destinations that support attachments at all (QuickBooks Online and Sage Intacct); it has no effect on NetSuite, Xero, or Rillet, which don't receive an attachment either way.

QuickBooks Online

QuickBooks Online re-uses journal entries on re-sync, uses its own journal-number format, and supports both dimension mapping and workpaper attachments:

• Journal entries are re-used on re-sync: syncing an already-posted, still-open period updates the existing journal entry rather than creating a new one. Closed/locked periods in QuickBooks Online can't be updated this way.
• Journal entry numbers use a QuickBooks-safe format to fit QuickBooks Online's stricter DocNumber constraints, rather than the standard Maxio-YYYY-MM numbering used on other destinations.
• Supports attaching a workpaper file to the posted journal entry. Re-syncing replaces the previously attached Maxio-generated file so only the current one remains attached; a non-Maxio attachment already on the journal entry is left in place.
• Supports an optional Class dimension applied to every line.

NetSuite

NetSuite posts one journal entry per period and supports dimension mapping, but not workpaper attachments:

• Journal entries are posted per period; NetSuite dimension mapping supports Subsidiary, Department, Class, and Location.
• Does not support workpaper attachments. There's no NetSuite-specific attachment handling, so attaching is skipped on every sync.

Xero

Xero supports dimension mapping and can reconcile against an existing record, but not workpaper attachments:

• Supports an optional Tracking Category dimension.
• Does not support workpaper attachments; attaching is explicitly unsupported and skipped on every sync.
• Can reconcile a sync to a previously created record in Xero even without a stored external ID from Maxio's side, which helps recover cleanly if a prior sync's result wasn't saved on the Maxio side.

Sage Intacct

Sage Intacct re-uses journal entries on re-sync the same way QuickBooks Online does, and supports both dimension mapping and workpaper attachments:

• Journal entries are re-used on re-sync in the same way as QuickBooks Online: an already-posted, still-open period is updated in place; closed periods in Sage Intacct block the update.
• Supports dimension mapping across Location, Department, Class, Project, Task, Vendor, Employee, and Warehouse.
• Supports attaching a workpaper file via Sage Intacct's Supporting Documents. If a non-Maxio attachment is already linked to the journal entry, it's preserved rather than replaced.

Rillet

Rillet doesn't support dimension mapping or workpaper attachments, but it can reconcile against an existing record and includes a link back to the Maxio report:

• Does not support dimension mapping. Dimensions aren't sent to Rillet at all, even if configured elsewhere.
• Does not support workpaper attachments. Instead, the sync sends a link to the Maxio report as part of the payload, so the source report is still reachable from Rillet even without an attached file.
• Can reconcile a sync to a previously created record without a stored external ID, similar to Xero.
• Treats a changed, previously-synced period as an update rather than a new post, using an idempotency key to avoid duplicate entries. Rillet documents that it saves and replays idempotency responses for 24 hours.

Related information

To configure these mappings, see Set Up Advanced Revenue Summary GL Sync.

For a conceptual overview of GL Sync's capabilities and limitations, see Understand Advanced Revenue Summary GL Sync.

If a sync fails for one of these destinations, see Troubleshoot Advanced Revenue Summary GL Sync.